All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Kernel mode fault at addr 0x92c00000, ip 0x80bcead
Date: Fri, 13 Oct 2006 16:07:47 -0400	[thread overview]
Message-ID: <20061013200747.GB5517@ccure.user-mode-linux.org> (raw)
In-Reply-To: <452C29F2.8050908@theshore.net>

On Tue, Oct 10, 2006 at 06:17:06PM -0500, Christopher S. Aker wrote:
> This is 2.6.18-um, on top of a 2.6.16.29-skas3-v8.2 host.
> 
> Kernel file is here:
> http://www.theshore.net/~caker/uml/kernels/2.6.18-linode25
> 
> 
> Kernel panic - not syncing: Kernel mode fault at addr 0x92c00000, ip 
> 0x80bcead

The stack I get from that is:

85a0f49c:  [<800350cf>] csum_partial+0xdb/0xe8
85a0f74c:  [<802aafe2>] skb_checksum+0xe7/0x28f
85a0f788:  [<802afd31>] skb_checksum_help+0x9c/0x13e
85a0f7ac:  [<803292fc>] ip_nat_fn+0x1d2/0x1e7
85a0f7e0:  [<80329528>] ip_nat_local_fn+0x75/0xf3
85a0f808:  [<802d8569>] nf_iterate+0x63/0x7b
85a0f830:  [<802d85ec>] nf_hook_slow+0x6b/0xe4
85a0f86c:  [<802e4a44>] ip_queue_xmit+0x3d7/0x4c2
85a0f944:  [<802f7668>] tcp_transmit_skb+0x2b8/0x4b1
85a0f984:  [<802f91fd>] tcp_push_one+0xde/0x159
85a0f9ac:  [<802eca55>] tcp_sendmsg+0x438/0xe54
85a0fa30:  [<8030a718>] inet_sendmsg+0x4a/0x56
			__sock_sendmsg
85a0fa48:  [<802a4aad>] do_sock_write+0xbb/0xc5
85a0fa6c:  [<802a4c5f>] sock_aio_write+0x95/0x99
85a0fae0:  [<80082978>] do_sync_write+0xde/0x124
85a0fb90:  [<80082b81>] vfs_write+0x1c3/0x23d
85a0fbc8:  [<80082ccc>] sys_write+0x51/0x80
85a0fbf0:  [<80022bda>] handle_syscall+0x11a/0x138
85a0fc6c:  [<80033b68>] handle_trap+0x31/0x12d
85a0fc94:  [<80034192>] userspace+0x1c7/0x21e
85a0fcf0:  [<80022808>] fork_handler+0xef/0xff
85a0fd1c:  [<8039a828>] __restore+0x0/0x8
85a0fd5c:  [<8039aa81>] kill+0x11/0x20

> Is this a UML issue?

Hard to say.  With a kernel fault, I'd be tempted to say so, but I see no
UML code on the stack.

Have you seen just this one occurence of this?  I spent part of the
afternoon dusting off a patch which would provide the registers at the
time of the segfault.  That maybe would have helped here.

				Jeff

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2006-10-13 20:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 23:17 [uml-devel] Kernel mode fault at addr 0x92c00000, ip 0x80bcead Christopher S. Aker
2006-10-13 20:07 ` Jeff Dike [this message]
2006-10-14  0:42   ` Blaisorblade
2006-10-14  1:19     ` Christopher S. Aker
2006-10-14  2:35       ` Blaisorblade
2006-10-14  3:17         ` Christopher S. Aker
2006-10-16 14:44     ` Jeff Dike
2006-10-21  1:05       ` Blaisorblade
2006-10-25 15:17         ` Jeff Dike

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=20061013200747.GB5517@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=caker@theshore.net \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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.