From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rtl8139 ether driver
Date: Wed, 26 Jun 2002 09:07:51 +0100 [thread overview]
Message-ID: <8e9dc00a405691564e1741326151b1b5@caldo.demon.co.uk> (raw)
>>It may hard to read the error message even if I make it run in debugging
>>mode, because it occures very rarely, and when it happenes, that machine
>>reboots automatically, ..
you don't say whether it reboots without comment or simply because it has lost the
file system link. i suppose the former, because otherwise prints in the driver
would otherwise work (though you'd need to stop automatic reset to read
them all). i'd first start checking that memmove parameters (eg, count)
are always correct.
next reply other threads:[~2002-06-26 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 8:07 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-28 10:37 okamoto
2002-06-27 2:49 okamoto
2002-06-26 9:22 okamoto
2002-06-26 2:31 okamoto
2002-06-26 1:58 jmk
2002-06-26 1:45 okamoto
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=8e9dc00a405691564e1741326151b1b5@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).