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 169] New: x86_64 - Unable to handle kernel paging reques

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 169] New: x86_64 - Unable to handle kernel paging request at ffff8000003e0000 RIP:
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 16 Aug 2005 20:54:23 +0000
Delivery-date: Tue, 16 Aug 2005 20:54:28 +0000
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/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
<ffffffff8015d16c>{unmap_vmas+1084}
X-Bugzilla-Reason: AssignedTo

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=169

           Summary: x86_64 - Unable to handle kernel paging request at
                    ffff8000003e0000 RIP:
                    <ffffffff8015d16c>{unmap_vmas+1084}
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: dbarrera@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx


This oops shows on dmesg on an x86_64 SLES 9 SP2 box. Dom0 and DomU both seem
unaffected by it, however. It seems somewhat similar in nature to Bugzilla #167,
but the trace is different.

There were no workloads running at the time the oops was produced.

Unable to handle kernel paging request at ffff8000003e0000 RIP:
<ffffffff8015d16c>{unmap_vmas+1084}
PGD 55555555067 BAD
Oops: 0000 [1]
CPU 0
Modules linked in: thermal processor fan button battery ac
Pid: 9830, comm: X Not tainted 2.6.12-xen0
RIP: e030:[<ffffffff8015d16c>] <ffffffff8015d16c>{unmap_vmas+1084}
RSP: e02b:ffff88000c45bdd8  EFLAGS: 00010206
RAX: 00000000000f8000 RBX: ffff880008ab7090 RCX: 00000000000f8000
RDX: 80000000f8000067 RSI: ffff800000000000 RDI: 03fffffffffff000
RBP: 00002aaaab612000 R08: 00002aaaab692000 R09: ffff88000c45bec8
R10: 0000000000000030 R11: ffffffffff577000 R12: ffff880017ee71f8
R13: 0000000000000000 R14: ffff880017eb4ad8 R15: 00002aaaab692000
FS:  00002aaaab35e4c0(0000) GS:ffffffff8058b300(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process X (pid: 9830, threadinfo ffff88000c45a000, task ffff88000f74eb10)
Stack: 00002aaaab691fff 00002aaaab691fff 00002aaaab691fff 00002aaaab692000
       ffff880017762550 00002aaaab692000 ffff88000210e2a8 0000000000000000
       00002aaaab692000 ffffffff80541d00
Call Trace:<ffffffff80161083>{unmap_region+163} 
<ffffffff80161fa5>{do_munmap+389}
       <ffffffff80162088>{sys_munmap+72} <ffffffff80111f1d>{system_call+117}
       <ffffffff80111ea8>{system_call+0}

Code: 8b 14 86 48 8b 35 22 53 3f 00 48 39 f2 73 0f 48 8b 05 fe f4
RIP <ffffffff8015d16c>{unmap_vmas+1084} RSP <ffff88000c45bdd8>
CR2: ffff8000003e0000

-- 
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>
  • [Xen-bugs] [Bug 169] New: x86_64 - Unable to handle kernel paging request at ffff8000003e0000 RIP:, bugzilla-daemon <=