From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: David Vrabel <david.vrabel@csr.com>
Cc: "Moore, Eric" <Eric.Moore@lsi.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Prakash, Sathya" <Sathya.Prakash@lsi.com>
Subject: Re: [PATCH 2/2] fusion: Implement generic interrupt misroute handling
Date: Tue, 05 Aug 2008 09:36:27 -0700 [thread overview]
Message-ID: <1217954187.9923.15.camel@localhost.localdomain> (raw)
In-Reply-To: <48970A4D.2090309@csr.com>
On Mon, 2008-08-04 at 14:55 +0100, David Vrabel wrote:
> Moore, Eric wrote:
> > Thanks, I will try this out. However I thought I saw lost
> > interrupts occurring randomly, meaning it was not necessarily the
> > first config page access. I'm back in the office on 8/11, I will
> > test it out then and provide feedback.
>
> Is this using MSI on a device without per-vector mask bits? If so, then
> this patch may help.
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ce6fce4295ba727b36fdc73040e444bd1aae64cd
We don't really know what the problem is. MSI interrupts get lost on
older motherboards (the ones most likely to contain a 1030). Why is
anybody's guess although the clever money is on the motherboard bridge
having issues.
James
next prev parent reply other threads:[~2008-08-05 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 18:05 [PATCH 2/2] fusion: Implement generic interrupt misroute handling James Bottomley
2008-08-03 22:59 ` Moore, Eric
2008-08-03 23:07 ` James Bottomley
2008-08-04 13:55 ` David Vrabel
2008-08-05 16:36 ` James Bottomley [this message]
2008-08-05 17:38 ` Jesse Barnes
2008-08-05 20:45 ` James Bottomley
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=1217954187.9923.15.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Eric.Moore@lsi.com \
--cc=Sathya.Prakash@lsi.com \
--cc=david.vrabel@csr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@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