From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Rolf Offermanns <roffermanns@sysgo.com>
Cc: list linux-ide <linux-ide@vger.kernel.org>
Subject: Re: Linux hangs during IDE initialization at boot for 30 sec
Date: Sat, 05 Feb 2005 10:32:35 +1100 [thread overview]
Message-ID: <1107559955.2189.95.camel@gaston> (raw)
In-Reply-To: <200502041122.09390.roffermanns@sysgo.com>
On Fri, 2005-02-04 at 11:22 +0100, Rolf Offermanns wrote:
> On Thursday 03 February 2005 23:17, Benjamin Herrenschmidt wrote:
> >
> > Do not register interfaces that you know aren't populated...
> >
> > One thing is, the wait code does explicitely check for a value of 0xff
> > and exists in this case (assuming this means no HW at all is wired
> > there). So for some reason, you interface is returning something else,
> > it would be interesting to "see" what value you are getting.
> It's 0xff like you guessed in the first reply. As soon, as I connect a drive
> (no need to turn it on actually), everything is fine.
Well, that's strange then, since the code is explicitely returning
-ENODEV when it encounters that, maybe the caller isn't properly testing
for the error, I'll have to double check. (Can't today)
Ben.
next prev parent reply other threads:[~2005-02-04 23:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 11:57 Linux hangs during IDE initialization at boot for 30 sec Michael Brade
2005-02-01 20:22 ` Richard Hughes
2005-02-01 23:18 ` Benjamin Herrenschmidt
2005-02-02 12:46 ` Richard Hughes
2005-02-02 12:52 ` Con Kolivas
2005-02-02 14:20 ` Richard Hughes
2005-02-03 10:03 ` Alan Cox
2005-02-03 12:58 ` Rolf Offermanns
2005-02-03 22:17 ` Benjamin Herrenschmidt
2005-02-04 10:22 ` Rolf Offermanns
2005-02-04 23:32 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 18:48 Aleksey Gorelov
2005-02-02 20:01 Aleksey Gorelov
2005-02-02 22:16 ` Michael Brade
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=1107559955.2189.95.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-ide@vger.kernel.org \
--cc=roffermanns@sysgo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.