WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] kernel BUG at drivers/xen/balloon.c:528!

To: Łukasz Oleś <lukaszoles@xxxxxxxxx>
Subject: Re: [Xen-devel] kernel BUG at drivers/xen/balloon.c:528!
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Tue, 20 Jul 2010 15:47:23 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 20 Jul 2010 07:47:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTilEkTYAkIhdOu6BkvRdZWMOGC8cD-mwGncb-y-Q@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimEw0zMg2rShy22t1_52f8IFe0dF4vbVZsLV436@xxxxxxxxxxxxxx> <4C3F46B3.9000702@xxxxxxxx> <alpine.DEB.2.00.1007151840070.21432@kaball-desktop> <AANLkTinA2oRdZH6e0_XVQwuC6dmZ6pbnv-MIuF21musC@xxxxxxxxxxxxxx> <alpine.DEB.2.00.1007161640150.21432@kaball-desktop> <AANLkTimqPURWH5nDebTEJ9XP4OCiO1yio1jPcKEKPhTt@xxxxxxxxxxxxxx> <alpine.DEB.2.00.1007191516160.21432@kaball-desktop> <AANLkTimBhPCLthJPi7Uq1jXZbn6YblqCWDy5d19P1vZa@xxxxxxxxxxxxxx> <alpine.DEB.2.00.1007191733250.21432@kaball-desktop> <AANLkTilEkTYAkIhdOu6BkvRdZWMOGC8cD-mwGncb-y-Q@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Tue, 20 Jul 2010, Łukasz Oleś wrote:
> > diff --git a/arch/x86/xen/platform-pci-unplug.c 
> > b/arch/x86/xen/platform-pci-unplug.c
> > index 2f7f3fb..4513202 100644
> > --- a/arch/x86/xen/platform-pci-unplug.c
> > +++ b/arch/x86/xen/platform-pci-unplug.c
> > @@ -98,8 +98,10 @@ void __init xen_unplug_emulated_devices(void)
> >                }
> >        }
> >        /* Now unplug the emulated devices */
> > -       if (!(xen_emul_unplug & XEN_UNPLUG_IGNORE))
> > +       if (!(xen_emul_unplug & XEN_UNPLUG_IGNORE)) {
> >                outw(xen_emul_unplug, XEN_IOPORT_UNPLUG);
> > +               printk("DEBUG unplug %x\n", xen_emul_unplug);
> > +       }
> >        xen_platform_pci_unplug = xen_emul_unplug;
> >  }
> >
> 
> dmesg output from busybox and qemu log are in attachment
> 
 
As you can see from the logs xen_emul_unplug was 0 and that shouldn't
cause any unplug at all in qemu.
I see that you have a complicated set of kernel command line options,
what guest are you using? Is there a simple way for me to reproduce
your problem?
I tried to remove the platform pci driver from my kernel's config but I
am still able to mount the emulated disk without any issues.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel