From: linux@horizon.com
To: linux@horizon.com, romieu@fr.zoreil.com
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, shemminger@linux-foundation.org
Subject: Re: 2.6.24-rc6 oops in net_tx_action
Date: 7 Jan 2008 01:43:50 -0500 [thread overview]
Message-ID: <20080107064350.5042.qmail@science.horizon.com> (raw)
In-Reply-To: <20080106235719.GA10588@electric-eye.fr.zoreil.com>
> 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.)
next prev parent reply other threads:[~2008-01-07 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 22:29 2.6.24-rc6 oops in net_tx_action linux
2008-01-06 23:57 ` Francois Romieu
2008-01-07 6:43 ` linux [this message]
2008-01-07 8:23 ` David Miller
2008-01-07 19:13 ` linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080107064350.5042.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).