[linux-dvb] System load raises when budget_av is loaded

Oliver Endriss o.endriss at gmx.de
Sun Aug 19 15:54:06 CEST 2007


e9hack wrote:
> Oliver Endriss schrieb:
> >> It seems, the delay of 100usec is too short. During booting of the ARM,
> >> DEBI_E is set for ca. 360usec after some debi commands. I've changed the
> >> delay to 500usec. The load average is dropped from 0.65 to 0.0 with
> >> budget_av and dvb_ttpci loaded and vdr isn't running.
> > 
> > With this patch I get random error messages from av7110_debiread|write:
> > 
> > | Aug 19 01:26:05 orion kernel: av7110_debiread: wait_for_debi_done #1 failed
> > | Aug 19 01:26:05 orion kernel: av7110_debiwrite: wait_for_debi_done failed
> > 
> 
> I saw the same messages, if I used a too short delay (100usec). For testing, I printed out the time,
> while the DEBI_E was active.
> 
> Startup of the TT-C2300:
> Aug 19 08:53:38 darkstar kernel: Linux video capture interface: v2.00
> Aug 19 08:53:38 darkstar kernel: saa7146: register extension 'dvb'.
> Aug 19 08:53:38 darkstar kernel: ACPI: PCI Interrupt 0000:04:06.0[A] -> Link [LNKA] -> GSI 17
> (level, low) -> IRQ 22
> Aug 19 08:53:38 darkstar kernel: saa7146: found saa7146 @ mem fab6ec00 (revision 1, irq 22)
> (0x13c2,0x000a).
> Aug 19 08:53:38 darkstar kernel: DVB: registering new adapter (Technotrend/Hauppauge WinTV Nexus-CA
> rev1.X)
> Aug 19 08:53:38 darkstar kernel: adapter has MAC addr = ??:??:??:??:??:??
> Aug 19 08:53:38 darkstar kernel: (saa7146_core.c:136) saa7146 (0): SEBI_E was active for 30usec
> Aug 19 08:53:38 darkstar kernel: (saa7146_core.c:136) saa7146 (0): SEBI_E was active for 360usec
> Aug 19 08:53:38 darkstar kernel: (saa7146_core.c:136) saa7146 (0): SEBI_E was active for 360usec
> Aug 19 08:53:38 darkstar kernel: (saa7146_core.c:136) saa7146 (0): SEBI_E was active for 360usec
> Aug 19 08:53:38 darkstar kernel: (saa7146_core.c:136) saa7146 (0): SEBI_E was active for 360usec
> Aug 19 08:53:38 darkstar kernel: (saa7146_core.c:136) saa7146 (0): SEBI_E was active for 360usec
> Aug 19 08:53:38 very-new-darkstar kernel:
> 
> 
> vdr is running:
> Aug 19 08:59:33 darkstar kernel: (saa7146_core.c:132) saa7146 (1): SEBI_E was active for 38(253)msec
> Aug 19 08:59:33 darkstar kernel: (saa7146_core.c:132) saa7146 (1): SEBI_E was active for 38(253)msec
> Aug 19 08:59:33 darkstar kernel: (saa7146_core.c:136) saa7146 (0): SEBI_E was active for 20usec
> Aug 19 08:59:33 darkstar kernel: (saa7146_core.c:132) saa7146 (1): SEBI_E was active for 38(253)msec
> Aug 19 08:59:34 darkstar kernel: (saa7146_core.c:132) saa7146 (1): SEBI_E was active for 38(253)msec
> Aug 19 08:59:34 darkstar kernel: (tda10021.c:305) ckoff=26, sroffset=672, sr=6900000
> Aug 19 08:59:34 darkstar kernel: (saa7146_core.c:136) saa7146 (0): SEBI_E was active for 30usec
> Aug 19 08:59:34 darkstar kernel: (tda10021.c:305) ckoff=0, sroffset=0, sr=6900672
> Aug 19 08:59:34 darkstar kernel: (saa7146_core.c:132) saa7146 (1): SEBI_E was active for 38(253)msec
> Aug 19 08:59:34 darkstar kernel: (saa7146_core.c:132) saa7146 (1): SEBI_E was active for 38(253)msec
> Aug 19 08:59:35 darkstar kernel: (saa7146_core.c:132) saa7146 (1): SEBI_E was active for 38(253)msec
> Aug 19 08:59:35 darkstar kernel: (saa7146_core.c:136) saa7146 (0): SEBI_E was active for 110usec
> 
> The longest time from the TT-C2300 was 370us. The Cinergy does always timeout with a debi error.
> I've used the attached patch.

For full-featured cards it may take some time until the debi transfer
has completed, because those cards use debi dma.

I wonder
- why the error bit gets set at all, and.
- whether the debi status bits are updated before the transfer has
  been completed/stopped.

I'll try to look into this next week.

Oliver

-- 
----------------------------------------------------------------
VDR Remote Plugin 0.3.9: http://www.escape-edv.de/endriss/vdr/
----------------------------------------------------------------




More information about the linux-dvb mailing list