From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Jeff Garzik <jgarzik@pobox.com>, Andi Kleen <ak@suse.de>,
Pavel Machek <pavel@suse.cz>, Matt Domsch <Matt_Domsch@dell.com>,
David Balazic <david.balazic@hermes.si>
Subject: Long delay on bootup with wait_hwif_ready
Date: Tue, 30 May 2006 08:01:00 -0400 [thread overview]
Message-ID: <1148990460.11270.53.camel@localhost.localdomain> (raw)
Hi,
I got a board I'm working with which has the following IDE controller.
# lspci
...
0000:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
..
On boot up there's a 35 second delay that happens right here:
(happens on 2.6.9 - 2.6.16)
/* Now make sure both master & slave are ready */
SELECT_DRIVE(&hwif->drives[0]);
hwif->OUTB(8, hwif->io_ports[IDE_CONTROL_OFFSET]);
mdelay(2);
rc = ide_wait_not_busy(hwif, 35000);
if (rc)
return rc;
SELECT_DRIVE(&hwif->drives[1]);
hwif->OUTB(8, hwif->io_ports[IDE_CONTROL_OFFSET]);
mdelay(2);
Delaying function
|
V
rc = ide_wait_not_busy(hwif, 35000);
There is no secondary drive, but for some reason the return of the
status is 0x80 which is "busy". So on boot up, we wait every time for
this 35 second timeout.
I noticed that this was discussed before (got my CC from this thread):
http://marc.theaimsgroup.com/?l=linux-kernel&m=108890865325793&w=2
But I didn't see a solution at the end.
So my question is. Is this just a bad response from hardware, or is
there a better way to find out if the drive exists or not?
My current work around is to remove the wait for the second drive
(removed the if(rc) from above to always return there), which is not
robust, but suites my needs.
-- Steve
next reply other threads:[~2006-05-30 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 12:01 Steven Rostedt [this message]
2006-05-30 12:10 David Balazic
2006-05-30 14:11 ` Steven Rostedt
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=1148990460.11270.53.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=Matt_Domsch@dell.com \
--cc=ak@suse.de \
--cc=david.balazic@hermes.si \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®