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] can't access SATA drives on a VIA board

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] can't access SATA drives on a VIA board
From: Peter Berg <xen@xxxxxxxx>
Date: Thu, 17 Mar 2005 23:43:44 +0100
Delivery-date: Thu, 17 Mar 2005 22:40:53 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.7.1
Hi,

The dom0 kernel hangs during the boot when accessing my SATA drives.
This seems to be a problem with the PCI IRQ routing.

The machine has a VIA K8 board with VIA SATA and PROMISE SATA.
The drivers are connected to the VIA interface.

These are the messages just before the kernel hangs:

PCI: Obtained IRQ 17 for device 0000:00:0d.0
ata1: SATA max UDMA/133 cmd 0xF180E200 ctl 0xF180E238 bmdma 0x0 irq 17
ata2: SATA max UDMA/133 cmd 0xF180E280 ctl 0xF180E2B8 bmdma 0x0 irq 17
ata1: no device found (phy stat 00000000)
scsi0 : sata_promise
ata2: no device found (phy stat 00000000)
scsi1 : sata_promise
PCI: Obtained IRQ 17 for device 0000:00:0f.0
sata_via(0000:00:0f.0): routed to hard irq line 1
ata3: SATA max UDMA/133 cmd 0xDC00 ctl 0xD802 bmdma 0xCC00 irq 17
ata4: SATA max UDMA/133 cmd 0xD400 ctl 0xD002 bmdma 0xCC08 irq 17
ata3: dev 0 ATA, max UDMA7, 312581808 sectors: lba48


These are the corresponding messages when booting a standard Debian 2.6.10 
kernel:

SCSI subsystem initialized
libata version 1.10 loaded.
sata_promise version 1.01
ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 17 (level, low) -> IRQ 169
ata1: SATA max UDMA/133 cmd 0xF884C200 ctl 0xF884C238 bmdma 0x0 irq 169
ata2: SATA max UDMA/133 cmd 0xF884C280 ctl 0xF884C2B8 bmdma 0x0 irq 169
ata1: no device found (phy stat 00000000)
scsi0 : sata_promise
ata2: no device found (phy stat 00000000)
scsi1 : sata_promise
elevator: using anticipatory as default io scheduler
sata_via version 1.0
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 177
sata_via(0000:00:0f.0): routed to hard irq line 10
ata3: SATA max UDMA/133 cmd 0xDC00 ctl 0xD802 bmdma 0xCC00 irq 177
ata4: SATA max UDMA/133 cmd 0xD400 ctl 0xD002 bmdma 0xCC08 irq 177
ata3: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c69 86:3e01 87:4003 
88:80ff
ata3: dev 0 ATA, max UDMA7, 312581808 sectors: lba48
ata3: dev 0 configured for UDMA/133
scsi2 : sata_via
ata4: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c69 86:3e01 87:4003 
88:80ff
ata4: dev 0 ATA, max UDMA7, 312581808 sectors: lba48
ata4: dev 0 configured for UDMA/133
scsi3 : sata_via
  Vendor: ATA       Model: SAMSUNG SP1614C   Rev: SW10
  Type:   Direct-Access                      ANSI SCSI revision: 05
Attached scsi generic sg0 at scsi2, channel 0, id 0, lun 0,  type 0
  Vendor: ATA       Model: SAMSUNG SP1614C   Rev: SW10
  Type:   Direct-Access                      ANSI SCSI revision: 05
Attached scsi generic sg1 at scsi3, channel 0, id 0, lun 0,  type 0


Cheers,
Peter


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>