On Sat, Oct 29, 2005 at 07:52:40PM +0200, Hans Verkuil wrote:
> Can you move the card to another slot (and so to another IRQ number)? If the 
> same problem occurs, then it does seem as if something might be wrong in the 
> driver, but it could very well be caused by something else.

Yes and no... my MB has 3 PCI slots, and whichever slot I put the card
in, it still ends up on IRQ 9 or 10 shared with acpi (although the
other devices sharing the interrupt differ).  The bios doesn't allow
explicit assignment of interrupts to be sure it's on its own IRQ.
Whichever slot the card is in, the IRQ gets disabled within 24 hours if
"ondemand" is on.  Works great with "userspace" and cpudyn, so I've
gone back to that.  It seems just as likely that the bug is elsewhere
as in ivtv, so I'm just posting this followup in case others are
running into the same problem.

JMC

For reference, here's my current IRQ assignment:
> cat /proc/interrupts 
           CPU0       
  0:   39236406          XT-PIC  timer
  1:         10          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
  9:   14175025          XT-PIC  acpi, ivtv0, SiS SI7012
 11:    3240013          XT-PIC  ehci_hcd:usb1, eth0
 12:        110          XT-PIC  i8042
 14:    1119721          XT-PIC  ide0
 15:     250771          XT-PIC  ide1
NMI:          0 
ERR:      45087

vs the one I reported before:
> > > cat /proc/interrupts
> >
> >            CPU0
> >   0:   48513481          XT-PIC  timer
> >   1:         10          XT-PIC  i8042
> >   2:          0          XT-PIC  cascade
> >   5:          0          XT-PIC  ehci_hcd:usb1
> >   8:          1          XT-PIC  rtc
> >   9:   16830118          XT-PIC  acpi, ivtv0
> >  11:     629701          XT-PIC  eth0, SiS SI7012
> >  12:        110          XT-PIC  i8042
> >  14:     636422          XT-PIC  ide0
> > NMI:          0
> > ERR:      49590

-- 
John-Marc Chandonia ([EMAIL PROTECTED])
http://www.dolorespark.org/

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

Reply via email to