Hi, w_scan tool on kernel 6.3.7 hangs so badly that it cannot be killed by kill -9 I tried also w_scan_cpp 20230604 but it also fails I have 2040:8268 Hauppauge soloHD device as reported by lsusb. During reboot of the OS it prints a lot of kernel errors but it is after syslog is killed I guess and in syslog messages I do not see anything. On default Debian kernel 5.10.0-23 this problem does not exists. Best regards, Łukasz
(In reply to Lukasz Kalamlacki from comment #0) > Hi, > > w_scan tool on kernel 6.3.7 hangs so badly that it cannot be killed by kill > -9 > I tried also w_scan_cpp 20230604 but it also fails I have 2040:8268 > Hauppauge soloHD device as reported by lsusb. During reboot of the OS it > prints a lot of kernel errors but it is after syslog is killed I guess and > in syslog messages I do not see anything. On default Debian kernel 5.10.0-23 > this problem does not exists. > > Best regards, > Łukasz dmesg please? And also, can you bisect between v5.10 and v6.3 to find the culprit? Can you also try latest mainline?
Created attachment 304400 [details] dmesg output
Created attachment 304401 [details] kernel config
It seems that kernel 6.1.33 works fine and also kernel 6.3.6 works fine
Created attachment 304402 [details] the bug screenshot
I've observed a similar issue with vdr and kernel v6.3.7 and v6.3.8-rc1 (v6.3.6 was fine) and bisected it down to https://lkml.kernel.org/r/<20230607200927.531074599@linuxfoundation.org>, reported to linux-stable@vger.k.o with https://lkml.kernel.org/r/<20230613053314.70839926@mir>.