[pvrusb2] pvrusb2-dev-0c73d0aa725b

[Mike Isely]

Martin:

We need to figure out if this is kernel-specific or something in the 
v4l-dvb repo.  Right now all I can tell you is what I think I said 
before: the tda9887 module appears to be reporting an I/O error when it 
thinks it should have transferred 4 bytes over I2C.  Obviously if the 
pvrusb2 driver's I2C adapter were broken we'd be seeing A LOT more 
problems than this.  So the tda9887 module might be doing something 
wrong.

I haven't seen this problem HOWEVER I haven't really tried that hard 
yet, and I'm not running under 2.6.29 yet.  This could be specific to 
that kernel.  Any chance you could try this with the same v4l-dvb under 
2.6.27.x?

  -Mike


On Sun, 10 May 2009, Martin Dauskardt wrote:

> Hi Mike,
> 
> I am currently testing your latest hg snapshot with a 2.6.29 kernel.
> 
> There is the same problem I noticed with older drivers from April:
> 
> [   23.416616] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   23.419605] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   23.543003] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   23.546750] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   23.747292] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   23.774541] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   23.956073] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   23.957570] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   23.960445] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   26.640770] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   26.644641] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   26.777423] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   63.445509] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   65.281437] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   66.988846] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   69.052181] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   70.499326] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   72.572142] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   74.546719] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   76.318888] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [   78.090329] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  100.009212] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  101.962395] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  104.185785] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  107.161885] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  109.230875] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  109.232477] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  109.235352] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  109.302618] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  117.956809] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  117.960555] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  162.813248] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  162.814743] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  162.817745] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  168.826624] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  168.837878] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  172.321837] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  172.323452] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  172.326457] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  176.675808] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  176.679670] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  181.258949] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> [  183.027602] tda9887 0-0043: i2c i/o error: rc == -5 (should be 4)
> 
> My first impression was that it is only a "cosmetic" error. But now I 
> discovered a problem that may be related: When switching from the radio input 
> to TV input I have very often no sound. (I am not closing the device, so 
> there is no encoder stop.) Switching to another TV channel brings back the 
> audio.
> 
> I checked an older kernel (2.6.25.11) with a v4l-dvb hg from September 2008. 
> It does not have these problems.
> 
> Any idea?
> 
> Greets,
> Martin
> _______________________________________________
> pvrusb2 mailing list
> pvrusb2 at isely.net
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
> 

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8