Created attachment 198811 [details] Contains dmesg and cpuinfo It used to work at kernel 4.2. It won't work anymore since kernel 4.3 and higher. I have to boot with the kernel argument "nolapic" otherwise the system won't boot at all.
Would it be possible for you to do a "git bisect" to identify the commit which breaks your hardware?
(In reply to H. Peter Anvin from comment #1) > Would it be possible for you to do a "git bisect" to identify the commit > which breaks your hardware? As far as I tested it today the results are this: version v4.2.8 is working, but version 4.3.0 is not I am not sure how to proceed with identifying which commit causes the problem.
(In reply to H. Peter Anvin from comment #1) > Would it be possible for you to do a "git bisect" to identify the commit > which breaks your hardware? I have found the commit which is causing trouble. It is this one: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=v4.3-rc7&id=018155365dccecd9ea9f26e1b26fb0f960c1ee32
Try to boot with kernel option intel_idle.max_cstate=7 If you can boot, then I guess this bug is probably just a duplicate of https://bugzilla.kernel.org/show_bug.cgi?id=109081 4.3 is the kernel version that introduced the code specific to the intel Skylake architecture (and so the processor you have)
(In reply to Ludovic Magerand from comment #4) > Try to boot with kernel option intel_idle.max_cstate=7 > If you can boot, then I guess this bug is probably just a duplicate of > https://bugzilla.kernel.org/show_bug.cgi?id=109081 > > 4.3 is the kernel version that introduced the code specific to the intel > Skylake architecture (and so the processor you have) Dear Ludovic Magerand, The system did indeed boot with that kernel string. Stupid of me that I couldn't find that other bugreport. I am going to mark this bug report as duplicate. Thanks you! With kind regards. *** This bug has been marked as a duplicate of bug 109081 ***