From: Johannes Stezenbach <js@linuxtv.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
shemminger@osdl.org, netdev@vger.kernel.org
Subject: Re: Linux 2.6.15-rc5: sk98lin broken
Date: Mon, 5 Dec 2005 00:43:20 +0100 [thread overview]
Message-ID: <20051204234320.GA7478@linuxtv.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0512032155290.3099@g5.osdl.org>
On Sat, Dec 03, 2005, Linus Torvalds wrote:
> shemminger@osdl.org:
> sk98lin: fix checksumming code
> sk98lin: add permanent address support
> sk98lin: avoid message confusion with skge
I have an Asus P4P800 "Deluxe" with 3c940 LOM.
If I ping the box I get the following:
Dec 4 22:57:02 abc kernel: [<c0103c00>] dump_stack+0x17/0x19
Dec 4 22:57:02 abc kernel: [<c03b99e9>] netdev_rx_csum_fault+0x27/0x2d
Dec 4 22:57:02 abc kernel: [<c03b75a9>] __skb_checksum_complete+0x5a/0x60
Dec 4 22:57:02 abc kernel: [<c0404c51>] icmp_error+0xbd/0x193
Dec 4 22:57:02 abc kernel: [<c0402291>] ip_conntrack_in+0x67/0x279
Dec 4 22:57:02 abc kernel: [<c03c8cbf>] nf_iterate+0x59/0x7d
Dec 4 22:57:02 abc kernel: [<c03c8d3a>] nf_hook_slow+0x57/0x106
Dec 4 22:57:02 abc kernel: [<c03d1074>] ip_rcv+0x1af/0x580
Dec 4 22:57:02 abc kernel: [<c03ba1ed>] netif_receive_skb+0x15a/0x1ef
Dec 4 22:57:02 abc kernel: [<c03ba301>] process_backlog+0x7f/0x10d
Dec 4 22:57:02 abc kernel: [<c03ba40c>] net_rx_action+0x7d/0x110
Dec 4 22:57:02 abc kernel: [<c01250a2>] __do_softirq+0x72/0xe1
Dec 4 22:57:02 abc kernel: [<c0104ed7>] do_softirq+0x5d/0x61
Dec 4 22:57:02 abc kernel: =======================
Dec 4 22:57:02 abc kernel: [<c01251fa>] irq_exit+0x48/0x4a
Dec 4 22:57:02 abc kernel: [<c0104d9d>] do_IRQ+0x5d/0x8f
Dec 4 22:57:02 abc kernel: [<c010372e>] common_interrupt+0x1a/0x20
Dec 4 22:57:02 abc kernel: [<c0100d51>] cpu_idle+0x49/0xa0
Dec 4 22:57:02 abc kernel: [<c01002d7>] rest_init+0x37/0x39
Dec 4 22:57:02 abc kernel: [<c057f8cf>] start_kernel+0x164/0x177
Dec 4 22:57:02 abc kernel: [<c0100210>] 0xc0100210
(once for each ICMP packet)
2.6.15-rc2 works fine.
Johannes
next prev parent reply other threads:[~2005-12-04 23:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 6:03 Linux 2.6.15-rc5: off-line for a week Linus Torvalds
2005-12-04 15:34 ` Gene Heskett
2005-12-04 18:50 ` Michael Krufky
2005-12-04 20:47 ` Gene Heskett
2005-12-04 21:14 ` Michael Krufky
2005-12-05 0:16 ` Gene Heskett
2005-12-04 16:56 ` Jesper Juhl
2005-12-04 17:26 ` Michal Piotrowski
2005-12-04 18:35 ` Jesper Juhl
2005-12-04 22:25 ` Andrea Arcangeli
2005-12-04 23:43 ` Johannes Stezenbach [this message]
2005-12-05 19:00 ` [PATCH linux-2.6.15-rc5] sk98lin: rx checksum offset not set Stephen Hemminger
2005-12-05 19:22 ` Johannes Stezenbach
2005-12-05 19:13 ` Linux 2.6.15-rc5: sk98lin broken Bill Davidsen
2005-12-07 21:59 ` Linux 2.6.15-rc5: off-line for a week Rich Walker
2005-12-10 16:27 ` Linux 2.6.15-rc5: multiuser scheduling trouble Helge Hafting
2005-12-12 0:09 ` Linus Torvalds
2005-12-12 6:51 ` Ingo Molnar
2005-12-12 11:18 ` Helge Hafting
2005-12-12 11:30 ` Nix
2005-12-12 12:31 ` Helge Hafting
2005-12-12 10:51 ` Helge Hafting
2005-12-10 21:23 ` Linux 2.6.15-rc5 bad page with fglrx on Radeon X300 Brice Goglin
2005-12-10 21:43 ` Lee Revell
2005-12-11 10:49 ` Hugh Dickins
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=20051204234320.GA7478@linuxtv.org \
--to=js@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.