From: Terence Ripperda <TRipperda@nvidia.com>
To: Andrew Morton <akpm@zip.com.au>
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 13:35:24 -0500 [thread overview]
Message-ID: <20020903183524.GC2343@hygelac> (raw)
In-Reply-To: <3D6FE062.A48B6F03@zip.com.au>
On Fri, Aug 30, 2002 at 02:15:14PM -0700, akpm@zip.com.au wrote:
> This CPU is spinning, waiting for kernel_flag. It will take the IPI
> and the other CPU's smp_call_function() will succeed.
thank you for the clarification, Andrew. I was unclear whether the 'lock' command would block out the IPI or not.
> Possibly the IPI has got lost - seems that this is a popular failure mode
> for flakey chipsets/motherboards.
this sounds like the most likely candidate. I'm working on tracking down documentation for further study. Is there an easy way to determine this as the cause?
> Or someone has called sys_ioctl() with interrupts disabled. That's very
> doubtful.
I agree, that's highly doubtful.
one of our QA guys tried to reproduce this issue on an ATI card, but was unable to get through viewperf long enough to repro this problem before hitting other system lockups. I'm also installing an ATI card to try and see if I can reproduce the problem.
Terence
next prev parent reply other threads:[~2002-09-03 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 20:40 lockup on Athlon systems, kernel race condition? Terence Ripperda
2002-08-30 21:15 ` Andrew Morton
2002-08-31 0:36 ` Alan Cox
2002-09-03 18:35 ` Terence Ripperda [this message]
2002-09-03 18:54 ` Andrew Morton
2002-09-03 20:46 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-09-03 21:46 Manfred Spraul
2002-09-03 22:04 ` Terence Ripperda
2002-09-04 15:05 ` Manfred Spraul
2002-09-04 16:17 ` Terence Ripperda
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=20020903183524.GC2343@hygelac \
--to=tripperda@nvidia.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
/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