From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jens Axboe <axboe@suse.de>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: SMP+irq handling broken in current git?
Date: Thu, 23 Jun 2005 12:58:35 -0600 [thread overview]
Message-ID: <200506231258.35258.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20050623184234.GE9768@suse.de>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
On Thursday 23 June 2005 12:42 pm, Jens Axboe wrote:
> On Thu, Jun 23 2005, Jeff Garzik wrote:
> > 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?
>
> 2.6.11 works, 2.6.12 does not.
Do you have any VIA devices? If so, you might try the attached.
(Just for debugging; if the patch helps, I have no idea how to
do it correctly.)
[-- Attachment #2: via-irq --]
[-- Type: text/x-diff, Size: 528 bytes --]
Index: work/drivers/pci/quirks.c
===================================================================
--- work.orig/drivers/pci/quirks.c 2005-06-21 13:43:29.000000000 -0600
+++ work/drivers/pci/quirks.c 2005-06-23 10:40:55.000000000 -0600
@@ -510,7 +510,7 @@
pci_write_config_byte(dev, PCI_INTERRUPT_LINE, new_irq);
}
}
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq);
+DECLARE_PCI_FIXUP_ENABLE(PCI_ANY_ID, PCI_ANY_ID, quirk_via_irq);
/*
* PIIX3 USB: We have to disable USB interrupts that are
next prev parent reply other threads:[~2005-06-23 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 13:53 Jens Axboe
2005-06-23 16:59 ` Jeff Garzik
2005-06-23 18:42 ` Jens Axboe
2005-06-23 18:58 ` Bjorn Helgaas [this message]
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=200506231258.35258.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®