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

[Xen-devel] RE: PAE dom0 is broken with the default config

To: "Kamble, Nitin A" <nitin.a.kamble@xxxxxxxxx>, <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] RE: PAE dom0 is broken with the default config
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Thu, 6 Apr 2006 11:50:09 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 06 Apr 2006 03:50:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZZBKscXIXfn2EaRpODaCPq3uVrJQABH1RgAAMIYRAAFItTMA==
Thread-topic: PAE dom0 is broken with the default config
>    I did rebuild the initrd for the new kernel/modules. The 
> system has sata disk. scsi driver is the same ata_piix, 
> libata. The same config is working fine for the non-PAE build. 
>    The VMX status report mail says PAE is fine, but they are 
> not using the default (linux-defconfig_xen_x86_32) config. 
> They are using the xen0 config for PAE testing. What config 
> do you use for your PAE testing?

The majority testing is done with the -xen kernel, which seems to boot
and run fine on all of our machines, including those with root fs on
SATA.

It might be worth comparing the scsi/acpi/pci etc options closely
between the two different configs, and try a 'binary' chop to see which
are important.

Thanks,
Ian
 
> In summary here is my observation
> PAE build with linux-defconfig_xen_x86_32 config:     dom0 does not
> boot
> PAE build with linux-defconfig_xen0_x86_32 config:    boots
> Non-PAE build with either config:                             boots
> 
> All of the above kernels need corresponding initrd to boot.
> 
> Thanks & Regards,
> Nitin
> --------------------------------------------------------------
> ----------
> -----------
> Open Source Technology Center, Intel Corp
> 
> >-----Original Message-----
> >From: Ian Pratt [mailto:m+Ian.Pratt@xxxxxxxxxxxx]
> >Sent: Wednesday, April 05, 2006 4:34 PM
> >To: Kamble, Nitin A; Keir.Fraser@xxxxxxxxxxxx
> >Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; ian.pratt@xxxxxxxxxxxx
> >Subject: RE: PAE dom0 is broken with the default config
> >
> >>   I built PAE Xen with the default config, and it is not 
> booting. Log 
> >> is bellow. If I replace the
> >> linux-defconfig_xen_x86_32 file with the
> >> linux-defconfig_xen0_x86_32 before building then dom0 is 
> able to boot 
> >> and see more than 4Gig memory. This looks like a dom0 
> kernel config 
> >> issue. Do you care PAE dom0 for 3.0.2 with the default config? Is 
> >> anybody working on this?
> >
> >This seems pretty unlikely to be a PAE issue -- we do quite 
> extensive 
> >testing.
> >
> >Are you sure you have the right initrd? Is the same scsi 
> driver being 
> >used as in the -xen0 case?
> >
> >Thanks,
> >Ian
> >
> >>
> >>
> >> IP route cache hash table entries: 262144 (order: 8, 1048576 bytes)
> >>
> >> TCP established hash table entries: 524288 (order: 10, 
> 4194304 bytes)
> >>
> >> TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
> >>
> >> TCP: Hash tables configured (established 524288 bind 65536)
> >>
> >> TCP reno registered
> >>
> >> NET: Registered protocol family 8
> >>
> >> NET: Registered protocol family 20
> >>
> >> Using IPI No-Shortcut mode
> >>
> >> Freeing unused kernel memory: 172k freed
> >>
> >> scsi_mod: no version for "struct_module" found: kernel tainted.
> >>
> >> SCSI subsystem initialized
> >>
> >> ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) 
> -> IRQ 17
> >>
> >> ata1: SATA max UDMA/133 cmd 0x0 ctl 0xC402 bmdma 0xBC00 irq 17
> >>
> >> ata2: SATA max UDMA/133 cmd 0x0 ctl 0xC002 bmdma 0xBC08 irq 17
> >>
> >> ata1: dev 0 ATA-6, max UDMA/133, 312581808 sectors: LBA48
> >>
> >> ata1: dev 0 configured for UDMA/133
> >>
> >> scsi0 : ata_piix
> >>
> >> ATA: abnormal status 0x7F on port 0xC087
> >>
> >> scsi1 : ata_piix
> >>
> >>   Vendor: ATA       Model: ST3160023AS       Rev: 3.00
> >>
> >>   Type:   Direct-Access                      ANSI SCSI revision: 05
> >>
> >> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> >>
> >> sda: Write Protect is off
> >>
> >> SCSI device sda: drive cache: write back
> >>
> >> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> >>
> >> sda: Write Protect is off
> >>
> >> SCSI device sda: drive cache: write back
> >>
> >>  sda: unknown partition table
> >>
> >> sd 0:0:0:0: Attached scsi disk sda
> >>
> >> Kernel panic - not syncing: Attempted to kill init!
> >>
> >>  (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> 

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