Danie, I had this problem at one stage. It was an on-board eepro chipset that was also suspected of causing a bunch of other problems at the time. I ended up with a new card, but the other problems turned out to be dodgy RAM. I don't know if the problems were related (in fact it sounds pretty unlikely), but it can't hurt to run memtest86 over it. Tom On 0, Danie Roux <droux@tuks.co.za> wrote: > Having a funny one here: > > The eepro card stops functioning, for hours on end. Then suddenly it > would start responding again. In the logfile, just before it stopped > functioning: > > Sep 11 09:21:43 buzzer kernel: eth0: XMT status = 0xffff8841 > > And then before it started responding: > > Sep 12 04:08:03 buzzer kernel: eth0: set Rx mode to 1 address. > > Netsaint is telling me it has been up for 4 hours now. Yesterday it > stopped working while I was ssh'ing into the PC, and I think it has > something to do with that. HTTP is fine (but it is a very low load PC). > > I've talked with someone on IRC, and he says he's dmesg says something > about a work-around being enabled for this card. I have the stock 2.4.18 > on that PC, it's an old Pentium. But I don't have a msg regarding a > workaround. > -- Tom Cook Information Technology Services, The University of Adelaide Never be irreplacable: If you are irreplacable then you are unpromotable. Get my GPG public key: https://pinky.its.adelaide.edu.au/~tkcook/tom.cook-at-adelaide.edu.au
Attachment:
pgpdeL4wXLiKW.pgp
Description: PGP signature