Martin Rogge wrote:
Could you git-bisect this? Although I have a couple of patch suspects (dealing with interrupts), all worked fine with PCI-649 just fine. PCI-648 is not really much different from 649 according to specs...
Yes, I found the same when I managed to send the CMD 648 into UDMA-100 mode years ago (by treating it like a 649).
Anyway, I found the git patches on kernel.org and bisected away. For completeness, this is the table containing all my results.
Kernel System reaction ============================================================================ 2.6.21 CMD 648 working fine 2.6.21-git4 CMD 648 working fine 2.6.21-git5 CMD 648 working fine 2.6.21-git6 irg 15: nobody cared [...] Disabling IRQ #15 etc. 2.6.21-git8 irg 15: nobody cared [...] Disabling IRQ #15 etc. 2.6.22-rc1 irg 15: nobody cared [...] Disabling IRQ #15 etc. 2.6.22 irg 15: nobody cared [...] Disabling IRQ #15 etc. 2.6.23 irg 15: nobody cared [...] Disabling IRQ #15 etc.
Well, most likely the CMD related patches in git6 are the culprit.
Erm... usually bisection leaves you with one patch startting from which kernel was broken. It seems you've done sort iof manual bisecting. Thanks anyway. :-)
Regards,
cu Martin
MBR, Sergei - 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
