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 for Android: free password hash cracker in your pocket

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

Message-Id: <1252103589.10901.14.camel@maxim-laptop>
Date:	Sat, 05 Sep 2009 01:33:09 +0300
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	Tim Blechmann <tim@...ngt.org>
Cc:	Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org
Subject: Re: 2.6.31-rc5 regression: hd don't show up

On Sat, 2009-09-05 at 00:06 +0200, Tim Blechmann wrote:
> >>>>>> booting the machine today, one hd is missing again ... bootlog attached
> >>>>> Hmmm... strange.  I don't really see how it could be escaping.  Can
> >>>>> you please apply the attached patch?  It still won't change the
> >>>>> behavior but should be able to catch where it's escaping.
> >>>> attached you find two bootlogs, for a correct boot, and with one hd
> >>>> missing ...
> >>> Heh heh, this is getting a bit embarrassing.  Seems like I wasn't
> >>> looking at the right path.  Can you please try this one too?  If it
> >>> says "XXX D7 pulldown quick exit path" and then succeed to probe,
> >>> that's the previous failure case so you don't need to keep trying to
> >>> reproduce the problem.
> >>
> >> i've attached the two boot logs again ...
> > 
> > Okay, it was another wrong guess.  Can you please try this one?
> 
> unfortunately, i haven't been able to get a bootlog of a failure the
> issue after rebooting like 20 times with yesterday's linus/master.
> once i couldn't boot, since the root hd wasn't found, so i don't think,
> the issue is solved, it just doesn't show very frequently ...
> 
> the bootlog of a working system is attached, if i experience another
> issue, i will send you another bootlog. since i am out of town for a few
> days, it may take some time, though ...
> 
> tim
> 

Note, that I did see this once on my desktop, few weeks ago, but only
once.
(After a reboot, everything did work fine)

Best regards,
	Maxim Levitsky

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