All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: john cooper <john.cooper@timesys.com>
Cc: Luca Falavigna <dktrkranz@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Softlockup detected with linux-2.6.14-rt6
Date: Tue, 15 Nov 2005 21:00:10 +0100	[thread overview]
Message-ID: <20051115200010.GA13802@elte.hu> (raw)
In-Reply-To: <437A14FB.8050206@timesys.com>


* john cooper <john.cooper@timesys.com> wrote:

> Ingo Molnar wrote:
> >* Luca Falavigna <dktrkranz@gmail.com> wrote:
> >>I found this softlockup bug involving arts daemon using a
> >>linux-2.6.14-rt6 kernel (with "Complete Preemption" and "Detect Soft
> >>Lockups" compiled in).
> >>This bug does not happen everytime: I was able to reproduce it only
> >>three times in a week. [...]
> >
> >
> >does this happen with -rt13 too? I have fixed a softlockup 
> >false-positive in it.
> 
> Just curious what the cause of the false positive was?

the fix is below - we didnt reset the 'light' counter in the else 
branch.

	Ingo

Index: linux/kernel/softlockup.c
===================================================================
--- linux.orig/kernel/softlockup.c
+++ linux/kernel/softlockup.c
@@ -90,7 +90,8 @@ void softlockup_tick(void)
 
 		wake_up_process(per_cpu(watchdog_task, this_cpu));
 		per_cpu(timeout, this_cpu) = jiffies + msecs_to_jiffies(1000);
-	}
+	} else
+		touch_light_softlockup_watchdog();
 
 	if (per_cpu(print_timestamp, this_cpu) == timestamp)
 		return;

  reply	other threads:[~2005-11-15 20:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 16:00 [BUG] Softlockup detected with linux-2.6.14-rt6 Luca Falavigna
2005-11-14 19:48 ` john cooper
2005-11-15 15:32 ` Ingo Molnar
2005-11-15 17:03   ` john cooper
2005-11-15 20:00     ` Ingo Molnar [this message]
2005-11-15 20:07       ` Daniel Walker
2005-11-16  0:16         ` Luca Falavigna
2005-11-18 15:18           ` Luca Falavigna
2005-11-18 18:33             ` K.R. Foley
2005-11-19  0:50               ` Luca Falavigna

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=20051115200010.GA13802@elte.hu \
    --to=mingo@elte.hu \
    --cc=dktrkranz@gmail.com \
    --cc=john.cooper@timesys.com \
    --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 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.