linux-kernel - Re: [2.6.19-rc2] SATA boot problems

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]

Date:	Fri, 20 Oct 2006 17:56:04 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Mark Lord <lkml@....ca>
CC:	Robert Wruck <wruck@...erlei.de>,
	IDE/ATA development list <linux-ide@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6.19-rc2] SATA boot problems

Mark Lord wrote:
> Hi.  I'm copying your posting for the linux-ide mailing list,
> where the libata designers hang out.
> 
> Robert Wruck wrote:
>> Hi,
>>
>> I'm having problems booting from a SATA disk with 2.6.19-rc2.
>> Grub loads fine, but when the kernel boots, it *sometimes* ends up with
>> VFS: Cannot open root device "sda5" or unknown-block(0,0)
>>
>> The strange thing is that this happens only in 2/3 of the boot attempts.
>> If I reset the machine, the next attempt is likely to succeed.
>> I first noted this when switching from 2.6.17 (2.6.17.11, IIRC) to
>> 2.6.18 and it persists in 2.6.19-rc2 (Windows does not encounter similar
>> problems on the same machine).
>>
>> I attached a diff of a successful and an unsuccessful netconsole log
>> below. It seems that the drive is sometimes simply not detected...
>> I'm not using an initrd and changing the kernel command line from
>> root=/dev/sda5 to root=0x0805 did not help.
>>
>> The controller is:
>> 00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA
>> Controller (rev 03)
>>
>> Any ideas? Please CC me, as I'm not subscribed.
>> Robert

Can you give a shot at the latest -mm (2.6.19-rc2-mm2)?  It contains 
device-detection-via-polling which is supposed to fix problems similar 
to yours.

-- 
tejun
-
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/