From: Andreas Mohr <andi@lisas.de>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Andreas Mohr <andi@lisas.de>, LKML <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, Tejun Heo <htejun@gmail.com>,
Sergei Shtylyov <sshtylyov@ru.mvista.com>,
WimVanSebroeck@rhlx01.hs-esslingen.de
Subject: Re: [BUG] 2.6.29-rc2-git1 to -rc5: libata lockup on boot, LED solid, 100% CPU
Date: Tue, 17 Feb 2009 21:01:27 +0100 [thread overview]
Message-ID: <20090217200127.GA30981@rhlx01.hs-esslingen.de> (raw)
<wim@iguana.be>
Bcc:
Subject: Re: [BUG] 2.6.29-rc2-git1 to -rc5: libata lockup on boot, LED
solid, 100% CPU
Reply-To:
In-Reply-To: <18841.54304.460011.351580@harpo.it.uu.se>
X-Priority: none
[CC'd Sergei and Wim; thanks a lot for your work!]
Hi,
On Mon, Feb 16, 2009 at 10:01:20PM +0100, Mikael Pettersson wrote:
> Andreas Mohr writes:
> > Should I test 2.6.28.5? Every build will take two hours though...
> > Not ATA-SFF 32bit bug problem, right? (already committed?)
> > http://marc.info/?l=linux-kernel&m=123254501314058&w=2
>
> To me it looks like the 32-bit PIO bug. The patch you cited above was
> just the first to identify the issue. This is still unfixed in 29-rc5.
> Please test Sergei's latest proposed patch posted yesterday to linux-ide.
Bingo. That patch ( http://marc.info/?l=linux-ide&m=123482861218381&w=2 )
made -rc5 boot for me. Well, after additionally disabling iTCO_wdt.ko,
that is... (on my Dell Inspiron 8000 i810)
And HDD did seem to be a wee bit more reponsive, too, but that could be
mere illusion...
Thanks,
Andreas Mohr
next reply other threads:[~2009-02-17 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 20:01 Andreas Mohr [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-16 20:06 Andreas Mohr
2009-02-16 21:01 ` Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090217200127.GA30981@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=WimVanSebroeck@rhlx01.hs-esslingen.de \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=sshtylyov@ru.mvista.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®