From: Geoff Mishkin <gmishkin@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.5 panic while unloading cisco_ipsec
Date: Thu, 13 May 2004 17:12:06 -0400 [thread overview]
Message-ID: <1084482726.7506.6.camel@amsa> (raw)
Please let me know if I'm posting this in the wrong place. I get a
kernel panic with kernel 2.6.5 (compiled with gcc 2.95.3) when I try to
unload the Cisco VPN client's (4.0.3b) cisco_ipsec module. I know it's
a binary-only module, so I'm not sure how much help this will be, but
here's the text I managed to pull off the screen when I tried rmmod'ing
it:
(Not sure if there is anything above this, this is all that fit on the
screen, and I didn't find anything in the logs)
PREEMPT
CPU: 0
EIP: 0060:[<c02a9d26>] Tainted: PF
EFLAGS: 00010202 (2.6.5)
EIP is at qdisc_destroy+0x6/0xc4
eax: 00000064 ebx: c6daa000 ecx: c6dabf20 edx: c6dabf28
esi: 00000064 edi: ce5fd028 ebp: c6dabf6c esp: c6dabf28
ds: 007b es: 007b ss:0068
Process rmmod (pid: 7134, threadinfo=c6daa000 task=c6db19c0)
Stack: c6daa000 d0abb600 c02a9ff3 00000064 d0abb600 d0abb600 c02a1426
d0abb600
d0abb600 00000000 c0398a9c c02440c8 d0abb600 d0ae8f80 d0a99aec
d0abb600
d0ae8f80 c6daa000 c012f724 bffff730 00000000 bffff730 00000000
63736963
Call Trace:
[<c02a9ff3>] dev_shutdown+0x57/0xe4
[<c02a1426>] unregister_netdevice+0x192/0x288
[<c02440c8>] unregister_netdev+0x10/0x28
[<d0a99aec>] cleanup_module+0x1c/0x30 [cisco_ipsec]
[<c012f724>] sys_delete_module+0x140/0x174
[<c0143803>] sys_munmap+0x37/0x54
[<c0108f2f>] syscall_call+0x7/0xb
Code: 8b 5e 0c ff 4e 18 0f 94 c0 84 c0 0f 84 a8 00 00 00 8b 56 2c
<0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing
--Geoff Mishkin <gmishkin@comcast.net>
next reply other threads:[~2004-05-13 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 21:12 Geoff Mishkin [this message]
2004-05-13 21:41 ` Helge Deller
2004-05-13 22:12 ` Felipe Alfaro Solana
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=1084482726.7506.6.camel@amsa \
--to=gmishkin@comcast.net \
--cc=linux-kernel@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 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®