From: Matthew Wilcox <matthew@wil.cx>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Carlos O'Donell <carlos@systemhalted.org>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: No drives come online in 2.6.32?
Date: Sat, 26 Dec 2009 12:40:22 -0700 [thread overview]
Message-ID: <20091226194022.GA3521@parisc-linux.org> (raw)
In-Reply-To: <20091225234654.GA23763@lackof.org>
On Fri, Dec 25, 2009 at 04:46:55PM -0700, Grant Grundler wrote:
> On Wed, Dec 23, 2009 at 09:19:19PM -0500, Carlos O'Donell wrote:
> > When booting 2.6.32, my scsi drives don't come online, all I see during boot is:
> > ~~~
> > sym53c8xx 0000:00:01.0: enabling device (0000 -> 0003)
> > sym53c8xx 0000:00:01.0: enabling SERR and PARITY (0003 -> 0143)
> > sym53c8xx 0000:00:01.1: enabling device (0000 -> 0003)
> > sym53c8xx 0000:00:01.1: enabling SERR and PARITY (0003 -> 0143)
> > sym53c8xx 0000:00:02.0: enabling device (0000 -> 0003)
> > sym53c8xx 0000:00:02.0: enabling SERR and PARITY (0003 -> 0143)
> > sym53c8xx 0000:00:02.1: enabling device (0146 -> 0147)
> > ~~~
> > When booting 2.6.32-rc6 the drives come online right away after they
> > are enabled.
> >
> > No amount of waiting helps.
>
> Do you have CONFIG_SCSI_SCAN_ASYNC=y ?
>
> If so, add CONFIG_SCSI_WAIT_SCAN=m or disable SCAN_ASYNC.
>
> While this should work, it sounds like it's not working.
Huh? The wait scan module will wait for scans to complete. This sounds
like the scans are never starting.
--
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:[~2009-12-26 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 2:19 No drives come online in 2.6.32? Carlos O'Donell
2009-12-24 5:40 ` Carlos O'Donell
2009-12-25 23:46 ` Grant Grundler
2009-12-26 19:40 ` Matthew Wilcox [this message]
2009-12-27 8:02 ` Grant Grundler
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=20091226194022.GA3521@parisc-linux.org \
--to=matthew@wil.cx \
--cc=carlos@systemhalted.org \
--cc=grundler@parisc-linux.org \
--cc=linux-parisc@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