From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: kfree_skb on hard IRQ ???
Date: Wed, 14 Apr 2004 13:59:02 +0200 [thread overview]
Message-ID: <407D2786.3080801@imc-berlin.de> (raw)
In-Reply-To: <407C1601.2080100@imc-berlin.de>
Steven Scholz wrote:
> And what means
>
> alloc_skb called nonatomically from interrupt c00eb8d0
> kernel BUG at skbuff.c:174!
> Oops: Kernel Mode Software FPU Emulation, sig: 8
> NIP: C00E065C XER: 00000000 LR: C00E065C SP: C016BC80 REGS: c016bbd0 TRAP:
> 1000 Not tainted
> MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
> TASK = c0169fa0[0] 'swapper' Last syscall: 120
> last math 00000000 last altivec 00000000
> ...
> Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing
> <0>Rebooting in 10 seconds..
BTW the backtrace shows
0xc00dd374 -- 0xc00dd2f4 + 0x0080 alloc_skb
0xc00e85e8 -- 0xc00e85c0 + 0x0028 rtmsg_ifinfo
0xc00e8bb4 -- 0xc00e8b50 + 0x0064 rtnetlink_event
0xc001c200 -- 0xc001c1c0 + 0x0040 notifier_call_chain
0xc00e1668 -- 0xc00e15b0 + 0x00b8 dev_close
0xc00e3b84 -- 0xc00e3b60 + 0x0024 unregister_netdevice
0xc00b396c -- 0xc00b394c + 0x0020 unregister_netdev
0xc39c320c -- 0xc01afe08 + 0x3813404 _end
0xc39c5bbc -- 0xc01afe08 + 0x3815db4 _end
0xc39a8b60 -- 0xc01afe08 + 0x37f8d58 _end
0xc39a8c80 -- 0xc01afe08 + 0x37f8e78 _end
0xc39b4dac -- 0xc01afe08 + 0x3804fa4 _end
0xc0003844 -- 0xc00036b4 + 0x0190 ppc_irq_dispatch_handler
0xc0003924 -- 0xc00038e8 + 0x003c do_IRQ
The irq comes from unplugging the WLAN pcmcia card without calling "cardctl
eject" before (which btw worked for every other wlan card so far).
Ideas?
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-04-14 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 15:25 kfree_skb on hard IRQ ??? Steven Scholz
2004-04-13 15:54 ` Steven Scholz
2004-04-13 16:32 ` Steven Scholz
2004-04-14 11:59 ` Steven Scholz [this message]
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=407D2786.3080801@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.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.