public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Terence Ripperda <tripperda@nvidia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lockup on Athlon systems, kernel race condition?
Date: Fri, 30 Aug 2002 14:15:14 -0700	[thread overview]
Message-ID: <3D6FE062.A48B6F03@zip.com.au> (raw)
In-Reply-To: 20020830204022.GC736@hygelac

Terence Ripperda wrote:
> 
> ...
>
> asmlinkage long sys_ioctl(unsigned int fd, unsigned int cmd, unsigned long arg)
> {
>         struct file * filp;
>         unsigned int flag;
>         int on, error = -EBADF;
> 
>         filp = fget(fd);
>         if (!filp)
>                 goto out;
>         error = 0;
>         lock_kernel();    <====
>         switch (cmd) {

This CPU is spinning, waiting for kernel_flag.  It will take the IPI
and the other CPU's smp_call_function() will succeed.

Possibly the IPI has got lost - seems that this is a popular failure mode
for flakey chipsets/motherboards.

Or someone has called sys_ioctl() with interrupts disabled.  That's very
doubtful.

  reply	other threads:[~2002-08-30 21:13 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 [this message]
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
  -- 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=3D6FE062.A48B6F03@zip.com.au \
    --to=akpm@zip.com.au \
    --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