WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Xen 3.1.3 / Kernel 2.6.18.8 "NULL pointer dereference" Panic

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen 3.1.3 / Kernel 2.6.18.8 "NULL pointer dereference" Panic
From: Joshua West <jwest@xxxxxxxxxxxx>
Date: Thu, 14 Feb 2008 19:52:29 -0500
Delivery-date: Thu, 14 Feb 2008 16:54:04 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (X11/20071031)
Hey y'all,

Has anybody ever seen or have any information on a kernel panic such as
the paste below?  It occurred in a VM when a user was removing a large
number of files.  There was no mention of anything in dom0's logs or in
"xm dmesg".

This machine is a Dell PowerEdge 1950 running Xen 3.1.3 64-bit with
32-bit dom0 and domU (PAE) kernels.

Feb 13 14:35:25 build kernel: BUG: unable to handle kernel NULL pointer
dereference at virtual address 00000004
Feb 13 14:35:25 build kernel:  printing eip:
Feb 13 14:35:25 build kernel: c01726bb
Feb 13 14:35:25 build kernel: 15253000 -> *pde = 00000003:9b471027
Feb 13 14:35:25 build kernel: 1dbeb000 -> *pme = 00000000:00000000
Feb 13 14:35:25 build kernel: Oops: 0002 [#1]
Feb 13 14:35:25 build kernel: SMP
Feb 13 14:35:25 build kernel: Modules linked in:
Feb 13 14:35:25 build kernel: CPU:    0
Feb 13 14:35:25 build kernel: EIP:    0061:[<c01726bb>]    Not tainted VLI
Feb 13 14:35:25 build kernel: EFLAGS: 00010082   (2.6.18.8-32bit-4-xenU #1)
Feb 13 14:35:25 build kernel: EIP is at free_block+0x8b/0x120
Feb 13 14:35:25 build kernel: eax: 00001000   ebx: c0866180   ecx:
c5e5a000   edx: 00000000
Feb 13 14:35:25 build kernel: esi: c5e5ac0c   edi: c1712f40   ebp:
c09c0400   esp: d3215ee4
Feb 13 14:35:26 build kernel: ds: 007b   es: 007b   ss: 0069
Feb 13 14:35:26 build kernel: Process rm (pid: 11371, ti=d3214000
task=c1767a90 task.ti=d3214000)
Feb 13 14:35:26 build kernel: Stack: 00000680 0000001b 0000000b c09c03d4
0000001b c1712f40 0000001b c017227a
Feb 13 14:35:26 build kernel:        00000000 dc3ea3ec ca3584c4 c09c03c0
c0866180 c09c03c0 c1712f40 00000000
Feb 13 14:35:26 build kernel:        ca35842c c0172566 00000003 00000000
cf256000 d6f98d94 ca3584c4 c0201ced
Feb 13 14:35:26 build kernel: Call Trace:
Feb 13 14:35:26 build kernel:  [<c017227a>] cache_flusharray+0x5a/0xd0
Feb 13 14:35:26 build kernel:  [<c0172566>] kmem_cache_free+0x106/0x130
Feb 13 14:35:26 build kernel:  [<c0201ced>] ext3_destroy_inode+0x1d/0x30
Feb 13 14:35:26 build kernel:  [<c0189d15>] do_unlinkat+0xf5/0x160
Feb 13 14:35:26 build kernel:  [<c0107f62>] do_syscall_trace+0x222/0x235
Feb 13 14:35:26 build kernel:  [<c01053a3>] syscall_call+0x7/0xb
Feb 13 14:35:26 build kernel: Code: 03 15 10 59 7f c0 8b 02 f6 c4 40 0f
85 8b 00 00 00 8b 02 84 c0 0f 89 8a 00 00 00 8b 4a 1c 8b 44 24 20 8b 11
8b 5c 87 30 8b 41 0
4 <89> 42 04 89 10 31 d2 2b 71 0c c7 01 00 01 10 00 c7 41 04 00 02
Feb 13 14:35:26 build kernel: EIP: [<c01726bb>] free_block+0x8b/0x120
SS:ESP 0069:d3215ee4

Thanks.

-- 
Joshua West
Systems Engineer
Brandeis University
http://www.brandeis.edu


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>