I've forced ASPM on both my (affected) machines, and they've been fine. But all I've really done is return to the pre-2.6.38 behaviour, so why wouldn't they have been?
So anyone who ran 2.6.37 OK can probably enable ASPM safely
Posted Jul 4, 2011 14:08 UTC (Mon) by nix (subscriber, #2304)
[Link]
Well, with the bug I was seeing, if I forced ASPM on, I ended up with ASPM enabled on my buggy network card, and it hung up. If I forced ASPM off, the same thing happened. So force_aspm isn't a panacea.