From: emre kara <emrekara2002@yahoo.co.uk>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: emrekara2002@yahoo.co.uk
Subject: powerpc kernel 2.6.35.6 crash with gianfar ethernet at full line rate traffic
Date: Tue, 28 Sep 2010 13:32:24 +0000 (GMT) [thread overview]
Message-ID: <864381.11683.qm@web25607.mail.ukl.yahoo.com> (raw)
Hi all,
I have a serious problem with latest stable kernel (2.6.35.6) and gianfar ethernet driver.
I'am using default SMP kernel configuration and MPC8572DS development board and also using an hardware packet generator.
My test is ip forwarding between eth0 and eth1, and Hardware packet generator produces full duplex, full line rate traffic with random packet length and random payload . After 1.2 billion packet passed, kernel produces this bellow crash message.
I have done same test with an intel quad core pc and sky2 gigabit ethernet controller. No errors occured yet. So that it seems that this problem may be related with gianfar.
Any comment and help are appreciated.
Thanks.
Emre
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:127!
Oops: Exception in kernel mode, sig: 5 [#1]
SMP NR_CPUS=8 MPC8572 DS
last sysfs file: /sys/devices/pci0002:03/0002:03:00.0/subsystem_device
Modules linked in:
NIP: c0255260 LR: c0255260 CTR: c0221f64
REGS: effebd70 TRAP: 0700 Not tainted (2.6.35.6)
MSR: 00029000 <EE,ME,CE> CR: 24028022 XER: 20000000
TASK = ef03ce10[3] 'ksoftirqd/0' THREAD: ef04a000 CPU: 0
GPR00: c0255260 effebe20 ef03ce10 0000007c 00021000 ffffffff c0225ac0 c04364cc
GPR08: c042e9ac c04364e0 effea000 c0430000 20028048 1001a108 ef550000 ef0f6d70
GPR16: ef0f6e18 ef0f685c 00000000 ef550800 00000008 00000001 ef0f6800 0000003f
GPR24: ef141a80 ef0f6b60 00000000 ef550950 ef0f6b60 00000420 ef3f0400 ef525600
NIP [c0255260] skb_put+0x8c/0x94
LR [c0255260] skb_put+0x8c/0x94
Call Trace:
[effebe20] [c0255260] skb_put+0x8c/0x94 (unreliable)
[effebe30] [c023e004] gfar_clean_rx_ring+0x10c/0x4d8
[effebe90] [c023e794] gfar_poll+0x3c4/0x5f4
[effebf60] [c0262498] net_rx_action+0xf8/0x1a4
[effebfa0] [c0049dcc] __do_softirq+0xe0/0x178
[effebff0] [c0010790] call_do_softirq+0x14/0x24
[ef04bf50] [c0004868] do_softirq+0x90/0xa0
[ef04bf70] [c004a98c] run_ksoftirqd+0xb4/0x164
[ef04bfb0] [c005dacc] kthread+0x78/0x7c
[ef04bff0] [c0010b9c] kernel_thread+0x4c/0x68
Instruction dump:
81030098 2f800000 409e000c 3d20c03d 3809e0d8 3c60c03d 7c8802a6 7d695b78
3863ee60 90010008 4cc63182 4bdefaa9 <0fe00000> 48000000 9421fff0 7c0802a6
Kernel panic - not syncing: Fatal exception in interrupt
Call Trace:
[effebb20] [c00082fc] show_stack+0x4c/0x180 (unreliable)
[effebb50] [c0043720] panic+0xa0/0x11c
[effebbe0] [c000db44] die+0x184/0x1d0
[effebc10] [c000dcfc] _exception+0x114/0x130
[effebd60] [c0011440] ret_from_except_full+0x0/0x4c
--- Exception: 700 at skb_put+0x8c/0x94
LR = skb_put+0x8c/0x94
[effebe30] [c023e004] gfar_clean_rx_ring+0x10c/0x4d8
[effebe90] [c023e794] gfar_poll+0x3c4/0x5f4
[effebf60] [c0262498] net_rx_action+0xf8/0x1a4
[effebfa0] [c0049dcc] __do_softirq+0xe0/0x178
[effebff0] [c0010790] call_do_softirq+0x14/0x24
[ef04bf50] [c0004868] do_softirq+0x90/0xa0
[ef04bf70] [c004a98c] run_ksoftirqd+0xb4/0x164
[ef04bfb0] [c005dacc] kthread+0x78/0x7c
[ef04bff0] [c0010b9c] kernel_thread+0x4c/0x68
Rebooting in 180 seconds..
reply other threads:[~2010-09-28 13:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=864381.11683.qm@web25607.mail.ukl.yahoo.com \
--to=emrekara2002@yahoo.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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
all inboxes | Powered by JetHome®