Comment 32 for bug 209454

Revision history for this message
Jon Ogilvie (svtdragon) wrote :

I'm running Jaunty, and I still have this issue. The relevant output from lspci -vvnn is:

00:09.0 SATA controller [0106]: nVidia Corporation Device [10de:0584] (rev a2) (prog-if 01)
 Subsystem: nVidia Corporation Device [10de:cb84]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0 (750ns min, 250ns max)
 Interrupt: pin A routed to IRQ 2299
 Region 0: I/O ports at a480 [size=8]
 Region 1: I/O ports at a400 [size=4]
 Region 2: I/O ports at a080 [size=8]
 Region 3: I/O ports at a000 [size=4]
 Region 4: I/O ports at 9c00 [size=16]
 Region 5: Memory at f3f76000 (32-bit, non-prefetchable) [size=8K]
 Capabilities: <access denied>
 Kernel driver in use: ahci

I can boot up with or without pci=nomsi, but only because I have a PCIe RAID controller that I'm using to run my OS off of. The system will only recognize my SATA drives with pci=nomsi and the drives in AHCI mode, but I'd like to be able to use msi for PCI passthrough with KVM.

I haven't yet tried the Karmic kernel because I've got a very fragile system configuration that doesn't adapt well to change. :)

Is there a fix out there for this?