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

Re: [Xen-users] domU kernel panic report

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU kernel panic report
From: "Ulrich Windl" <ulrich.windl@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 07 Feb 2007 08:02:15 +0100
Delivery-date: Tue, 06 Feb 2007 23:02:48 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070206181840.GA7288@xxxxxxxxxxxxxxxx>
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>
Organization: Universitaet Regensburg, Klinikum
Priority: normal
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I have no oops, but very strange problems with NFS mounting and locking. Maybe 
either in XEN or in the NFS there's an odd bug that triggers rarely. My guess...
Could it be in your case that you are out of memory?

Ulrich

On 6 Feb 2007 at 10:18, Tom Marshall wrote:

> I just saw this kernel panic.  I've been running Xen for over a year, and
> this particular combination of software for a couple weeks.  I've never seen
> a kernel panic under Xen before (I know, knock on wood...) so I thought it
> might be worthwhile to report.
> 
> Setup...
> 
> Xen 3.0.4 hypervisor, locally compiled, PAE enabled
> dom0 is Ubuntu Edgy, 2.6.16.33-xen0, locally compiled, PAE enabled
> domU is CentOS 3.8, 2.4.21-47.EL.xs10xenU/i686, from Xen package
> 
> Panic text from console...
> 
> Unable to handle kernel paging request at virtual address e332c000            
>              
>  printing eip:                                                                
>              
> c01ab365
> *pde = ma 00000000 pa fffff000
> Oops: 0003
> nfs lockd sunrpc ext3 jbd
> CPU:    1
> EIP:    0061:[<c01ab365>]    Not tainted
> EFLAGS: 00010206
> 
> EIP is at _arch_exit_mmap [kernel] 0x2f5 (2.4.21-47.EL.xs10xenU/i686)
> eax: 00000000   ebx: 00000000   ecx: 00000400   edx: e332c000
> esi: a4fc5001   edi: e332c000   ebp: 00000001   esp: c1f6bec8
> ds: 0068   es: 0068   ss: 0068
> Process bash (pid: 15427, stackpage=c1f6b000)
> Stack: e332c000 00000000 c01a9eed e332c000 00000000 00001000 e40a0008 c02f3d60
>        c1f6a000 cf729a60 e40a0000 eb8dbbe0 d5b6b380 cd090000 eb8dbbe0 c010e13a
>        eb8dbbe0 00000000 00000020 00000000 c010e417 eb8dbbe0 d5b6b380 000000f8
> Call Trace:   [<c01a9eed>] pgd_alloc [kernel] 0x7d (0xc1f6bed0)
> [<c010e13a>] mm_init [kernel] 0xaa (0xc1f6bf04)
> [<c010e417>] copy_mm [kernel] 0xc7 (0xc1f6bf18)
> [<c010ee66>] copy_process [kernel] 0x4d6 (0xc1f6bf3c)
> [<c010f64e>] do_fork [kernel] 0x4e (0xc1f6bf6c)
> [<c019ac37>] sys_fork [kernel] 0x37 (0xc1f6bfa4)
> 
> Code: f3 ab eb a7 8d b4 26 00 00 00 00 c1 e9 02 89 d7 f3 ab aa eb
> 
> Kernel panic: Fatal exception
> 
> -- 
> To use violence is to already be defeated.
>         -- Chinese proverb
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users



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

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