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

[Xen-bugs] [Bug 1579] New: xen 3.4.2 domU BUG: unable to handle kernel p

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1579] New: xen 3.4.2 domU BUG: unable to handle kernel paging request at virtual address
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 7 Feb 2010 13:39:10 -0800
Delivery-date: Sun, 07 Feb 2010 13:39:16 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1579

           Summary: xen 3.4.2 domU BUG: unable to handle kernel paging
                    request at virtual address
           Product: Xen
           Version: unspecified
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: 2.6.18 domU
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: jwestfall@xxxxxxxxxxxxxxxx
                CC: jwestfall@xxxxxxxxxxxxxxxx


Hi

I have a reproducible kernel BUG() in a stock xen 3.4.2 domU kernel.

I am running Xen 3.4.2 64bit hypervisor, 32bit dom0 with the bug occurring on
32bit 2.6.18.8 domU kernels.  I have tried using a combined dom0/U and
domU-only kernels, both have the issue.  The issue been test and confirmed on
multiple different servers.

Once the BUG() has triggered the domU becomes unstable, it appears anything
that attempts to access process info on the process that triggered it gets
stuck, ie ps auwwx, will stall.

domU is configured with 2gig ram, 2xVCPU with ubuntu dapper userspace.  The
trigger is restarting opennms (java version 1.5.0_22) over and over.  It will
trigger the BUG() within a day.

Here are some of the BUG() backtraces.

BUG: unable to handle kernel paging request at virtual address 6baaaaa0
 printing eip:
c0152152
2b4dd000 -> *pde = 00000004:744b7027
2bb64000 -> *pme = 00000000:00000000
Oops: 0000 [#1]
SMP
Modules linked in: xt_tcpudp iptable_filter ip_tables x_tables
CPU:    1
EIP:    0061:[<c0152152>]    Not tainted VLI
EFLAGS: 00010286   (2.6.18.8-xenU #2)
EIP is at page_address+0x12/0xb0
eax: 6baaaaa0   ebx: 6baaaaa0   ecx: 55555000   edx: 00000555
esi: 74405067   edi: 00000000   ebp: ebb8de34   esp: ebb8de24
ds: 007b   es: 007b   ss: 0069
Process java (pid: 6120, ti=ebb8c000 task=eb5f5550 task.ti=ebb8c000)
Stack: 00000000 00000555 74405067 00000000 ebb8df1c c01556c8 6baaaaa0 ec018c7c
       857ff000 00000001 00000001 00000000 ebb8df08 00000004 c1579f6c ebb8dfbc
       ebb8de8c c044e200 c0416068 00000000 00000000 00000000 00000000 00000000
Call Trace:
 [<c0105d5b>] show_stack_log_lvl+0xab/0xd0
 [<c0105fb6>] show_registers+0x1b6/0x240
 [<c0106171>] die+0x131/0x2f0
 [<c01152a8>] do_page_fault+0x688/0xcb2
 [<c010588f>] error_code+0x2b/0x30
 [<c01556c8>] __handle_mm_fault+0x108/0x1540
 [<c0115397>] do_page_fault+0x777/0xcb2
 [<c010588f>] error_code+0x2b/0x30
Code: e9 cf fe ff ff 0f 0b 3b 02 10 14 3a c0 e9 e2 fe ff ff 8d b4 26 00 00 00
00 55 89 e5 83 ec 10 89 5d f4 8b 5d 08 89 75 f8 89 7d fc <8b> 03 c1 e8 1e 8b 14
85 94 29 42 c0 8b 82 2c 03 00 00 05 c0 09
EIP: [<c0152152>] page_address+0x12/0xb0 SS:ESP 0069:ebb8de24

BUG: unable to handle kernel paging request at virtual address bffffd24
printing eip:
c016426b
29ef9000 -> *pde = 00000004:c83f9027
29fb1000 -> *pme = 00000000:00000000
Oops: 0000 [#1]
SMP 
Modules linked in: ipv6 ipt_REJECT ipt_LOG xt_limit xt_state ip_conntrack
nfnetlink xt_tcpudp iptable_filter ip_tables x_tables ext3 jbd dm_mirror
dm_snapshot dm_m
od processor
CPU:    1
EIP:    0061:[<c016426b>]    Tainted: GF     VLI
EFLAGS: 00010282   (2.6.18.8-xen #1) 
EIP is at __handle_mm_fault+0x11b/0x15a0
eax: bffff000   ebx: 00000fff   ecx: 00000d20   edx: c0369180
esi: c8b6d067   edi: 00000000   ebp: bffffd20   esp: e9ba7e68
ds: 007b   es: 007b   ss: 0069
Process java (pid: 10300, ti=e9ba6000 task=e988b100 task.ti=e9ba6000)
Stack: 08077478 e9ba7e78 c013ec70 00000001 08077000 e9cafc80 00000478 08077400 
c041bf80 080a8318 00000001 aeba4000 ecfd1334 e9cafc80 00000000 00000000 
00000000 00000000 00000000 00000000 00000d20 e9fb1ba8 a8275025 00000004 
Call Trace:
[<c013ec70>] futex_wake+0xb0/0xd0
[<c0104e7c>] do_notify_resume+0x8c/0x780
[<c0118e4a>] do_page_fault+0x78a/0xccb
[<c011e9d0>] default_wake_function+0x0/0x10
[<c014068d>] sys_futex+0x8d/0x110
[<c01186c0>] do_page_fault+0x0/0xccb
[<c0105b7b>] error_code+0x2b/0x30
Code: 85 4b 01 00 00 03 05 90 92 44 c0 e8 b0 ca ff ff 8b 4c 24 2c c1 e9 09 81
e1 f8 0f 00 00 89 cd 01 c5 89 4c 24 50 0f 84 08 02 00 00 <8b> 5d 04 89 9c 24 98
00 00 00 8b 75 00 89 b4 24 94 00 00 00 f6 
EIP: [<c016426b>] __handle_mm_fault+0x11b/0x15a0 SS:ESP 0069:e9ba7e68

BUG: unable to handle kernel paging request at virtual address bffff004
printing eip:
c016426b
2acea000 -> *pde = 00000004:a64a9027
2b789000 -> *pme = 00000000:00000000
Oops: 0000 [#1]
SMP 
Modules linked in: ipv6 ipt_REJECT ipt_LOG xt_limit xt_state ip_conntrack
nfnetlink xt_tcpudp iptable_filter ip_tables x_tables ext3 jbd dm_mirror
dm_snapshot dm_m
od processor
CPU:    0
EIP:    0061:[<c016426b>]    Tainted: GF     VLI
EFLAGS: 00010286   (2.6.18.8-xen #1) 
EIP is at __handle_mm_fault+0x11b/0x15a0
eax: bffff000   ebx: 00000fff   ecx: 00000000   edx: c0369180
esi: bcd31067   edi: 00000000   ebp: bffff000   esp: eac2fe68
ds: 007b   es: 007b   ss: 0069
Process java (pid: 349, ti=eac2e000 task=eacf8f50 task.ti=eac2e000)
Stack: 000048c7 eacf8f50 eac2fe70 eac2fe70 eac2ffbc 00000004 eac2ffbc 00000000 
c041bf80 c1b8bcec 00000001 83200dd0 eb99b9bc eb05e900 00000000 00000000 
00000000 00000000 00000000 00000000 00000000 eb7890c8 c8939025 00000004 
Call Trace:
[<c0118e4a>] do_page_fault+0x78a/0xccb
[<c012b4fa>] tasklet_action+0x7a/0x130
[<c012aec4>] __do_softirq+0x94/0x130
[<c01186c0>] do_page_fault+0x0/0xccb
[<c0105b7b>] error_code+0x2b/0x30
Code: 85 4b 01 00 00 03 05 90 92 44 c0 e8 b0 ca ff ff 8b 4c 24 2c c1 e9 09 81
e1 f8 0f 00 00 89 cd 01 c5 89 4c 24 50 0f 84 08 02 00 00 <8b> 5d 04 89 9c 24 98
00 00 00 8b 75 00 89 b4 24 94 00 00 00 f6 
EIP: [<c016426b>] __handle_mm_fault+0x11b/0x15a0 SS:ESP 0069:eac2fe68

thanks
jim


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

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