From: "Sylvain Le Briero" <s.lebriero@free.fr>
To: "Joshua Newton" <jpnewton@speakeasy.net>, <linux-kernel@vger.kernel.org>
Subject: Re: Incredible weirdness with eepro100?
Date: Wed, 19 Jun 2002 15:55:15 +0200 [thread overview]
Message-ID: <001c01c21798$f100e230$3d5e06c7@slebriero2> (raw)
In-Reply-To: <1024420841.2631.14.camel@claymore.corona>
it seems that some older kernels do the same...
I have discovered recently I have the same problem with a HP Netserver LH
3000 wich works fine in any other case :
uname-a
Linux databaseserver 2.4.10 #1 Tue Nov 13 17:28:13 CET 2001 i686 unknown
excerpt of dmesg :
eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
<saw@saw.sw.com.sg> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:30:6E:00:1A:49, IRQ 18.
Receiver lock-up bug exists -- enabling work-around.
Board assembly 506477-150, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
Receiver lock-up workaround activated.
on a Slackware 8.0 running postgreSQL.
When i mount a SMB share and copy a large file to an NT Server (postgres
database files : 2-3 GBytes) all network connections are closed and a
reboot is needed.
It seems also that this problem is related
This server has been in production state for almost 1 year and is very
stable as long as you don't transfer large files to a network mount point.
Hope this helps
next prev parent reply other threads:[~2002-06-19 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 17:20 Joshua Newton
2002-06-19 13:55 ` Sylvain Le Briero [this message]
2002-06-19 14:03 ` Dave Gilbert (Home)
2002-06-19 13:55 ` Sylvain Le Briero
[not found] <Pine.LNX.4.21.0206191129040.19899-100000@mammut.nsc.liu.se>
2002-06-19 16:39 ` Joshua Newton
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='001c01c21798$f100e230$3d5e06c7@slebriero2' \
--to=s.lebriero@free.fr \
--cc=jpnewton@speakeasy.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®