LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Lukasz Trabinski <lukasz@wsisiz.edu.pl>,
	linux-kernel@vger.kernel.org,
	Bartlomiej Solarz-Niesluchowski <solarz@wsisiz.edu.pl>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.20 BUG: soft lockup detected on CPU#0!
Date: Thu, 8 Feb 2007 10:16:21 +0100	[thread overview]
Message-ID: <200702081016.21124.dada1@cosmosbay.com> (raw)
In-Reply-To: <20070208080644.GA14579@elte.hu>

On Thursday 08 February 2007 09:06, Ingo Molnar wrote:
> * Andrew Morton <akpm@linux-foundation.org> wrote:
> > The softlock detector has a long history of false positives and
> > precious few true positives, in my experience.
>
> hm, not so the latest & lamest in my experience. The commit that made it
> quite robust was 6687a97d4041f996f725902d2990e5de6ef5cbe5, as of March
> 2006, and first showed up in 2.6.17. (OTOH, since the merge of lockdep
> the main source of soft lockups in the field has been quite severely
> reduced. Nevertheless it's still good to have it around, occasionally
> there happen other types of soft lockups too, in open-coded loops, etc.)

This reminds me the current problem in close_files()
 code, where we trigger soft lockup quite regularly.

Is there any chance/interest we can solve the issue Andrew had with this 
patch ?

http://lkml.org/lkml/2006/5/2/273

Thank you
Eric



  parent reply	other threads:[~2007-02-08  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 23:02 Lukasz Trabinski
2007-02-08  4:47 ` Andrew Morton
2007-02-08  8:06   ` Ingo Molnar
2007-02-08  8:15     ` Andrew Morton
2007-02-08  9:16     ` Eric Dumazet [this message]
2007-02-08  9:56       ` Ingo Molnar
2007-02-08 10:12         ` Andrew Morton
2007-02-08 15:51   ` Lukasz Trabinski

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=200702081016.21124.dada1@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz@wsisiz.edu.pl \
    --cc=mingo@elte.hu \
    --cc=solarz@wsisiz.edu.pl \
    --cc=tglx@linutronix.de \
    --subject='Re: 2.6.20 BUG: soft lockup detected on CPU#0'\!'' \
    /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

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).