Re: [linux-dvb] Very quiet around Nova-T 500
On Wed, Feb 20, 2008 at 4:14 PM, hermann pitton [EMAIL PROTECTED] wrote: Hi Nico, Am Mittwoch, den 20.02.2008, 07:12 + 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
Re: [linux-dvb] Very quiet around Nova-T 500
The strange thing is that modinfo does not say anything about a level 15 debug for the dvb_usb_dib0700 module. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700 The debug value is a bit field, with each bit representing a different category. With all bits on (ie full debugging) the decimal value becomes 15. // J ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
On Wed, 2008-02-20 at 10:36 +0100, Jonas Anden wrote: The strange thing is that modinfo does not say anything about a level 15 debug for the dvb_usb_dib0700 module. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700 The debug value is a bit field, with each bit representing a different category. With all bits on (ie full debugging) the decimal value becomes 15. I should have guessed. Documented for poor souls with slow brains like me. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
On Wed, 2008-02-20 at 08:38 +0100, Patrik Hansson wrote: On 2/19/08, Jonas Anden [EMAIL PROTECTED] wrote: There is not a lot being said about the Nova-T 500 the last week. Don´t know if that is a good (coders coding) or a bad (nothin happening) Or coders busy on other code, or coders who ran out of ideas, or coders enjoying life, etc. ..or just waiting for the problem to reappear ;( The trouble with the second tuner dying is tricky (for me) to isolate. As a workaround, enabling full debug (debug=15) on the dvb_usb_dib0700 module has made my system rock solid. I turned on debugging to try to isolate the issue, but with debugging enabled the problem does not appear (at least not on my system). I haven't really figured out *what* in the debug code is helping yet, but I still suspect that this is timing-related and the debug code simply slows things down a bit. Enabling debugging will put a whole lot of junk in your system log files, but at least the second tuner wont die on you. If you go this path, make sure your log rotation works as it should -- my weekly rotated logs are up to 130 MB in size ;) // J Could someone that knows what they are doing document that option on the wiki ? Corrected. The strange thing is that modinfo does not say anything about a level 15 debug for the dvb_usb_dib0700 module. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700 Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
I have now set the debug to 15 and will test this tonight. On 2/20/08, Nicolas Will [EMAIL PROTECTED] wrote: On Wed, 2008-02-20 at 10:36 +0100, Jonas Anden wrote: The strange thing is that modinfo does not say anything about a level 15 debug for the dvb_usb_dib0700 module. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700 The debug value is a bit field, with each bit representing a different category. With all bits on (ie full debugging) the decimal value becomes 15. I should have guessed. Documented for poor souls with slow brains like me. Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
Hi Nico, Am Mittwoch, den 20.02.2008, 07:12 + 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
Re: [linux-dvb] Very quiet around Nova-T 500
On Tue, 2008-02-19 at 22:56 +0100, Jonas Anden wrote: There is not a lot being said about the Nova-T 500 the last week. Don´t know if that is a good (coders coding) or a bad (nothin happening) Or coders busy on other code, or coders who ran out of ideas, or coders enjoying life, etc. ..or just waiting for the problem to reappear ;( The trouble with the second tuner dying is tricky (for me) to isolate. As a workaround, enabling full debug (debug=15) on the dvb_usb_dib0700 module has made my system rock solid. I turned on debugging to try to isolate the issue, but with debugging enabled the problem does not appear (at least not on my system). I haven't really figured out *what* in the debug code is helping yet, but I still suspect that this is timing-related and the debug code simply slows things down a bit. Enabling debugging will put a whole lot of junk in your system log files, but at least the second tuner wont die on you. If you go this path, make sure your log rotation works as it should -- my weekly rotated logs are up to 130 MB in size ;) 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 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
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 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
On 2/19/08, Jonas Anden [EMAIL PROTECTED] wrote: There is not a lot being said about the Nova-T 500 the last week. Don´t know if that is a good (coders coding) or a bad (nothin happening) Or coders busy on other code, or coders who ran out of ideas, or coders enjoying life, etc. ..or just waiting for the problem to reappear ;( The trouble with the second tuner dying is tricky (for me) to isolate. As a workaround, enabling full debug (debug=15) on the dvb_usb_dib0700 module has made my system rock solid. I turned on debugging to try to isolate the issue, but with debugging enabled the problem does not appear (at least not on my system). I haven't really figured out *what* in the debug code is helping yet, but I still suspect that this is timing-related and the debug code simply slows things down a bit. Enabling debugging will put a whole lot of junk in your system log files, but at least the second tuner wont die on you. If you go this path, make sure your log rotation works as it should -- my weekly rotated logs are up to 130 MB in size ;) // J ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Could someone that knows what they are doing document that option on the wiki ? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
On Mon, 2008-02-11 at 21:07 +0100, Patrik Hansson wrote: Hello There is not a lot being said about the Nova-T 500 the last week. Don´t know if that is a good (coders coding) or a bad (nothin happening) Or coders busy on other code, or coders who ran out of ideas, or coders enjoying life, etc. but i would like to know if there is anything we could do ? I can´t write code but maybe i can help in some other way ? Testing builds or whatever. Frustrating, heh? I took up documenting in the wiki as a way of contributing back, somehow... Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
