Messages in this thread |  | | Date | Thu, 02 Nov 2000 22:19:21 -0800 | From | David Ford <> | Subject | Re: [bug] NETDEV WATCHDOG: eth0: transmit timed out |
| |
Dan Hollis wrote:
> On Thu, 2 Nov 2000, David Ford wrote: > > Ok, something happend to the tulip driver in the recent testN kernels. > > I haven't found a reason why it happens and I can't easily reproduce it > > but what happens is noted on the subject line. > > I have three machines now that do this. It's unfixable until reboot (I > > don't have these as modules). > > What card, linksys lne100tx? > > -Dan
yep
00:13.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) Subsystem: Netgear FA310TX Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 set Interrupt: pin A routed to IRQ 10 Region 0: I/O ports at 6200 [size=256] Region 1: Memory at e4001000 (32-bit, non-prefetchable) [size=256] Expansion ROM at <unassigned> [disabled] [size=256K]
-d
-- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'."
begin:vcard n:Ford;David x-mozilla-html:TRUE org:<img src="http://www.kalifornia.com/images/paradise.jpg"> adr:;;;;;; version:2.1 email;internet:david@kalifornia.com title:Blue Labs Developer x-mozilla-cpt:;-12480 fn:David Ford end:vcard
|  |