From: Justin Sanchez <jsanchez@cs.ucf.edu>
To: netdev@oss.sgi.com
Subject: Re: [Bug 1030] New: racoon causes oops when implementing IPSec key
Date: 03 Aug 2003 01:51:22 -0400 [thread overview]
Message-ID: <1059889883.1187.15.camel@mobile> (raw)
In-Reply-To: <20030802212018.B14141@electric-eye.fr.zoreil.com>
[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]
Hi. I had this problem on 2.6.0-test1 and -test2 and -test2-bk2, so I'll
try to report it. I'm new to the scene, so I apologize in advance for
this post.
Background. 2 machines. e100 cards on each, if it matters. ipsec-tools
0.2.2. I give each of them directives to use esp and ah in transport
mode. I turn on racoon on each box. I ping. Both panic. Following is
about the message:.
Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
c02bbd06
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c02bbd06>] Not tainted
EFLAGS: 00010206
EIP is at memcpy+0x1e/0x39
eax: 00000018 ebx: f6fe8a00 ecx: 00000006 edx: 00000000
esi: 00000000 edi: 00000000 ebp: c0562520 esp: f6fb5ccc
ds: 007b es: 007b ss:0068
Process racoon (pid: 418, threadinfo=f6fb4000 task=f6fbb300)
Stack:
Call Trace:
xfrm_state_update
pfkey_add
parse_exthdrs
pfkey_process
pfkey_sendmsg
sock_sendmsg
verify_iovec
sys_sendmsg
sockfd_lookup
sys_sendto
sys_getsockname
__pollwait
update_process
sys_send
sys_socketcall
syscall_call
Code: f3 a5 a8 02 74 02 66 a5 a8 01 74 01 a4 89 d0 8b 74 24 02 8b
<0>Kernel panic: Fatal exception in interrupt
In interrupt handler = not syncing
If you want the full text of it, its at 67.9.9.32/oops.jpg.
I'm probably just doing something stupid...
On Sat, 2003-08-02 at 15:20, Francois Romieu wrote:
> Justin Sanchez <jsanchez@cs.ucf.edu> :
> [...]
> > How current? I've just seen it in -test2-bk2.
>
> Forwarded to davem@redhat.com.
>
> You may consider posting the data of the bug-report updated to -test2-bk2
> on netdev@oss.sgi.com.
>
> --
> Ueimor
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
parent reply other threads:[~2003-08-03 5:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030802212018.B14141@electric-eye.fr.zoreil.com>]
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=1059889883.1187.15.camel@mobile \
--to=jsanchez@cs.ucf.edu \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).