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-bugs] [Bug 1279] New: Xen HV crashes while doing dom0 S3

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1279] New: Xen HV crashes while doing dom0 S3
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 20 Jun 2008 06:26:47 -0700
Delivery-date: Fri, 20 Jun 2008 06:27:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Xen HV crashes while doing dom0 S3
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx

Service OS (ia32/ia32e/IA64): ia32 ia32e
Guest OS (ia32/ia32e/IA64): 
Change Set: 17879
Hardware: Stoakley/Clovertown

Bug detailed description:
Firstly we create one HVM guest with PCIE NIC assgined(Xen & guest MSI
enabled), and destroy it. then let dom0 do S3, it will cause Xen hypervisor
crash. Xen serial log is pasted below.

But in other conditions, dom0 S3 can succeed
a). do dom0 S3 just after dom0 booting up without guest created.
b). do dom0 S3 after creating one HVM guest without NIC assgined
c). do dom0 S3 after creating one HVM guest with PCIE NIC assgined(MSI disabled
in guest)

Reproduce steps:
1) create one HVM guest with PCIE NIC assgined(guest MSI enabled)
2) destory this guest
3) do S3

Current result:

Expected result:

Basic root-causing log:
Freezing cpus ...
CPU1 is down
CPU2 is down
CPU3 is down
CPU4 is down
CPU5 is down
CPU6 is down
CPU7 is down
Stopping tasks:
(XEN) <PM> Preparing system for ACPI S3 state.
(XEN) Freezing cpus ...
(XEN) Prepare to bring CPU1 down...
(XEN) ----[ Xen-3.3-unstable  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    e008:[<ffff828c8013a1e7>] read_msi_msg+0x37/0x170
(XEN) RFLAGS: 0000000000010002   CONTEXT: hypervisor
(XEN) rax: ffff828c8025d100   rbx: 0000000000000000   rcx: 0000000000000000
(XEN) rdx: 0000000000000008   rsi: ffff8300cf0cfde0   rdi: 0000000000003080
(XEN) rbp: ffff8300cf0cfde0   rsp: ffff8300cf0cfda0   r8:  0000000000000020
(XEN) r9:  0000000000000000   r10: 0000000000000001   r11: ffff828c801ee120
(XEN) r12: 0000000000000061   r13: ffff828c8025d100   r14: 0000000000000020
(XEN) r15: ffff828c801d0588   cr0: 000000008005003b   cr4: 00000000000026b0
(XEN) cr3: 00000000cf03c000   cr2: 0000000000000000
(XEN) ds: 002b   es: 002b   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff8300cf0cfda0:
(XEN)    ffff828c80266f04 0000000000000008 0000000000000061 0000000000000061
(XEN)    ffff828c8025d100 0000000000000020 ffff828c801d0588 ffff828c8013a379
(XEN)    0000000000000000 0000000000000000 0000000000000061 0000000000000061
(XEN)    00000000000000fd ffff828c8013abee 0000000000000001 0000000000000020
(XEN)    0000000000000700 ffff828c801d0488 0000000000000020 ffff828c801492bf
(XEN)    ffff828c8013637a ffff828c801d0480 ffff828c801ee100 0000000000000001
(XEN)    00000000000000fd ffff828c801cd7e0 ffff8300cf0cff28 0000000000000003
(XEN)    ffff8300cf0cff28 ffff828c8024f800 ffff828c8024e800 ffff828c801ee100
(XEN)    0000000001c9c380 ffff828c80116dae 000000009177f0fd 0000000000000001
(XEN)    ffff8300cf0cff28 ffff828c80116ad0 000000000000e008 ffff8300cf0cff28
(XEN)    ffff828c801cd7e0 ffff828c801ec534 ffff828c8024e800 ffff828c801306d9
(XEN)    ffff8300cf0f4080 ffff828c801ee120 ffff8300cfdf8080 ffff8300cfdf8080
(XEN)    0000090a1cb97ca3 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000246
(XEN)    0000000000007ff0 00000000000036ed ffff880039be7bc0 0000000000000000
(XEN)    ffffffff8020630a 0000000000000000 0000000000000006 0000000000000002
(XEN)    0000010000000000 ffffffff8020630a 000000000000e033 0000000000000246
(XEN)    ffff88000632ff38 000000000000e02b 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000001 ffff8300cfdf8080
(XEN) Xen call trace:
(XEN)    [<ffff828c8013a1e7>] read_msi_msg+0x37/0x170
(XEN)    [<ffff828c8013a379>] set_msi_irq_affinity+0x59/0x90
(XEN)    [<ffff828c8013abee>] fixup_irqs+0xbe/0x120
(XEN)    [<ffff828c801492bf>] __cpu_disable+0x1df/0x220
(XEN)    [<ffff828c8013637a>] event_check_interrupt+0x2a/0x30
(XEN)    [<ffff828c80116dae>] stopmachine_softirq+0x5e/0x80
(XEN)    [<ffff828c80116ad0>] do_softirq+0x70/0x80
(XEN)    [<ffff828c801306d9>] idle_loop+0x99/0xa0
(XEN) Pagetable walk from 0000000000000000:
(XEN)  L4[0x000] = 000000022fdf7063 5555555555555555
(XEN)  L3[0x000] = 000000022fdf6063 5555555555555555
(XEN)  L2[0x000] = 000000022fdf5063 5555555555555555 
(XEN)  L1[0x000] = 0000000000000000 ffffffffffffffff
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) [error_code=0000]
(XEN) Faulting linear address: 0000000000000000
(XEN) ****************************************
(XEN) Reboot in five seconds...

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 1279] New: Xen HV crashes while doing dom0 S3, bugzilla-daemon <=