[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Re: pv_ops dom0 USB fixed
Andrew Lyon wrote: 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 Yes, that's OK. In a dom0 kernel devices will generally get a different irq. The important thing is that it has the same GSI (18, in this case). In native linux irq == gsi, but in dom0 they're remapped (to make room for irqs for non-hardware events). 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 So this is where things start falling apart. I'm guessing there's some DMA problem; either the drive isn't getting the right command, or we're not seeing a proper response. I suspect the former, since the error message is a timeout rather than complains about bad data. J _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |