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 1757] Dom0 hangs after few hours when using pci passthro

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1757] Dom0 hangs after few hours when using pci passthrough
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 14 Apr 2011 08:39:20 -0700
Delivery-date: Thu, 14 Apr 2011 08:41:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1757-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
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

------- Comment #12 from konrad.wilk@xxxxxxxxxx  2011-04-14 08:39 -------
(In reply to comment #11)
> > You can use the Alt-SysRQ to figure out where in the Linux kernel it is 
> > stuck.
> > Or if it is stuck in the hypervisor.
> Magic Sysrq keys did always work (I saw the output in the console), even if
> 'Alt'+'PrintScrn/SysRq'+'q' didn't really reboot the system, I just saw the
> message in the console.

OK, can you use that when the dom0 is hung during shutdown then to see why it
can't turn itself off? One of the options is to print the stack trace (and
there is also a correspoding option with the Xen hypervisor).

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

Xen-bugs mailing list