Tejun Heo wrote: > Jon Masters wrote: >> Chuck Ebbert wrote: >> >>> If you try to load both the pata_atiixp and the ahci driver >>> (for the same ATI SB600 adapter), very strange things happen. >>> The AHCI driver churns for three minutes or so, spewing >>> messages like this, then nothing works: >>> >>> <6>ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >>> <4>ata3.00: qc timeout (cmd 0xec) >>> <4>ata3.00: failed to IDENTIFY (I/O error, err_mask=0x104) >>> Shouldn't it be able to tell the device has already been >>> claimed by some other driver? >> One would assume it'd fail to grab the PCI IO ranges twice? I haven't >> looked at the code but I have seen this bug mentioned elsewhere so I >> might well end up having to do that yet :-) > > Dunno much about sb600 but ahci and pata_atiixp are probably using > separate IO regions && separate PCI functions. > > Conke, care to educate us a bit here? > The really funny part is that it works for some if they use: pci=noacpi,irqpoll - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
