[DC LoCo] Kernel Panic!

[Daniel Chen]

2011/2/1 Frank J. Gómez <frank at crop-circle.net>:
> Call Trace:
> <IRQ> [<some address>] panic+0x90/0x111
> [<some address>] oops_end+0xea/0xf0
> [<some address>] die+05b/0x90
> [<some address>] ? tick_sched_timer+0x0/0xc0
> [<some address>] do_general_protection+0x162/0x170
> [<some address>] ? tick_sched_timer+0x0/0xc0
> [<some address>] ? hrtimer_forward+0x1e/0xc0
> [<some address>] tick_sched_timer+0x82/0xc0
> [<some address>] __run_hrtimer+0x8f/0x1b0
> [<some address>] ? update_wall_time+0x295/0x450
> [<some address>] ? read_tsc+0x9/0x20
> [<some address>] hrtimer__interrupt+0xd6/0x220
> [<some address>] smp_apic_timer_interrupt+0x6b/0x9b
> [<some address>] apic_timer_interrupt+0x13/0x20
> <EOI> [<some address>] ? native_safe_halt+0xb/0x10
> [<some address>] default_idle+0x3d/0x90
> [<some address>] cpu_idle+0xb3/0x110
> [<some address>] rest_init+0x8a/0x90
> [<some address>] start_kernel+0x387/0x390
> [<some address>] x86_64_start_reservations+0x12c/0x130
> [<some address>] x86_64_start_kernel+0xfa/0x109
> So you think this is a non-hard-drive, non-ram hardware failure?  Any idea
> how I'd determine what I need to replace?  The four hard drives are on two
> array controllers, and both arrays seem to come up fine before the CD is
> read.

None of those functions touch IO for your storage, so I wouldn't think
they're putting a finger on your storage. It's possible you need a
kernel parameter, but you'll need to provide more information using
the ubuntu-bug command for a bug report.

-Dan