From: Arjan van de Ven <arjanv@redhat.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Chris Caputo <ccaputo@alt.net>, linux-kernel@vger.kernel.org
Subject: Re: inode_unused list corruption in 2.4.26 - spin_lock problem?
Date: Thu, 29 Jul 2004 14:21:09 +0200 [thread overview]
Message-ID: <20040729122107.GA1024@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040729105755.GA6897@logos.cnet>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Thu, Jul 29, 2004 at 07:57:55AM -0300, Marcelo Tosatti wrote:
> On Thu, Jul 29, 2004 at 09:54:29AM +0200, Arjan van de Ven wrote:
> > On Wed, Jul 28, 2004 at 11:27:41PM -0700, Chris Caputo wrote:
> > > On Wed, 28 Jul 2004, Marcelo Tosatti wrote:
> > > > Changing the affinity writes new values to the IOAPIC registers, I can't see
> > > > how that could interfere with the atomicity of a spinlock operation. I dont
> > > > understand why you think irqbalance could affect anything.
> > >
> > > Because when I stop running irqbalance the crashes no longer happen.
> >
> > what is the irq distribution when you do that?
> > Can you run irqbalance for a bit to make sure there's a static distribution
> > of irq's and then disable it and see if it survives ?
>
> Chris, Yes I'm also running irqbalance.
>
> Arjan, what is an easy way for me to make irqbalance change the affinity
> as crazy on the SMP 8way box, just for a test?
there is a sleep(10 seconds) in the code, if you change that to something
really short and then cause irq burst rates on different devices...
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-29 12:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 0:47 inode_unused list corruption in 2.4.26 - spin_lock problem? Chris Caputo
2004-06-20 0:15 ` Marcelo Tosatti
2004-06-20 3:33 ` Trond Myklebust
2004-06-21 0:45 ` Marcelo Tosatti
2004-06-21 17:10 ` Trond Myklebust
2004-06-21 18:23 ` Marcelo Tosatti
2004-06-24 1:51 ` Chris Caputo
2004-06-25 7:47 ` Chris Caputo
2004-06-24 1:50 ` Chris Caputo
2004-06-25 8:04 ` Chris Caputo
2004-06-25 10:18 ` Chris Caputo
2004-06-25 12:17 ` Marcelo Tosatti
2004-07-02 20:00 ` Chris Caputo
2004-07-03 5:15 ` Arjan van de Ven
2004-07-26 17:41 ` Chris Caputo
2004-07-27 14:19 ` Marcelo Tosatti
2004-07-27 16:08 ` Chris Caputo
2004-07-29 0:25 ` Marcelo Tosatti
2004-07-29 6:27 ` Chris Caputo
2004-07-29 7:54 ` Arjan van de Ven
2004-07-29 10:57 ` Marcelo Tosatti
2004-07-29 12:21 ` Arjan van de Ven [this message]
2004-07-29 16:22 ` Chris Caputo
2004-07-29 16:23 ` Arjan van de Ven
2004-08-04 15:38 ` Chris Caputo
2004-08-04 18:47 ` Chris Caputo
[not found] <20040805225549.GA18420@logos.cnet>
2004-08-07 16:00 ` Chris Caputo
2004-08-07 18:31 ` Marcelo Tosatti
2004-08-07 19:36 ` Marcelo Tosatti
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=20040729122107.GA1024@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=ccaputo@alt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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