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: Fri, 04 Feb 2005 09:17:12 +1100 [thread overview]
Message-ID: <1107469032.2363.44.camel@gaston> (raw)
In-Reply-To: <200502031358.16827.roffermanns@sysgo.com>
On Thu, 2005-02-03 at 13:58 +0100, Rolf Offermanns wrote:
> On Wednesday 02 February 2005 00:18, you wrote:
>
> >
> > The IDE layer waits up to 30 seconds for a device to drop it's busy bit,
> > which is necessary for some drives that aren't fully initialized yet.
> >
> > I suspect in your case, it's reading "ff", which indicates either that
> > there is no hardware where the kernel tries to probe, or that there is
> > bogus IDE interfaces which don't properly have the D7 line pulled low so
> > that BUSY appears not set in absence of a drive.
> >
> I have the same kind of bogus hardware here. What would be the right place to
> workaround this? (unfortunately it's not possible to fix/change the
> hardware).
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.
Ben.
next prev parent reply other threads:[~2005-02-03 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200502011257.40059.brade@informatik.uni-muenchen.de>
[not found] ` <pan.2005.02.01.20.21.46.334334@surrey.ac.uk>
2005-02-01 23:18 ` Linux hangs during IDE initialization at boot for 30 sec Benjamin Herrenschmidt
2005-02-03 10:03 ` Alan Cox
2005-02-03 12:58 ` Rolf Offermanns
2005-02-03 22:17 ` Benjamin Herrenschmidt [this message]
2005-02-04 10:22 ` Rolf Offermanns
2005-02-04 23:32 ` Benjamin Herrenschmidt
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=1107469032.2363.44.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).