From: "Charles Coffing" <ccoffing@novell.com>
To: xen-devel@lists.sourceforge.net
Subject: panic in e100_exec_cb()
Date: Mon, 20 Sep 2004 16:22:03 -0600 [thread overview]
Message-ID: <s14f03b1.045@sinclair.provo.novell.com> (raw)
With today's build, my domain 0 crashes during boot when it tries to
bring eth0 up (it's an E100).
cb->prev (eax) is NULL in e100_exec_cb() (e100.c:827). Just from code
inspection, I don't see how this can be. e100_alloc_cbs() was just
called, which looks like it should have correctly linked up all the
cb->prev/cb->next pointers.
It happens regardless of CONFIG_XEN_WRITABLE_PAGETABLES.
Has anyone else seen this?
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Unable to handle kernel NULL pointer dereference at virtual address
00000002
printing eip:
c022d6d2
*pde = ma 00000000 pa 55555000
[<c022ea3a>] e100_alloc_cbs+0x74/0x140
[<c022f5bb>] e100_up+0x39/0x1d6
[<c0127f8b>] queue_delayed_work+0x50/0x6d
[<c02307b3>] e100_open+0x23/0x69
[<c031198b>] dev_open+0x8a/0xe6
[<c0312e6e>] dev_change_flags+0x51/0x11f
[<c03479d6>] devinet_ioctl+0x4f1/0x5b2
[<c03496b9>] inet_ioctl+0x7e/0xa8
[<c030a026>] sock_ioctl+0x184/0x25d
[<c015c4e6>] sys_ioctl+0x16f/0x211
[<c010d1b7>] syscall_call+0x7/0xb
Oops: 0002 [#1]
Modules linked in:
CPU: 0
EIP: 0061:[<c022d6d2>] Not tainted
EFLAGS: 00013202 (2.6.8.1-xen0)
EIP is at e100_hw_init+0x19c/0x6e3
eax: 00000000 ebx: c66c8000 ecx: 00000005 edx: c7c19220
esi: c7c19220 edi: 0000003f ebp: 00000000 esp: c73cfe40
ds: 0069 es: 0069 ss: 0069
Process ip (pid: 1708, threadinfo=c73ce000 task=c745a680)
Stack: c7c19220 c66c8000 00000000 00000040 c7c19220 00000000 c022ea3a
c1199844
00006700 c7c19484 00000000 00000000 00000000 c7c19220 c7c19220
00000000
c022f5bb c7c19220 c7fee260 0000004f c0127f8b c03f6698 c7c19000
00000000
Call Trace:
[<c022ea3a>] e100_alloc_cbs+0x74/0x140
[<c022f5bb>] e100_up+0x39/0x1d6
[<c0127f8b>] queue_delayed_work+0x50/0x6d
[<c02307b3>] e100_open+0x23/0x69
[<c031198b>] dev_open+0x8a/0xe6
[<c0312e6e>] dev_change_flags+0x51/0x11f
[<c03479d6>] devinet_ioctl+0x4f1/0x5b2
[<c03496b9>] inet_ioctl+0x7e/0xa8
[<c030a026>] sock_ioctl+0x184/0x25d
[<c015c4e6>] sys_ioctl+0x16f/0x211
[<c010d1b7>] syscall_call+0x7/0xb
Code: 66 81 60 02 ff bf 8b 86 14 01 00 00 3b 86 10 01 00 00 3e 75
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
next reply other threads:[~2004-09-20 22:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 22:22 Charles Coffing [this message]
2004-09-21 0:11 ` panic in e100_exec_cb() Paul Dorman
2004-09-21 7:36 ` Keir Fraser
2004-09-21 17:48 ` Brian Wolfe
2004-09-21 19:40 ` Paul Dorman
2004-09-21 7:30 ` Keir Fraser
2004-09-21 7:37 ` Ian Pratt
2004-09-21 11:25 ` Problems rebooting xen guest Thomas E. Conway-Poulsen
2004-09-22 7:44 ` Ian Pratt
2004-09-22 7:47 ` Keir Fraser
2004-09-21 19:42 ` panic in e100_exec_cb() Paul Dorman
2004-09-21 20:45 ` Keir Fraser
2004-09-21 11:25 ` Ian Pratt
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=s14f03b1.045@sinclair.provo.novell.com \
--to=ccoffing@novell.com \
--cc=xen-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.