linux-kernel - Re: 2.6.31-rc5 regression: hd don't show up

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: <4A965E3B.3000808@klingt.org>
Date:	Thu, 27 Aug 2009 12:21:47 +0200
From:	Tim Blechmann <tim@...ngt.org>
To:	Tejun Heo <tj@...nel.org>
CC:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: 2.6.31-rc5 regression: hd don't show up

On 08/27/2009 10:38 AM, Tejun Heo wrote:
> Tim Blechmann wrote:
>>>>>> running 2.6.31-rc5 (7cb7beb31aa3d941833b6a6e553687422c31e4b6 to be
>>>>>> exact), sometimes some hard disks don't show up.
>>>>>>
>>>>>> after booting, my root hd (sda) is mounted to /, while two other hds
>>>>>> (sdb/sdc) are mounted as a user. sda is always present, but the other
>>>>>> two sometimes don't show up (i.e. they are not listed in /dev/disk/, nor
>>>>>> to they have a /dev/sdX link). with 2.6.29 and 2.6.30, all three disks
>>>>>> are reported correctly.
>>>>> Can you please attach boot logs of a successful and a failed boot?
>>>> i have two files attached:
>>>> - dmesg_good - all hds are available
>>>> - dmesg_bad - on hd is missing
>>> Can you please apply the attached patch and post the bad boot log?
>>
>> attached you find boot logs for both a good ad a bad boot
> 
> Sorry about the long delay.  I somehow marked the message read without
> actually reading it.
> 
> I suspected the problem was with getting the wrong classification code
> or phantom device detection kicking in spuriously.  Looks like the
> problem happens way before that.  Can you please apply the attached
> patch and report the result?

i applied your patch onto of the current linus/master branch and
currently (after rebooting 5 or 6 times) i cannot reproduce the problem
any more ...
however, there is a warning stack trace in the boot log from libata code
(bootlog attached)

tim

-- 
tim@...ngt.org
http://tim.klingt.org

... to make life worth living ...
  Keith Rowe on making music

View attachment "bootlog" of type "text/plain" (65583 bytes)

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)