From: Mikael Pettersson <mikpe@it.uu.se>
To: Andreas Mohr <andi@lisas.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, Tejun Heo <htejun@gmail.com>
Subject: Re: [BUG] 2.6.29-rc2-git1 to -rc5: libata lockup on boot, LED solid, 100% CPU
Date: Mon, 16 Feb 2009 22:01:20 +0100 [thread overview]
Message-ID: <18841.54304.460011.351580@harpo.it.uu.se> (raw)
In-Reply-To: <20090216200643.GA2393@rhlx01.hs-esslingen.de>
Andreas Mohr writes:
> Hello all,
>
> My Inspiron 8000 ICH2 (i810) P3/700 UP has a hard time booting 2.6.29 things:
>
> [loaded init, shell stuff]
> ...
> ata1.00: configured for UDMA/100
> ata1.01: configured for UDMA/33
> ata1: EH complete
> ...
> Uniform CD-ROM driver Revision: 3.20
> [LAST LINE, FULL STOP]
> ---> hangs with IDE LED solidly on! <---
>
> NOTE: kernel did NOT hang when accidentally running rc2-git1 w/o any modules loaded!
> (IOW, probably a module-related hang)
> disabling sr_mod.ko will make a boot proceed a tiny bit, then hang anyway
>
> Could be mutex deadlock (CPU hot, 100%?)
> no log errors whatsoever
> latest known working: .28-rc6 (admittedly somewhat old; DOES work currently)
> earliest known buggy: -rc2-git1, -rc4 also, -rc5 also
> no SysRq available (notebook keys: no workey, /proc/sysrq obviously
> not available either)
>
> 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.
next prev parent reply other threads:[~2009-02-16 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 20:06 Andreas Mohr
2009-02-16 21:01 ` Mikael Pettersson [this message]
2009-02-17 20:01 Andreas Mohr
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=18841.54304.460011.351580@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=andi@lisas.de \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®