linux-kernel - Re: Is sata_nv compatible with async scsi scan?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49ED9FAC.1080303@garzik.org>
Date:	Tue, 21 Apr 2009 06:27:56 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Benny Halevy <bhalevy@...asas.com>
CC:	Jeff Garzik <jgarzik@...hat.com>,
	lkml <linux-kernel@...r.kernel.org>, linux-ide@...r.kernel.org,
	linux-scsi <linux-scsi@...r.kernel.org>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: Is sata_nv compatible with async scsi scan?

Benny Halevy wrote:
> Hi Jeff,
> 
> Since 2.6.29 I'm having intermittent problems with booting kernels.
> After supposedly waiting for scsi async scan to complete,
> quite frequently I see errors from the init resume process
> when it fails to find the swap partition and later the root
> file system fails to load.
> 
> A workaround that I found to be helpful is booting the kernel
> with scsi_mod.scan=sync so I suspect sata_nv has a problem
> with asynchronous scanning.

Personally, I think the whole system is broken, so continue to use this 
workaround until it gets fixed upstream.  This sounds like some timing 
issues related to waiting for the device probe to finish, something that 
people keep breaking (witness my USB flash drive boot breakage).

	Jeff



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/