Hung U4

[Grumpy_Geoff]

Any idea on the below entries from the "messages" file from the time of the hang (according to last update time of the debug log)?

Code: Select all

May 17 12:20:11 beyonwizu4 user.err kernel: INFO: task enigma2:860 blocked for more than 120 seconds.
May 17 12:20:11 beyonwizu4 user.err kernel:       Tainted: G           O    4.9.51 #1
May 17 12:20:11 beyonwizu4 user.err kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 17 12:20:11 beyonwizu4 user.info kernel: enigma2         D    0   860    834 0x00000000
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0cac6f8>] (__schedule) from [<c0cacaac>] (schedule+0x40/0xa0)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0cacaac>] (schedule) from [<c0caf6fc>] (schedule_timeout+0x1c4/0x274)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0caf6fc>] (schedule_timeout) from [<c0cad598>] (wait_for_common+0x160/0x184)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0cad598>] (wait_for_common) from [<c023bdc8>] (flush_work+0xe0/0x1dc)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c023bdc8>] (flush_work) from [<c023df40>] (__cancel_work_timer+0x80/0x1a0)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c023df40>] (__cancel_work_timer) from [<bf07451c>] (hcs16sm18t_ops_display_icon+0x534/0x5cc [dvb])
May 17 12:20:11 beyonwizu4 user.warn kernel: [<bf07451c>] (hcs16sm18t_ops_display_icon [dvb]) from [<bf0185f0>] (xpt_record_feed_stop+0x2b0/0x574 [dvb])
May 17 12:20:11 beyonwizu4 user.warn kernel: [<bf0185f0>] (xpt_record_feed_stop [dvb]) from [<bf00d684>] (odin_dvb_demux_stop_feed+0x5c/0xb8 [dvb])
May 17 12:20:11 beyonwizu4 user.warn kernel: [<bf00d684>] (odin_dvb_demux_stop_feed [dvb]) from [<c09a3a64>] (dmx_ts_feed_stop_filtering+0x40/0xa8)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c09a3a64>] (dmx_ts_feed_stop_filtering) from [<c09a23e4>] (dvb_demux_do_ioctl+0x550/0x5cc)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c09a23e4>] (dvb_demux_do_ioctl) from [<c09a0494>] (dvb_usercopy+0x40/0x188)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c09a0494>] (dvb_usercopy) from [<c030f7ec>] (do_vfs_ioctl+0x9c/0x800)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c030f7ec>] (do_vfs_ioctl) from [<c030ff84>] (SyS_ioctl+0x34/0x60)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c030ff84>] (SyS_ioctl) from [<c0207600>] (ret_fast_syscall+0x0/0x34)
May 17 12:20:11 beyonwizu4 user.err kernel: INFO: task kworker/0:1:9006 blocked for more than 120 seconds.
May 17 12:20:11 beyonwizu4 user.err kernel:       Tainted: G           O    4.9.51 #1
May 17 12:20:11 beyonwizu4 user.err kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 17 12:20:11 beyonwizu4 user.info kernel: kworker/0:1     D    0  9006      2 0x00000000
May 17 12:20:11 beyonwizu4 user.info kernel: Workqueue: dvb_core_wq hcs16sm18t_recording_worker [dvb]
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0cac6f8>] (__schedule) from [<c0cacaac>] (schedule+0x40/0xa0)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0cacaac>] (schedule) from [<c0cace24>] (schedule_preempt_disabled+0xc/0x10)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0cace24>] (schedule_preempt_disabled) from [<c0cae198>] (__mutex_lock_slowpath+0x9c/0x150)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0cae198>] (__mutex_lock_slowpath) from [<c0cae294>] (mutex_lock+0x48/0x4c)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0cae294>] (mutex_lock) from [<bf073c90>] (hcs16sm18t_recording_worker+0x14/0x36c [dvb])
May 17 12:20:11 beyonwizu4 user.warn kernel: [<bf073c90>] (hcs16sm18t_recording_worker [dvb]) from [<c023d4f0>] (process_one_work+0x1ec/0x410)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c023d4f0>] (process_one_work) from [<c023e35c>] (worker_thread+0x4c/0x594)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c023e35c>] (worker_thread) from [<c0242f48>] (kthread+0xec/0xf4)
May 17 12:20:11 beyonwizu4 user.warn kernel: [<c0242f48>] (kthread) from [<c02076a8>] (ret_from_fork+0x14/0x2c)

[peteru]

You got unlucky and triggered an obscure bug in the way the front panel display icons are updated. Unfortunately the U4 driver tries to be clever and updates the icons based on various heuristics, which at times can lead to a deadlock. It's a U4 only bug and very hard to reproduce. It was probably triggered by a recording or file playback starting/ending or by a channel change.

[Grumpy_Geoff]

It was probably triggered by a recording or file playback starting/ending or by a channel change.

Thanks. Likely it was the latter (service streaming).

[gtwundke]

You got unlucky and triggered an obscure bug in the way the front panel display icons are updated. Unfortunately the U4 driver tries to be clever and updates the icons based on various heuristics, which at times can lead to a deadlock. It's a U4 only bug and very hard to reproduce. It was probably triggered by a recording or file playback starting/ending or by a channel change.

Ahh, this may explain why I sometimes get the old spinning wheel of death when changing channels (i.e. the "busy" icon comes up and stays; nothing works except to ssh in and reboot). Probably happens once every couple of months. I've never bothered looking at the logs, because, lazy