found 986863 5.10.0-6-arm64 notfound 986863 5.8.0-3-arm64 thanks I blacklisted the vc4 module, and the console works reliably again, so that's a way to get a working system. I will blacklist in the images I produce, but this should not be needed for users to know!
I am also trying with a kernel from the 5.8 series, as noted in the pseudo-headers to the BTS. The bug does not happen under kernel 5.8.0-3. I will try to more precisely pinpoint the place where it stopped working. Just to have as much information together -- If I boot without loading the vc4 module, then load it via modprobe, I get the following messages: root@rpi4-20210226:~# modprobe vc4 [ 71.824867] debugfs: Directory 'fef00700.hdmi' with parent 'vc4-hdmi-0' already present! [ 71.835045] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops [vc4]) [ 71.869840] debugfs: Directory 'fef05700.hdmi' with parent 'vc4-hdmi-1' already present! [ 71.879230] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4]) [ 71.899628] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4]) [ 71.906197] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4]) [ 71.912815] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 71.920100] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 71.927301] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 71.934495] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 71.941850] fb0: switching to vc4drmfb from simple [ 71.947094] Console: switching to colour dummy device 80x25 [ 71.974285] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0 [ 72.035497] Console: switching to colour frame buffer device 160x45 [ 72.041942] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device root@rpi4-20210226:~# After which, the console becomes unoperative. I tested this in the p400 as well, the behavior us the same.
signature.asc
Description: PGP signature
