From: Scott <linux-kernel@bluecamel.eml.cc>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cx88 pci_abort messages
Date: Sat, 06 Oct 2007 17:15:03 -0400 [thread overview]
Message-ID: <1191705303.7536.6.camel@oasis.donpoo.home> (raw)
In-Reply-To: <4707D876.8080306@shaw.ca>
On Sat, 2007-10-06 at 12:48 -0600, Robert Hancock wrote:
> > On Oct 4, 2007, at 11:52 AM, Scott wrote:
> >
> >> I'm having what I think is a PCI bus problem.
> >>
> >> I have a ASUS P5B Intel 965 motherboard and a DVICO Fusion HDTV5 RT
> >> adapter on the PCI bus. When this adapter is recording (anything) I see
> >> Oct 2 21:59:12 htpc cx88[0]: irq mpeg [0x80000] pci_abort*
> >> Oct 2 21:59:12 htpc cx88[0]/2-mpeg: general errors: 0x00080000
> >> Oct 2 21:59:20 htpc cx88[0]: irq mpeg [0x80000] pci_abort*
> >> Oct 2 21:59:20 htpc cx88[0]/2-mpeg: general errors: 0x00080000
> >> Oct 2 21:59:32 htpc cx88[0]: irq mpeg [0x80000] pci_abort*
> >> Oct 2 21:59:32 htpc cx88[0]/2-mpeg: general errors: 0x0008000
> >
> PCI aborts won't have anything to do with interrupts. It's a PCI DMA
> transfer that either the initiator (here, the TV card) or the target
> (the chipset host bridge) decided to puke on for some reason. Possibly
> parity errors?
I assumed it was an interrupt issue based on the 'irq mepg' error, not a
DMA issue. Any suggestions on how to log more information about PCI DMA
events on a system wide basis?
I've seen this since 2.6.18.
--
Scott <linux-kernel@bluecamel.eml.cc>
next prev parent reply other threads:[~2007-10-06 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.9BwFZjxkV7dKD7EmsWMTtKId3Qc@ifi.uio.no>
[not found] ` <fa.m+2QwZVzW3oTWJBsJ4fdAiUZWkM@ifi.uio.no>
2007-10-06 18:48 ` Robert Hancock
2007-10-06 21:15 ` Scott [this message]
2007-10-08 7:44 ` Gerd Hoffmann
2007-10-08 11:43 ` Scott
2007-10-04 15:52 Scott
2007-10-05 12:04 ` Scott
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=1191705303.7536.6.camel@oasis.donpoo.home \
--to=linux-kernel@bluecamel.eml.cc \
--cc=hancockr@shaw.ca \
--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®