On Sun, 20 Aug 2023 16:08:30 +0900 Takashi Yano wrote: > I tried various kernel versions and the results are as follows. > > linux-image-5.19.0-0.deb11.2-686-pae 5.19.11-1~bpo11+1 : OK > linux-image-6.0.0-0.deb11.2-686-pae 6.0.3-1~bpo11+1 : OK > linux-image-6.1.0-0.deb11.5-686-pae 6.1.12-1~bpo11+1 : OK > linux-image-6.1.0-0.deb11.7-686-pae 6.1.20-2~bpo11+1 : OK > linux-image-6.1.0-10-686-pae 6.1.38-2 : NG > linux-image-6.1.0-11-686-pae 6.1.38-4 : NG > linux-image-6.4.0-0.deb12.2-686-pae-unsigned 6.4.4-3~bpo12+1 : NG > linux-image-6.4.0-2-686-pae 6.4.4-3 : NG > linux-image-6.5.0-0-686-pae-unsigned 6.5~rc6-1~exp1 : NG > > OK: Works without the problem. > NG: Has the problem. > > It seems that kernels built for bullseye do not have this issue. > Or maybe the kernel before 6.1.0-0 works.
I have tried another kernel: linux-image-6.1.0-0.deb11.9-686-pae-unsigned 6.1.27-1~bpo11+1 : NG The built date are: linux-image-6.1.0-0.deb11.7-686-pae 2023-05-22 11:37 linux-image-6.1.0-0.deb11.9-686-pae-unsigned 2023-07-18 17:29 It seems that the recent (in a few months) change in the kernel causes this issue. -- Takashi Yano <takashi.y...@nifty.ne.jp>
