Re: 2.6.24-rc6 oops in net_tx_action

Re: 2.6.24-rc6 oops in net_tx_action

[linux]

> linux@horizon.com <linux@horizon.com> :
>> Kernel is 2.6.24-rc6 + linuxpps patches, which are all to the serial
>> port driver.
>> 
>> 2.6.23 was known stable.  I haven't tested earlier 2.6.24 releases.
>> I think it happened once before; I got a black-screen lockup with
>> keyboard LEDs blinking, but that was with X running so I couldn't see a
>> console oops.  But given that I installed 2.6.24-rc6 about 24 hours ago,
>> that's a disturbing pattern.

> It is probably this one:
>
> http://marc.info/?t=119782794000003&r=1&w=2

Thanks!  I got the patch from
http://marc.info/?l=linux-netdev&m=119756785219214
(Which didn't make it into -rc7; please fix!)
and am recompiling now.

Actually, I grabbed the hardware mitigation followon patch while I was
at it.  I notice that the comment explaining the format of CSR11 and
what 0x80F10000 means got lost; perhaps it would be nice to resurrect it?

0x80F10000
  80000000 = Cycle size (timer control)
  78000000 = TX timer in 16 * Cycle size
  07000000 = No. pkts before Int. (0 =  interrupt per packet)
  00F00000 = Rx timer in Cycle size
  000E0000 = No. pkts before Int.
  00010000 = Continues mode (CM)
  
(Boy, that tulip driver could use a whitespace overhaul.)

Re: 2.6.24-rc6 oops in net_tx_action

[David Miller]

From: linux@horizon.com
Date: 7 Jan 2008 01:43:50 -0500

> Thanks!  I got the patch from
> http://marc.info/?l=linux-netdev&m=119756785219214
> (Which didn't make it into -rc7; please fix!)
> and am recompiling now.

Jeff is busy so he's asked me to pick up the more important
driver bug fixes that get posted.

I'll push this around, thanks.

Re: 2.6.24-rc6 oops in net_tx_action

[linux]

>> Thanks!  I got the patch from
>> http://marc.info/?l=linux-netdev&m=119756785219214
>> (Which didn't make it into -rc7; please fix!)
>> and am recompiling now.

> Jeff is busy so he's asked me to pick up the more important
> driver bug fixes that get posted.
>
> I'll push this around, thanks.

Much obliged.  It's only 11 hours of uptime, but no problems so far,
even trying abusive things like "ping -f -l64 -s8000".