At 07:33 AM 10/10/2000, MONZ wrote: >octave klaba wrote: > > > On a server we got thoses errors and server is still working :) > > what does it mean ? > > > eepro100.c:v1.09j-t 9/29/99 Donald Becker > > http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html > > eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V. > > Savochkin <saw@saw.sw.com.sg> and others > > > eth0: Printing Rx ring (next to receive into 97744181, dirty index > > 97744180). > > eth0: can't fill rx buffer (force 1)! > > eth0: Tx ring dump, Tx queue 120752133 / 120752133: > >Dunno about those messages, but it might look like either a card or >driver problem. What about eg. ifconfig, does it show many dropped >packets? >I'm not up to date on ee100 driver revisions, but you might take a look >at Becker's driver pages, which include info about known problems. He >doesn't work at cesdis anymore, but there are links to whereever... >Think I resently read about some ee100 problem... hmm, forgot where. >Oh, a resent thread here suggested an ee100 problem with 2.2.16 kernels. They are debugging messages for driver errors. Overruns and such are not unusual, but you should consider yourself lucky that your server is "still running" afterwards. You can change the debug level in the driver to get rid of the messages. Dennis - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
