From: Philip Van-Houtte <jvan_1@students.concordia.ca>
To: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: oops in process_backlog : kernel 2.6.9
Date: Fri, 18 Feb 2005 12:03:00 -0500 [thread overview]
Message-ID: <1108746180.42161fc4a86f6@webmail.cam.org> (raw)
I have an embedded application, running a stock kernel 2.6.9, on an 8240
receiving UDP. Occasionaly after a (re)boot the system will oops after
opening (socket/bind) its first connection just as the traffic comes in.
It always occurs after the call to netif_receive_skb has competed.
Oops: kernel access of bad area, sig: 11 [#1]
PREEMPT
NIP: C021FD14 LR: C021FCB4 SP: C3049C70 REGS: c3049bc0 TRAP: 0300 Tainted: P
MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00003CAE, DSISR: 20000000
TASK = c309d050[162] 'rtp_daemon' THREAD: c3048000Last syscall: 102
GPR00: 00001032 C3049C70 C309D050 00000000 C3049B50 00000000 00000000 C5023E04
GPR08: 00000002 0000000D 00000000 C036496C 2010C002 00000000 037FB000 038D0000
GPR16: 00002020 00000000 10000000 7FFFF960 00000001 00000000 C0300000 C3049CB8
GPR24: FFFBDE37 C0364960 C0364988 00000040 00000000 C0429800 00000001 C036496C
NIP [c021fd14] process_backlog+0x108/0x188
LR [c021fcb4] process_backlog+0xa8/0x188
Call trace:
[c021fe2c] net_rx_action+0x98/0x178
[c011fdd0] __do_softirq+0xdc/0xec
[c011fe38] do_softirq+0x58/0x5c
[c0106188] do_IRQ+0xdc/0xe0
[c01048ec] ret_from_except+0x0/0x14
[c0217f68] lock_sock+0x6c/0x84
[c02152ac] sys_bind+0x70/0x94
[c0215f58] sys_socketcall+0xc8/0x1d8
[c0104240] ret_from_syscall+0x0/0x44
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 180 seconds..
Any insights/work-arounds/ would be appreciated.
next reply other threads:[~2005-02-18 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 17:03 Philip Van-Houtte [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-18 23:26 oops in process_backlog : kernel 2.6.9 Rune Torgersen
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=1108746180.42161fc4a86f6@webmail.cam.org \
--to=jvan_1@students.concordia.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@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