On Mon, 27 Oct 1997, Thomas Baetzler wrote: > Rolf Obrecht wrote: > :messages in kern.log: > > Maybe you could provide more info on the > hardware configuration you're running (i.e. memory, CPU, network adapters). > It is a 486DX2/66 with 16MB and two SMC Ultra ethernet cards, running nothing but some daemons (like nacctd), no X, no user accounts
> causes could be > - a buggy network adapter driver; > - low memory situations where a buffer doesn't get allocated; > - race conditions due to CPU overload where the buffer gets purged due to > a queue overflow. > We had some trouble on the LAN; a hub filled all of the bandwidth with silly messages, so that ping from/to machines within the LAN produced 70% packet loss. Could this be an explanation for a buffer overflow with causes nacctd to die? > problem like an overclocked/faked CPU, or a defective cache. Those can be GCC works fine (several kernels compiled w/o err's) Thanks! Rolf Obrecht Institut fuer Elektrische Maschinen RWTH Aachen Schinkelstrasse 4 D-52056 Aachen Tel. +49 241 807646 Fax +49 241 8888270 PGP public key available. "Wer Butter vom Amt will, muss Milch auf den Dienstweg schicken." -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
