From: Ben Greear <greearb@candelatech.com>
To: netdev <netdev@vger.kernel.org>
Subject: r8169 crash (probably my fault) in 3.3.0-rc1+ (net-next)
Date: Thu, 09 Feb 2012 14:20:27 -0800 [thread overview]
Message-ID: <4F3446AB.2080209@candelatech.com> (raw)
I am hacking on the 8169 code, (adding RX-ALL and RX-FCS support on top of
my previously posted patches) so this could easily be my
fault..but just in case someone else has seen it, please
let me know....
BUG: unable to handle kernel NULL pointer dereference at 00000c9c
IP: [<c07083f6>] skb_gro_reset_offset+0x3a/0x73
*pde = 00000000
Oops: 0000 [#1] SMP
Modules linked in: bridge 8021q garp stp llc ip_gre gre veth fuse macvlan pktgen coretemp hwmon nfs lockd]
Pid: 7659, comm: tshark Not tainted 3.3.0-rc1+ #25 To Be Filled By O.E.M. To Be Filled By O.E.M./To be fi.
EIP: 0060:[<c07083f6>] EFLAGS: 00210246 CPU: 0
EIP is at skb_gro_reset_offset+0x3a/0x73
EAX: 00000c9c EBX: f16353c0 ECX: f175d030 EDX: f16353c0
ESI: f16353d8 EDI: f4e47c68 EBP: f580bf48 ESP: f580bf3c
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process tshark (pid: 7659, ti=f580a000 task=f14ede60 task.ti=f1444000)
Stack:
f16353c0 f4d184cc f4e47c40 f580bf58 c070c1ad f4d18000 00000002 f580bfb0
f88fff68 f4d18bb4 3148c000 00000003 f5959060 00000040 0003dc40 f4d18b88
00000040 803fbf8c f4d18000 f4d184c0 00000003 f4d184cc 00000000 f16353c0
Call Trace:
[<c070c1ad>] napi_gro_receive+0x10/0x24
[<f88fff68>] rtl8169_poll+0x2d6/0x443 [r8169]
[<c070c2ba>] net_rx_action+0x92/0x1a2
[<c042ad54>] __do_softirq+0x6d/0xfa
[<c042ace7>] ? irq_enter+0x4d/0x4d
<IRQ>
[<c042aba4>] ? irq_exit+0x32/0x93
[<c0403a20>] ? do_IRQ+0x7c/0x90
[<c07a96e9>] ? common_interrupt+0x29/0x30
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2012-02-09 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 22:20 Ben Greear [this message]
2012-02-10 9:30 ` r8169 crash (probably my fault) in 3.3.0-rc1+ (net-next) Francois Romieu
2012-02-10 17:09 ` Ben Greear
2012-02-10 19:29 ` Ben Greear
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=4F3446AB.2080209@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.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.