From: Rolf Offermanns <roffermanns@sysgo.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: Linux hangs during IDE initialization at boot for 30 sec
Date: Thu, 3 Feb 2005 13:58:16 +0100 [thread overview]
Message-ID: <200502031358.16827.roffermanns@sysgo.com> (raw)
In-Reply-To: <1107299901.5624.28.camel@gaston>
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).
-Rolf
--
Rolf Offermanns <roffermanns@sysgo.com>
SYSGO AG Tel.: +49-6136-9948-0
Am Pfaffenstein 14 Fax: +49-6136-9948-10
55270 Klein-Winternheim http://www.sysgo.com
next prev parent reply other threads:[~2005-02-03 12:58 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 [this message]
2005-02-03 22:17 ` Benjamin Herrenschmidt
2005-02-04 10:22 ` Rolf Offermanns
2005-02-04 23:32 ` Benjamin Herrenschmidt
-- 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=200502031358.16827.roffermanns@sysgo.com \
--to=roffermanns@sysgo.com \
--cc=benh@kernel.crashing.org \
--cc=linux-ide@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 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.