From: Robert Hancock <hancockr@shaw.ca>
To: Scott <linux-kernel@bluecamel.eml.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cx88 pci_abort messages
Date: Sat, 06 Oct 2007 12:48:22 -0600 [thread overview]
Message-ID: <4707D876.8080306@shaw.ca> (raw)
In-Reply-To: <fa.m+2QwZVzW3oTWJBsJ4fdAiUZWkM@ifi.uio.no>
Scott 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
>> pci_abort messages repeating in the /var/log/messages file. As a result
>> I see some minor video corruption during playback. I've installed the
>> adapter into a PCI slot that shares an IRQ with the onboard USB.
>> However, I've also disabled all USB support in BIOS, so the adapter is
>> the only thing on the IRQ, and still see the same errors.
>>
>> Any suggestions for further troubleshooting? Is this a PCI bus quirk on
>> this motherboard? A copy of my .config is at
>> http://donpoo.net/kernel_config
>>
>> 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
>
> I was poking around the PCI bus with setpci/lspci last night and tried
> adjusting the latency from 64 to 32. This didn't make a difference. I
> also changed my core2duo speedstep governor from ondemand to performance
> to prevent the CPUs from changing speed. I eventualy saw the same
> pci_abort message but I might have seen less of them.
>
> Is there a way to log every device pci device that throws an interrupt?
> I'm thinking if I could find out which pci device was stealing the
> interrupt that I could disable it or look at the code and see what it
> was doing.
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?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-10-06 18:48 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 [this message]
2007-10-06 21:15 ` cx88 pci_abort messages Scott
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=4707D876.8080306@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@bluecamel.eml.cc \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.