lkml.org 
[lkml]   [2007]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: cx88 pci_abort messages
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/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-10-06 20:51    [W:0.043 / U:0.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site