We need to work out what's going wrong here before we rush into a band-aid. What changed between v3.4 and v3.4.1 that exposed this problem? "git log --oneline v3.4..v3.4.1" doesn't show any likely culprits. Paul, are those the versions you tested? Your dmesg logs at https://bugzilla.kernel.org/show_bug.cgi?id=92351 show "3.4.0-030400-generic" and "3.4.1-030401-generic" but I don't know whether those are precisely v3.4 and v3.4.1. I assume this system works fine with Windows, and I doubt Windows has a hack like "never move LSI devices." So it would be useful to know if we're doing something stupid in Linux that makes us trip over this. Paul, if you happen to have Windows on this machine as well, a complete AIDA64 report (free trial version at http://www.aida64.com) would show what Windows did. The resource allocation we're doing is related SR-IOV, and unfortunately we don't print enough information in dmesg to figure everything out. Paul, can you attach the complete "lspci -vv" output to the bugzilla? Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
