<div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">---------- Missatge reenviat ----------<br>From:&nbsp;thomas schorpp &lt;<a href="mailto:thomas.schorpp@googlemail.com">thomas.schorpp@googlemail.com</a>&gt;<br>
To:&nbsp;linux-dvb &lt;<a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a>&gt;<br>Date:&nbsp;Fri, 22 Aug 2008 11:41:49 +0200<br>Subject:&nbsp;Re: [linux-dvb] New firmware for dib0700 (Nova-T-500 and others)<br>Nicolas Will wrote:<br>

<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
All,<br>
<br>
There is a new firmware file fixing the last cause for i2c errors and<br>
disconnects and providing a new, more modular i2c request formatting.<br>
<br>
</blockquote>
<br>
this is not firmware since it does not occur with the &quot;other OS&quot; and it&#39;s gone better upgrading 2.6.24-&gt;<a href="http://2.6.26.2" target="_blank">2.6.26.2</a> but the driver is still buggy:<br>
<br>
do lsusb and...<br>
<br>
INFO: task khubd:1966 blocked for more than 120 seconds.<br>
&quot;echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs&quot; disables this message.<br>
khubd &nbsp; &nbsp; &nbsp; &nbsp; D ffff81003dca9bc0 &nbsp; &nbsp; 0 &nbsp;1966 &nbsp; &nbsp; &nbsp;2<br>
ffff81003dca9bb0 0000000000000046 ffff81003eeb6220 ffff81003f0ea7d0<br>
ffff81003eeb6478 ffff81003eeb6478 ffff81003dca9b90 ffffffff80245e8f<br>
ffff81003dca9bb0 ffff81003dd33800 ffff81003dca9bc0 0000000000000000<br>
Call Trace:<br>
[&lt;ffffffff80245e8f&gt;] ? kthread_stop+0x7f/0x90<br>
[&lt;ffffffffa0099645&gt;] :dvb_core:dvb_unregister_frontend+0xb5/0x100<br>
[&lt;ffffffff80246150&gt;] ? autoremove_wake_function+0x0/0x40<br>
[&lt;ffffffffa021bf0d&gt;] :dvb_usb:dvb_usb_adapter_frontend_exit+0x1d/0x40<br>
[&lt;ffffffffa021b42c&gt;] :dvb_usb:dvb_usb_exit+0x4c/0xe0<br>
[&lt;ffffffffa021b505&gt;] :dvb_usb:dvb_usb_device_exit+0x45/0x60<br>
[&lt;ffffffffa00f3e47&gt;] :usbcore:usb_unbind_interface+0x47/0x90<br>
[&lt;ffffffff804cd57d&gt;] __device_release_driver+0x9d/0xe0<br>
[&lt;ffffffff804cd70b&gt;] device_release_driver+0x2b/0x40<br>
[&lt;ffffffff804cc9e5&gt;] bus_remove_device+0xb5/0xf0<br>
[&lt;ffffffff804cb133&gt;] device_del+0x123/0x190<br>
[&lt;ffffffffa00f1054&gt;] :usbcore:usb_disable_device+0x94/0x120<br>
[&lt;ffffffffa00ec233&gt;] :usbcore:usb_disconnect+0xb3/0x140<br>
[&lt;ffffffffa00ecf2e&gt;] :usbcore:hub_thread+0x37e/0x1210<br>
[&lt;ffffffff80209ccf&gt;] ? __switch_to+0x1f/0x3b0<br>
[&lt;ffffffff80246150&gt;] ? autoremove_wake_function+0x0/0x40<br>
[&lt;ffffffffa00ecbb0&gt;] ? :usbcore:hub_thread+0x0/0x1210<br>
[&lt;ffffffff80245bd9&gt;] kthread+0x49/0x80<br>
[&lt;ffffffff8020c1e8&gt;] child_rip+0xa/0x12<br>
[&lt;ffffffff80245b90&gt;] ? kthread+0x0/0x80<br>
[&lt;ffffffff8020c1de&gt;] ? child_rip+0x0/0x12<br>
<br>
y<br>
tom<br>
</blockquote></div><br><br>By the reports here it seems better to wait and keep using the old 1.10 file, which has been rock solid these last months.<br>By the way, could you confirm also the continuos reboots that Nicolas told us about with this file?<br>
<br>Regards, <br>&nbsp;&nbsp; Eduard Huguet<br><br><br><br><br></div>