lkml.org 
[lkml]   [2002]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: lockup on Athlon systems, kernel race condition?
On Tue, Sep 03, 2002 at 11:46:11PM +0200, manfred@colorfullife.com wrote:
> Which compiler to you use, and which kernel? Which additional patches?
>
> With my 2.4.20-pre4-ac1 kernel, the lock_kernel is at offset +3a,
> according to your dump it's at +6a.

I'm using gcc 2.95.4 (on debian). The kernel I'm currently using is 2.4.19, with the kdb patch and apic_routing patches applied. Neither of these is required to reproduce the problem, they're just to help debug the problem.

that reminds me. when I originally tried to use the nmi watchdog to break into the debugger when the hang occured, I got the following at bootup:

Sep 3 14:56:49 localhost kernel: activating NMI Watchdog ... done.
Sep 3 14:56:49 localhost kernel: testing NMI watchdog ... CPU#0: NMI appears to be stuck!


> Is it possible to display the cpu registers with kdb? Could you check
> that the interrupts are enabled?

I don't have things caught in the debugger currently, but I did check the registers at the time. bit 9 of eflags was enabled on both cpus.

Terence
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.073 / U:10.364 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site