Messages in this thread | | | Date | Tue, 04 May 1999 23:39:15 -0600 | From | Bill Anderson <> | Subject | Re: [OT] Comments to WinNT Mag !! |
| |
Pavel Machek wrote: > > Hi! > > > sorry for the later anwer but I was out for the week-end. > > I've readed Mark article and all Ingo answers, They speak about low level > > system implementations that are very interesting for me but, the _really_ > > question for Mark is : > > > > Can You explain to me why I've to reboot my NT 4.0 SP4 ( low charged ) > > server > > every 48-72 hours becouse It stop responding to every networks > > queries ? > > This is unfair. There are unstable machines out there. Some of them > are unstable because of hardware (I remember my 486 with ne2000 would > lock sometimes; moving ne2000 around helped). Some of them are > unstable because of sw/hw combination (friend of me just asked me > about linux printing something about tx timeouts and then locking up > hard). Of course, difference is that NT will not tell you about tx > timeouts :-). Of course, difference #2 is you can debug linux if you > happen to own bad linux/hw combination.
Any ideas on the Tx errors? Are they Tx FIFO errors on the NIC?
If so which one?
I have this problem on 2.2.x kernels, running the Symbios scsi/ethernet combo (PCNet32 driver), when running on 100Base lan, but none on ten. It appears to be largely occuring when connecting to an HP-UX 11.x server (CVS and NFS).
Bill
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |