Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf.sub.org!flatlin!bad From: bad@flatlin.ka.sub.org (Christoph Badura) Subject: Re: Lance query Organization: Guru Systems/Funware Department Date: Fri, 9 Oct 1992 19:40:04 GMT Message-ID: <BvvDAt.ItC@flatlin.ka.sub.org> References: <12764.9210021637@thor.cf.ac.uk> <718075048snx@crynwr.com> Lines: 26 In <718075048snx@crynwr.com> nelson@crynwr.com (Russell Nelson) writes: >In article <12764.9210021637@thor.cf.ac.uk> spedpr@thor.cf.ac.uk writes: > I've been getting a number of is1:reset errors from the isolink driver > and the cause is due to the lance stopping its transmitter. > Specifically, in the interrupt routine the transmitter-on (TXON) bit of > the lance is checked and if it isn't set then a reset occurs. >I don't know, particularly. However, AMD insists that there are no >bugs in the LANCE, so the answer to your question lies in their >published documentation. No hidden bug sheet/shit. Well, according to SunOS 4.0.somethings le(4S): lr%d: transmitter frozen - resetting A bug in the LANCE chip has stopped the chip's transmitter section. The driver has detected this condition and reinitialized the chip. The next to pages list a lot additonal anomalies (:-)) of the chip. -- Christoph Badura --- bad@flatlin.ka.sub.org AIX is a better... is a better... is a better... OpenSystem. IBM Rep at GUUG Symposium '92