> > [<c023d9d8>] serial8250_console_write+0x68/0x1f0
> > [<c0121459>] __call_console_drivers+0x49/0x50
> > [<c0121541>] call_console_drivers+0x71/0x100
> > [<c012196d>] release_console_sem+0xbd/0x170
> > [<c01217cc>] printk+0x18c/0x220
> > [<c01170d5>] nmi_add_task+0xc5/0xe0
> > [<c01177e0>] nmi_watchdog_tick+0x0/0x120
>
> the oops occur during a NMI so I wonder how a NMI
> can occur and clobber ebx
Actually it didn't occur during the NMI, it just appears to be that way
(ie don't consider the nmi_watchdog_tick ;) nmi_add_task is a registration
function and is called from normal kernel context.
Zwane
-- function.linuxpower.ca- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/