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-devel

RE: [Xen-devel] Another dom0 crash (Unable to handle kernel NULLpointer

To: "Christopher S. Aker" <caker@xxxxxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Another dom0 crash (Unable to handle kernel NULLpointer dereference)
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 19 Apr 2006 10:08:07 +0100
Delivery-date: Wed, 19 Apr 2006 02:08:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZjZc5yzMnYgyeKQGCji9cAI0Y/pQAKkqUg
Thread-topic: [Xen-devel] Another dom0 crash (Unable to handle kernel NULLpointer dereference)
> Subject: [Xen-devel] Another dom0 crash (Unable to handle 
> kernel NULLpointer dereference)
> 
> This time running Xen 3.0.2-2, PAE

Please can you supply more information e.g. how many VMs were running,
do you know what they were doing, can you repro, details about the h/w,
amount of memory etc. This is a separate issue from the previous one. 

I seem to recall a similar crash has been reported before, but there was
no repro information in the report either.

Thanks,
Ian
 
> Previous post:
> http://lists.xensource.com/archives/html/xen-devel/2006-04/msg
> 00446.html
> 
> Unable to handle kernel NULL pointer dereference at virtual 
> address 00000004
>   printing eip:
> c0161905
> 07786000 -> *pde = 00000001:058d6001
> 06e54000 -> *pme = 00000000:00000000
> Oops: 0002 [#1]
> SMP
> Modules linked in:
> CPU:    1
> EIP:    0061:[<c0161905>]    Not tainted VLI
> EFLAGS: 00010046   (2.6.16-xen0 #1)
> EIP is at cache_alloc_refill+0x185/0x560
> eax: c0670f00   ebx: ffffffff   ecx: 00000010   edx: 00000000
> esi: c8bd1000   edi: 00000002   ebp: c00dfe00   esp: cfa7be3c
> ds: 007b   es: 007b   ss: 0069
> Process kjournald (pid: 1187, threadinfo=cfa7a000 task=cfa0ca70)
> Stack: <0>000016a7 00000000 c0525e40 00000050 00000050 
> 00000050 c0673b40 c066f800
>         c0670f00 c01408db c0664958 cfa7a000 c10f06e0 c8bd101c 
> 00000001 c10f06e0
>         00000000 00000000 00001000 c0161777 c10f06e0 00000000 
> c01679e9 c0673b40 Call Trace:
>   [<c01408db>] add_to_page_cache+0x6b/0x100
>   [<c0161777>] kmem_cache_alloc+0x77/0x80
>   [<c01679e9>] alloc_buffer_head+0x19/0x50
>   [<c01695fc>] alloc_page_buffers+0x3c/0xe0
>   [<c016b16f>] __getblk+0x15f/0x2b0
>   [<c01ea978>] journal_get_descriptor_buffer+0x68/0xd0
>   [<c01e68d1>] journal_commit_transaction+0xd01/0x11f0
>   [<c0128300>] lock_timer_base+0x20/0x50
>   [<c0129259>] try_to_del_timer_sync+0x49/0x60
>   [<c01e9680>] kjournald+0xc0/0x230
>   [<c01e8e80>] commit_timeout+0x0/0x10
>   [<c0134130>] autoremove_wake_function+0x0/0x60
>   [<c01e95c0>] kjournald+0x0/0x230
>   [<c0102cc5>] kernel_thread_helper+0x5/0x10
> Code: 56 0c 8b 3c b8 89 7e 14 89 54 8d 14 41 89 4d 00 8b 44 
> 24 18 8b 7e 10 3b 78 38 0f 83 3a ff ff ff 4b 83 fb ff 75 c0 
> 8b 16 8b 46 04 <89> 42
> 04 89 10 83 7e 14 ff c7 06 00 01 10 00 c7 46 04 00 02 20
> 
> -Chris
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

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

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