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-users] Segfault at reboot caused by pciback.hide

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Segfault at reboot caused by pciback.hide
From: Gabor HALASZ <halasz.g@xxxxxxxxxxx>
Date: Fri, 08 Sep 2006 14:55:54 +0200
Delivery-date: Fri, 08 Sep 2006 05:57:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Debian Thunderbird 1.0.7 (X11/20051017)

I created a dedicated driver domain on my opteron machine (xen-3.0.2-3, changeset: 9762:1e225598ce82,, Debian Sid), and I discovered an interesting segfault at the last step of reboot: when the kernel flush out the md devices (raid1) the kernel prints the stack dump and reboot immidietly. After rebooting, the state of first md deveice is clean, but the second md device is dirty and starts the remirror procedure. The halt procedure stops cleanly the machine (the halt command or acpi button event). The reboot works correctly without the pciback.hide parameter. Any idea?!


Gabor HALASZ <halasz.g@xxxxxxxxxxx>

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Segfault at reboot caused by pciback.hide, Gabor HALASZ <=