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-users

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-users] ahci sata detection disparity between standalone and Dom0 ke

from [Tim Harig] [Permanent Link][Original]
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] ahci sata detection disparity between standalone and Dom0 kernels
From: Tim Harig <xenml@xxxxxxxxxx>
Date: Sat, 1 Mar 2008 04:00:25 -0600
Delivery-date: Sat, 01 Mar 2008 02:01:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.2i 
What would cause a difference in drive detection between a similarly
configured standalone kernel and a Dom0 kernel?

The system in question is an ASUS M2N-SLI motherboad with an AMD AthlonX2
3600 micropcoprocessor and 4GB RAM.  Xen and the kernel are both compiled
to use PAE.  The chipset works fine under the AHCI kernel driver while
running standalone.  SCSI support and the AHCI drivers are built directly
into the kernel.

The drives are enumerated as follows:

> $ cat /proc/scsi/scsi 
> Attached devices:
> Host: scsi2 Channel: 00 Id: 00 Lun: 00
>   Vendor: PHILIPS  Model: SPD6104P         Rev: NP02
>   Type:   CD-ROM                           ANSI SCSI revision: 05
> Host: scsi3 Channel: 00 Id: 00 Lun: 00
>   Vendor: ATA      Model: ST3250410AS      Rev: 3.AA
>   Type:   Direct-Access                    ANSI SCSI revision: 05
> Host: scsi4 Channel: 00 Id: 00 Lun: 00
>   Vendor: ATA      Model: ST3250410AS      Rev: 3.AA
>   Type:   Direct-Access                    ANSI SCSI revision: 05
> Host: scsi5 Channel: 00 Id: 00 Lun: 00
>   Vendor: ATA      Model: ST3250410AS      Rev: 3.AA
>   Type:   Direct-Access                    ANSI SCSI revision: 05

Driver detection under the normal boot sequence looks like:

> ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA
> mode
> ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
> ata1: SATA max UDMA/133 cmd 0xF8820100 ctl 0x0 bmdma 0x0 irq 18
> ata2: SATA max UDMA/133 cmd 0xF8820180 ctl 0x0 bmdma 0x0 irq 18
> scsi0 : ahci
> ata1: SATA link down (SStatus 0 SControl 300)
> scsi1 : ahci
> ata2: SATA link down (SStatus 0 SControl 300)
> ACPI: PCI Interrupt Link [APSI] enabled at IRQ 21
> ACPI: PCI Interrupt 0000:00:05.0[A] -> Link [APSI] -> GSI 21 (level, low)
> -> IRQ 19
> ata3: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xDC00 irq 19
> ata4: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xDC08 irq 19
> scsi2 : sata_nv
> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: ATAPI, max UDMA/100
> ata3.00: configured for UDMA/100
> scsi3 : sata_nv
> ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
> ata4.00: ata4: dev 0 multi count 1
> ata4.00: configured for UDMA/133
>   Vendor: PHILIPS   Model: SPD6104P          Rev: NP02
>   Type:   CD-ROM                             ANSI SCSI revision: 05
>   Vendor: ATA       Model: ST3250410AS       Rev: 3.AA
>   Type:   Direct-Access                      ANSI SCSI revision: 05
> ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 20
> ACPI: PCI Interrupt 0000:00:05.1[B] -> Link [APSJ] -> GSI 20 (level, low)
> -> IRQ 20
> ata5: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xC800 irq 20
> ata6: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xC808 irq 20
> scsi4 : sata_nv
> ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata5.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
> ata5.00: ata5: dev 0 multi count 1
> ata5.00: configured for UDMA/133
> scsi5 : sata_nv
> ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata6.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
> ata6.00: ata6: dev 0 multi count 1
> ata6.00: configured for UDMA/133
>   Vendor: ATA       Model: ST3250410AS       Rev: 3.AA
>   Type:   Direct-Access                      ANSI SCSI revision: 05
>   Vendor: ATA       Model: ST3250410AS       Rev: 3.AA
>   Type:   Direct-Access                      ANSI SCSI revision: 05
> ACPI: PCI Interrupt Link [ASA2] enabled at IRQ 23
> ACPI: PCI Interrupt 0000:00:05.2[C] -> Link [ASA2] -> GSI 23 (level, low)
> -> IRQ 16
> ata7: SATA max UDMA/133 cmd 0xC400 ctl 0xC002 bmdma 0xB400 irq 16
> ata8: SATA max UDMA/133 cmd 0xBC00 ctl 0xB802 bmdma 0xB408 irq 16
> scsi6 : sata_nv
> ata7: SATA link down (SStatus 0 SControl 300)
> ATA: abnormal status 0x7F on port 0xC407
> scsi7 : sata_nv
> ata8: SATA link down (SStatus 0 SControl 300)
> ATA: abnormal status 0x7F on port 0xBC07
> SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
> SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
>  sda: sda1 sda2
> sd 3:0:0:0: Attached scsi disk sda
> SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
> sdb: Write Protect is off
> SCSI device sdb: drive cache: write back
> SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
> sdb: Write Protect is off
> SCSI device sdb: drive cache: write back
>  sdb: sdb1 sdb2
> sd 4:0:0:0: Attached scsi disk sdb
> SCSI device sdc: 488397168 512-byte hdwr sectors (250059 MB)
> sdc: Write Protect is off
> SCSI device sdc: drive cache: write back
> SCSI device sdc: 488397168 512-byte hdwr sectors (250059 MB)
> sdc: Write Protect is off
> SCSI device sdc: drive cache: write back
>  sdc: sdc1 sdc2
> sd 5:0:0:0: Attached scsi disk sdc
> scsi 2:0:0:0: Attached scsi generic sg0 type 5
> sd 3:0:0:0: Attached scsi generic sg1 type 0
> sd 4:0:0:0: Attached scsi generic sg2 type 0
> sd 5:0:0:0: Attached scsi generic sg3 type 0

however, the boot log for the same configuration on the Dom0 kernel fails
to detect any of the buses containing drives:

> ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA
> mode
> ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part 
> ata1: SATA max UDMA/133 cmd 0xE1020100 ctl 0x0 bmdma 0x0 irq 18
> ata2: SATA max UDMA/133 cmd 0xE1020180 ctl 0x0 bmdma 0x0 irq 18
> scsi0 : ahci
> ata1: SATA link down (SStatus 0 SControl 300)
> scsi1 : ahci
> ata2: SATA link down (SStatus 0 SControl 300)

No further output concerning the SATA bus, the AHCI driver, or the SCSI
subsystem is provided.  Later, the Dom0 kernel panics because it is unable
to load the root filesystem which normally resides on /dev/sda1.

The dumps above reflect Xen 3.1.3 and Linux 2.6.18.8 but it doesn't seem to
be limited to that version alone.

I have been banging my head against this for a few weeks without much
gain and I am unsure of how to troubleshoot much further.  I am sure I am
missing something very simple but I have not yet been able to fathom what
it could be.  I am willing to post more information if necessary.  If
anybody could point me in the right direction, I would very much
appreciate it.

Thanks,
Tim Harig

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] ahci sata detection disparity between standalone and Dom0 kernels, Tim Harig <=
Previous by Date:  [Xen-users] sched-credit & reboots, --[ UxBoD ]--
Next by Date:  Re: Fw: [Xen-users] Can I install domU without virt-manager?, Tom Brown
Previous by Thread:  [Xen-users] sched-credit & reboots, --[ UxBoD ]--
Next by Thread:  Re: Fw: [Xen-users] Can I install domU without virt-manager?, Tom Brown
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy