Re: [linux-dvb] cx88 pci_abort messages

2006-09-22 Thread Scott
Okay, I think I'm at the end of my rope. I can _reduce_ the frequency  
of pci_abort messages on my FusionHDTV5 RT Gold by:


A) In BIOS, setting my DDR2 667 memory to run at DDR2 533
B) In BIOS, setting the default PCI Bus Latency to 32 instead of 64

But, I cannot eliminate them. Regardless of the bios tweaks and  
kernel tweaks I've tried they never go away completely. Maybe I'm  
expecting to much? Is it normal for the current driver to  
occasionally report a pci_abort? For me occasionally appears to be  
between 1 and 3 times every hour the tuner is busy recording.


Outside of BIOS, I have tried many many things:

1) Placed the card in two different PCI slots
2) Ensured that the card was not sharing an IRQ at the hardware level  
or as reported by /proc/interrupts

3) Moved from 2.6.17-r8 Gentoo kernel to the released 2.6.18 kernel
4) Verified my frontend and backend matches the loaded modules
5) Assorted kernel options including: noapic, nolapic, pci=routeirq,  
irqpoll, acpi=off, acpi=noirq, pci=noacpi


None of these things seem to eliminate the pci_abort errors I'm  
seeing. Any more clues or suggestions? See below for my dmesg, the  
actual error I'm seeing, and the list of dvb modules I have loaded.


cx2388x dvb driver version 0.0.6 loaded
CORE cx88[0]: subsystem: 18ac:d500, board: DViCO FusionHDTV 5 Gold  
[card=31,autodetected]

TV tuner 64 at 0x1fe, Radio tuner -1 at 0x1fe
ACPI: PCI Interrupt :04:02.2[A] - GSI 23 (level, low) - IRQ 217
cx88[0]/2: found at :04:02.2, rev: 5, irq: 217, latency: 32,  
mmio: 0xfd00

cx88[0]/2: cx2388x based dvb card
DVB: registering new adapter (cx88[0]).
DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM  
Frontend)...


Sep 22 17:10:34 htpc cx88[0]: irq mpeg  [0x8] pci_abort*
Sep 22 17:10:34 htpc cx88[0]/2: general errors: 0x0008
Sep 22 17:12:19 htpc cx88[0]: irq mpeg  [0x8] pci_abort*
Sep 22 17:12:19 htpc cx88[0]/2: general errors: 0x0008

cx88_dvb3076  16
cx8802  5380  1 cx88_dvb
cx88xx 41060  2 cx88_dvb,cx8802
ir_common  18244  1 cx88xx
i2c_algo_bit5576  1 cx88xx
btcx_risc   2056  2 cx8802,cx88xx
tveeprom9360  1 cx88xx
video_buf_dvb   2180  1 cx88_dvb
video_buf  11332  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
dvb_pll 7492  1 cx88_dvb
lgdt330x4636  1 cx88_dvb

--
Scott



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] cx88 pci_abort messages

2006-09-22 Thread Michael Krufky
Scott wrote:
 Okay, I think I'm at the end of my rope. I can _reduce_ the frequency of
 pci_abort messages on my FusionHDTV5 RT Gold by:
 
 A) In BIOS, setting my DDR2 667 memory to run at DDR2 533
 B) In BIOS, setting the default PCI Bus Latency to 32 instead of 64
 
 But, I cannot eliminate them. Regardless of the bios tweaks and kernel
 tweaks I've tried they never go away completely. Maybe I'm expecting to
 much? Is it normal for the current driver to occasionally report a
 pci_abort? For me occasionally appears to be between 1 and 3 times every
 hour the tuner is busy recording.

I have the original FusionHDTV5 Gold, and also the FusionHDTV5 RT Gold.
(each in a different machine) I have never seen anything like this on
any of my hardware.

I have a bunch of other cards based on the cx2388x, including:

FusionHDTV3 Gold-T, KWorld HardwareMpegTvXpert, and some others
These pci_abort messages never happen to me.

Do you have another motherboard that you can try?  It sounds to me like
this problem is specific to your platform.

Sorry,

Michael Krufky


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] cx88 pci_abort messages

2006-09-22 Thread Scott


On Sep 22, 2006, at 5:51 PM, hermann pitton wrote:
there was a report once caused by that on the disk dma was not  
enabled.

Checked already if this could be the bottleneck with hdparm?


My drive is an SATA WD SE16 500G attached to the onboard SATA  
controller. It's part of the Intel 965P southbridge IHC8 chip. With  
kernel 2.6.18 I can use either AHCI or IDE mode for this controller  
and have my SATA drive show up as ata1 at /dev/sda. hdparm doesn't  
return info about DMA for SATA drives by testing performance looks  
pretty good:


/dev/sda:
Timing cached reads:   12644 MB in  2.00 seconds = 6326.00 MB/sec
Timing buffered disk reads:  210 MB in  3.01 seconds =  69.79 MB/sec

Here is what the kernel says about it when the drivers load. All in  
all, this looks pretty normal to me. Unless there's some bug in the  
SATA code causing this problem? Anyone else using Fusion cards with  
SATA drives?


I appreciate the fresh set of eyes looking it over.

libata version 2.00 loaded.
ata_piix :00:1f.2: version 2.00
ata_piix :00:1f.2: MAP [ P0 -- P1 -- ]
ACPI: PCI Interrupt :00:1f.2[B] - GSI 19 (level, low) - IRQ 177
PCI: Setting latency timer of device :00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE882 bmdma 0xE400 irq 177
ata2: SATA max UDMA/133 cmd 0xE800 ctl 0xE482 bmdma 0xE408 irq 177
scsi0 : ata_piix
ata1.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi1 : ata_piix
ata2.00: ATAPI, max UDMA/100
ata2.00: configured for UDMA/100
  Vendor: ATA   Model: WDC WD5000KS-00M  Rev: 07.0
  Type:   Direct-Access  ANSI SCSI revision: 05
  Vendor: LITE-ON   Model: COMBO SHC-52S7K   Rev: VK02
  Type:   CD-ROM ANSI SCSI revision: 05
ata_piix :00:1f.5: MAP [ P0 -- P1 -- ]
ACPI: PCI Interrupt :00:1f.5[B] - GSI 19 (level, low) - IRQ 177
PCI: Setting latency timer of device :00:1f.5 to 64
ata3: SATA max UDMA/133 cmd 0xD400 ctl 0xD082 bmdma 0xC880 irq 177
ata4: SATA max UDMA/133 cmd 0xD000 ctl 0xCC02 bmdma 0xC888 irq 177
scsi2 : ata_piix
ATA: abnormal status 0x7F on port 0xD407
scsi3 : ata_piix
ATA: abnormal status 0x7F on port 0xD007
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4  sda5 
sd 0:0:0:0: Attached scsi disk sda
sr0: scsi3-mmc drive: 47x/62x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0

--
Scott

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] cx88 pci_abort messages

2006-09-22 Thread Scott


On Sep 22, 2006, at 5:33 PM, Michael Krufky wrote:

I have the original FusionHDTV5 Gold, and also the FusionHDTV5 RT  
Gold.

(each in a different machine) I have never seen anything like this on
any of my hardware.


What motherboard chipset are you currently running on? For me it's  
the Intel P965 / ICH8 on an Asus P5B. It's good to hear that these  
error messages are not the normal way of things :)


Do you have another motherboard that you can try?  It sounds to me  
like

this problem is specific to your platform.


This is my greatest fear! No, I don't have another system with enough  
juice to do hdtv capture.


--
Scott 


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] cx88 pci_abort messages

2006-09-21 Thread Michael Krufky
Scott wrote:
 cx2388x dvb driver version 0.0.5 loaded
 CORE cx88[0]: subsystem: 18ac:d500, board: DViCO FusionHDTV 5 Gold
 [card=31,autodetected]
 TV tuner 64 at 0x1fe, Radio tuner -1 at 0x1fe
 ACPI: PCI Interrupt :04:02.2[A] - Link [LNKH] - GSI 7 (level, low)
 - IRQ 7
 cx88[0]/2: found at :04:02.2, rev: 5, irq: 7, latency: 32, mmio:
 0xfd00
 cx88[0]/2: cx2388x based dvb card
 DVB: registering new adapter (cx88[0]).
 DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM Frontend)...
 
 This seems to match my actual device which is the FusionHDTV 5 RT
 Gold. I had read that the FusionHDTV5 RT Gold and the FusionHDTV5
 Gold Plus were actually identical boards. The chips seemed to match up
 with the modules and the dvb-v4l tables I've seen.
 
 04:02.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and
 Audio Decoder [MPEG Port] (rev 05)
 Subsystem: DViCO Corporation DViCO FusionHDTV5 Gold
 Flags: bus master, medium devsel, latency 32, IRQ 7
 Memory at fd00 (32-bit, non-prefetchable) [size=16M]


That is correct.  The FusionHDTV5 RT Gold is identical to the
FusionHDTV5 Gold  The only difference is that the RT model has an RTC,
and you might notice two addional addresses on the i2c bus.

The RT functionality is not yet supported under linux, but the card has
100% functionality for atsc capture and analog framegrabbing.

HTH,

Mike Krufky

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] cx88 pci_abort messages

2006-09-21 Thread Scott


On Sep 21, 2006, at 8:45 AM, Michael Krufky wrote:

The RT functionality is not yet supported under linux, but the card  
has

100% functionality for atsc capture and analog framegrabbing.


This refers to the RTC on the RT? Honestly, it looked like mostly a  
software branding issue between the Gold Plus and the RT Gold.  
Overall I'm fairly happy, pci_abort problem aside, with this adapter.  
The picture is nice and sharp for OTA ATSC capture and the board  
appears to tune at least as well as my DirecTV HDTV box.


I am currently trying yet-another-config to try and eliminate the  
pci_abort problem. This time I've reworked my USB bus so I only need  
uhci-hcd instead of uhci-hcd and ehci-hcd. I also rebuilt the dvb-v4l  
kernel modules so that only the modules I need are built and loaded.  
Previously the build all frontends option was enabled. That was  
kind of ugly if not effective :)


[EMAIL PROTECTED] ~ $ lsmod | grep cx88
cx88_dvb2628  21
cx8802  4868  1 cx88_dvb
cx88xx 39588  2 cx88_dvb,cx8802
ir_common  17604  1 cx88xx
i2c_algo_bit5576  1 cx88xx
btcx_risc   1992  2 cx8802,cx88xx
tveeprom9360  1 cx88xx
video_buf_dvb   2116  1 cx88_dvb
video_buf  11588  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
lgdt330x4252  1 cx88_dvb


I really appreciate all the help from the list.

--
Scott

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] cx88 pci_abort messages

2006-09-20 Thread Scott

On Sep 19, 2006, at 7:12 PM, Peter Fern wrote:

Scott wrote:

I have a FusionHDTV5 Gold RT running under Gentoo and vanilla kernel
2.6.18-rc7. The drivers load and I can view OTA ATSC streams using
mplayer.

I'm seeing the following message log:

cx88[0]: irq mpeg  [0x8] pci_abort*
cx88[0]/2: general errors: 0x0008

What can cause these messages? Are the safe to ignore? Some output
from my logs and lspci:


These are generally caused by another device stealing the IRQ from the
tuner card, and this is likely to cause corruption in your MPEG  
stream.

To find out what devices the card is sharing an interrupt with, `cat
/proc/interrupts`.  Shuffle the card around until it's not sharing any
more, or
until it's sharing with a device that has sensible interrupt handling.


I'm continuing to troubleshoot the above problem. Since I was seeing  
this under 2.6.18-r7 and 2.6.17-r8-gentoo (uses a slightly older  
version of linux-dvb and cx88 driver) I've moved back to using the  
2.6.17-r8-gentoo kernel. That of course didn't make to much of a  
difference, I didn't expect it to.


As suggested, I moved the card to another PCI slot. Now, instead of  
sharing an IRQ with the onboard Intel HDA audio, the card shares an  
IRQ with two USB controllers. That shouldn't be to bad. The only  
items on the USB bus are an LCD/IR imon receiver and other unused hub  
devices. But I still see the pci_abort messages while using the  
FusionHDTV5 Gold RT card to capture capture or view video. This is  
seen using either MythTV or mplayer.


So I'm wondering, what _else_ besides a device hogging the PCI bus  
might cause the above errors? I did find that by playing around in  
bios and setting my DDR2 667 memory to DDR2 533 and changing the  
default PCI bus latency from 64 to 32 seemed to help things out  
greatly. I still see the errors, but I don't see dozens of errors  
every few seconds now.


Any suggestions? Appreciate all the help!

--
Scott

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


RE: [linux-dvb] cx88 pci_abort messages

2006-09-20 Thread Lincoln Dale
 I'm continuing to troubleshoot the above problem. Since I was seeing
 this under 2.6.18-r7 and 2.6.17-r8-gentoo (uses a slightly older
 version of linux-dvb and cx88 driver) I've moved back to using the
 2.6.17-r8-gentoo kernel. That of course didn't make to much of a
 difference, I didn't expect it to.

i'd suggest you try latest 2.6.18  perhaps combine it with dvb-v4l
tip-of-tree.

 As suggested, I moved the card to another PCI slot. Now, instead of
 sharing an IRQ with the onboard Intel HDA audio, the card shares an
 IRQ with two USB controllers. That shouldn't be to bad. The only
 items on the USB bus are an LCD/IR imon receiver and other unused hub
 devices. But I still see the pci_abort messages while using the
 FusionHDTV5 Gold RT card to capture capture or view video. This is
 seen using either MythTV or mplayer.

most motherboard bioses allow you to configure explicit IRQs for different
PCI slots.  you should be able to find a combination where at least cx88
doesn't share its IRQ with any other device.

 So I'm wondering, what _else_ besides a device hogging the PCI bus
 might cause the above errors? 

from personal experience, i've found in the past that i got cx88_abort
errors where something had (incorrectly) put an incorrect card=XX into
/etc/modprobe.conf - so the card wasn't being autodetected but instead was
being forced to something it wasn't.

you may want to verify that it is indeed autodetecting it and/or 'dmesg'
output shows that it _is_ the correct card.

of course, when i had the incorrect setting, tuning via tzap didn't work.
(well - it did - it would lock on but never actually tune to what you
asked... presumably just locked onto what it was previously set to..).


cheers,

lincoln.


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] cx88 pci_abort messages

2006-09-20 Thread Scott


On Sep 20, 2006, at 11:05 PM, Lincoln Dale wrote:


I'm continuing to troubleshoot the above problem. Since I was seeing
this under 2.6.18-r7 and 2.6.17-r8-gentoo (uses a slightly older
version of linux-dvb and cx88 driver) I've moved back to using the
2.6.17-r8-gentoo kernel. That of course didn't make to much of a
difference, I didn't expect it to.


i'd suggest you try latest 2.6.18  perhaps combine it with dvb-v4l
tip-of-tree.


2.6.18-rc7 was the most recent available snapshot as of 48hrs ago and  
I didn't see any differences. I didn't try to use linux-dvb tip  
though. I did look at the code differences between linux-dvb in  
2.6.18-rc7 and dvb-tip. It looked like it was mostly refactoring and  
I saw nothing to indicate new support. I could be wrong.


most motherboard bioses allow you to configure explicit IRQs for  
different
PCI slots.  you should be able to find a combination where at least  
cx88

doesn't share its IRQ with any other device.


I'm fairly sure that the current Asus P5B bios does not allow for  
this. Of course, I'll double check it, and,I could always achieve the  
same result by disabling onboard audio in the BIOS and testing the  
card on it's dedicated irq. It's something new to try but I don't  
have much hope for it.


I don't see how it's current shared IRQ with a _very_ lightly loaded  
USB hub would be causing the problems I'm seeing. Prior to the  
current slot it was sharing an IRQ with the onboard audio. If I'm not  
playing any sound, don't have the audio portion of the dvb card  
loaded, and I'm capturing an ATSC stream which has the audio embedded  
right into it, I don't see how the onboard audio could be stealing  
the IRQ.



from personal experience, i've found in the past that i got cx88_abort
errors where something had (incorrectly) put an incorrect card=XX into
/etc/modprobe.conf - so the card wasn't being autodetected but  
instead was

being forced to something it wasn't.


This is a good suggestion. From dmesg:

cx2388x dvb driver version 0.0.5 loaded
CORE cx88[0]: subsystem: 18ac:d500, board: DViCO FusionHDTV 5 Gold  
[card=31,autodetected]

TV tuner 64 at 0x1fe, Radio tuner -1 at 0x1fe
ACPI: PCI Interrupt :04:02.2[A] - Link [LNKH] - GSI 7 (level,  
low) - IRQ 7
cx88[0]/2: found at :04:02.2, rev: 5, irq: 7, latency: 32, mmio:  
0xfd00

cx88[0]/2: cx2388x based dvb card
DVB: registering new adapter (cx88[0]).
DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM  
Frontend)...


This seems to match my actual device which is the FusionHDTV 5 RT  
Gold. I had read that the FusionHDTV5 RT Gold and the FusionHDTV5  
Gold Plus were actually identical boards. The chips seemed to match  
up with the modules and the dvb-v4l tables I've seen.


04:02.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and  
Audio Decoder [MPEG Port] (rev 05)

Subsystem: DViCO Corporation DViCO FusionHDTV5 Gold
Flags: bus master, medium devsel, latency 32, IRQ 7
Memory at fd00 (32-bit, non-prefetchable) [size=16M]


Thanks for the help!

--
Scott

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


RE: [linux-dvb] cx88 pci_abort messages

2006-09-20 Thread Lincoln Dale
 DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM
 Frontend)...
 
 This seems to match my actual device which is the FusionHDTV 5 RT
 Gold. I had read that the FusionHDTV5 RT Gold and the FusionHDTV5
 Gold Plus were actually identical boards. The chips seemed to match
 up with the modules and the dvb-v4l tables I've seen.
 
 04:02.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and
 Audio Decoder [MPEG Port] (rev 05)
  Subsystem: DViCO Corporation DViCO FusionHDTV5 Gold
  Flags: bus master, medium devsel, latency 32, IRQ 7
  Memory at fd00 (32-bit, non-prefetchable) [size=16M]

in my case, a DViCO FusionHDTV DVB-T1 was being set to a FusionHDTV
DVB-T-Plus - and these were sufficiently different

if you're physically looking at the PCI card, maybe check that the frontend
is indeed a LG LGDT3303...


cheers,

lincoln.


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] cx88 pci_abort messages

2006-09-19 Thread Peter Fern
Scott wrote:
 Greets.

 I have a FusionHDTV5 Gold RT running under Gentoo and vanilla kernel
 2.6.18-rc7. The drivers load and I can view OTA ATSC streams using
 mplayer.

 I'm seeing the following message log:

 cx88[0]: irq mpeg  [0x8] pci_abort*
 cx88[0]/2: general errors: 0x0008

 What can cause these messages? Are the safe to ignore? Some output
 from my logs and lspci:

These are generally caused by another device stealing the IRQ from the
tuner card, and this is likely to cause corruption in your MPEG stream. 
To find out what devices the card is sharing an interrupt with, `cat
/proc/interrupts`.  Shuffle the card around until it's not sharing any
more, or
until it's sharing with a device that has sensible interrupt handling.

Cheers,
Pete

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


Re: [linux-dvb] cx88 pci_abort messages

2006-09-19 Thread Scott


On Sep 19, 2006, at 7:12 PM, Peter Fern wrote:


Scott wrote:

Greets.

I have a FusionHDTV5 Gold RT running under Gentoo and vanilla kernel
2.6.18-rc7. The drivers load and I can view OTA ATSC streams using
mplayer.

I'm seeing the following message log:

cx88[0]: irq mpeg  [0x8] pci_abort*
cx88[0]/2: general errors: 0x0008

What can cause these messages? Are the safe to ignore? Some output
from my logs and lspci:


These are generally caused by another device stealing the IRQ from the
tuner card, and this is likely to cause corruption in your MPEG  
stream.

To find out what devices the card is sharing an interrupt with, `cat
/proc/interrupts`.  Shuffle the card around until it's not sharing any
more, or
until it's sharing with a device that has sensible interrupt handling.


Okay, this is kind of what I expected. My problem is the only pci  
slot with a dedicated irq on the asus p5b is next to the pcie x16  
slot and is being blocked by a large heat sink on my video card. You  
can only plan for so much when building a pc... (I knew the pci slot  
would be blocked but did not realize it would be the only slot with a  
dedicated irq!)


Currently the dvb board is sharing an irq with the onboard audio.  
Since the audio isn't in use when I'm not watching any content this  
should be okay. The other option is to share it with the some usb  
devices. I also have set elevator=cfq. Maybe this is the real cause  
of my problems?


Any suggestions on how to find out which device is hogging the irqs?  
I've been looking through kernel docs but most of it is api info. :)


Appreciate the help!

--
Scott

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb