Esel, Could you provide me the stack trace you are facing (without intel_idle.max_cstate=0 in bootparam). Then you should test enabling intel_idle.max_cstate=0 into bootparams and see if the problems happen. If you problem is related to intel_idle module, I'd love to use your case as a "testcase" to fix this.
Do you know how to enable linux-crashdump ? Do you think you could enabled it and provide me the coredump when you get such error ? And yes! For your case (Proliant < Gen8) the "workaround" cmdline should be: "nox2apic intermap=off intel_idle.max_cstate=0" Tks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1398497 Title: HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic - General Protection Fault and X2APIC/XAPIC boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398497/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
