Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#29063 - [linux] Kernel panic with linux kernel 3.2.12 on motherboard z68x-ud3-b3

Attached to Project: Arch Linux
Opened by Lapin Roman (Lampus) - Thursday, 22 March 2012, 19:56 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 23 April 2012, 12:07 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas B├Ąchler (brain0)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No


After upgrading kernel version to 3.2.12 I have kernel panic on very early kernel boot stage. Upgrading BIOS version from F7 to F11 don't help. Starting kernel with "noacpi" boot param don't change anything too. I think it's motherboard-specific bug, because other users have the same problem with this motherboard and kernel version. Please, see this thread:
With linux kernel 3.2.11 all works fine.

My H/W Configuration:
Motherboard: Gigabyte Z68X-UD3-B3
CPU: Intel Core i7 2600K
Video: NVidia GeForce 9600 GT

I have attached log of next commands: lspci -vv, dmidecode, cat /proc/cpuinfo and photo of panic from other user.
If you need extra info about this panic I can try get backtarce via rs-232 serial console.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 23 April 2012, 12:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.3.1
Comment by Gunnar Kriik (krigun) - Friday, 23 March 2012, 00:23 GMT
Had the same problem, and was able to boot using the following kernel parameter:

Comment by Gunnar Kriik (krigun) - Friday, 23 March 2012, 13:04 GMT
Kernel bug report which looks very similar:
Comment by Arnau Oncins (nauar) - Saturday, 24 March 2012, 19:49 GMT
Same happens to me. I also have a Gigabyte MotherBoard with a Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz.
Gunnar Kriik's solution works perfectly, thank you.
Comment by niqingliang (niqingliang2003) - Sunday, 25 March 2012, 09:47 GMT
Same problem, my MB is asus's P8H67, CPU is i5-2300, GPU is Dataland 6870
Comment by cedlemo (cedlemo) - Monday, 26 March 2012, 09:55 GMT
Same problem

Motherboard Gigabyte PH67-UD3
CPU Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz

pcie_aspm = force resolve the problem.

Note: I have this problem with Kernel 3.2.13 too
Comment by Patrick (freethebee) - Wednesday, 28 March 2012, 15:12 GMT
Same problem here with a gigabyte Z86X-UD3H-B3 and kernel 3.2.13-1. The pcie_aspm=force workaround fortunately works for me as well.
Comment by Sergei Konduryan (serg36) - Wednesday, 28 March 2012, 16:45 GMT
Same problem, same solution.
Gigabyte GA-P67A-UD4-B3.
Updated linux and linux-lts are both problematic for me.
pcie_aspm=force works for me.
Comment by Christian Neukirchen (chneukirchen) - Thursday, 29 March 2012, 22:24 GMT
Same problem, same solution.
Gigabyte Z68XP-UD3
Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
Linux hecate 3.2.13-1-ARCH #1 SMP PREEMPT Sat Mar 24 09:10:39 CET 2012 x86_64 Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz GenuineIntel GNU/Linux
pcie_aspm=force works
Comment by niqingliang (niqingliang2003) - Friday, 30 March 2012, 02:01 GMT
what about the 3.2.13 kernel?
Comment by Douglas (Fixo) - Monday, 02 April 2012, 03:11 GMT
Gigabyte Z68XP-UD3
Intel(R) Core(TM) i5-2500k CPU

Same problem.
Comment by Max (zoidberg) - Monday, 02 April 2012, 18:09 GMT
same problem here on 3.2.13 and 3.3.1, my MB is a P8H67M-Pro from Asus + i3-2100
pcie_aspm=force also works.
Comment by Tobias Powalowski (tpowa) - Monday, 23 April 2012, 10:26 GMT
Status on 3.3.x?
Comment by Gunnar Kriik (krigun) - Monday, 23 April 2012, 10:59 GMT
I believe this issue can be closed. The fix was merged into 3.2.14 and 3.3.1.

See this comment:

It certainly works for me now (running 3.3.2 without pcie_aspm=force)