FS#29240 - [linux] ite-cir kernel panic at boot-up
Attached to Project:
Arch Linux
Opened by oblique (oblique) - Monday, 02 April 2012, 20:21 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 11 June 2012, 13:17 GMT
Opened by oblique (oblique) - Monday, 02 April 2012, 20:21 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 11 June 2012, 13:17 GMT
|
Details
Description:
i was getting kernel panic when udev loads the modules at boot-up Additional info: linux >= 3.2 How to fix it: the problem is caused by IRQ remapping subsystem which is experimental. unset CONFIG_IRQ_REMAP from configs. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Monday, 11 June 2012, 13:17 GMT
Reason for closing: Fixed
Additional comments about closing: 3.4.x
Monday, 11 June 2012, 13:17 GMT
Reason for closing: Fixed
Additional comments about closing: 3.4.x
and this bug exists also in 2.6.30 .. i didn't check in < 2.6.30 yet.. if you disable CONFIG_X86_X2APIC everything is ok..
intremap=on
enable Interrupt Remapping (default)
intremap=off
disable Interrupt Remapping
intremap=nosid
disable Source ID checking
intremap=no_x2apic_optout
BIOS x2APIC opt-out request will be ignored
I would try those option you mention.
I'm able to boot with acpi=off/noirq or noapic, but machine froze sooner or later anyway.
Last bootable kernel is linux-3.2.7. Everything above dies...
Booting with acpi=off "works", but then the nvidia driver crashes.
Is this "just" a hardware related problem? Seems Dell XPS' are suffering from it: https://bbs.archlinux.org/viewtopic.php?id=137248
I'm running newer kernel versions on an older machine that doesn't have these problems... it's not a laptop though.
I've found the responsible module: ite_cir. Blacklisting it in /etc/modprobe.d/*.conf helped!
I've tried all the intremap settings but they all led to kernel panic... related to ite_cir.
Hope this helps track down the issue.
https://www.dropbox.com/gallery/502921/3/archlinux/bugs/ite_cir?h=c447d0 (for intremap=nosid/off/no_x2apic_optout)
Found a related bug for upstream tracking: https://bugzilla.kernel.org/show_bug.cgi?id=43042
It should be fixed in 3.4.0-1.