From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "new" 9load freezes
Date: Tue, 7 Mar 2006 17:52:34 +0200 [thread overview]
Message-ID: <90c5b8c4d5a08240d6825395cd0e2d89@proxima.alt.za> (raw)
In-Reply-To: <440AF422.3010403@asgaard.homelinux.org>
> #l0: status 0xFFFF, diag 0xFFFF
> Which comes from etherelnk3.c. I removed that, and some
> other ether drivers from 9load, now it works !
There's an error in that driver or in a new kernel with that driver in
it, I'm not sure what it is. In the absence of an etherlink card, it
behaves itself, so it can't be too difficult to isolate. I have all
the history I thought I might need to isolate it, but I haven't yet
attacked the problem in all earnestness.
What did you do about the network?
++L
prev parent reply other threads:[~2006-03-07 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 11:52 "Nils O. Selåsdal"
2006-03-05 13:13 ` Russ Cox
2006-03-05 14:22 ` "Nils O. Selåsdal"
2006-03-05 14:54 ` Russ Cox
2006-03-05 15:14 ` "Nils O. Selåsdal"
2006-03-07 15:52 ` lucio [this message]
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=90c5b8c4d5a08240d6825395cd0e2d89@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).