lord xeon

Thanks for confirmation. I was looking for a controller so this might be the decision for me.

Does this only work with the OpenFan Controller hardware, or will any USB fan controller hardware work?

I can't kill the process (with it's new ID), and I can't run `docker stop` either. Kill does nothing and docker stop just hangs. running `dmseg` gives this output: [259950.359383] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 0-... } 19708313 jiffies s: 33861 root: 0x1/. [259950.359400] rcu: blocking rcu_node structures: [259950.359406] Task dump for CPU 0: [259950.359410] task:kdvb-ad-0-fe-0 state:R running task stack: 0 pid:14309 ppid: 2 flags:0x00004008 [259950.359420] Call Trace: [259950.359436] ? __schedule+0x456/0x494 [259950.359442] ? usleep_range+0x7a/0x7a [259950.359448] ? schedule+0x73/0x99 [259950.359453] ? schedule_timeout+0xa5/0xde [259950.359459] ? __next_timer_interrupt+0xe3/0xe3 [259950.359465] ? __wait_for_common+0xbb/0x135 [259950.359473] ? usb_start_wait_urb+0x8c/0xe8 [259950.359479] ? usb_control_msg+0x55/0x127 [259950.359485] ? usb_control_msg+0xd9/0x127 [259950.359498] ? au0828_writereg+0x75/0x9f [au0828] [259950.359506] ? au0828_set_frontend+0x3a/0xa6 [au0828] [259950.359517] ? dvb_frontend_swzigzag_autotune+0x174/0x1d1 [dvb_core] [259950.359532] ? dvb_frontend_swzigzag+0x208/0x28d [dvb_core] [259950.359540] ? __accumulate_pelt_segments+0x1d/0x2c [259950.359546] ? __update_load_avg_cfs_rq+0xf4/0x18f [259950.359553] ? update_cfs_rq_load_avg+0x136/0x13f [259950.359558] ? get_sd_balance_interval+0x19/0x3c [259950.359563] ? update_next_balance+0xf/0x1e [259950.359569] ? __switch_to_xtra+0x46/0x3d0 [259950.359576] ? __raw_spin_unlock_irq+0xa/0xb [259950.359581] ? finish_task_switch+0x125/0x1ee [259950.359586] ? arch_local_irq_save+0x11/0x17 [259950.359592] ? _raw_spin_lock_irqsave+0x7/0x24 [259950.359596] ? lock_timer_base+0x33/0x56 [259950.359602] ? _raw_spin_unlock_irqrestore+0xd/0xe [259950.359606] ? try_to_del_timer_sync+0x4f/0x6c [259950.359611] ? del_timer_sync+0x22/0x2c [259950.359616] ? arch_local_irq_save+0x11/0x17 [259950.359621] ? arch_local_irq_save+0x11/0x17 [259950.359631] ? dvb_frontend_thread+0x3eb/0x4cf [dvb_core] [259950.359636] ? init_wait_entry+0x24/0x24 [259950.359646] ? dvb_frontend_get_event.isra.0+0x17f/0x17f [dvb_core] [259950.359652] ? kthread+0xe5/0xea [259950.359658] ? kthread_associate_blkcg+0x96/0x96 [259950.359664] ? ret_from_fork+0x22/0x30 a bunch of times. Sometimes with more stack trace between each INFO section. I'll try another USB port right now when I reboot. And perhaps next step will be to build a custom kernel as you pointed to.

I have 1 (one) single USB device plugged in that shows up as 2 (two) tunners in TVHeadend: Most of the time I can yes. It seems to depend on when I catch it, and how long it's been locked up for. Right now I rebooted the server because I needed it so it's not locked. I'll try that in about 5 days when it locks up again.

I'm using the libreelec driver package and I have a Hauppauge WinTV HVR-950 USB tuner plugged in.

UPDATE: I uninstalled the plugin and was able to keep track of things for a few days and noticed something in the syslog related to the 6.8.x to 6.9.2 upgrade and networking in VMs. I'm sorry for missing that. I was able to catch that and fix it before too long. Without the plugin enabled, I had no problems with over a week of uptime. I decided to try turning it on again and trouble arises. I can go about 6 to 7 days with no problems and then one of my cores will show 100%. Unpon ssh and running top I see this: kdvb-ad-0-fe-0 is at 100% and when this happens the server is more or less un-useable. I can't reboot or shut it down via command line or the UI, I have to hold the power button down.

I haven't noticed anything. I have uninstalled and re-booted my system. I'll see if that helps and report back. The plugin was working perfectly and I was able to use it in the TVHeadEnd Docker Container - I had recorded TV and all. I'll keep you updated.

I have 3 (three) Linux VMs running on the server, all set to the virtio network model. EDIT - I have removed the plugin but kept Unraid 6.9.0-rc2 I'll see how the stability goes.

1. Thank you for the work on this plugin and getting TV to work easily! I've been experiencing some major stability issues every since I installed this though. I don't know if it's this plugin or Unraid 6.9.0-rc2. Prior to this I was running the stable branch of Unraid - 6.8.3 and I had a flawless 100+ day uptime. Now I need to manually reboot my system every 3 days. The Unraid UI becomes unresponsive, all my docker containers become unresponsive, all my VMs are down, but I can SSH into the machine fine and when I check top I get everything is fine. I'm struggling to get stability back my system because I rely on a number of things that it's running. I'd love some help trying to troubleshoot or solve this problem of mine.