Overview: until kernel 3.11.x poweroff or reboot worked fine, since 3.13 it crashes Steps to Reproduce: halt, poweroff or reboot Actual Results: the kernel crashed, screenshot attached Expected Results: halt, poweroff or reboot of the machine Hardware: Intel(R) Core(TM) i3-4330T CPU @ 3.00GHz AsRock Z87 Extreme4, BIOS P2.70 01/21/2014 I already tried to backport some patches from 3.15-rc, without success https://bugzilla.kernel.org/show_bug.cgi?id=69791#c12
Created attachment 137011 [details] dmesg
Created attachment 137021 [details] lsmod
Created attachment 137031 [details] lspci
Adding "xhci_hcd.quirks=270336", as suggested here: https://bugzilla.kernel.org/show_bug.cgi?id=66171#c67 did not help. Using 3.15-rc5 shows the same problem. Uploading larger attachments to this bug report, like the screenshot of the kernel oops and .config seems, seems to broken atm.
Created attachment 137191 [details] .config
Created attachment 137201 [details] screenshot of kernel oops
What is the earliest kernel version that fails? You mentioned 3.11 works and 3.13 fails -- does 3.12 work? What do you see when you boot with maxcpus=1? I expect this hardware supports 64-bit -- do you see the issue also with a 64-bit kernel?
The distro I am using (32bit userspace only, no 64bit kernel provided) bumped the kernel from 3.11 to 3.13, I did not use 3.12. Setting up bisecting will not be easy, but I will try if no other option remains. Using maxcpus=1 did not solve the bug, neither removing ?hci-*.ko usb modules.
please check if reverting commit 522e66464467543c0d88d023336eec4df03ad40b helps?
(In reply to Zhang Rui from comment #9) > please check if reverting commit 522e66464467543c0d88d023336eec4df03ad40b > helps? Yes, reverting this commit fixes the crash during reboot and poweroff, thanks!
Created attachment 137961 [details] patch used with 3.14.4, applies also to 3.15-rc8
An additional info: Another user using the same distro reported the same problem using an Intel D2500CC board: http://lists.spline.de/pipermail/fli4l_dev/2014-May/001746.html (German)
Is this issue reproducible on any board with 32-bit kernel? Is this issue reproducible every time on your board? I can not reproduce on a Thinkpad machine.
Hi, (In reply to Fenghua Yu from comment #13) > Is this issue reproducible on any board with 32-bit kernel? In total there were three reports of this bug, including mine: http://lists.spline.de/pipermail/fli4l_dev/2014-May/001746.html (Intel D2500CC) http://lists.spline.de/pipermail/fli4l_dev/2014-June/001815.html (ALIX APU1C) > Is this issue reproducible every time on your board? Yes, since Jan 31st, 2014, when the distro changed from 3.11 to 3.13, the crash happened always, 100% reproducible, until I applied the patch suggested by Zhang Rui, which also fixed the problem for the other two reporters.
Created attachment 139031 [details] /proc/cpuinfo
Some infos about my CPU: http://ark.intel.com/products/77770/Intel-Core-i3-4330T-Processor-4M-Cache-3_00-GHz
Created attachment 139351 [details] Bug fix patch: Disable local irq before disabling IO APIC This bug fix patch which disables local irq before disabling IO APIC during reboot is supposed to fix the issue here. It was tested and verified by Bernd. A new German 32-bit Linux distro will be released on this Friday to include this bug fix patch and will enable more German users to test it. After this patch is fully verified, I will publish this patch to lkml.
I really appreciate it if anyone can test this patch in any test enviornment to provide wider coverage.
(In reply to Fenghua Yu from comment #17) > Created attachment 139351 [details] > Bug fix patch: Disable local irq before disabling IO APIC Patch works fine and solves the problem, thanks!
(In reply to Bernd Kuhls from comment #14) > In total there were three reports of this bug, including mine: > http://lists.spline.de/pipermail/fli4l_dev/2014-May/001746.html (Intel > D2500CC) The forementioned bug reporter writes that the patch from comment #17 works fine for him and solves the reboot problem: http://lists.spline.de/pipermail/fli4l_dev/2014-June/001884.html
Has this patch been pushed to LKML.org?
The patch is in lkml now: https://lkml.org/lkml/2014/6/21/4
ping, any update about the inclusion of the patch into the kernel?