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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-devel] xen 4.0.2rc3/kernel 2.6.32.36: BUG: unable to handle ker

from [Konrad Rzeszutek Wilk] [Permanent Link][Original]
To: Gerd Jakobovitsch <gerd@xxxxxxxxxxx>
Subject: Re: [Xen-devel] xen 4.0.2rc3/kernel 2.6.32.36: BUG: unable to handle kernel paging request
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 18 Apr 2011 17:05:50 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 18 Apr 2011 14:07:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DA868A7.7020304@xxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4DA60F55.4000604@xxxxxxxxxxx> <20110414131543.GE5548@xxxxxxxxxxxx> <4DA85474.6060002@xxxxxxxxxxx> <20110415154449.GI32595@xxxxxxxxxxx> <4DA868A7.7020304@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14) 
On Fri, Apr 15, 2011 at 12:47:51PM -0300, Gerd Jakobovitsch wrote:
> Hello Pasi:
> 
> Yes, the kernel includes the last bugfix, and additionally the patch
> Daniel Stodden indicated yesterday:
> >>The BUG message at dmesg:

.. snip..
> >>
> >>[66007.135552] BUG: unable to handle kernel paging request at
> >>ffff8800004ca458
> >>[66007.135567] IP: [<ffffffff8100d4ae>] xen_set_pte+0x3e/0x4b
> >>[66007.135580] PGD 1002067 PUD 1006067 PMD 2d78067 PTE 100000004ca025
> >>[66007.135675] Oops: 0003 [#1] SMP DEBUG_PAGEALLOC

.. snip..
> >>[66007.135860] Call Trace:
> >>[66007.135868]  [<ffffffff81034740>] set_pte+0x17/0x1b
> >>[66007.135875]  [<ffffffff8103474d>] set_pte_atomic+0x9/0xb
> >>[66007.135882]  [<ffffffff81034e77>] __change_page_attr_set_clr+0x186/0x82d
> >>[66007.135936]  [<ffffffff8124f4a0>] ? _raw_spin_unlock+0xab/0xb1
> >>[66007.135951]  [<ffffffff8157641f>] ? _spin_unlock+0x26/0x2a
> >>[66007.135961]  [<ffffffff810e587d>] ? vm_unmap_aliases+0x151/0x160
> >>[66007.135969]  [<ffffffff81035695>] change_page_attr_set_clr+0x177/0x360
> >>[66007.135976]  [<ffffffff8103597a>] change_page_attr_set+0x27/0x29
> >>[66007.135983]  [<ffffffff810348e2>] ? pte_flags+0x9/0x18
> >>[66007.135990]  [<ffffffff81035c01>] do_pageattr_test+0x285/0x4b1
> >>[66007.135998]  [<ffffffff8103597c>] ? do_pageattr_test+0x0/0x4b1
> >>[66007.136097]  [<ffffffff8106a9c3>] kthread+0x69/0x71
> >>[66007.136105]  [<ffffffff81013daa>] child_rip+0xa/0x20
> >>[66007.136112]  [<ffffffff81012ee6>] ? int_ret_from_sys_call+0x7/0x1b
> >>[66007.136119]  [<ffffffff81013726>] ? retint_restore_args+0x5/0x6
> >>[66007.136127]  [<ffffffff81013da0>] ? child_rip+0x0/0x20

.. snip..
> >>(XEN) HVM43: Booting from 0000:7c00
> >>(XEN) HVM44: Press F12 for boot menu.
> >>(XEN) HVM44:
> >>(XEN) HVM44: Booting from Hard Disk...
> >>(XEN) HVM44: Booting from 0000:7c00
> >>(XEN) HVM44: int13_harddisk: function 42. LBA out of range
> >>(XEN) stdvga.c:151:d43 leaving stdvga
> >>(XEN) stdvga.c:147:d43 entering stdvga and caching modes
> >>(XEN) irq.c:243: Dom43 PCI link 0 changed 5 ->  0
> >>(XEN) irq.c:243: Dom43 PCI link 1 changed 10 ->  0
> >>(XEN) irq.c:243: Dom43 PCI link 2 changed 11 ->  0
> >>(XEN) irq.c:243: Dom43 PCI link 3 changed 5 ->  0
> >>(XEN) stdvga.c:151:d43 leaving stdvga
> >>(XEN) stdvga.c:151:d42 leaving stdvga
> >>(XEN) mm.c:3617:d0 PTE entry 81244b for address ffff88007caa0000 doesn't 
> >>match frame 621c4b
> >>(XEN) mm.c:3617:d0 PTE entry 812bed for address ffff88007caa1000 doesn't 
> >>match frame 6217ed
> >>(XEN) mm.c:3617:d0 PTE entry 812426 for address ffff88007caa2000 doesn't 
> >>match frame 621c26
> >>(XEN) mm.c:3617:d0 PTE entry 812590 for address ffff88007caa3000 doesn't 
> >>match frame 621d90
> >>(XEN) mm.c:3617:d0 PTE entry 812591 for address ffff88007caa4000 doesn't 
> >>match frame 621d91
> >>(XEN) mm.c:3617:d0 PTE entry 812492 for address ffff88007caa5000 doesn't 
> >>match frame 621c92
> >>(XEN) mm.c:3617:d0 PTE entry 812493 for address ffff88007caa6000 doesn't 
> >>match frame 621c93
> >>(XEN) mm.c:3617:d0 PTE entry 8124ca for address ffff88007caa7000 doesn't 
> >>match frame 621cca
> >>(XEN) mm.c:3617:d0 PTE entry 8124cb for address ffff88007caa8000 doesn't 
> >>match frame 621ccb
> >>(XEN) mm.c:3617:d0 PTE entry 80e8b0 for address ffff88007caa9000 doesn't 
> >>match frame 6258b0
> >>(XEN) mm.c:3617:d0 PTE entry 80e8b1 for address ffff88007caaa000 doesn't 
> >>match frame 6258b1
> >>(XEN) mm.c:3617:d0 PTE entry 803fe2 for address ffff88007caab000 doesn't 
> >>match frame 5cfde2
> >>(XEN) mm.c:3617:d0 PTE entry 80b3fd for address ffff88007ca99000 doesn't 
> >>match frame 46b1fd
> >>(XEN) mm.c:3617:d0 PTE entry 80b3fe for address ffff88007ca9a000 doesn't 
> >>match frame 46b1fe
> >>(XEN) mm.c:3617:d0 PTE entry 80ac10 for address ffff88007ca9b000 doesn't 
> >>match frame 46b610
> >>(XEN) mm.c:3617:d0 PTE entry 80c01e for address ffff88007ca9c000 doesn't 
> >>match frame 46a21e
> >>(XEN) mm.c:3617:d0 PTE entry 80ab16 for address ffff88007ca9d000 doesn't 
> >>match frame 46b916
> >>(XEN) mm.c:3617:d0 PTE entry 80b0f6 for address ffff88007ca9e000 doesn't 
> >>match frame 46b2f6
> >>(XEN) mm.c:3617:d0 PTE entry 809c8c for address ffff88007ca9f000 doesn't 
> >>match frame 46c68c
> >>(XEN) mm.c:3617:d0 PTE entry 8017e0 for address ffff88007cb9f000 doesn't 
> >>match frame 5b19e0
> >>(XEN) mm.c:3617:d0 PTE entry 8017e1 for address ffff88007cba0000 doesn't 
> >>match frame 5b19e1
> >>(XEN) mm.c:3617:d0 PTE entry 801fc4 for address ffff88007cba1000 doesn't 
> >>match frame 5b11c4
> >>(XEN) mm.c:3617:d0 PTE entry 801fc5 for address ffff88007cba2000 doesn't 
> >>match frame 5b11c5
> >>(XEN) mm.c:3617:d0 PTE entry 801f2a for address ffff88007cba3000 doesn't 
> >>match frame 5b112a
> >>(XEN) mm.c:3617:d0 PTE entry 801f2b for address ffff88007cba4000 doesn't 
> >>match frame 5b112b
> >>(XEN) mm.c:3617:d0 PTE entry 801ee8 for address ffff88007cba5000 doesn't 
> >>match frame 5b10e8
> >>(XEN) mm.c:3617:d0 PTE entry 801ee9 for address ffff88007cba6000 doesn't 
> >>match frame 5b10e9
> >>(XEN) mm.c:3617:d0 PTE entry 803fde for address ffff88007cba7000 doesn't 
> >>match frame 5af1de
> >>(XEN) mm.c:3617:d0 PTE entry 8120ec for address ffff88007cb9e000 doesn't 
> >>match frame 9660ec
> >>(XEN) mm.c:3617:d0 PTE entry 8120ed for address ffff88007cb9f000 doesn't 
> >>match frame 9660ed
> >>(XEN) mm.c:3617:d0 PTE entry 810e0a for address ffff88007cba0000 doesn't 
> >>match frame 96720a
> >>(XEN) mm.c:3617:d0 PTE entry 810e0b for address ffff88007cba1000 doesn't 
> >>match frame 96720b
> >>(XEN) mm.c:3617:d0 PTE entry 81080e for address ffff88007cba2000 doesn't 
> >>match frame 96780e
> >>(XEN) mm.c:3617:d0 PTE entry 81080f for address ffff88007cba3000 doesn't 
> >>match frame 96780f
> >>(XEN) mm.c:3617:d0 PTE entry 80ef3e for address ffff88007cba4000 doesn't 
> >>match frame 96933e
> >>(XEN) mm.c:3617:d0 PTE entry 802fd7 for address ffff88007c433000 doesn't 
> >>match frame 2111d7
> >>(XEN) mm.c:3617:d0 PTE entry 805131 for address ffff88007c434000 doesn't 
> >>match frame 20ef31
> >>(XEN) mm.c:3617:d0 PTE entry 80c1ea for address ffff88007c435000 doesn't 
> >>match frame 207fea
> >>(XEN) mm.c:3617:d0 PTE entry 814ae9 for address ffff88007c9b0000 doesn't 
> >>match frame 8866e9
> >>(XEN) mm.c:3617:d0 PTE entry 8113b9 for address ffff88007ca20000 doesn't 
> >>match frame 9277b9
> >>(XEN) mm.c:3617:d0 PTE entry 808ab2 for address ffff88007ca21000 doesn't 
> >>match frame 92feb2
> >>(XEN) mm.c:3617:d0 PTE entry 803bb3 for address ffff88007ca22000 doesn't 
> >>match frame 934fb3
> >>(XEN) mm.c:3617:d0 PTE entry 814747 for address ffff88007ca23000 doesn't 
> >>match frame 924347
> >>(XEN) mm.c:3617:d0 PTE entry 819873 for address ffff88007ca24000 doesn't 
> >>match frame 91f073
> >>(XEN) mm.c:3617:d0 PTE entry 80302c for address ffff88007ca25000 doesn't 
> >>match frame 93582c
> >>(XEN) mm.c:3617:d0 PTE entry 81b75c for address ffff88007ca26000 doesn't 
> >>match frame 91d35c
> >>(XEN) mm.c:3617:d0 PTE entry c5fd0b for address ffff88007ca86000 doesn't 
> >>match frame 95830b
> >>(XEN) mm.c:3617:d0 PTE entry 81a093 for address ffff88007ca87000 doesn't 
> >>match frame 9bde93
> >>(XEN) mm.c:3617:d0 PTE entry 815f11 for address ffff88007ca88000 doesn't 
> >>match frame 942111
> >>(XEN) mm.c:3617:d0 PTE entry 815bc5 for address ffff88007ca89000 doesn't 
> >>match frame 9425c5
> >>(XEN) mm.c:3617:d0 PTE entry 816875 for address ffff88007cb9b000 doesn't 
> >>match frame 59c675
> >>(XEN) mm.c:3617:d0 PTE entry 8158a8 for address ffff88007cb9c000 doesn't 
> >>match frame 59d6a8
> >>(XEN) mm.c:3617:d0 PTE entry 82fa1c for address ffff88007c926000 doesn't 
> >>match frame 5e321c
> >>(XEN) mm.c:3617:d0 PTE entry 82655e for address ffff88007c927000 doesn't 
> >>match frame 5ec95e
> >>(XEN) mm.c:3617:d0 PTE entry c5ce72 for address ffff88007c926000 doesn't 
> >>match frame 95b072
> >>(XEN) mm.c:3617:d0 PTE entry c5cea9 for address ffff88007c927000 doesn't 
> >>match frame 95b0a9
> >>(XEN) mm.c:2399:d0 Bad type (saw 1c00000000000002 != exp 7000000000000000) 
> >>for mfn 800569 (pfn 4569)
> >>(XEN) mm.c:878:d0 Error getting mfn 800569 (pfn 4569) from L1 entry 
> >>8010000800569267 for l1e_owner=0, pg_owner=0
> >>(XEN) mm.c:4664:d0 ptwr_emulate: could not get_page_from_l1e()
> >>(XEN) mm.c:3617:d0 PTE entry 80e284 for address ffff88007ca89000 doesn't 
> >>match frame 468084
> >>(XEN) mm.c:3617:d0 PTE entry 817918 for address ffff88007ca8a000 doesn't 
> >>match frame 47f118
> >>(XEN) common.c:3722:d0 tracking VRAM f0000 - f0160
> >>(XEN) common.c:3722:d0 tracking VRAM f0000 - f0160

So to reproduce this, what should I be doing? Can you give me a rough idea of 
what
your guests are doing, how big the NFS files are, etc?


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-devel] on starting HVM-domU whole system freezes with "soft lockup - CPU X stuck for XXs! [qemu-dm:...]" [xen 4.0, xen 4.1], Konrad Rzeszutek Wilk
Next by Date:  Re: [Xen-devel] on starting HVM-domU whole system freezes with "soft lockup - CPU X stuck for XXs! [qemu-dm:...]" [xen 4.0, xen 4.1], MadLoisae@xxxxxxx
Previous by Thread:  Re: [Xen-devel] xen 4.0.2rc3/kernel 2.6.32.36: BUG: unable to handle kernel paging request, Gerd Jakobovitsch
Next by Thread:  [Xen-devel] [xen-unstable test] 6830: regressions - FAIL, xen . org
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy