Launchpad has imported 139 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=66171.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2013-11-29T19:27:28+00:00 ganastasiouGR wrote:
Created attachment 116781
Dmesg output
I have intel core i5-4570 using asrock h87 pro4 motherboard.
The problem is that i cannot shutdown at all, i have to poweroff pressing and
holding power off button on case. This problem appeared using 3.12 kernel.
I have attached dmesg.
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-
utopic/+bug/1419355/comments/0
On 2013-11-29T19:27:56+00:00 ganastasiouGR wrote:
Created attachment 116791
config
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-
utopic/+bug/1419355/comments/1
On 2013-12-02T07:26:45+00:00 aaron.lu wrote:
Does v3.11 have this problem?
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-
utopic/+bug/1419355/comments/2
On 2013-12-02T07:31:16+00:00 ganastasiouGR wrote:
(In reply to Aaron Lu from comment #2)
> Does v3.11 have this problem?
No thanks for asking, because i forgot to mention this in my first post.
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-
utopic/+bug/1419355/comments/3
On 2013-12-02T07:37:56+00:00 aaron.lu wrote:
Can you please do a git bisect to find out the offending commit?
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-
utopic/+bug/1419355/comments/4
On 2013-12-02T10:04:15+00:00 ganastasiouGR wrote:
I will but i am not so familiar with git. But it would be a good way to
learn something. Thanks, i will be back.
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-
utopic/+bug/1419355/comments/5
On 2013-12-04T11:32:44+00:00 ganastasiouGR wrote:
The offending commit is the following.
638298dc66ea36623dbc2757a24fc2c4ab41b016 is the first bad commit
commit 638298dc66ea36623dbc2757a24fc2c4ab41b016
Author: Takashi Iwai
Date: Thu Sep 12 08:11:06 2013 +0200
xhci: Fix spurious wakeups after S5 on Haswell
Haswell LynxPoint and LynxPoint-LP with the recent Intel BIOS show
mysterious wakeups after shutdown occasionally. After discussing with
BIOS engineers, they explained that the new BIOS expects that the
wakeup sources are cleared and set to D3 for all wakeup devices when
the system is going to sleep or power off, but the current xhci driver
doesn't do this properly (partly intentionally).
This patch introduces a new quirk, XHCI_SPURIOUS_WAKEUP, for
fixing the spurious wakeups at S5 by calling xhci_reset() in the xhci
shutdown ops as done in xhci_stop(), and setting the device to PCI D3
at shutdown and remove ops.
The PCI D3 call is based on the initial fix patch by Oliver Neukum.
[Note: Sarah changed the quirk name from XHCI_HSW_SPURIOUS_WAKEUP to
XHCI_SPURIOUS_WAKEUP, since none of the other quirks have system names
in them. Sarah also fixed a collision with a quirk submitted around the
same time, by changing the xhci->quirks bit from 17 to 18.]
This patch should be backported to kernels as old as 3.0, that
contain the commit 1c12443ab8eba71a658fae4572147e56d1f84f66 "xhci: Add
Lynx Point to list of Intel switchable hosts."
Cc: Oliver Neukum
Signed-off-by: Takashi Iwai
Signed-off-by: Sarah Sharp
Cc: sta...@vger.kernel.org
:04 04 6ba54ba0725b8b93e1beff0ed0c8ac0a729f7502
8330c3a748392abc47843a538752d06048ecc0db M drivers
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-
utopic/+bug/1419355/comments/6
On 2013-12-04T13:07:19+00:00 tianyu.lan wrote:
The commit shows the bug is caused by xhci driver and so reassign to USB
component.
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-
utopic/+bug/1419355/comments/7
On 2013-12-04T16:29:36+00:00 sarah wrote:
Giorgos: Can you retest with 3.12, but revert commit
638298dc66ea36623dbc2757a24fc2c4ab41b016? I.e. `git reset --hard v3.12`
and then `git revert 638298dc66ea36623dbc2757a24fc2c4ab41b016`.
Takashi: Could this have been caused by not disabling PCI wakeup before
