linux-kernel - Re: cx88 pci

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1191705303.7536.6.camel@oasis.donpoo.home>
Date:	Sat, 06 Oct 2007 17:15:03 -0400
From:	Scott <linux-kernel@...ecamel.eml.cc>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: cx88 pci_abort messages

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@...ecamel.eml.cc>

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