On Wed, Feb 20, 2008 at 4:14 PM, hermann pitton <[EMAIL PROTECTED]> wrote: > Hi Nico, > > Am Mittwoch, den 20.02.2008, 07:12 +0000 schrieb Nicolas Will: > > > On Wed, 2008-02-20 at 01:12 +0100, hermann pitton wrote: > > > > Now stop that logging madness and get back to work! > > > > > > > > ... > > > > > > > > ;o) > > > > > > > > > > > > This is a rather comical situation, though... The debugging tool is > > > > providing a rather unexpected and unwelcomed fix. > > > > > > > > Nico > > > > > > > > > > Hi, > > > > > > no, it is not. It is well known! > > > > > > Timings are very critical on almost all drivers. > > > > > > We hold breath on almost everything coming down from above, nobody has > > > the ability, or whom should ever want it, to test all possible side > > > effects on all supported devices ... > > > > > > That something breaks is very common, and that others have to give the > > > plumbers, is nothing new. > > > > > > To stay fair, it mostly has a good reason, and if there are some > > > remaining ticks left, you might get it adjusted, but ... > > > > > > On the other side it is the same ... > > > > May post may have sounded offensive, apparently. > > > > Sorry about that, my intentions were on the lighter sides of life. > > > > Nico > > > > nothing offending at all, did enjoy your above comment :) > and like your active support for others. > > It is just not totally unexpected that high debug levels can have some > spin-off and I'm curious about it. > > Cheers, > Hermann > > > > > _______________________________________________ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >
Kernel 2.6.24-2 Debug=15 Got this after 5 minutes of LiveTV: (Dunno if it could be usefull or not) modifying (1) streaming state for 1 data for streaming: 10 13 >>> 0f 10 13 00 usb 10-1: USB disconnect, address 2 >>> 03 14 03 01 60 00 ep 0 write error (status = -19, len: 6) mt2060 I2C write failed >>> 03 14 04 07 ff ff ep 0 write error (status = -19, len: 6) >>> 03 14 04 08 ff ff ep 0 write error (status = -19, len: 6) >>> 03 14 04 09 ff f0 ep 0 write error (status = -19, len: 6) >>> 02 17 81 fd ep 0 read error (status = -19) <<< 77 8d I2C read failed on address b >>> 02 17 81 ca ep 0 read error (status = -19) <<< 00 20 I2C read failed on address b >>> 02 17 81 fd ep 0 read error (status = -19) <<< 77 8d I2C read failed on address b >>> 02 17 81 fd ep 0 read error (status = -19) <<< 77 8d I2C read failed on address b >>> 02 17 81 fd ep 0 read error (status = -19) <<< 77 8d I2C read failed on address b >>> 02 17 81 fd ep 0 read error (status = -19) <<< 77 8d I2C read failed on address b >>> 02 17 81 fd ep 0 read error (status = -19) <<< 77 8d I2C read failed on address b >>> 02 17 81 fd ep 0 read error (status = -19) <<< 77 8d I2C read failed on address b >>> 02 17 81 fd ep 0 read error (status = -19) <<< 77 8d I2C read failed on address b _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb