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/
Home Products Support Community News


[Xen-bugs] [Bug 89] nVidea onboard SATA Controller causes booting Proble

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 89] nVidea onboard SATA Controller causes booting Problems on dom0
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 23 Oct 2005 01:16:34 +0000
Delivery-date: Sun, 23 Oct 2005 01:16:42 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From tarmo@xxxxxxxx  2005-10-23 01:16 -------
I have an nvidia sata controller which works in uniprocessor mode, but fails to
find my sata drive in SMP (dualcore 3800+ X2) mode as-of xen revision 7421. 7414
is the last revision that works and the versions between 7414 and 7421 fail to
build (7421 is a build fix for smp). The controller itself is found, but for
some reason the drive is not:

libata version 1.11 loaded.
sata_nv version 0.6
ACPI: PCI Interrupt Link [APSI] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [APSI] -> GSI 22 (level, high) -> 
IRQ 22
PCI: Setting latency timer of device 0000:00:09.0 to 64
ata1: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xC800 irq 22
ata2: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xC808 irq 22
scsi0 : sata_nv
ata2: no device found (phy stat 00000000)
scsi1 : sata_nv
ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APSJ] -> GSI 21 (level, high) -> 
IRQ 21
PCI: Setting latency timer of device 0000:00:0a.0 to 64
ata3: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xB000 irq 21
ata4: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xB008 irq 21
ata3: no device found (phy stat 00000000)
scsi2 : sata_nv
ata4: no device found (phy stat 00000000)
scsi3 : sata_nv

Note, that there is no line for ata1, on a working kernel there should be a
lines similiar to those:
ata1: dev 0 cfg 49:2f00 82:3469 83:7f21 84:4003 85:3469 86:3c01 87:4003 88:203f
ata1: dev 0 ATA-6, max UDMA/100, 234375000 sectors: LBA48
ata1(0): applying bridge limits

The last revision that I tried, 7473 still has this problem.

Any idea what could be wrong or if I should open a separate bug report for this 

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list