RE: [Xen-devel] SATA detect fails on ICH7 chipset / Dell PoweredgeSC430

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

This is a pretty odd failure, as everything seems to be going fine with
the ACPI configuration right up until the ata_piix probe failure.

The only thing I can suggest is to add some "printk(KERN_ALERT" tracing
to the init function of the driver and see where its failing...

My guess is that it fails for some other reason before it tries using
ACPI to plumb the interrupt. 

Thanks,
Ian  

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Chris Bainbridge
> Sent: 30 August 2005 13:04
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] SATA detect fails on ICH7 chipset / 
> Dell PoweredgeSC430
> 
> > Having the bootlog from a native build of 2.6.12.5 would be 
> useful to 
> > compare against the 2.6.12.5-xen0.
> 
> Attached.
> 
> > When running native linux, what driver is used for the SATA 
> controller?
> > Are you sure its actually compiled in to our -xen0 config?
> 
> The one in Config->SCSI->Sata->Intel PIIX/ICH SATA Support.  
> I have the AHCI driver builtin as well.
> 
> I'm sure the SATA support works. I've used the exact same 
> hypervisor and kernel images to boot on the sc420, and the 
> same driver works on the sc430 without Xen.
> 
> The difference seems to be that under sc430-xen we get:
> 
> ata_piix: probe of 0000:00:1f.2 failed with error -12
> 
> instead of (sc430 native):
> 
> ACPI: PCI Interrupt 0000:00:1f.2[C] -> GSI 20 (level, low) -> IRQ 20
> ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 20
> ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 20
> 
> or (sc420-xen):
> 
> ACPI: PCI Interrupt 0000:00:1f.2[C] -> GSI 20 (level, low) -> IRQ 20
> ahci(0000:00:1f.2) AHCI 0001.0000 32 slots 4 ports 1.5 Gbps 
> 0xf impl IDE mode
> ahci(0000:00:1f.2) flags: 64bit ncq pm led slum part
> 
> It seems the sc430-xen isn't doing something related to ACPI 
> that enables the hardware to be detected?
> 
> > Incidently, have you tried using the -xen kerenel plus modules that 
> > are in our -unstable install tar ball?  This is the kernel that 
> > end-users are intended to use: -xen0/-xenU are just for developers' 
> > convenience (fewer modules, faster to build).
> 
> I took the unstable tarball, patched the kernel with the
> patches/linux-2.6.12 diffs, and copied over the 
> linux-2.6-xen-sparse directory. After building it boots on 
> the sc420 so I don't think it's a problem with the build 
> stage, but I can try something else if it would help.
> 

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