From: Jeff Garzik <jgarzik@pobox.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP+irq handling broken in current git?
Date: Thu, 23 Jun 2005 12:59:19 -0400 [thread overview]
Message-ID: <42BAEA67.7090606@pobox.com> (raw)
In-Reply-To: <20050623135318.GC9768@suse.de>
Jens Axboe wrote:
> Hi,
>
> Something strange is going on with current git as of this morning (head
> ee98689be1b054897ff17655008c3048fe88be94). On an old test box (dual p3
> 800MHz), using the same old config I always do on this box has very
> broken interrupt handling:
Does 2.6.12 work for you?
2.6.11?
I noticed a few "2.6.12 is broken, 2.6.11 works" bug reports with
vaguely similar circumstances -- irq handling being a culprit.
Jeff
next prev parent reply other threads:[~2005-06-23 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 13:53 SMP+irq handling broken in current git? Jens Axboe
2005-06-23 16:59 ` Jeff Garzik [this message]
2005-06-23 18:42 ` Jens Axboe
2005-06-23 18:58 ` Bjorn Helgaas
2005-06-23 19:11 ` Jens Axboe
2005-06-23 19:20 ` Bjorn Helgaas
2005-06-23 23:26 ` Alan Cox
2005-06-24 10:12 ` Jens Axboe
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=42BAEA67.7090606@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox