kernel-ml thread[1] states that a similiar issue was recently fixed "Fixed by 2.6.27.2. commit d344a53f2e264ea07c950691c1451a4ff355694b". There's also a perhaps related Ubuntu bug regarding[1], see [2]. I'm experiencing following regression with kernel 2.6.27 when booting a 64bit kernel on VMware ESX Server version=3.5.0 build=build-98103 (gentoo-sources-2.6.26-r1 works well). Gentoo kernel gentoo-sources-2.6.27-r5: Booting the kernel. Kernel alive Kernel really alive PANIC: early exception 0e rip 10:ffffffff804b0874 error 0 cr2 fffffffeff34003d SystemRescueCD kernel 2.6.27.8: Booting the kernel. Kernel alive Kernel really alive PANIC: early exception 0e rip 10:ffffffff816e98ee error 0 cr2 fffffffeff34003d [1] https://kerneltrap.org/mailarchive/linux-kernel/2008/10/16/3675174 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/54020 Reproducible: Always
Please assign bugs yourself if you can.
(In reply to comment #1) > Please assign bugs yourself if you can. Done, thanks. Wasn't sure if I need to add some keywords or if there's any more information I can provide to start with.
Can you try latest gentoo sources? Maybe it's a duplicate of http://bugs.gentoo.org/show_bug.cgi?id=249751
CONFIG_VMI isn't available on x86_64 kernels yet. I've also played around with switching VMI support for guests on/off in the ESX server, no change. I've also tried the latest gentoo-sources-2.6.27-r6 but without success, same for git-sources-2.6.28_rc8-r2 with a slightly altered panic msg: PANIC: early exception 0e rip 10:ffffffff815142c2 error 0 cr2 fffffffeff44003d gentoo-sources-2.6.26-r4 boots just fine.
Please try the latest gentoo-sources release anyway. That patch affected early boot code that was outside of CONFIG_VMI bounds.
(In reply to comment #5) > Please try the latest gentoo-sources release anyway. That patch affected early > boot code that was outside of CONFIG_VMI bounds. That's what I did, please see my above comment about gentoo-sources-2.6.27-r6 which also fails to work for me in 64bit guests, however it boots 32bit guests (even with enabled VMI support) just fine.
(In reply to comment #6) > That's what I did, please see my above comment about gentoo-sources-2.6.27-r6 > which also fails to work for me in 64bit guests, however it boots 32bit guests > (even with enabled VMI support) just fine. Can you try with first 2.6.27 vanilla release? Just to figure out, if the problem has been introduced within 2.6.27.y series or from 2.6.26 to 2.6.27. If we are lucky it's within 2.6.27.y.
(In reply to comment #7) > Can you try with first 2.6.27 vanilla release? > Just to figure out, if the problem has been introduced within 2.6.27.y series > or from 2.6.26 to 2.6.27. If we are lucky it's within 2.6.27.y. Looks like I'm not a lucky guy, vanilla 2.6.27: Booting the kernel. Kernel alive Kernel really alive PANIC: early exception 0e rip 10:ffffffff8151558d error 0 cr2 fffffffeff34003d
OK, thanks for testing. Please file this bug upstream at http://bugzilla.kernel.org emphasizing that this is a 2.6.27 regression (it worked in 2.6.26) that is still unfixed in unmodified 2.6.28-rc8. Also, be clear that you are booting a vmware guest, and the bug only appears when that guest is in 64 bit mode. Post the new bug URL here when done. Thanks!
Added URL to upstream bug.
We'll keep an eye on the upstream bug. --> http://bugzilla.kernel.org/show_bug.cgi?id=12236
Upstream bug was closed
