From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: ee21rh@surrey.ac.uk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
list linux-ide <linux-ide@vger.kernel.org>
Subject: Re: Linux hangs during IDE initialization at boot for 30 sec
Date: Thu, 03 Feb 2005 10:03:07 +0000 [thread overview]
Message-ID: <1107332790.14787.118.camel@localhost.localdomain> (raw)
In-Reply-To: <1107299901.5624.28.camel@gaston>
On Maw, 2005-02-01 at 23:18, Benjamin Herrenschmidt wrote:
> On Tue, 2005-02-01 at 20:22 +0000, Richard Hughes wrote:
> > On Tue, 01 Feb 2005 12:57:33 +0100, Michael Brade wrote:
> 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'm not sure how the list of intefaces is probed on this machine, that's
> probably where the problem is.
Known, fixed
There is a patch that allows probing for ISA ide4,5,6 etc only if there
is
no PCI bus
next prev parent reply other threads:[~2005-02-03 11:08 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 [this message]
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
-- 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=1107332790.14787.118.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=ee21rh@surrey.ac.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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.