From: Helge Deller <deller@gmx.de>
To: Michal Ludvig <mludvig@logix.net.nz>
Cc: Carlos O'Donell <carlos@systemhalted.org>, linux-parisc@vger.kernel.org
Subject: Re: scsi_wait_scan doesn't wait
Date: Thu, 21 Oct 2010 21:22:10 +0200 [thread overview]
Message-ID: <4CC092E2.4090900@gmx.de> (raw)
In-Reply-To: <4CC003BB.6080900@logix.net.nz>
On 10/21/2010 11:11 AM, Michal Ludvig wrote:
> On 10/20/2010 12:04 PM, Carlos O'Donell wrote:
>> On Mon, Oct 18, 2010 at 11:27 PM, Michal
>> Ludvig<mludvig@logix.net.nz> wrote:
>>> I'm having a problem with 2.6.36-rc8+ on HP PARISC machine (HP 9000
>>> RP3410) where I intend to wait for SCSI enumeration during boot before
>>> LVM2 kicks in and attempts to activate the root volume. I modprobe
>>> scsi_wait_scan in the initramdisk before lvm2 script is run. However
>>> the
>>> modprobe doesn't wait. I'm on Debian testing, fwiw.
>> If you're interested in helping, the best thing you could do is back
>> up to a kernel that works and then try to track down what commit broke
>> the wait scan. It's a bit tedious, but fairly easy.
> Yeah, I know. However a kernel rebuild takes nearly 2 hours on that
> machine so it may be a couple of months before I find the commit ;-)
> I'll see if I can come up with an automated process for that.
Hi Michal,
I'd propose that you use a cross-compiler (i686 to hppa) instead.
Then you can TFTP-boot the built kernel from your PC.
This is what I do, and it speeds up everything a lot and it's not too
hard to set it up.
Helge
prev parent reply other threads:[~2010-10-21 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 3:27 scsi_wait_scan doesn't wait Michal Ludvig
2010-10-19 23:04 ` Carlos O'Donell
2010-10-21 9:11 ` Michal Ludvig
2010-10-21 19:22 ` Helge Deller [this message]
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=4CC092E2.4090900@gmx.de \
--to=deller@gmx.de \
--cc=carlos@systemhalted.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mludvig@logix.net.nz \
/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