From: Miles Lane <miles@megapathdsl.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The horrible hack from hell called A20
Date: Wed, 06 Dec 2000 22:43:00 -0800 [thread overview]
Message-ID: <3A2F3174.60205@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10012061814020.7391-100000@penguin.transmeta.com>
Linus Torvalds wrote:
>
> On Wed, 6 Dec 2000, Miles Lane wrote:
>
>> Here is what goes wrong:
>>
>> Dec 6 04:21:32 agate kernel: eth0: Host error, FIFO diagnostic register 0000.
>
>
> But it continues to work, right?
I'll check. My system only has 80MB RAM, and I run Mozilla, which
pushes a lot of information into the swap space. When I encounter
this "Host error" problem, tons of messages start spewing into my
logs. This bogs my entire system down horribly.
<great educational material snipped>
I have reproduced this problem with all the drivers built
into the kernel.
I have also just tried a test pass with 3c59x built in and
USB built as modules. I booted with only the 3c575 inserted.
I got eth0 running and then loaded usb-ohci (with the enable
bus mastering change added). This resulted in modprobe hanging
again.
Now I'll try with all modules again and check to see whether eth0
is still usable.
Thanks,
Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-07 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 12:09 The horrible hack from hell called A20 Miles Lane
2000-12-06 20:05 ` Linus Torvalds
2000-12-06 22:35 ` Miles Lane
2000-12-07 2:27 ` Linus Torvalds
2000-12-07 6:43 ` Miles Lane [this message]
2000-12-07 7:10 ` Linus Torvalds
2000-12-07 15:29 ` Andrew Morton
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=3A2F3174.60205@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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