On Tuesday 28 August 2007 11:18:10 am David Engel wrote: > Hi, > > While investigating another problem, I noticed some suspicious log > messages that occurred at the beginning of MythTV recordings. Here's > some examples. > > Aug 27 14:50:03 tux kernel: tda9887 4-0042: i2c i/o error: rc == -121 > (should be 4) Aug 27 18:59:57 tux kernel: tda9887 3-0042: i2c i/o error: rc > == -121 (should be 4) Aug 27 20:00:03 tux kernel: tda9887 3-0042: i2c i/o > error: rc == -121 (should be 4) > > Going back in my logs, this has happened at the beginning of every > recording since switching from the 0.10.6 driver in the the 2.6.21.7 > kernel to the one included in the 2.6.22.2+ kernel. I'm attaching the > relavant section of kern.log from my last reboot in case it provides > any help. > > I haven't noticed any bad recordings, so perhaps this is harmless. > Should I be concerned aobut it, or should I take it up on the V4L > lists?
This sounds vaguely like the i2c bug that hit some lirc users... I2C_NAME_SIZE was reduced from 50 to 20 in 2.6.22, but some lirc drivers were doing strcpy of strings longer than 20 chars for i2c devices... -- Jarod Wilson [EMAIL PROTECTED] _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
