public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: Tulip bug?
@ 2002-03-06  4:25 Jerrad Pierce
  2002-03-05 17:35 ` Jeff Garzik
  2002-03-06  4:06 ` Keith Owens
  0 siblings, 2 replies; 6+ messages in thread
From: Jerrad Pierce @ 2002-03-06  4:25 UTC (permalink / raw)
  To: Linux Kernel Mailing List

Well I managed to switch the console to the 8x9 font which gave 42 lines of
spew... No mention of tulip this time, at least not in what was visible.
Also none of these ever get logged to messages so ksymoops wouldn't help?
Most of it is Call Trace and Stack, which I am guessing is useless without
knowing the exact state of the machine before hand (I do have Call Trace and
Stack available if useful)?

Other than that I got:

reference at virtual address 00000070 printing eip: c0120095
*pde=00000000
Oops: 0
CPI=0
EIP: 0010:[<c0120095>] Not tainted
...

AND

<1> Unable to hande kernel NULL pointer dereference at virtual address
00000000 printing eip: c010ee96
*pde=00000000
Oops=0000
CPU=0
EIP: 0010:[<c010ee96>] Not tainted
...

AND

<0> Kernel panic: Aieee, killing interrupt controller!

Thanks!

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Tulip Bug ?
@ 2002-03-13  7:28 Adam Schrotenboer
  0 siblings, 0 replies; 6+ messages in thread
From: Adam Schrotenboer @ 2002-03-13  7:28 UTC (permalink / raw)
  To: linux-kernel

I am currently running 2.4.18-pre9-mjc2, but this also happens w/ 
2.4.18-pre9 (and 2.4.18-pre7-mjc, maybe others)

I am getting NETDEV Watchdog timeouts

Mar 13 02:12:54 tabriel kernel: NETDEV WATCHDOG: eth1: transmit timed out
Mar 13 02:12:54 tabriel kernel: eth1: 21140 transmit timed out, status 
fc665410, SIA fffffeff ffffffff 1c09fdc0 fffffec8, resetting...
Mar 13 02:12:54 tabriel kernel: eth1: transmit timed out, switching to 
100baseTx-FDX media.
Mar 13 02:13:02 tabriel kernel: NETDEV WATCHDOG: eth1: transmit timed out
Mar 13 02:13:02 tabriel kernel: eth1: 21140 transmit timed out, status 
fc665410, SIA fffffe1b ffffffff 1c09fdc0 fffffec8, resetting...
Mar 13 02:13:02 tabriel kernel: eth1: transmit timed out, switching to 
10baseT media.
Mar 13 02:13:34 tabriel kernel: NETDEV WATCHDOG: eth1: transmit timed out
Mar 13 02:13:34 tabriel kernel: eth1: 21140 transmit timed out, status 
fc665410, SIA fffffe0b ffffffff 1c09fdc0 fffffec8, resetting...
Mar 13 02:13:34 tabriel kernel: eth1: transmit timed out, switching to 
100baseTx-FDX media.


I have been getting this at largely unpredictable intervals. The 
solutions seems to be to ifdown the ethdevs, and rmmod the driver. then 
ifup the ethdevs (which also means I have to stop my PPPoE-DSL 
connection).

eth1, the dev that is timing out is not sharing its interrupt.
These boards are/were marketed under the brand name SVEC. I cannot find 
the box they came in at the moment, so don't have the model number.

Just for reference, here's the relevant lines from lspci -vv

00:09.0 Ethernet controller: Macronix, Inc. [MXIC] MX98713
	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
	Interrupt: pin A routed to IRQ 9
	Region 0: I/O ports at e400 [size=256]
	Region 1: Memory at e0100000 (32-bit, non-prefetchable) [size=256]
	Expansion ROM at de000000 [disabled] [size=64K]

00:0c.0 Ethernet controller: Macronix, Inc. [MXIC] MX98713
	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
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at ec00 [size=256]
	Region 1: Memory at e0102000 (32-bit, non-prefetchable) [size=256]
	Expansion ROM at df000000 [disabled] [size=64K]


TIA
--
tabris.net

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Tulip bug?
@ 2002-03-02 13:29 Jerrad Pierce
  0 siblings, 0 replies; 6+ messages in thread
From: Jerrad Pierce @ 2002-03-02 13:29 UTC (permalink / raw)
  To: linux-kernel

Hello, I upgraded to 2.4.16 shortly after it was released and have since
experienced quasi-periodic kernel panics (every few weeks). I have tested
my memory and while I got a few faults after several hours this panic
behavior is not what I (perhaps erroneously) would expect from faulty memory
instigated kernel panics. I've also run 2.4.17 and also get kernel panics.

Yesterday I noticed something in the panic spew (it's hard to notice
much as more than a screenful is output, why is that? It seems to be
counterproductive.)

  eth0: Internal fault the skbuff addresses do not match in tulip_rx: 00000010
  vs. 077f8010 c77f8000/c77f8010

I have a Netgear Fastgear 310TX and compiled in the tulip and old DECChip
modules (it didn't seem to work with just tulip).

PS> Please (b)cc as I am not subscribed

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2002-03-13  7:29 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-03-06  4:25 Tulip bug? Jerrad Pierce
2002-03-05 17:35 ` Jeff Garzik
2002-03-06 17:10   ` Jerrad Pierce
2002-03-06  4:06 ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2002-03-13  7:28 Tulip Bug ? Adam Schrotenboer
2002-03-02 13:29 Tulip bug? Jerrad Pierce

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox