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/
Home Products Support Community News


[Xen-devel] Oops when loading xen_platform_pci module in HVM domain on C

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Oops when loading xen_platform_pci module in HVM domain on CS 11429
From: Steve Dobbelstein <steved@xxxxxxxxxx>
Date: Tue, 5 Sep 2006 19:56:00 -0500
Delivery-date: Tue, 05 Sep 2006 17:56:29 -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
I'm running 64-bit SLES 10 beta 10 (yes, we have to upgrade to the official
release) on a machine with four Xeon 7020s.  I got xen-unstable changeset
11429:66dd34f2f439 and built 64-bit uniprocessor kernels for dom0 and the
HVM domain (a baremetal kernel and its initrd).  The HVM domain
is also running SLES 10 beta 10.  I followed the instructions to build the
paravirtualized drivers for an HVM domain.  When I run "modprobe
xen_platform_pci" in the HVM domain I get a kernel oops.  Here is the
output in dmesg.

PCI: Found IRQ 10 for device 0000:00:03.0
Xen version 3.0.
Hypercall area is 1 pages (order 0 allocation)
Unable to handle kernel paging request at ffff81002aca5220 RIP:
PGD 8063 PUD 9063 PMD 800000002ac001e3 PTE 31e031e031e031e
Oops: 0011 [1]
Modules linked in: xen_platform_pci ext3 mbcache jbd edd processor lpfc
mptspi mptscsih mptbase ata_
piix libata
Pid: 4000, comm: modprobe Not tainted #1
RIP: 0010:[<ffff81002aca5220>] [<ffff81002aca5220>]
RSP: 0018:ffff8100265b5b60  EFLAGS: 00010282
RAX: ffff81002aca5220 RBX: 000000002aca5000 RCX: 0000000040000000
RDX: 0000000000000000 RSI: ffff8100265b5b68 RDI: 0000000000000006
RBP: ffff8100265b5b78 R08: ffff81002aca5000 R09: ffffffff7fffffff
R10: 00007f0000000000 R11: 0000000080000000 R12: ffff81002fea8000
R13: 00000000f3000000 R14: 000000000000c100 R15: 0000000000000001
FS:  00002b443d7726d0(0000) GS:ffffffff80533000(0000)
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffff81002aca5220 CR3: 0000000026f89000 CR4: 00000000000006e0
Process modprobe (pid: 4000, threadinfo ffff8100265b4000, task
Stack: ffffffff88086c5c ffff810000000000 ffffffff80146693 ffff8100265b5c08
       ffffffff88086635 0000000300000000 ffff8100265b5bb8 0000000000000000
       0000000000000100 0000000001000000
Call Trace: <ffffffff88086c5c>{:xen_platform_pci:setup_xen_features+40}
       <ffffffff8015efaa>{vfs_read+173} <ffffffff8010a8ba>{system_call+126}

Code: b8 11 00 00 00 0f 01 c1 c3 00 00 00 00 00 00 00 00 00 00 00
RIP [<ffff81002aca5220>] RSP <ffff8100265b5b60>
CR2: ffff81002aca5220

It is oopsing on line 25 in unmodified_drivers/linux-2.6
/platform-pci/features.c (which is a sym link to
if (HYPERVISOR_xen_version(XENVER_get_features, &fi) < 0)

Looks like something went wrong with the hypercall.  I crawled through the
code to see how the hypercall stubs are set up but got lost in the MSR
stuff.  I'll take a look at it again tomorrow.  Thought I should post it to
the list in case anyone else can reproduce the problem and either find a
fix or explain why it's a user error.

Let me know if you need more info on my setup.

Steve D.

Xen-devel mailing list

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