mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Dave Olson <olson@unixfolk.com>
Cc: mingo@elte.hu, ccb@acm.org, linux-kernel@vger.kernel.org,
	nickpiggin@yahoo.com.au
Subject: Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
Date: Wed, 21 Jun 2006 22:57:52 -0700	[thread overview]
Message-ID: <20060621225752.93cfffb0.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0606212243240.32136@osa.unixfolk.com>

On Wed, 21 Jun 2006 22:45:49 -0700 (PDT)
Dave Olson <olson@unixfolk.com> wrote:

> On Tue, 20 Jun 2006, Andrew Morton wrote:
> | > Intended to be more or less stock fc4 but with CONFIG_PCI_MSI=y and
> | > 2.6.17-based patch so the 8131 MSI quirk isn't enabled.
> | > 
> | > >From the config file:
> | > 	CONFIG_DEBUG_SPINLOCK=y
> | > 	CONFIG_DEBUG_SPINLOCK_SLEEP=y
> | 
> | OK, I goofed again.
> | 
> | It would be super-interesting to know whether CONFIG_DEBUG_SPINLOCK=n
> | improves things.
> 
> It does.   No stalls, hangs, or nmi's in several hours of running the
> test that previously failed on almost every run (with long stalls, system
> hangs, or NMI watchdogs), on the same hardware.
> 
> I made no other changes to the kernel config than turning both of
> the above off.
> 

Well isn't that interesting, thanks.   We have our 2.6.17.x patch.

Now we need to work out why.

  reply	other threads:[~2006-06-22  5:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22  5:45 Dave Olson
2006-06-22  5:57 ` Andrew Morton [this message]
2006-06-23  7:57 ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2006-06-23 16:27 Dave Olson
     [not found] <fa.VT2rwoX1M/2O/aO5crhlRDNx4YA@ifi.uio.no>
     [not found] ` <fa.Zp589GPrIISmAAheRowfRgZ1jgs@ifi.uio.no>
2006-06-20  5:35   ` Dave Olson
2006-06-20  6:39     ` Andrew Morton
2006-06-20  6:53       ` Dave Jones
2006-06-20  7:37       ` Nick Piggin
2006-06-20  8:03         ` Andrew Morton
2006-06-20  8:33         ` Ingo Molnar
2006-06-20  9:37           ` Nick Piggin
2006-06-20  9:51             ` Ingo Molnar
2006-06-20 10:59               ` Nick Piggin
2006-06-20 13:04                 ` Arjan van de Ven
2006-06-20 13:36                   ` Nick Piggin
2006-06-20 14:53                     ` Arjan van de Ven
2006-06-20 15:16                       ` Nick Piggin
2006-06-20 16:27                         ` Nick Piggin
2006-06-20  8:43         ` Arjan van de Ven
2006-06-20 16:11       ` Dave Olson
2006-06-20 21:10         ` Andrew Morton

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=20060621225752.93cfffb0.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ccb@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=olson@unixfolk.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

Powered by JetHome