(In reply to Niklas Schnelle from comment #26)
> - My original problem manifested itself as described in this bug
> https://bugzilla.kernel.org/show_bug.cgi?id=66551
> that was merged into this one.
It shouldn't be merged unless it's really spotted to be the exact same bug...
In anyway, I was confused by some description here and there. Now it's cleared. Thanks.
> I haven't done the git bisect though but can
> confirm that it works with a live system with 3.11
Then better to check whether the patch fixes the issue. It's much faster than bisecting.
(In reply to Niklas Schnelle from comment #26) /bugzilla. kernel. org/show_ bug.cgi? id=66551
> - My original problem manifested itself as described in this bug
> https:/
> that was merged into this one.
It shouldn't be merged unless it's really spotted to be the exact same bug...
In anyway, I was confused by some description here and there. Now it's cleared. Thanks.
> I haven't done the git bisect though but can
> confirm that it works with a live system with 3.11
Then better to check whether the patch fixes the issue. It's much faster than bisecting.
> - I tried
> #modprobe -r xhci_hcd
> #setpci -s 00:14.0 CAP_PM+4.b=08
Is it with the patched kernel? Otherwise something is wrong. Which kernel are you testing...?
The previous commit for Haswell S5 fix was to make this to 0b (= D3). 08 means it's still D0, i.e. the quirk wasn't applied.