You are not logged in.
Pages: 1
Hi,
after Kernel uprade yesterday; I cant power off my system:
I see "power off" on my screen, then the system seems to be powered off, but reboots after 1-2 seconds.
Upgrade yesterday:
[2014-05-11 21:07] [PACMAN] upgraded gawk (4.1.0-2 -> 4.1.1-1)
[2014-05-11 21:07] [PACMAN] upgraded imagemagick (6.8.9.0-1 -> 6.8.9.1-1)
[2014-05-11 21:07] [PACMAN] upgraded imagemagick-doc (6.8.9.0-1 -> 6.8.9.1-1)
[2014-05-11 21:07] [PACMAN] upgraded libva (1.3.0-1 -> 1.3.1-1)
[2014-05-11 21:07] [PACMAN] upgraded libva-intel-driver (1.3.0-1 -> 1.3.1-1)
[2014-05-11 21:07] [PACMAN] upgraded linux (3.14.2-1 -> 3.14.3-1)
[2014-05-11 21:07] [PACMAN] upgraded linux-headers (3.14.2-1 -> 3.14.3-1)Of course all wake up functions in UEFI are disabled.
Bios/Motherboard:
BIOS Information
Vendor: American Megatrends Inc.
Version: P2.00
Release Date: 12/06/2013
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8192 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 4.6
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: To Be Filled By O.E.M.
Product Name: To Be Filled By O.E.M.
Version: To Be Filled By O.E.M.
Serial Number: To Be Filled By O.E.M.
UUID: 03000200-0400-0500-0006-000700080009
Wake-up Type: Power Switch
SKU Number: To Be Filled By O.E.M.
Family: To Be Filled By O.E.M.
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASRock
Product Name: H87M Pro4
Version:
Serial Number: M80-39019500250
Asset Tag:
Features:
Board is a hosting board
Board is replaceable
Location In Chassis:
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: Any idea ?
Last edited by midixinga (2014-05-18 01:41:34)
Offline
THat looks like a regression.
[2014-05-11 21:07] [PACMAN] upgraded linux (3.14.2-1 -> 3.14.3-1)Maybe downgrade to v3.14.2 and confirm the issue goes away? Bisecting this should be really easy. Another option is to wait since I doubt it you will be the only one affected by this.
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
I started without any external USB HDDs -> didn't solve my problem
THat looks like a regression.
[2014-05-11 21:07] [PACMAN] upgraded linux (3.14.2-1 -> 3.14.3-1)Maybe downgrade to v3.14.2 and confirm the issue goes away?
yes that "solved" my problem. With kernel 3.14.2 the system shuts down properly.
Bisecting this should be really easy. Another option is to wait since I doubt it you will be the only one affected by this.
it seems, that I am the only one ?!?! I didn't find a appropriate current bug report.
I googled a little bit, and the problem seems to be a very diversified and the cause hard to determine in the past
Offline
Maybe try reverting this one:
45ada9f x86/efi: Correct EFI boot stub use of code32_startCommit is here.
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
Hi Rexilion,
first, the issue disappears with new kernel and disabled USB3.0 within UEFI
Maybe try reverting this one:
45ada9f x86/efi: Correct EFI boot stub use of code32_startCommit is here.
Sorry, please advise me, I don't have any idea, what I should do ? :-)
Offline
Hi Rexilion,
first, the issue disappears with new kernel and disabled USB3.0 within UEFI
Rexilion wrote:Maybe try reverting this one:
45ada9f x86/efi: Correct EFI boot stub use of code32_startCommit is here.
Sorry, please advise me, I don't have any idea, what I should do ? :-)
What I'm suggesting is to clone the kernel and then to rebuild some version between v3.14.2 and v3.14.3. Git can help you pin down which commit caused your issue. However, this requires some knowledge about git, grub2 and building + configuring a kernel. Plus, this could take quite some time.
5092b2b xhci: Switch Intel Lynx Point ports to EHCI on shutdown.You don't happen to have an Intel Lynx Point chipset by any chance?
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
What I'm suggesting is to clone the kernel and then to rebuild some version between v3.14.2 and v3.14.3. Git can help you pin down which commit caused your issue. However, this requires some knowledge about git, grub2 and building + configuring a kernel. Plus, this could take quite some time.
Oh, ok, I think I won't do that. I don't know how, and I have no time to read documentation in the moment.
I have gummiboot, no grub.
5092b2b xhci: Switch Intel Lynx Point ports to EHCI on shutdown.You don't happen to have an Intel Lynx Point chipset by any chance?
No, it's a desktop, Motherboard: ASRock H87M Pro4
I think I`ve found my bug here: https://bugzilla.kernel.org/show_bug.cgi?id=66171 and I hope the next kernel will solve my problem.
Thank you for your advices
Offline
Rexilion wrote:What I'm suggesting is to clone the kernel and then to rebuild some version between v3.14.2 and v3.14.3. Git can help you pin down which commit caused your issue. However, this requires some knowledge about git, grub2 and building + configuring a kernel. Plus, this could take quite some time.
Oh, ok, I think I won't do that. I don't know how, and I have no time to read documentation in the moment.
That is quite understandable.
I have gummiboot, no grub.
That would also work. As long as you know how it works so it can boot a custom kernel.
5092b2b xhci: Switch Intel Lynx Point ports to EHCI on shutdown.You don't happen to have an Intel Lynx Point chipset by any chance?
No, it's a desktop, Motherboard: ASRock H87M Pro4
Yes, it actually is.
I think I`ve found my bug here: https://bugzilla.kernel.org/show_bug.cgi?id=66171 and I hope the next kernel will solve my problem.
The bug you mention is a regression in v3.12. Not v3.14, so unless the same bug has returned, it's not the one you are suffering from.
Thank you for your advices
No problem.
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
I opened a bug and Arch devs asked me to bisect kernel, but I'm very unfamiliar with kernel, hardware, Compiling, ... and I didn't know which repository exactly to clone.
Thus I used:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-stable
git bisect bad v3.14.3
git bisect good v3.14.2My result:
Before last step:
# git bisect bad
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[e7573909b5b8df35591a66146d8629f7aa41675e] xhci: Prevent runtime pm from autosuspending during initializationAfter last step:
[root@dixi-arch linux-stable]# git bisect good
5092b2b3c54eeb1a41329661d14289f59f81bdcb is the first bad commit
commit 5092b2b3c54eeb1a41329661d14289f59f81bdcb
Author: Denis Turischev <denis.turischev@compulab.co.il>
Date: Fri Apr 25 19:20:14 2014 +0300
xhci: Switch Intel Lynx Point ports to EHCI on shutdown.
commit c09ec25d3684cad74d851c0f028a495999591279 upstream.
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
One example is Compulab's mini-desktop, the Intense-PC2.
The bug can be avoided if the USB ports are switched back to EHCI on
shutdown.
This patch should be backported to stable kernels as old as 3.12,
that contain the commit 638298dc66ea36623dbc2757a24fc2c4ab41b016
"xhci: Fix spurious wakeups after S5 on Haswell"
Signed-off-by: Denis Turischev <denis@compulab.co.il>
Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
:040000 040000 e178b761c73619963c1c130805e3722a9ccbdd7d 56b0434140c234293b1a34fb2e1f04fa2fd13d16 M driversno idea, if this helps or is correct
Offline
Yes, your result confirms my prediction in post #8. You could have saved yourself some time and just 'git revert 5092b2'. BUT, you have now done this yourself. This confirms you did the procedure correctly.
I think it's best to report this to bugzilla.kernel.org or the kernel mailing list.
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
Hi Rexilion,
I reported it to bugzilla.kernel.org and linux-usb@vger.kernel.org
I also had a look to this:
https://wiki.archlinux.org/index.php/Ke … ild_System
And I see in the linux PKGBUILD, that makepkg will download the major version 3.14
https://www.kernel.org/pub/linux/kernel … .14.tar.xz (without any patches)
And here the xhci-pci.c in linux-3.14/drivers/usb/host/ is still without the patch in the "commit" 5092b2b3c54eeb1a41329661d14289f59f81bdcb
Then, I think, makepkg will do the "upstream-patches" for 3.14.4:
# add upstream patch
patch -p1 -i "${srcdir}/patch-${pkgver}"After running makepkg I find in src/linux-3.14/drivers/usb/host/ a patched xhci-pci.c with the patch in the "commit".
Is there a possibility to use ABS which prevents the patch of xhci-pci.c with this "commit" 5092b2b3c54eeb1a41329661d14289f59f81bdcb, and only with this one "commit" ?
Thanks.
Edit: Aah
makepkg -oand
makepkg -eare my friends
Topic closed
Thanks again
Last edited by midixinga (2014-05-18 01:41:13)
Offline
Pages: 1