Re: [patch] VP-2.6.9-rc4-mm1-T6

[Daniel Walker]

On Tue, 2004-10-12 at 09:39, Mark_H_Johnson@xxxxxxxxxxxx wrote:

> Had to cycle power to get the machine back. Rebooting with max_cpus=1
> crashed in a different way. Was able to get past mounting the disks and
> some of the init script items before stopping at the same location with
> a different call trace:
> 
> Call Trace:
>  [<c011cb58>] scheduler_tick+0x148/0x490
>  [<c012bee3>] update_process_times+0x43/0x60
>  [<c0114b60>] mcount+0x14/0x18
>  [<c012beef>] update_process_times_0x4f/0x60
>  [<c0115141>] smp_apic_timer_interrupt+0xe1/0xf0
>  [<c011cb73>] scheduler_tick+0x16e/0x490
>  [<c010854a>] apic_timer_interrupt+0x1a/0x20
>  [<c031007b>] unix_stream_recvmsg+0x5b/0x450
>  [<c011cb7e>] scheduler_tick+0x16e/0x490
>  [<c012bee3>] update_process_times+0x43/0x60
>  [<c0114b60>] mcount+0x14/0x18
>  [<c012beef>] update_process_times+0x4f/0x60
>  [<c0115141>] smp_apic_timer_interrupt+0xe1/0xf0
>  [<c01225d4>] release_console_sem+0x64/0xe0
>  [<c012236d>] printk+0x1d/0x30


Do you have hyper threading turned on? Seems like I've seen this trace a
few times before..


Daniel Walker

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/