| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <9599edfc0906051439s7e006edcrdb68ccde60d51815@mail.gmail.com> Date: Fri, 5 Jun 2009 17:39:28 -0400 From: Jeff Mitchell <jeffrey.mitchell@...il.com> To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Panic early in boot I have a x86_64 system running inside a VMware virtual machine. It works very well with 2.6.25; however, I have tried both 2.6.27 and 2.6.29, and both give me a panic immediately upon boot. I have to use earlyprintk to get anything useful. Output is pasted below. It's hand-typed from a screenshot, so hopefully I didn't mistype anything. I can get the memory ranges if need be. Hopefully someone knows of the solution/can fix the problem. Thanks, Jeff console [earlyvga0] enabled DMI present. PANIC: early exception 0e rip 10:ffffffff80866edc error 0 cr2 ffffffffeff44003d Pid: 0, comm: swapper Not tainted 2.6.29-gentoo-r5 #2 Call Trace: early_idt_handler+0x5e/0x71 dmi_string_nosave+0x34/0x80 dmi_string_nosave+0x67/0x80 dmi_string+0xa/0x6e dmi_save_ident+0x1b/0x2a dmi_decode+0x72/0x492 _spin_unlock_irqrestore+0x14/0x17 __early_set_fixmap+0xa0/0xa7 dmi_table+0x4e/0x78 dmi_scan_machine+0x132/0x19f setup_arch+0x34d/0x636 early_idt_handler+0x0/0x71 start_kernel+0x86/0x35e x86_64_start_kernel+0xed/0xf6 RIP dmi_string_nosave+0x34/0x80 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists