From: Steven Rostedt <rostedt@goodmis.org>
To: David Balazic <david.balazic@hermes.si>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>, Andi Kleen <ak@suse.de>,
Pavel Machek <pavel@suse.cz>, Matt Domsch <Matt_Domsch@dell.com>
Subject: RE: Long delay on bootup with wait_hwif_ready
Date: Tue, 30 May 2006 10:11:12 -0400 [thread overview]
Message-ID: <1148998272.8104.7.camel@localhost.localdomain> (raw)
In-Reply-To: <B216E7A91F67B6429E3ACF162402A02D0E5F90@hsl-lj-mail.hermes.si>
On Tue, 2006-05-30 at 14:10 +0200, David Balazic wrote:
> Hi!
>
> My "final conclusion" last time was, that there is some memory
> area, that comes out too short in certain cases.
> This is some early kernel boot code, that deals with the BIOS (and
> confuses it, it seems, by running out the mentioned memory area).
>
> As I understood, the kernel could be tweaked to increase/decrease
> the problemtatic memory area (or the usage of it).
>
> It is some kind of stack, heap or segment, I don't know, but somebody
> mentioned it last time.
>
> Regards,
> David
>
> PS: Feel free to ask me for testing patches ;-)
> I still have the same PC (with a certain weird behavior lately,
> I can't switch the IDE mode from "RAID" to "normal" ...)
>
After rereading the thread (after my first cup of coffee this time), I
see that the problem was slightly different than what I had. The thread
showed some delay before the console was initialized (the EDD code). But
I'm experiencing the delay with the wait_not_busy.
My problem is that the secondary status register is returning busy when
there isn't anything there. So I have to wait 35 seconds for the
timeout to expire. This could just be a fluke with the way the board is
designed (it wouldn't surprise me).
-- Steve
next prev parent reply other threads:[~2006-05-30 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 12:10 David Balazic
2006-05-30 14:11 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-30 12:01 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=1148998272.8104.7.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®