The link is ftp://ftp.nc.orc.ru/pub/Linux/people/saw/kernel/ and the
author is Savochkin Andrey Vladimirovich <saw@msu.ru>
As for being able to shut the machine down cleanly, we have another box
attached to the one that is wobbling and they are connected via a serial
cable. We are using a serial console to log in when it wobbles and do a
clean shutdown... Not an optimal solution, but better than watching your
mounted data die.
Another thing, we are only noticing this under heavy load.
-- /* Wayne Pascoe <wayne@moneyworld.co.uk> - MoneyWorld(o_ PenguinPowered! (o_ (o_ //\ (/)_ (/)_ V_/_ /*
On 4 Jan 2000, Nick Burrett wrote:
> > Hello, > > We have a couple of Linux servers here with identical hardware. Both > are running kernel 2.2.12 with an SMP kernel, dual processor motherboard > with one connected processor and an Intel EtherExpress Pro 10/100B network > card. > > After many days of uptime (usually 20, but most recently 93) the kernel > repeats the follow error every 5 seconds. > > eth0: Transmit timed out: status 0050 0090 at 287931865/287931880 command 000c0000. > eth0: Trying to restart the transmitter... > > The error has been seen on kernels 2.2.10, 2.2.11 and 2.2.12. Does anybody > have any insight into this ? > > Unfortunately the error has the additional side effect of preventing the > user from shutting down the computer cleanly from the console. Magic SysRq > is usuable but it isn't possible to do an emergency sync or Remount R/O. > > > Regards, > > > Nick Burrett. > > - > 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/ >
- 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/