Deti Fliegl wrote:
>This happens when unplugging a cinergyT2:
> Sep 28 20:02:40 dvbmon kernel: Call
> Trace:<ffffffff883f4401>{:cinergyT2:cinergyt2_query+113}
> <ffffffff8014369f>{worker_thread+415}
Looks like canceling the query_work thread is not done on disconnect.
Something like this should fix the problem:
--- cinergyT2.c~ 2005-10-05 20:08:27.000000000 +0200
+++ cinergyT2.c 2005-10-05 20:08:27.000000000 +0200
@@ -887,6 +887,7 @@
input_unregister_device(&cinergyt2->rc_input_dev);
#endif
+ cancel_delayed_work(&cinergyt2->query_work);
cinergyt2->demux.dmx.close(&cinergyt2->demux.dmx);
dvb_net_release(&cinergyt2->dvbnet);
dvb_dmxdev_release(&cinergyt2->dmxdev);
But still a problem with cinergy T2 remains: After 2-3 days of
continuous access to the device it does not answer on frontend
commands... therfore no tuning is possible etc. On VDR is looks like:
"ERROR: frontend 1: Connection timed out" or "ERROR: frontend 2: Value
too large for defined data type"
Can anyone please confirm/comment/explain/fix this problem?
Deti
