From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rtl8139 ether driver
Date: Wed, 26 Jun 2002 18:22:08 +0900 [thread overview]
Message-ID: <20020626092313.C844019A97@mail.cse.psu.edu> (raw)
Actually, it becomes more often today. I must have experienced
more than several times in a worktime. I may be better to check it
for a terminal machine, but not CPU server machine...
At first, I doubted power problem, because we use 100 V power for
designed 115 V power. It usually does not cause problem. However,
I experienced fail before when the switching power supply would be
poor. In this time, 300W power supply is used. The machine only has
a 1.6GHz Pen 4, 51MB memory, a CDROM, a floppy drive and a VGA card.
I tried slidac to make up the power from 100 to 115 V, but it did not solve
the problem either.
>you don't say whether it reboots without comment or simply because
>it has lost the file system link.
From the file server's log, I know only it's link to file server hanged-up.
I've never been at front of our CPU server when it lost the link to the
file server. So, I can see only lines of messages after new reboot on a
console of CPU/Auth server.
>i'd first start checking that memmove parameters (eg, count)
>are always correct.
As Jim know, kernel level checking would exceed my ability, sorry...
If someone kindly contact me detailed, I may be able to try it. Anyway,
It'd be better to use that machine for a terminal at first, and I'll do it later.
And I'm planing to parchase a new motherboard using dual Athron
for our CPU server. Yes, I got a good news from a shop who can still sell
that kind of motherboard.
Kenji
next reply other threads:[~2002-06-26 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 9:22 okamoto [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 8:07 forsyth
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=20020626092313.C844019A97@mail.cse.psu.edu \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).