On Fri, Dec 12, 2008 at 10:57 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Fri, Dec 12, 2008 at 09:12:03AM +0000, Andrew Lyon wrote:
>> On Thu, Dec 11, 2008 at 10:27 PM, Todd Deshane <deshantm@xxxxxxxxx> wrote:
>> > On Thu, Dec 11, 2008 at 5:24 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
>> > wrote:
>> >> Todd Deshane wrote:
>> >>>
>> >>> Just pulled the latest and re-compiled.
>>
>> I did the same at exactly 09:00 12/12/2008 GMT, compiled a new kernel
>> and tried it on my Optiplex 755 test system, I disabled MSI in the
>> kernel config and added pci=nomsi to be absolutely sure, it fails to
>> boot because the HD is not detected:
>>
>
> <snip>
>
>>
>> Driver 'sd' needs updating - please use bus_type methods
>> Driver 'sr' needs updating - please use bus_type methods
>
I get the same messages with 2.6.27 Xen kernel (vanilla patched with
openSUSE xen patches)
> I wonder if these are related.. ?
>
>> ahci 0000:00:1f.2: PCI INT C -> GSI 18 (level, low) -> IRQ 31
>> xen: PCI device 0000:00:1f.2 pin 3 -> irq 31
>> ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x27 impl SATA mode
>> ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pmp pio slum part ems
>> scsi0 : ahci
>> scsi1 : ahci
>> scsi2 : ahci
>> scsi3 : ahci
>> scsi4 : ahci
>> scsi5 : ahci
>> ata1: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970100 irq 31
>> ata2: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970180 irq 31
>> ata3: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970200 irq 31
>> ata4: DUMMY
>> ata5: DUMMY
>> ata6: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970380 irq 31
>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata1.00: qc timeout (cmd 0xec)
>> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata1.00: qc timeout (cmd 0xec)
>> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata1.00: qc timeout (cmd 0xec)
>> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata2.00: ATAPI: HL-DT-ST DVD+/-RW GSA-H73N, B103, max UDMA/100
>> ata2.00: configured for UDMA/100
>> ata3: SATA link down (SStatus 4 SControl 300)
>> ata6: SATA link down (SStatus 4 SControl 300)
>> scsi 1:0:0:0: CD-ROM HL-DT-ST DVD+-RW GSA-H73N B103 PQ: 0 ANSI: 5
>> sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
>> Uniform CD-ROM driver Revision: 3.20
>> sr 1:0:0:0: Attached scsi generic sg0 type 5
>
> Ok, so AHCI controller driver is loaded, but the disks are not detected..
> "failed to IDENTIFY".
>
> Wonder what's causing that..
With 2.6.27 they are detected, and I notice the controller gets a different irq:
dmesg | grep -E "ata|scsi|ahci"
PERCPU: Allocating 42976 bytes of per cpu data
Memory: 3626568k/3847580k available (3374k kernel code, 212420k
reserved, 1712k data, 288k init)
libata version 3.00 loaded.
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x27 impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pmp pio slum part ems
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 irq_stat 0x00000040, connection status changed irq 18
ata2: SATA max UDMA/133 irq_stat 0x00000040, connection status changed irq 18
ata3: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970200 irq 18
ata4: DUMMY
ata5: DUMMY
ata6: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970380 irq 18
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-6: WDC WD360GD-00FLA2, 31.08F31, max UDMA/133
ata1.00: 72303840 sectors, multi 0: LBA48
ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATAPI: HL-DT-ST DVD+/-RW GSA-H73N, B103, max UDMA/100
ata2.00: configured for UDMA/100
ata3: SATA link down (SStatus 4 SControl 300)
ata6: SATA link down (SStatus 4 SControl 300)
scsi 0:0:0:0: Direct-Access ATA WDC WD360GD-00FL 31.0 PQ: 0 ANSI: 5
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: CD-ROM HL-DT-ST DVD+-RW GSA-H73N B103 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
sr 1:0:0:0: Attached scsi CD-ROM sr0
sr 1:0:0:0: Attached scsi generic sg1 type 5
scsi6 : SCSI emulation for USB Mass Storage devices
EXT3-fs: mounted filesystem with ordered data mode.
Write protecting the kernel read-only data: 4772k
scsi 6:0:0:0: Direct-Access TEAC USB HS-CF Card 4.08 PQ: 0 ANSI: 0
sd 6:0:0:0: Attached scsi generic sg2 type 0
>
>> md: Waiting for all devices to be available before autodetect
>> md: If you don't use raid, use raid=noautodetect
>> md: Autodetecting RAID arrays.
>> md: Scanned 0 and added 0 devices.
>> md: autorun ...
>> md: ... autorun DONE.
>
> No disks to scan here.. because none were detected.
>
>
>> Root-NFS: No NFS server available, giving up.
>> VFS: Unable to mount root fs via NFS, trying floppy.
>> VFS: Cannot open root device "sda2" or unknown-block(2,0)
>> Please append a correct "root=" boot option; here are the available
>> partitions:
>> 0b00 1048575 sr0 driver: sr
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(2,0)
>
> Yep, can't find root device because no disks were detected..
>
> -- Pasi
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home