From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [OT] Cisco 4.0.5 VPN client prints non-fatal stack
Date: Tue, 10 Aug 2004 17:26:25 +0200 [thread overview]
Message-ID: <4118E921.7040902@oracle.com> (raw)
...and works, as I'm currently connected via a 4.0.5 VPN tunnel.
VPN client 4.0.4.B works without printing the kernel messages.
Problem happens with 4.0.5 on both 2.6.8-rc3-bk4 and 2.6.8-rc4,
didn't test earlier kernels.
Since I know Cisco people are reading this list, and in case
someone else may be interested... I'm aware this may not be a
Linux kernel problem at all, but just in case - h
ere it goes:
cisco_ipsec: module license 'Proprietary' taints kernel.
Cisco Systems VPN Client Version 4.0.5 (Rel) kernel module loaded
Badness in local_bh_enable at kernel/softirq.c:136
[<c011942d>] local_bh_enable+0x62/0x81
[<f9cfbf19>] handle_vpnup+0x8d/0x1b7 [cisco_ipsec]
[<f9cfbca4>] interceptor_ioctl+0x133/0x161 [cisco_ipsec]
[<c031e962>] dev_ifsioc+0x133/0x43d
[<c031ee4b>] dev_ioctl+0x1df/0x336
[<c0314cfd>] sock_ioctl+0x100/0x2c4
[<c015f4e8>] sys_ioctl+0x148/0x280
[<c0110620>] do_page_fault+0x0/0x570
[<c0103d7d>] sysenter_past_esp+0x52/0x71
Badness in local_bh_enable at kernel/softirq.c:136
[<c011942d>] local_bh_enable+0x62/0x81
[<c031c712>] dev_remove_pack+0xf/0x17
[<f9cfbf47>] handle_vpnup+0xbb/0x1b7 [cisco_ipsec]
[<f9cfbca4>] interceptor_ioctl+0x133/0x161 [cisco_ipsec]
[<c031e962>] dev_ifsioc+0x133/0x43d
[<c031ee4b>] dev_ioctl+0x1df/0x336
[<c0314cfd>] sock_ioctl+0x100/0x2c4
[<c015f4e8>] sys_ioctl+0x148/0x280
[<c0110620>] do_page_fault+0x0/0x570
[<c0103d7d>] sysenter_past_esp+0x52/0x71
bad: scheduling while atomic!
[<c038c99c>] schedule+0x498/0x4cb
[<c0103f3c>] common_interrupt+0x18/0x20
[<c011007b>] show_mem+0xb3/0x121
[<c038ca83>] wait_for_completion+0x76/0xd0
[<c01123b5>] default_wake_function+0x0/0x12
[<c0124f1b>] __kernel_text_address+0x28/0x36
[<c01123b5>] default_wake_function+0x0/0x12
[<c010421f>] show_trace+0x5c/0x8e
[<c0124a7b>] synchronize_kernel+0x31/0x36
[<c0104304>] dump_stack+0x1c/0x20
[<c0124a3e>] wakeme_after_rcu+0x0/0xc
[<c031c712>] dev_remove_pack+0xf/0x17
[<f9cfbf47>] handle_vpnup+0xbb/0x1b7 [cisco_ipsec]
[<f9cfbca4>] interceptor_ioctl+0x133/0x161 [cisco_ipsec]
[<c031e962>] dev_ifsioc+0x133/0x43d
[<c031ee4b>] dev_ioctl+0x1df/0x336
[<c0314cfd>] sock_ioctl+0x100/0x2c4
[<c015f4e8>] sys_ioctl+0x148/0x280
[<c0110620>] do_page_fault+0x0/0x570
[<c0103d7d>] sysenter_past_esp+0x52/0x71
--alessandro
"Practice is more important than theory. A _lot_ more important."
(Linus Torvalds on lkml, 1 June 2004)
reply other threads:[~2004-08-10 15:29 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=4118E921.7040902@oracle.com \
--to=alessandro.suardi@oracle.com \
--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 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.