Ricardo, thanks for you input.  I tried this out tonight and found
that it really did not help.  Let me tell you what I did so I make
sure this is what you ment.

Aug 22 21:54:12 samwise kernel: ivtv0 warning: 1000 ms time out
waiting for firmware
Aug 22 21:54:12 samwise kernel: ivtv0 warning: Failed api call
0x00000082 with result 0xfffffff0
Aug 22 21:54:12 samwise kernel: ivtv0 warning: ENC: Failed stopping capture -16
Aug 22 21:54:20 samwise kernel: ivtv0 warning: 1000 ms time out
waiting for firmware
Aug 22 21:54:20 samwise kernel: ivtv0 warning: Failed api call
0x00000082 with result 0xfffffff0
Aug 22 21:54:20 samwise kernel: ivtv0 warning: ENC: Failed stopping capture -16

I did not recompile the kernel, howver, I did $ chkconfig irqbalance off
I am not sure if the card is sharing an irq.  When I look at
/proc/interefupts here is what I see.
           CPU0       CPU1
  0:     182705          0    IO-APIC-edge  timer
  1:       1641          0    IO-APIC-edge  i8042
  7:          1          0    IO-APIC-edge  parport0
  8:          0          0    IO-APIC-edge  rtc
  9:          0          0   IO-APIC-level  acpi
 14:       6877          0    IO-APIC-edge  ide0
 58:       4905          0   IO-APIC-level  ohci_hcd:usb1
 66:       5314          0   IO-APIC-level  ivtv0
 74:      59313          0   IO-APIC-level  nvidia
 82:          3          0   IO-APIC-level  bttv0, Bt87x audio
 90:        547          0       PCI-MSI-X  eth0
 98:        558          0       PCI-MSI-X  eth0
106:      71347          0       PCI-MSI-X  eth0
225:         76          0   IO-APIC-level  libata, ehci_hcd:usb2
233:      25954          0   IO-APIC-level  libata, HDA Intel
NMI:        120         77
LOC:     182677     182654
ERR:          0
MIS:          0

echo "1" > /proc/irq/`grep ivtv /proc/interrupts  | awk -F: '{print
$1}' | sed -e 's/ //g'`/smp_affinity
# cat /proc/irq/66/smp_affinity
00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001

# lspci -v -s 01:00.0
01:00.0 Multimedia video controller: Internext Compression Inc iTVC16
(CX23416) MPEG-2 Encoder (rev 01)
        Subsystem: Hauppauge computer works Inc. Unknown device 8801
        Flags: bus master, medium devsel, latency 64, IRQ 66
        Memory at cc000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2

My 250GB hard disk gets here tomorrow so I will be loading FC4 x86 and
x86_64 to do some testing.  I might also try FC5 x86 as well like Tim
mentioned.

Thanks for your help.  This was a really good idea to try.

Keith
On 8/21/06, Tim Berger <[EMAIL PROTECTED]> wrote:
>
> On 8/21/06, Ricardo Lugo <[EMAIL PROTECTED]> wrote:
>
>
>
> >
> >
> > Keith,
> >
> >
> > I have had some success minimizing these kinds of problems on my SMP 
> > machine by tweaking my machine's IRQs. If any devices share your ivtv 
> > card's IRQ, remove / shuffle the cards until you have a good config where 
> > the card has its own IRQ.
>
>
>
> Ricardo, was this on 64bit as well?  Because it's looking to me like some 
> 64bit bug was introduced after 0.6.1.  If people on 64bit  are only having 
> trouble after this version but with 32bit are ok, then can this still be IRQ 
> related?  On my machine, ivtv0 and ivtv1 have their own, non-shared 
> interrupts.
>
> I never looked at the source before this evening, but it looks like 
> ivtv_pause_encoder() was completely ripped out and replaced with some new api 
> call ivtv_vapi().  Maybe that has somethig to do with it?  I really have no 
> idea.  Something new has caused the firmware to go out to lunch though (or 
> appear to be out to lunch), and only on dual core 64bit as far as I can tell.
>
> Maybe I'll just punt and reinstall with FC5 32bit.  I wonder how many people 
> out there have had ivtv success with an athlon X2, and 64bit disto.  Please 
> let me know off-list. Thx.
>
> -snip-
>
> --
>
>  -Tim
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to