From: Matthew Wilcox <matthew@wil.cx>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Bug 15288] kernel 2.6.31 loading goes in loop on IBM xSeries 330
Date: Fri, 12 Feb 2010 13:37:18 -0700 [thread overview]
Message-ID: <20100212203717.GI11239@parisc-linux.org> (raw)
In-Reply-To: <201002122028.o1CKSOFI005099@demeter.kernel.org>
On Fri, Feb 12, 2010 at 08:28:24PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> --- Comment #3 from Andrew Morton <akpm@linux-foundation.org> 2010-02-12 20:28:19 ---
> I'll reassign this regression to scsi.
>
> I reattached the most interesting jpg screenshot: scsi_async_scan got stuck.
This probably isn't anything to do with the scsi async scan (boot with
scsi_mod.scan=sync to eliminate the possibility). It's probably a driver
failing to finish the scan. Probably the reason for that is broken
interrupt routing. But that's a lot of probables, so some investigation
with scsi_mod.scan=sync should be used to confirm the first hypothesis
before assigning the blame elsewhere.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2010-02-12 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15288-11613@http.bugzilla.kernel.org/>
2010-02-12 20:28 ` [Bug 15288] kernel 2.6.31 loading goes in loop on IBM xSeries 330 bugzilla-daemon
2010-02-12 20:37 ` Matthew Wilcox [this message]
2010-02-12 21:15 ` bugzilla-daemon
2010-02-15 12:01 ` bugzilla-daemon
2010-02-15 12:02 ` bugzilla-daemon
2010-02-15 15:15 ` James Bottomley
2010-02-15 15:55 ` bugzilla-daemon
2010-02-16 6:43 ` bugzilla-daemon
2010-02-17 12:33 ` bugzilla-daemon
2010-02-18 3:20 ` bugzilla-daemon
2010-02-18 3:29 ` Yinghai Lu
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=20100212203717.GI11239@parisc-linux.org \
--to=matthew@wil.cx \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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