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: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] kernel BUG at drivers/xen/balloon.c:528!
From: Łukasz Oleś <lukaszoles@xxxxxxxxx>
Date: Tue, 20 Jul 2010 10:02:04 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Jul 2010 01:03:22 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=wtKYTACYzoNool5kD0a5yaXxW6NB3m0ItCjbfBeMbeY=; b=AlOnAD17tYzBAZFSEbP+N3vi99c7cF/mUA99fNguzb3R9tJ5ZFszsMrMNXsBfcVcBv i9hHaZ1THvweH5ZorK5ST4f3oyRTO+/6A4nZmThfyvST3ityMGXYCvA3B9zwCsOUARu+ SE8s/TM0oma4aq3S56nSsN2CmguCQzMbcxtnI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=VrFiwo9QaBN8v5u8sIs8qDm1Sr8kP9LVsSYUKz6Ysfm89jTL86tN8SA/Jx40eC3iwp UtieS2OXsDPa3Wb5mV/uLevGcl+IJMk6eCuuv3XajCR85C73uyqq2o4/iNct7iaSNEWv +jKpTOPvLUhDSa5CypEdaokufv4zTX/5QnLys=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1007191733250.21432@kaball-desktop>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
W dniu 19 lipca 2010 18:39 użytkownik Stefano Stabellini
<stefano.stabellini@xxxxxxxxxxxxx> napisał:
> On Mon, 19 Jul 2010, Łukasz Oleś wrote:
>> W dniu 19 lipca 2010 16:19 użytkownik Stefano Stabellini
>> <stefano.stabellini@xxxxxxxxxxxxx> napisał:
>> > On Mon, 19 Jul 2010, Łukasz Oleś wrote:
>> >> >
>> >> > In any case you should enable CONFIG_XEN_PLATFORM_PCI in your kernel
>> >> > config, otherwise the pv frontends won't load properly and you are not
>> >> > going to have any benefits running a PV on HVM kernel.
>> >> >
>> >> > I am not sure why you cannot mount your root device, maybe you didn't
>> >> > specify the correct root= in your kernel command line options?
>> >>
>> >> It works fine on bare metal and  ESX. It looks like in initrd system
>> >> doesn't see any disks.
>> >>
>> >> When I enabled option CONFIG_XEN_PLATFORM_PCI I was finally able to
>> >> boot my sytem. Is this suposed to work in this way?
>> >>
>> > but you should be able
>> > to mount /dev/hd* just fine without CONFIG_XEN_PLATFORM_PCI.
>>
>> This one is not true on my system.
>>
>> If something in my initrd fails it launches  busybox then I can run
>> fdisk -l or cat /proc/partitions and they return nothing.  Whats more
>> intresting at the system start I can see:
>>
>> Probing IDE interface ide0...
>> hda: QEMU HARDDISK, ATA DISK drive
>> hdb: QEMU HARDDISK, ATA DISK drive
>> hda: host max PIO4 wanted PIO255(auto-tune) selected PIO2
>> hda: MWDMA2 mode selected
>> hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO2
>> hdb: MWDMA2 mode selected
>> Probing IDE interface ide1...
>> hdc: QEMU HARDDISK, ATA DISK drive
>> hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO2
>> hdc: MWDMA2 mode selected
>> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>> ide1 at 0x170-0x177,0x376 on irq 15
>> ide-cd driver 5.00
>>
>> but later disks disappear. Full log in earlier mail
>>
>
> Yes, I have seen that.
> I am not sure what is the cause of the problem because if you see
> those messages it means no unplug has been done so you should be able to
> access the emulated disks without any issues.
> Just to be sure, could you please add this patch to your kernel and tell
> me if it gets printed?
>
>
>
> 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

-- 
Łukasz Oleś

Attachment: qemu.log
Description: Text Data

Attachment: dmesg.log
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel