lkml.org 
[lkml]   [2009]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Panic early in boot
On 06/05/2009 11:39 PM, Jeff Mitchell wrote:
> Output is pasted below. It's hand-typed from a screenshot, so
> hopefully I didn't mistype anything.

Don't worry to append a link to the screenshot next time ;).

> 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

Looks like dmi_string_nosave gets a mess. It tries to dereference
0xffffffffeff44003d. Could you investigate to which save_indent in
dmi_decode does the dmi_decode+0x72 correspond to?

Is this vanilla, i.e. what does -gentoo-r5 mean?

And also append a dmidecode output from a working kernel.


\
 
 \ /
  Last update: 2009-06-06 11:43    [W:0.025 / U:4.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site