From: Terence Ripperda <TRipperda@nvidia.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Terence Ripperda <TRipperda@nvidia.com>, linux-kernel@vger.kernel.org
Subject: Re: lockup on Athlon systems, kernel race condition?
Date: Tue, 3 Sep 2002 17:04:24 -0500 [thread overview]
Message-ID: <20020903220424.GL2343@hygelac> (raw)
In-Reply-To: <3D752DA3.6030000@colorfullife.com>
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
next prev parent reply other threads:[~2002-09-03 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 21:46 lockup on Athlon systems, kernel race condition? Manfred Spraul
2002-09-03 22:04 ` Terence Ripperda [this message]
2002-09-04 15:05 ` Manfred Spraul
2002-09-04 16:17 ` Terence Ripperda
-- strict thread matches above, loose matches on Subject: below --
2002-08-30 20:40 Terence Ripperda
2002-08-30 21:15 ` Andrew Morton
2002-08-31 0:36 ` Alan Cox
2002-09-03 18:35 ` Terence Ripperda
2002-09-03 18:54 ` Andrew Morton
2002-09-03 20:46 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020903220424.GL2343@hygelac \
--to=tripperda@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.