[Regression] No framebuffer console on Rpi since 5.14-rc1

[Regression] No framebuffer console on Rpi since 5.14-rc1

[Stefan Wahren]

Hi guys,

starting with Linux 5.14-rc1 the framebuffer console on Raspberry Pi 3/4
(no U-Boot, multi_v7_defconfig) isn't available anymore. The display
shows the rainbow screen from the bootloader and than the HDMI screen
goes black instead of kernel messages.

I bisected the issue:

62fb9874f5da54fdb243003b386128037319b219 good
e73f0f0ee7541171d89f2e2491130c7771ba58d3 bad
e058a84bfddc42ba356a2316f2cf1141974625c9 bad
a6eaf3850cb171c328a8b0db6d3c79286a1eba9d good
007b312c6f294770de01fbc0643610145012d244 good
18703923a66aecf6f7ded0e16d22eb412ddae72f good
334200bf52f0637a5ab8331c557dfcecbb9c30fa bad
c707b73f0cfb1acc94a20389aecde65e6385349b bad
caa18dd6dd9305d52943a6b59f410cbc960ad0a0 good
691cf8cd7a531dbfcc29d09a23c509a86fd9b24f bad
2fdcb55dfc86835e4845e3f422180b5596d23cb4 bad
6c3f953381e526a1623d4575660afae8b19ffa20 bad
5ea4dba68305d9648b9dba30036cc36d4e877bca bad
4a888ba03fd97d1cb0253581973533965bf348c4 good
c5ef15ae09637fb51ae43e1d1d98329d67dd4fd6 good
f611b1e7624ccdbd495c19e9805629e22265aa16 bad
ff323d6d72e1e4971c8ba9e2f3cf8afc48f22383 good

f611b1e7624ccdbd495c19e9805629e22265aa16 is the first bad commit
commit f611b1e7624ccdbd495c19e9805629e22265aa16
Author: Kees Cook <keescook@chromium.org>
Date:   Wed Jun 2 14:52:50 2021 -0700

    drm: Avoid circular dependencies for CONFIG_FB
   
    When cleaning up other drm config dependencies, it is too easy to create
    larger problems. Instead, mark CONFIG_FB as a "depends":
   
    drivers/gpu/drm/Kconfig:74:error: recursive dependency detected!

I compared the changes to the config (based on multi_v7_defconfig) with
and without this patch and it shows a lot of changes. Is this intended?

Best regards
Stefan

Re: [Regression] No framebuffer console on Rpi since 5.14-rc1

[Stefan Wahren]

Hi,

Am 15.07.21 um 18:35 schrieb Stefan Wahren:
> Hi guys,
>
> starting with Linux 5.14-rc1 the framebuffer console on Raspberry Pi 3/4
> (no U-Boot, multi_v7_defconfig) isn't available anymore. The display
> shows the rainbow screen from the bootloader and than the HDMI screen
> goes black instead of kernel messages.
>
> I bisected the issue:
>
> 62fb9874f5da54fdb243003b386128037319b219 good
> e73f0f0ee7541171d89f2e2491130c7771ba58d3 bad
> e058a84bfddc42ba356a2316f2cf1141974625c9 bad
> a6eaf3850cb171c328a8b0db6d3c79286a1eba9d good
> 007b312c6f294770de01fbc0643610145012d244 good
> 18703923a66aecf6f7ded0e16d22eb412ddae72f good
> 334200bf52f0637a5ab8331c557dfcecbb9c30fa bad
> c707b73f0cfb1acc94a20389aecde65e6385349b bad
> caa18dd6dd9305d52943a6b59f410cbc960ad0a0 good
> 691cf8cd7a531dbfcc29d09a23c509a86fd9b24f bad
> 2fdcb55dfc86835e4845e3f422180b5596d23cb4 bad
> 6c3f953381e526a1623d4575660afae8b19ffa20 bad
> 5ea4dba68305d9648b9dba30036cc36d4e877bca bad
> 4a888ba03fd97d1cb0253581973533965bf348c4 good
> c5ef15ae09637fb51ae43e1d1d98329d67dd4fd6 good
> f611b1e7624ccdbd495c19e9805629e22265aa16 bad
> ff323d6d72e1e4971c8ba9e2f3cf8afc48f22383 good
>
> f611b1e7624ccdbd495c19e9805629e22265aa16 is the first bad commit
> commit f611b1e7624ccdbd495c19e9805629e22265aa16
> Author: Kees Cook <keescook@chromium.org>
> Date:   Wed Jun 2 14:52:50 2021 -0700
>
>     drm: Avoid circular dependencies for CONFIG_FB
>    
>     When cleaning up other drm config dependencies, it is too easy to create
>     larger problems. Instead, mark CONFIG_FB as a "depends":
>    
>     drivers/gpu/drm/Kconfig:74:error: recursive dependency detected!
>
> I compared the changes to the config (based on multi_v7_defconfig) with
> and without this patch and it shows a lot of changes. Is this intended?

just one question: does the VC4 drm driver functionally depend on
CONFIG_FB / FRAMEBUFFER_CONSOLE ?

Or with other words should we re-enable CONFIG_FB like this [1] but for
Raspberry Pi related configs?

[1] -
https://lore.kernel.org/linux-samsung-soc/20210611100204.6240-1-m.szyprowski@samsung.com/

>
> Best regards
> Stefan
>
>

Re: [Regression] No framebuffer console on Rpi since 5.14-rc1

[Maxime Ripard]

[-- Attachment #1: Type: text/plain, Size: 2435 bytes --]

Hi Stefan,

On Wed, Jul 28, 2021 at 05:14:38PM +0200, Stefan Wahren wrote:
> Hi,
> 
> Am 15.07.21 um 18:35 schrieb Stefan Wahren:
> > Hi guys,
> >
> > starting with Linux 5.14-rc1 the framebuffer console on Raspberry Pi 3/4
> > (no U-Boot, multi_v7_defconfig) isn't available anymore. The display
> > shows the rainbow screen from the bootloader and than the HDMI screen
> > goes black instead of kernel messages.
> >
> > I bisected the issue:
> >
> > 62fb9874f5da54fdb243003b386128037319b219 good
> > e73f0f0ee7541171d89f2e2491130c7771ba58d3 bad
> > e058a84bfddc42ba356a2316f2cf1141974625c9 bad
> > a6eaf3850cb171c328a8b0db6d3c79286a1eba9d good
> > 007b312c6f294770de01fbc0643610145012d244 good
> > 18703923a66aecf6f7ded0e16d22eb412ddae72f good
> > 334200bf52f0637a5ab8331c557dfcecbb9c30fa bad
> > c707b73f0cfb1acc94a20389aecde65e6385349b bad
> > caa18dd6dd9305d52943a6b59f410cbc960ad0a0 good
> > 691cf8cd7a531dbfcc29d09a23c509a86fd9b24f bad
> > 2fdcb55dfc86835e4845e3f422180b5596d23cb4 bad
> > 6c3f953381e526a1623d4575660afae8b19ffa20 bad
> > 5ea4dba68305d9648b9dba30036cc36d4e877bca bad
> > 4a888ba03fd97d1cb0253581973533965bf348c4 good
> > c5ef15ae09637fb51ae43e1d1d98329d67dd4fd6 good
> > f611b1e7624ccdbd495c19e9805629e22265aa16 bad
> > ff323d6d72e1e4971c8ba9e2f3cf8afc48f22383 good
> >
> > f611b1e7624ccdbd495c19e9805629e22265aa16 is the first bad commit
> > commit f611b1e7624ccdbd495c19e9805629e22265aa16
> > Author: Kees Cook <keescook@chromium.org>
> > Date:   Wed Jun 2 14:52:50 2021 -0700
> >
> >     drm: Avoid circular dependencies for CONFIG_FB
> >    
> >     When cleaning up other drm config dependencies, it is too easy to create
> >     larger problems. Instead, mark CONFIG_FB as a "depends":
> >    
> >     drivers/gpu/drm/Kconfig:74:error: recursive dependency detected!
> >
> > I compared the changes to the config (based on multi_v7_defconfig) with
> > and without this patch and it shows a lot of changes. Is this intended?
> 
> just one question: does the VC4 drm driver functionally depend on
> CONFIG_FB / FRAMEBUFFER_CONSOLE ?

No, just the fbdev emulation but it can work perfectly fine without it.

> Or with other words should we re-enable CONFIG_FB like this [1] but for
> Raspberry Pi related configs?
> 
> [1] -
> https://lore.kernel.org/linux-samsung-soc/20210611100204.6240-1-m.szyprowski@samsung.com/

It should work indeed

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

vc4: Couldn't stop firmware display driver during boot

[Stefan Wahren]

Hi,

today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my 
HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware: 
2021-01-08T14:31:16) and i'm getting these strange errors from 
raspberrypi-firmware driver / vc4 during boot:

[   13.094733] fb0: switching to vc4 from simple
[   13.110759] Console: switching to colour dummy device 80x30
[   13.120691] raspberrypi-firmware soc:firmware: Request 0x00030066 
returned status 0x80000001
[   13.120715] vc4-drm gpu: [drm] Couldn't stop firmware display driver: -22
[   13.120839] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
[   13.121213] Bluetooth: Core ver 2.22
[   13.121266] NET: Registered PF_BLUETOOTH protocol family
[   13.121270] Bluetooth: HCI device and connection manager initialized
[   13.121281] Bluetooth: HCI socket layer initialized
[   13.121286] Bluetooth: L2CAP socket layer initialized
[   13.121297] Bluetooth: SCO socket layer initialized
[   13.132879] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
[   13.164278] Bluetooth: HCI UART driver ver 2.3
[   13.164293] Bluetooth: HCI UART protocol H4 registered
[   13.166608] raspberrypi-firmware soc:firmware: Request 0x00030066 
returned status 0x80000001
[   13.166633] vc4-drm gpu: [drm] Couldn't stop firmware display driver: -22
[   13.166717] vc4-drm gpu: bound fe400000.hvs (ops vc4_drm_unregister 
[vc4])
[   13.176173] Bluetooth: HCI UART protocol Broadcom registered
[   13.182365] hci_uart_bcm serial0-0: supply vbat not found, using 
dummy regulator
[   13.182505] hci_uart_bcm serial0-0: supply vddio not found, using 
dummy regulator
[   13.300636] uart-pl011 fe201000.serial: no DMA platform data
[   13.422683] raspberrypi-firmware soc:firmware: Request 0x00030066 
returned status 0x80000001
[   13.422700] vc4-drm gpu: [drm] Couldn't stop firmware display driver: -22
[   13.422788] vc4-drm gpu: bound fe400000.hvs (ops vc4_drm_unregister 
[vc4])
[   13.458620] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
[   13.461925] raspberrypi-firmware soc:firmware: Request 0x00030066 
returned status 0x80000001
[   13.461941] vc4-drm gpu: [drm] Couldn't stop firmware display driver: -22
[   13.462006] vc4-drm gpu: bound fe400000.hvs (ops vc4_drm_unregister 
[vc4])
[   13.469287] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   13.507497] vc4-drm gpu: bound fef00700.hdmi (ops vc4_drm_unregister 
[vc4])
[   13.521840] brcmfmac: brcmf_fw_alloc_request: using 
brcm/brcmfmac43456-sdio for chip BCM4345/9
[   13.522128] brcmfmac mmc0:0001:1: Direct firmware load for 
brcm/brcmfmac43456-sdio.raspberrypi,400.bin failed with error -2
[   13.535444] brcmfmac mmc0:0001:1: Direct firmware load for 
brcm/brcmfmac43456-sdio.raspberrypi,400.txt failed with error -2
[   13.564153] Bluetooth: hci0: BCM: chip id 130
[   13.564675] Bluetooth: hci0: BCM: features 0x0f
[   13.566157] Bluetooth: hci0: BCM4345C5
[   13.566164] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0000
[   13.568434] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.hcd' Patch
[   13.570485] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
[   13.576820] vc4-drm gpu: bound fef05700.hdmi (ops vc4_drm_unregister 
[vc4])
[   13.576967] vc4-drm gpu: bound fe004000.txp (ops vc4_drm_unregister 
[vc4])
[   13.577044] vc4-drm gpu: bound fe206000.pixelvalve (ops 
vc4_drm_unregister [vc4])
[   13.577118] vc4-drm gpu: bound fe207000.pixelvalve (ops 
vc4_drm_unregister [vc4])
[   13.577185] vc4-drm gpu: bound fe20a000.pixelvalve (ops 
vc4_drm_unregister [vc4])
[   13.577237] vc4-drm gpu: bound fe216000.pixelvalve (ops 
vc4_drm_unregister [vc4])
[   13.613504] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0

Best regards

Re: vc4: Couldn't stop firmware display driver during boot

[Phil Elwell]

[-- Attachment #1: Type: text/plain, Size: 3984 bytes --]

You know the drill, Stefan - what's in your config.txt?

Phil

On Sat, 9 Apr 2022, 20:26 Stefan Wahren, <stefan.wahren@i2se.com> wrote:

> Hi,
>
> today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
> HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware:
> 2021-01-08T14:31:16) and i'm getting these strange errors from
> raspberrypi-firmware driver / vc4 during boot:
>
> [   13.094733] fb0: switching to vc4 from simple
> [   13.110759] Console: switching to colour dummy device 80x30
> [   13.120691] raspberrypi-firmware soc:firmware: Request 0x00030066
> returned status 0x80000001
> [   13.120715] vc4-drm gpu: [drm] Couldn't stop firmware display driver:
> -22
> [   13.120839] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
> [   13.121213] Bluetooth: Core ver 2.22
> [   13.121266] NET: Registered PF_BLUETOOTH protocol family
> [   13.121270] Bluetooth: HCI device and connection manager initialized
> [   13.121281] Bluetooth: HCI socket layer initialized
> [   13.121286] Bluetooth: L2CAP socket layer initialized
> [   13.121297] Bluetooth: SCO socket layer initialized
> [   13.132879] cfg80211: Loading compiled-in X.509 certificates for
> regulatory database
> [   13.164278] Bluetooth: HCI UART driver ver 2.3
> [   13.164293] Bluetooth: HCI UART protocol H4 registered
> [   13.166608] raspberrypi-firmware soc:firmware: Request 0x00030066
> returned status 0x80000001
> [   13.166633] vc4-drm gpu: [drm] Couldn't stop firmware display driver:
> -22
> [   13.166717] vc4-drm gpu: bound fe400000.hvs (ops vc4_drm_unregister
> [vc4])
> [   13.176173] Bluetooth: HCI UART protocol Broadcom registered
> [   13.182365] hci_uart_bcm serial0-0: supply vbat not found, using
> dummy regulator
> [   13.182505] hci_uart_bcm serial0-0: supply vddio not found, using
> dummy regulator
> [   13.300636] uart-pl011 fe201000.serial: no DMA platform data
> [   13.422683] raspberrypi-firmware soc:firmware: Request 0x00030066
> returned status 0x80000001
> [   13.422700] vc4-drm gpu: [drm] Couldn't stop firmware display driver:
> -22
> [   13.422788] vc4-drm gpu: bound fe400000.hvs (ops vc4_drm_unregister
> [vc4])
> [   13.458620] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
> [   13.461925] raspberrypi-firmware soc:firmware: Request 0x00030066
> returned status 0x80000001
> [   13.461941] vc4-drm gpu: [drm] Couldn't stop firmware display driver:
> -22
> [   13.462006] vc4-drm gpu: bound fe400000.hvs (ops vc4_drm_unregister
> [vc4])
> [   13.469287] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> [   13.507497] vc4-drm gpu: bound fef00700.hdmi (ops vc4_drm_unregister
> [vc4])
> [   13.521840] brcmfmac: brcmf_fw_alloc_request: using
> brcm/brcmfmac43456-sdio for chip BCM4345/9
> [   13.522128] brcmfmac mmc0:0001:1: Direct firmware load for
> brcm/brcmfmac43456-sdio.raspberrypi,400.bin failed with error -2
> [   13.535444] brcmfmac mmc0:0001:1: Direct firmware load for
> brcm/brcmfmac43456-sdio.raspberrypi,400.txt failed with error -2
> [   13.564153] Bluetooth: hci0: BCM: chip id 130
> [   13.564675] Bluetooth: hci0: BCM: features 0x0f
> [   13.566157] Bluetooth: hci0: BCM4345C5
> [   13.566164] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0000
> [   13.568434] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.hcd' Patch
> [   13.570485] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
> [   13.576820] vc4-drm gpu: bound fef05700.hdmi (ops vc4_drm_unregister
> [vc4])
> [   13.576967] vc4-drm gpu: bound fe004000.txp (ops vc4_drm_unregister
> [vc4])
> [   13.577044] vc4-drm gpu: bound fe206000.pixelvalve (ops
> vc4_drm_unregister [vc4])
> [   13.577118] vc4-drm gpu: bound fe207000.pixelvalve (ops
> vc4_drm_unregister [vc4])
> [   13.577185] vc4-drm gpu: bound fe20a000.pixelvalve (ops
> vc4_drm_unregister [vc4])
> [   13.577237] vc4-drm gpu: bound fe216000.pixelvalve (ops
> vc4_drm_unregister [vc4])
> [   13.613504] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0
>
> Best regards
>
>

[-- Attachment #2: Type: text/html, Size: 4671 bytes --]

Re: vc4: Couldn't stop firmware display driver during boot

[Stefan Wahren]

Hi Phil,

Am 09.04.22 um 22:03 schrieb Phil Elwell:
> You know the drill, Stefan - what's in your config.txt?

sure. Everything commented out.

Regards

>
> Phil
>
> On Sat, 9 Apr 2022, 20:26 Stefan Wahren, <stefan.wahren@i2se.com> wrote:
>
>     Hi,
>
>     today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
>     HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware:
>     2021-01-08T14:31:16) and i'm getting these strange errors from
>     raspberrypi-firmware driver / vc4 during boot:
>
>     [   13.094733] fb0: switching to vc4 from simple
>     [   13.110759] Console: switching to colour dummy device 80x30
>     [   13.120691] raspberrypi-firmware soc:firmware: Request 0x00030066
>     returned status 0x80000001
>     [   13.120715] vc4-drm gpu: [drm] Couldn't stop firmware display
>     driver: -22
>     [   13.120839] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
>     [   13.121213] Bluetooth: Core ver 2.22
>     [   13.121266] NET: Registered PF_BLUETOOTH protocol family
>     [   13.121270] Bluetooth: HCI device and connection manager
>     initialized
>     [   13.121281] Bluetooth: HCI socket layer initialized
>     [   13.121286] Bluetooth: L2CAP socket layer initialized
>     [   13.121297] Bluetooth: SCO socket layer initialized
>     [   13.132879] cfg80211: Loading compiled-in X.509 certificates for
>     regulatory database
>     [   13.164278] Bluetooth: HCI UART driver ver 2.3
>     [   13.164293] Bluetooth: HCI UART protocol H4 registered
>     [   13.166608] raspberrypi-firmware soc:firmware: Request 0x00030066
>     returned status 0x80000001
>     [   13.166633] vc4-drm gpu: [drm] Couldn't stop firmware display
>     driver: -22
>     [   13.166717] vc4-drm gpu: bound fe400000.hvs (ops
>     vc4_drm_unregister
>     [vc4])
>     [   13.176173] Bluetooth: HCI UART protocol Broadcom registered
>     [   13.182365] hci_uart_bcm serial0-0: supply vbat not found, using
>     dummy regulator
>     [   13.182505] hci_uart_bcm serial0-0: supply vddio not found, using
>     dummy regulator
>     [   13.300636] uart-pl011 fe201000.serial: no DMA platform data
>     [   13.422683] raspberrypi-firmware soc:firmware: Request 0x00030066
>     returned status 0x80000001
>     [   13.422700] vc4-drm gpu: [drm] Couldn't stop firmware display
>     driver: -22
>     [   13.422788] vc4-drm gpu: bound fe400000.hvs (ops
>     vc4_drm_unregister
>     [vc4])
>     [   13.458620] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
>     [   13.461925] raspberrypi-firmware soc:firmware: Request 0x00030066
>     returned status 0x80000001
>     [   13.461941] vc4-drm gpu: [drm] Couldn't stop firmware display
>     driver: -22
>     [   13.462006] vc4-drm gpu: bound fe400000.hvs (ops
>     vc4_drm_unregister
>     [vc4])
>     [   13.469287] cfg80211: Loaded X.509 cert 'sforshee:
>     00b28ddf47aef9cea7'
>     [   13.507497] vc4-drm gpu: bound fef00700.hdmi (ops
>     vc4_drm_unregister
>     [vc4])
>     [   13.521840] brcmfmac: brcmf_fw_alloc_request: using
>     brcm/brcmfmac43456-sdio for chip BCM4345/9
>     [   13.522128] brcmfmac mmc0:0001:1: Direct firmware load for
>     brcm/brcmfmac43456-sdio.raspberrypi,400.bin failed with error -2
>     [   13.535444] brcmfmac mmc0:0001:1: Direct firmware load for
>     brcm/brcmfmac43456-sdio.raspberrypi,400.txt failed with error -2
>     [   13.564153] Bluetooth: hci0: BCM: chip id 130
>     [   13.564675] Bluetooth: hci0: BCM: features 0x0f
>     [   13.566157] Bluetooth: hci0: BCM4345C5
>     [   13.566164] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0000
>     [   13.568434] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.hcd' Patch
>     [   13.570485] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
>     [   13.576820] vc4-drm gpu: bound fef05700.hdmi (ops
>     vc4_drm_unregister
>     [vc4])
>     [   13.576967] vc4-drm gpu: bound fe004000.txp (ops
>     vc4_drm_unregister
>     [vc4])
>     [   13.577044] vc4-drm gpu: bound fe206000.pixelvalve (ops
>     vc4_drm_unregister [vc4])
>     [   13.577118] vc4-drm gpu: bound fe207000.pixelvalve (ops
>     vc4_drm_unregister [vc4])
>     [   13.577185] vc4-drm gpu: bound fe20a000.pixelvalve (ops
>     vc4_drm_unregister [vc4])
>     [   13.577237] vc4-drm gpu: bound fe216000.pixelvalve (ops
>     vc4_drm_unregister [vc4])
>     [   13.613504] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0
>
>     Best regards
>

Re: vc4: Couldn't stop firmware display driver during boot

[Stefan Wahren]

Am 09.04.22 um 21:25 schrieb Stefan Wahren:
> Hi,
>
> today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my 
> HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware: 
> 2021-01-08T14:31:16) and i'm getting these strange errors from 
> raspberrypi-firmware driver / vc4 during boot:
>
> [   13.094733] fb0: switching to vc4 from simple
> [   13.110759] Console: switching to colour dummy device 80x30
> [   13.120691] raspberrypi-firmware soc:firmware: Request 0x00030066 
> returned status 0x80000001
> [   13.120715] vc4-drm gpu: [drm] Couldn't stop firmware display 
> driver: -22
This is a new error which was introduced with Linux 5.18-rc1 
(c406ad5e4a85 "drm/vc4: Notify the firmware when DRM is in charge"). 
0x00030066 stands for the new firmware property 
RPI_FIRMWARE_NOTIFY_DISPLAY_DONE. And i guess the firmware from January 
2021 doesn't support it?
> [ 13.120839] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
> [   13.121213] Bluetooth: Core ver 2.22
> [   13.121266] NET: Registered PF_BLUETOOTH protocol family
> [   13.121270] Bluetooth: HCI device and connection manager initialized
> [   13.121281] Bluetooth: HCI socket layer initialized
> [   13.121286] Bluetooth: L2CAP socket layer initialized
> [   13.121297] Bluetooth: SCO socket layer initialized
> [   13.132879] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
> [   13.164278] Bluetooth: HCI UART driver ver 2.3
> [   13.164293] Bluetooth: HCI UART protocol H4 registered
> [   13.166608] raspberrypi-firmware soc:firmware: Request 0x00030066 
> returned status 0x80000001
> [   13.166633] vc4-drm gpu: [drm] Couldn't stop firmware display 
> driver: -22
> [   13.166717] vc4-drm gpu: bound fe400000.hvs (ops vc4_drm_unregister 
> [vc4])
> [   13.176173] Bluetooth: HCI UART protocol Broadcom registered
> [   13.182365] hci_uart_bcm serial0-0: supply vbat not found, using 
> dummy regulator
> [   13.182505] hci_uart_bcm serial0-0: supply vddio not found, using 
> dummy regulator
> [   13.300636] uart-pl011 fe201000.serial: no DMA platform data
> [   13.422683] raspberrypi-firmware soc:firmware: Request 0x00030066 
> returned status 0x80000001
> [   13.422700] vc4-drm gpu: [drm] Couldn't stop firmware display 
> driver: -22
> [   13.422788] vc4-drm gpu: bound fe400000.hvs (ops vc4_drm_unregister 
> [vc4])
> [   13.458620] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
> [   13.461925] raspberrypi-firmware soc:firmware: Request 0x00030066 
> returned status 0x80000001
> [   13.461941] vc4-drm gpu: [drm] Couldn't stop firmware display 
> driver: -22
> [   13.462006] vc4-drm gpu: bound fe400000.hvs (ops vc4_drm_unregister 
> [vc4])
> [   13.469287] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> [   13.507497] vc4-drm gpu: bound fef00700.hdmi (ops 
> vc4_drm_unregister [vc4])
> [   13.521840] brcmfmac: brcmf_fw_alloc_request: using 
> brcm/brcmfmac43456-sdio for chip BCM4345/9
> [   13.522128] brcmfmac mmc0:0001:1: Direct firmware load for 
> brcm/brcmfmac43456-sdio.raspberrypi,400.bin failed with error -2
> [   13.535444] brcmfmac mmc0:0001:1: Direct firmware load for 
> brcm/brcmfmac43456-sdio.raspberrypi,400.txt failed with error -2
> [   13.564153] Bluetooth: hci0: BCM: chip id 130
> [   13.564675] Bluetooth: hci0: BCM: features 0x0f
> [   13.566157] Bluetooth: hci0: BCM4345C5
> [   13.566164] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0000
> [   13.568434] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.hcd' Patch
> [   13.570485] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
> [   13.576820] vc4-drm gpu: bound fef05700.hdmi (ops 
> vc4_drm_unregister [vc4])
> [   13.576967] vc4-drm gpu: bound fe004000.txp (ops vc4_drm_unregister 
> [vc4])
> [   13.577044] vc4-drm gpu: bound fe206000.pixelvalve (ops 
> vc4_drm_unregister [vc4])
> [   13.577118] vc4-drm gpu: bound fe207000.pixelvalve (ops 
> vc4_drm_unregister [vc4])
> [   13.577185] vc4-drm gpu: bound fe20a000.pixelvalve (ops 
> vc4_drm_unregister [vc4])
> [   13.577237] vc4-drm gpu: bound fe216000.pixelvalve (ops 
> vc4_drm_unregister [vc4])
> [   13.613504] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0
>
> Best regards
>

Re: vc4: Couldn't stop firmware display driver during boot

[Maxime Ripard]

Hi Stefan,

On Sun, Apr 10, 2022 at 02:32:02AM +0200, Stefan Wahren wrote:
> Am 09.04.22 um 21:25 schrieb Stefan Wahren:
> > Hi,
> > 
> > today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
> > HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware:
> > 2021-01-08T14:31:16) and i'm getting these strange errors from
> > raspberrypi-firmware driver / vc4 during boot:
> > 
> > [   13.094733] fb0: switching to vc4 from simple
> > [   13.110759] Console: switching to colour dummy device 80x30
> > [   13.120691] raspberrypi-firmware soc:firmware: Request 0x00030066
> > returned status 0x80000001
> > [   13.120715] vc4-drm gpu: [drm] Couldn't stop firmware display driver:
> > -22
>
> This is a new error which was introduced with Linux 5.18-rc1 (c406ad5e4a85
> "drm/vc4: Notify the firmware when DRM is in charge"). 0x00030066 stands for
> the new firmware property RPI_FIRMWARE_NOTIFY_DISPLAY_DONE. And i guess the
> firmware from January 2021 doesn't support it?

If I remember well, this was added some time in the middle of last year,
so it wouldn't surprise me that your firmware doesn't support it.

It's not really harmful, but it might still be a good idea to upgrade
your firmware. The display pipeline has an unflushable FIFO between
devices and if we don't take special care when disabling all the devices
in that pipeline, we end up with a shift of one pixel for the rest of
the system's life.

We have some code to deal with the transition between the firmware and
the kernel, but we couldn't make it work reliably so we ended up asking
the firmware instead.

So.. Yeah, it's bad if you want to use the displays output, but it not
critical either.

Maxime

Re: vc4: Couldn't stop firmware display driver during boot

[Stefan Wahren]

Hi Maxime,

Am 11.04.22 um 09:35 schrieb Maxime Ripard:
> Hi Stefan,
>
> On Sun, Apr 10, 2022 at 02:32:02AM +0200, Stefan Wahren wrote:
>> Am 09.04.22 um 21:25 schrieb Stefan Wahren:
>>> Hi,
>>>
>>> today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
>>> HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware:
>>> 2021-01-08T14:31:16) and i'm getting these strange errors from
>>> raspberrypi-firmware driver / vc4 during boot:
>>>
>>> [   13.094733] fb0: switching to vc4 from simple
>>> [   13.110759] Console: switching to colour dummy device 80x30
>>> [   13.120691] raspberrypi-firmware soc:firmware: Request 0x00030066
>>> returned status 0x80000001
>>> [   13.120715] vc4-drm gpu: [drm] Couldn't stop firmware display driver:
>>> -22
>> This is a new error which was introduced with Linux 5.18-rc1 (c406ad5e4a85
>> "drm/vc4: Notify the firmware when DRM is in charge"). 0x00030066 stands for
>> the new firmware property RPI_FIRMWARE_NOTIFY_DISPLAY_DONE. And i guess the
>> firmware from January 2021 doesn't support it?
> If I remember well, this was added some time in the middle of last year,
> so it wouldn't surprise me that your firmware doesn't support it.
>
> It's not really harmful, but it might still be a good idea to upgrade
> your firmware. The display pipeline has an unflushable FIFO between
> devices and if we don't take special care when disabling all the devices
> in that pipeline, we end up with a shift of one pixel for the rest of
> the system's life.
>
> We have some code to deal with the transition between the firmware and
> the kernel, but we couldn't make it work reliably so we ended up asking
> the firmware instead.
>
> So.. Yeah, it's bad if you want to use the displays output, but it not
> critical either.

I understand. I think it would be nice to give the user a more helpful 
warning how to possible fix this, because we cannot assume that every 
system has the latest firmware.

Also i'm not sure if should give this warning once or on every probing 
attempt.

Best regards
Stefan

>
> Maxime

Re: vc4: Couldn't stop firmware display driver during boot

[Stefan Wahren]

Hi,

Am 11.04.22 um 13:00 schrieb Stefan Wahren:
> Hi Maxime,
>
> Am 11.04.22 um 09:35 schrieb Maxime Ripard:
>> Hi Stefan,
>>
>> On Sun, Apr 10, 2022 at 02:32:02AM +0200, Stefan Wahren wrote:
>>> Am 09.04.22 um 21:25 schrieb Stefan Wahren:
>>>> Hi,
>>>>
>>>> today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
>>>> HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware:
>>>> 2021-01-08T14:31:16) and i'm getting these strange errors from
>>>> raspberrypi-firmware driver / vc4 during boot:
>>>>
>>>> [   13.094733] fb0: switching to vc4 from simple
>>>> [   13.110759] Console: switching to colour dummy device 80x30
>>>> [   13.120691] raspberrypi-firmware soc:firmware: Request 0x00030066
>>>> returned status 0x80000001
>>>> [   13.120715] vc4-drm gpu: [drm] Couldn't stop firmware display 
>>>> driver:
>>>> -22
>>> This is a new error which was introduced with Linux 5.18-rc1 
>>> (c406ad5e4a85
>>> "drm/vc4: Notify the firmware when DRM is in charge"). 0x00030066 
>>> stands for
>>> the new firmware property RPI_FIRMWARE_NOTIFY_DISPLAY_DONE. And i 
>>> guess the
>>> firmware from January 2021 doesn't support it?
>> If I remember well, this was added some time in the middle of last year,
>> so it wouldn't surprise me that your firmware doesn't support it.
>>
>> It's not really harmful, but it might still be a good idea to upgrade
>> your firmware. The display pipeline has an unflushable FIFO between
>> devices and if we don't take special care when disabling all the devices
>> in that pipeline, we end up with a shift of one pixel for the rest of
>> the system's life.
>>
>> We have some code to deal with the transition between the firmware and
>> the kernel, but we couldn't make it work reliably so we ended up asking
>> the firmware instead.
>>
>> So.. Yeah, it's bad if you want to use the displays output, but it not
>> critical either.
>
> I understand. I think it would be nice to give the user a more helpful 
> warning how to possible fix this, because we cannot assume that every 
> system has the latest firmware.
>
> Also i'm not sure if should give this warning once or on every probing 
> attempt.

while chasing a vchiq performance regression, i was possibly able to 
crash the VPU firmware (2021-04-30T13:47:07) during boot of my Raspberry 
Pi 3B+ based on 3d7285a335ed + the bcm2835 clock fix. So this is just a 
warning, it's not totally harmless:

    10.172282] raspberrypi-firmware soc:firmware: Request 0x00030066 
returned status 0x80000001
[   10.172321] vc4-drm soc:gpu: [drm] Couldn't stop firmware display 
driver: -22
[   10.172452] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[   10.200134] Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.hcd' Patch
[   10.222634] usbcore: registered new interface driver lan78xx
[   10.225538] raspberrypi-firmware soc:firmware: Request 0x00030066 
returned status 0x80000001
[   10.225563] vc4-drm soc:gpu: [drm] Couldn't stop firmware display 
driver: -22
[   10.225645] vc4-drm soc:gpu: bound 3f400000.hvs (ops 
vc4_drm_unregister [vc4])
[   10.298306] raspberrypi-firmware soc:firmware: Request 0x00030066 
returned status 0x80000001
[   10.298354] vc4-drm soc:gpu: [drm] Couldn't stop firmware display 
driver: -22
[   10.298485] vc4-drm soc:gpu: bound 3f400000.hvs (ops 
vc4_drm_unregister [vc4])
[   10.305977] brcmfmac: brcmf_fw_alloc_request: using 
brcm/brcmfmac43455-sdio for chip BCM4345/6
[   10.306214] brcmfmac mmc1:0001:1: Direct firmware load for 
brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.bin failed with error -2
[   10.311775] raspberrypi-firmware soc:firmware: Request 0x00030066 
returned status 0x80000001
[   10.311808] vc4-drm soc:gpu: [drm] Couldn't stop firmware display 
driver: -22
[   10.311924] vc4-drm soc:gpu: bound 3f400000.hvs (ops 
vc4_drm_unregister [vc4])
[   10.357778] brcmfmac mmc1:0001:1: Direct firmware load for 
brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
[   10.508333] brcmfmac: brcmf_fw_alloc_request: using 
brcm/brcmfmac43455-sdio for chip BCM4345/6
[   10.534262] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: 
Jan  4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
[   10.705127] snd_bcm2835: module is from the staging directory, the 
quality is unknown, you have been warned.
[   10.721668] mc: Linux media interface: v0.10
[   10.746851] videodev: Linux video capture interface: v2.00
[   10.783077] bcm2835_mmal_vchiq: module is from the staging directory, 
the quality is unknown, you have been warned.
[   10.813073] bcm2835_v4l2: module is from the staging directory, the 
quality is unknown, you have been warned.
[   11.049270] Bluetooth: hci0: BCM43455 37.4MHz Raspberry Pi 3+
[   11.049294] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0342
[   11.837093] ------------[ cut here ]------------
[   11.837113] WARNING: CPU: 2 PID: 40 at 
drivers/firmware/raspberrypi.c:63 rpi_firmware_property_list+0x1ac/0x250
[   11.837142] Firmware transaction timeout
[   11.837144] Modules linked in: bcm2835_v4l2(C+) snd_soc_hdmi_codec 
bcm2835_mmal_vchiq(C) videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_common videodev mc snd_bcm2835(C+) brcmfmac brcmutil vc4 
microchip snd_soc_core ac97_bus snd_pcm_dmaengine snd_pcm sha256_generic 
libsha256 lan78xx sha256_arm cfg80211 snd_timer hci_uart snd btbcm 
soundcore crc32_arm_ce drm_cma_helper bluetooth ecdh_generic 
raspberrypi_hwmon ecc libaes bcm2835_thermal vchiq(C)
[   11.837252] CPU: 2 PID: 40 Comm: kworker/u8:1 Tainted: G         
C        5.18.0-rc7-00121-g3d7285a335ed-dirty #49
[   11.837260] Hardware name: BCM2835
[   11.837265] Workqueue: events_unbound deferred_probe_work_func
[   11.837286]  unwind_backtrace from show_stack+0x10/0x14
[   11.837300]  show_stack from dump_stack_lvl+0x40/0x4c
[   11.837313]  dump_stack_lvl from __warn+0x144/0x148
[   11.837326]  __warn from warn_slowpath_fmt+0x70/0xb4
[   11.837336]  warn_slowpath_fmt from 
rpi_firmware_property_list+0x1ac/0x250
[   11.837347]  rpi_firmware_property_list from 
rpi_firmware_property+0x60/0x8c
[   11.837358]  rpi_firmware_property from vc4_drm_bind+0x150/0x234 [vc4]
[   11.837423]  vc4_drm_bind [vc4] from 
try_to_bring_up_aggregate_device+0x15c/0x1b4
[   11.837469]  try_to_bring_up_aggregate_device from 
component_master_add_with_match+0xc4/0xf8
[   11.837479]  component_master_add_with_match from 
vc4_platform_drm_probe+0xa8/0xcc [vc4]
[   11.837523]  vc4_platform_drm_probe [vc4] from platform_probe+0x5c/0xb8
[   11.837568]  platform_probe from really_probe+0xc0/0x278
[   11.837578]  really_probe from __driver_probe_device+0x84/0xe4
[   11.837590]  __driver_probe_device from driver_probe_device+0x34/0xd4
[   11.837601]  driver_probe_device from __device_attach_driver+0x88/0xb4
[   11.837612]  __device_attach_driver from bus_for_each_drv+0x54/0xb4
[   11.837624]  bus_for_each_drv from __device_attach+0xdc/0x148
[   11.837635]  __device_attach from bus_probe_device+0x84/0x8c
[   11.837646]  bus_probe_device from deferred_probe_work_func+0x7c/0xa8
[   11.837657]  deferred_probe_work_func from process_one_work+0x228/0x4fc
[   11.837671]  process_one_work from worker_thread+0x40/0x544
[   11.837682]  worker_thread from kthread+0xd8/0xf4
[   11.837693]  kthread from ret_from_fork+0x14/0x2c
[   11.837702] Exception stack(0xf090dfb0 to 0xf090dff8)
[   11.837709] dfa0:                                     00000000 
00000000 00000000 00000000
[   11.837716] dfc0: 00000000 00000000 00000000 00000000 00000000 
00000000 00000000 00000000
[   11.837722] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
[   11.837726] ---[ end trace 0000000000000000 ]---
[   11.837746] vc4-drm soc:gpu: [drm] Couldn't stop firmware display 
driver: -110
[   11.837846] vc4-drm soc:gpu: bound 3f400000.hvs (ops 
vc4_drm_unregister [vc4])
[   12.877131] raspberrypi-clk raspberrypi-clk: Failed to change 
fw-clk-arm frequency: -110
[   13.917073] hwmon hwmon1: Failed to get throttled (-110)

>
> Best regards
> Stefan
>
>>
>> Maxime