Package: xen-hypervisor-4.1-amd64 Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important I updated from xen-hypervisor-4.0-amd64 to xen-hypervisor-4.1-amd64 and the system did not boot anymore (Xen panic). A downgrade made the system work again. I cannot paste the boot error messages but the main message was: Xen BUG at pci_amd_iommu.c:33 The bug appears for Linux images 3.2.0.2 from squeeze and for 3.4-trunk and 3.5-trunk from experimental. Best Stephan PS: Furthermore note that on Linux 3.2.0.2, xen-hypervisor-4.0-amd64 floods the console/logs with powernow-k8 transition error messages, see * http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1789 * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373947 However, Linux image 3.5-trunk and xen-hypervisor-4.0-amd64 seem to work nicely.
Ian Campbell
2012-Aug-17 11:50 UTC
[Pkg-xen-devel] Bug#684661: Bug#684661: Xen panic on boot
On Sun, 2012-08-12 at 17:25 +0200, Stephan Beyer wrote:> Package: xen-hypervisor-4.1-amd64 > Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 > Severity: important > > I updated from xen-hypervisor-4.0-amd64 to xen-hypervisor-4.1-amd64 > and the system did not boot anymore (Xen panic). > A downgrade made the system work again. > I cannot paste the boot error messages but the main message was: > > Xen BUG at pci_amd_iommu.c:33The BUG is "BUG_ON ( bdf >= ivrs_bdf_entries );" and ivrs_bdf_entries has come from ACPI -- do you have the latest firmware in this machine? I'm afraid that without some more information (e.g. a stack trace) I think this is going to be pretty hard to track down. Can you either configure a serial console (http://wiki.xen.org/wiki/Xen_Serial_Console) or use the "noreboot" option on the hypervisor command line to capture a digital picture of the error. Thanks, Ian.
I'm also getting the same error. I don't have anything with serial ports, but hopefully this will be of some use. -------------- next part -------------- A non-text attachment was scrubbed... Name: IMG_20120903_165005.jpg Type: image/jpeg Size: 959138 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20120903/76aeaf88/attachment-0001.jpg>
Debian Bug Tracking System
2013-Feb-25 18:27 UTC
[Pkg-xen-devel] Bug#684661: marked as done (Xen panic on boot)
Your message dated Mon, 25 Feb 2013 19:22:57 +0100 with message-id <20130225182257.GA4379 at waldi.eu.org> and subject line Re: [Pkg-xen-devel] Bug#684661: Xen panic on boot has caused the Debian Bug report #684661, regarding Xen panic on boot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 684661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684661 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Stephan Beyer <s-beyer at gmx.net> Subject: Xen panic on boot Date: Sun, 12 Aug 2012 17:25:50 +0200 Size: 2500 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20130225/01309b52/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: Bastian Blank <waldi at debian.org> Subject: Re: [Pkg-xen-devel] Bug#684661: Xen panic on boot Date: Mon, 25 Feb 2013 19:22:57 +0100 Size: 2021 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20130225/01309b52/attachment-0001.mht>