Bug 217540

Summary:	w_scan hangs on 6.3.7 and does not react on kill -9
Product:	v4l-dvb	Reporter:	Lukasz Kalamlacki (kalamlacki)
Component:	dvb-other	Assignee:	dvb-other (v4l-dvb_dvb-other)
Status:	NEW ---
Severity:	normal	CC:	bagasdotme, s.l-h
Priority:	P3
Hardware:	All
OS:	Linux
Kernel Version:	6.3.7	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	dmesg output kernel config the bug screenshot

Description Lukasz Kalamlacki 2023-06-11 18:20:50 UTC

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

Comment 1 Bagas Sanjaya 2023-06-12 00:59:38 UTC

(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?

Comment 2 Lukasz Kalamlacki 2023-06-12 13:41:34 UTC

Created attachment 304400 [details]
dmesg output

Comment 3 Lukasz Kalamlacki 2023-06-12 13:42:02 UTC

Created attachment 304401 [details]
kernel config

Comment 4 Lukasz Kalamlacki 2023-06-12 13:55:24 UTC

It seems that kernel 6.1.33 works fine and also kernel 6.3.6 works fine

Comment 5 Lukasz Kalamlacki 2023-06-12 14:03:54 UTC

Created attachment 304402 [details]
the bug screenshot

Comment 6 Stefan Lippers-Hollmann 2023-06-13 08:18:38 UTC

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>.