From: Manfred Spraul <manfred@colorfullife.com>
To: Terence Ripperda <tripperda@nvidia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lockup on Athlon systems, kernel race condition?
Date: Wed, 04 Sep 2002 17:05:58 +0200 [thread overview]
Message-ID: <3D762156.5050907@colorfullife.com> (raw)
In-Reply-To: 20020903220424.GL2343@hygelac
Terence Ripperda wrote:
>
> 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.
>
That rules out a disabled interrupt flag.
What was cpu1 doing? There are 3 loops in smp_call_function:
spin_lock(&call_lock), and 2 while loops with barrier() [first one for
IPI arrival, second one for synchroneous ipi's. TLB flush is sync].
--
Manfred
next prev parent reply other threads:[~2002-09-04 15:01 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
2002-09-04 15:05 ` Manfred Spraul [this message]
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=3D762156.5050907@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tripperda@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).