This version survived for a little longer, but hung (on the 486 box) whilst
doing a recursive ls of a large directory tree. Again, no messages, except
for one which came up as the box was booting, whilst it was starting squid.
The box was OK for about 4 minutes after this message, which was
"rl0:
Whoops... I just noticed I made a small boo-boo in that last patch,
which I just fixed. When downloading, make sure you get the version of
if_rl.c with the following ID strings:
for 3.0: $Id: if_rl.c,v 1.28 1999/04/06 15:29:01 wpaul Exp $
for 2.2: $Id: if_rl.c,v 1.17 1999/04/06 15:
Of all the gin joints in all the towns in all the world, Stephen
Hocking-Senior Programmer PGS Tensor Perth had to walk into mine and say:
> OK - I've banged on the new version with extra debug messages and it still
> locks up, but without any messages!
Grr.
> I can only conclude that the 486
OK - I've banged on the new version with extra debug messages and it still
locks up, but without any messages! I can only conclude that the 486MB BIOS is
iffy. I haven't tried any other slots in the MB, but have tried various PCI
settings, all to no avail. I have swapped the de0 and the rl0 bet
Of all the gin joints in all the towns in all the world, Stephen
Hocking-Senior Programmer PGS Tensor Perth had to walk into mine and say:
> Well, I nipped home over my lunch break & gave it a try - some progress, of a
> sort. My NFS problems have gone away (at least under light activity), but i
Well, I nipped home over my lunch break & gave it a try - some progress, of a
sort. My NFS problems have gone away (at least under light activity), but it
now seems rather sensitive to sending lots of stuff. The symptoms observed are
a hard hang of the whole machine, no response to pings or keyb
Hi Bill,
Just tried the new Realtek driver with 4.0, and it works MUCH better. I
was seeing weird NFS transmit errors with UDP, and the ping you
suggested below did not work with the old driver (it reported an out of
buffer space message and didn't transmit any packets). With the new
driver, t
Okay, today (and over part of the weekend) I ripped the RealTek driver
apart and put it back together again, this time in a hopefully working
form. The temporary patch version is at the following locations:
http://www.freebsd.org/~wpaul/RealTek/test/2.2 source for FreeBSD 2.2.x
http://www.freebsd
