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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
