Moving Linux Kernel to 6.1

[dickon]

There is IMO no point to run a 32-bit OS with 64-bit kernel, but instead the 64-bit OS should be used then.

You are, I'm afraid, quite wrong about that. The bigger address space available to userland, and more efficient use of RAM at sizes >512M (see Linus Torvalds' LPAE rant from a few years back for details), are two obvious gains.

This is a positive move. I'm a little disappointed in how it's been dumped on users, but I definitely approve.

[DougieLawson]

I find it highly problematic that the default `arm_64bit` value on RPi 4 is suddenly `1`. This means that all RPi 4 systems with a 32-bit userland will suddenly boot in 64-bit mode, and all installers which use `uname -m` to decide which binaries to install, will install non-functional 64-bit binaries, if any shared system libraries are required.

I vote for leaving it as it is. My RPi3B systems have run with a 64 bit kernel and 32 bit userspace for a few years now and it doesn't pose a problem.

[MichaIng]

A single process cannot use more than ~3 GiB with 32-bit, a very rare case on an RPi/SBC system, one that I literally was never faced with. That is all I'm aware of which does not need 64-bit userland software as well to make use of it. Not sure what you mean by "more efficient"? There are quite many benchmarks floating around which show equal performance with 64-bit kernel and 32-bit userland.

Users may not like the change because they usually care about whether something practically works or not, and not about theoretical benefits which practically do rarely apply and cannot even be measured (correct me if I'm wrong). What happens now is that many users face failing software installs/service starts when installers rely on "uname -m" to pick a binary, and that is a real practical regression. Of course one should use "dpkg --print-architecture" or check for actual libraries to know the userland arch, but that is more complicated, especially for installers which support multiple Linux distributions. And RPi is a very special case in this regards as no other distro ships a 64-bit kernel with a 32-bit userland.

A real benefit of course one gains by using RPi OS 64-bit, which should be promoted for every RPi 2 v1.2 and up hardware. But changing how RPi OS 32-bit boots without admin consent is IMO wrong. Of course everyone is and should be free to chose by explicitly setting the flag.

[dickon]

A single process cannot use more than ~3 GiB with 32-bit, a very rare case on an RPi/SBC system, one that I literally was never faced with. That is all I'm aware of which does not need 64-bit userland software as well to make use of it. Not sure what you mean by "more efficient"? There are quite many benchmarks floating around which show equal performance with 64-bit kernel and 32-bit userland.

With a 64b kernel -- and 32b userland -- that address space is increased to close to (?) 4GB. We have had examples of this making a difference around these parts.

Of course one should use "dpkg --print-architecture" or check for actual libraries to know the userland arch, but that is more complicated, especially for installers which support multiple Linux distributions. And RPi is a very special case in this regards as no other distro ships a 64-bit kernel with a 32-bit userland.

This used to be fairly common on x86 back in the day, and for more or less the same reasons.

A real benefit of course one gains by using RPi OS 64-bit, which should be promoted for every RPi 2 v1.2 and up hardware. But changing how RPi OS 32-bit boots without admin consent is IMO wrong. Of course everyone is and should be free to chose by explicitly setting the flag.

It needed much better comms -- the first anyone knew of it was in this thread, late on a Friday afternoon. That's my own, personal disappointment with how this has been handled. I do still think it's a good thing.

[MichaIng]

> We have had examples of this making a difference around these parts.

I would be quite interested in details, concrete examples or numbers/benchmarks, as I have never seen anything clearly indicating a benefit, and as said never seen an RPi system which runs software that fails because a single process failed to allocate >3 GiB memory. And we are dealing with about 65.000 RPi systems, most of them RPi 4 (okay, most of them also with 64-bit userland in the meantime, since we started to more aggressively promote it for RPi 3 and above).

Even well communicated it is still problematic, as many users are often not fully aware of the implication and would enable 64-bit when being asked. Users facing issues with it are relatively rarely seen here. They report it as bug at those software developers/vendors whose installers fail on theses systems, respectively the installed binaries, or otherwise do wrong decisions based on unexpected kernel arch. We already have some reports, and I know quite some 3rd party installers which are affected as well.

I'll now ship out a patch to our users to re-enforce 32-bit mode on 32-bit userland and see where we need to make our own code fully compatible with the mixed variant, but when 3rd party installers are used, it is out of our control.

[PhilE]

The main limitation with a 32-bit kernel is that all the kernel resources must fit within a 1GB address space - the core kernel code, the modules, heaps, CMA, etc. Addressing things outside that area requires the creation of a temporary mapping.

[dickon]

> We have had examples of this making a difference around these parts.

I would be quite interested in details, concrete examples or numbers/benchmarks, as I have never seen anything clearly indicating a benefit, and as said never seen an RPi system which runs software that fails because a single process failed to allocate >3 GiB memory.

I'm afraid you'll have to search for it. I did comment on the thread, so I know it exists, but I don't recall the details OTTOMH.

Even well communicated it is still problematic, as many users are often not fully aware of the implication and would enable 64-bit when being asked. Users facing issues with it are relatively rarely seen here. They report it as bug at those software developers/vendors whose installers fail on theses systems, respectively the installed binaries, or otherwise do wrong decisions based on unexpected kernel arch. We already have some reports, and I know quite some 3rd party installers which are affected as well.

I'm not going to argue.

I'll now ship out a patch to our users to re-enforce 32-bit mode on 32-bit userland and see where we need to make our own code fully compatible with the mixed variant, but when 3rd party installers are used, it is out of our control.

Depending on your specific use-case, I'd likely try and ensure that this combination of 64b kernel and 32b userland just worked, rather than trying to fix an outdated system. I fully acknowledge that this may well be nontrivial.

[redvli]

openSUSE has and maintains a separate (.rpm) package that is just config.txt. They seem to consider it as part of the OS or firmware, like a .service file in /lib/...
So it gets overwritten, but if there are important changes, a notification question can be shown of course by the package manager tool. There is inclusion of extraconfig.txt, that is for the user. And all is installed on rootfs and copied to /boot/efi/ with a POSTINST command or similar.

Anyhow, RasPiOS completely lacks some proper multiversion package management for kernel. That could have prevented all this.
The 0-to-1 flipping on a Friday afternoon is now mainly useful for making jokes on how to drive customers to the competition.
.

[MichaIng]

Depending on your specific use-case, I'd likely try and ensure that this combination of 64b kernel and 32b userland just worked, rather than trying to fix an outdated system. I fully acknowledge that this may well be nontrivial.

We provide a multi-purpose OS, so there is no specific use case. But due to the nature of it, it has a relatively large share of less experienced users, hence we are often the first once which receive feedback when such kind of breaking changes (in a way this is) are done.

As said, it is often about 3rd party installers people use or developers provide, which are out of our control. So whatever we do, this will remain an issue as long as RPi OS 32-bit runs on 64-bit capable RPi systems.

So it gets overwritten

As the default changed, not the config.txt, openSUSE can be generally hit by the same issue, as long as they even provide a 64-bit kernel on their 32-bit repository, which I doubt.

Anyhow, RasPiOS completely lacks some proper multiversion package management for kernel.

Different topic, but I agree. I brought this up some years ago regarding kernel and headers packages. IMO best would be to split packages consequently to ship only 32-bit resp. only 64-bit kernel (and headers). For 64-bit is of course true already, but 32-bit ships both. The 64-bit kernel could then be shipped as dedicated package on the 32-bit repo, with different name or `:arm64` appendix (and the other way round, at least for 32-bit headers for kernel cross-compiling), using the native DEB multi-arch feature. If I'm not mistaken, this automatically deals with duplicate files on both arch variants (copyright, docs and such), otherwise "Replaces=" DEB attribute can be used. That way kernel installs on 32-bit systems are also faster/smaller. But this means a larger rework of the kernel packaging.

[MichaIng]

The main limitation with a 32-bit kernel is that all the kernel resources must fit within a 1GB address space - the core kernel code, the modules, heaps, CMA, etc. Addressing things outside that area requires the creation of a temporary mapping.

Ah sorry, I missed your post. I read about the possible issues with 512 MiB CMA being now the default. Just in case it would be considered to revert the default kernel to 32-bit, probably it is possible to set the default CMA based on the kernel arch, i.e. to 512 MiB on 64-bit and lower on 32-bit? But I see the conflict between proper 4k support and reliably staying within the 1 GiB range. Is this temporary mapping done automatically and only a performance downside, or does it mean that things can crash if temporary mapping is not implemented on software/driver level?

I decided on our end to not offer a patch for reverting the change but instead a patch to add support for it in out software install tool for now and see how it goes. Does someone know how typical compilers and build toolchains react to this? I've seen many Makefiles using "uname -m", at least if no target architecture is explicitly passed. Or is this mostly defined by the architecture of the compiler/tools and headers?

[redvli]

So it gets overwritten

As the default changed, not the config.txt, openSUSE can be generally hit by the same issue, as long as they even provide a 64-bit kernel on their 32-bit repository, which I doubt.

Anyhow, RasPiOS completely lacks some proper multiversion package management for kernel.

Different topic, but I agree. I brought this up some years ago regarding kernel and headers packages. IMO best would be to split packages consequently to ship only 32-bit resp. only 64-bit kernel (and headers). For 64-bit is of course true already, but 32-bit ships both. The 64-bit kernel could then be shipped as dedicated package on the 32-bit repo, with different name or `:arm64` appendix (and the other way round, at least for 32-bit headers for kernel cross-compiling), using the native DEB multi-arch feature. If I'm not mistaken, this automatically deals with duplicate files on both arch variants (copyright, docs and such), otherwise "Replaces=" DEB attribute can be used. That way kernel installs on 32-bit systems are also faster/smaller. But this means a larger rework of the kernel packaging.

This forum topic is "Moving Linux Kernel to 6.1". But it is a sort of do-or-die situation. Maybe some invest their time in tryboot or some other FAT level hacking. I know even lilo/grub from 2 decades ago that makes the 'moving' much more relaxed and having things under control. Nowadays, for example, there is armmp or lpae suffixes. RPi don't need that as PI0/1 is single core, rest is multicore. But they seem to need a method to push the conservatives among the Pi4-multiGB users to 64-bit. If all your Pi4 users are on 32-bit userland than competition has an easy prey with lets say a Cortex-A55 platform that only can and does 64-bit userland.

The troubles arise from the fact that RPF/RPT mixes this with closed-source firmware updates. Only Broadcom-under-NDA-people know or can know the details. Others, like major distros and you and your 65k products/customers get a 'blob' what Debian now calls 'non-free-firmware' I think (bootcode.bin, start*.elf, fixup*.dat and 'EEPROM'). Or should it be called BIOS/firmware? And handled by 'fwupd' ? Note that SUSE (Tumbleweed) still has dtoverlay=disable-v3d in the [pi4] section and is currently kernel 6.2.6. And they use U-boot; the config.txt section:

Code: Select all

[all]

# Allow u-boot to set arm_control
include ubootconfig.txt

# Allow user overrides of config options
include extraconfig.txt

The U-boot package you install determines what happens; as ubootconfig.txt contains:

Code: Select all

# Boot in AArch64 mode
arm_64bit=1

I don't remember how it was for BananaPiPro (2-core Cortex-A9) and RaspberryPi2 (4-core Cortex-A7).

[aicom]

I ran into an interesting breakage today in my own code that was related to this aarch64 kernel switch.

I'm writing some DRM code that creates and maps dumb buffers that are later displayed on screen. The code to create and map is essentially as follows:

Code: Select all

// Create a dumb buffer
struct drm_mode_create_dumb createBuf = {};
createBuf.width = frame->width;
createBuf.height = frame->height;
createBuf.bpp = bpc;
drmIoctl(fd, DRM_IOCTL_MODE_CREATE_DUMB, &createBuf);

// Get the magic offset needed to map it
struct drm_mode_map_dumb mapBuf = {};
mapBuf.handle = createBuf.handle;
drmIoctl(fd, DRM_IOCTL_MODE_MAP_DUMB, &mapBuf);

// Map it
void* mapping = mmap(NULL, createBuf.size, PROT_READ | PROT_WRITE, MAP_SHARED, fd, mapBuf.offset);

With matched 32-bit kernel and 32-bit userspace or 64-bit kernel and 64-bit userspace, this all works. However, with mismatched 64-bit kernel with 32-bit userspace, the mmap() call fails with EINVAL.

The reason mmap() fails here is that drm_mode_map_dumb.offset is a 64-bit field and the 64-bit kernel is returning an offset greater than 32 bits. Unless the userspace program is built with _FILE_OFFSET_BITS=64, that last parameter of mmap() is a 32-bit off_t which truncates the offset returned by DRM_IOCTL_MODE_MAP_DUMB.

Of course I can easily fix this by using _FILE_OFFSET_BITS=64 or mmap64(), but I suspect there are plenty more landmines out there just like this that might impact folks that cannot so easily fix them (maybe it's proprietary software or they aren't a developer). Just some food for thought.

[navels]

I find it highly problematic that the default `arm_64bit` value on RPi 4 is suddenly `1`. This means that all RPi 4 systems with a 32-bit userland will suddenly boot in 64-bit mode, and all installers which use `uname -m` to decide which binaries to install, will install non-functional 64-bit binaries, if any shared system libraries are required.

This is exactly the pickle I find myself in (installers using `uname` and installing the wrong binaries). Meanwhile setting `arm_64bit=0` results in an unstable system (possibly caused by https://github.com/raspberrypi/linux/issues/5395 ?).

Can someone advise how to roll back the kernel? I tried these instructions:

Code: Select all

sudo apt update
sudo apt install --reinstall raspberrypi-bootloader raspberrypi-kernel

and they do not work, I'm still on 6.1.

Update: omg now I'm stuck on the GPU test rainbow screen.

Edit: I think this reverts to 5.15.84, although I've gotta get past the rainbow first . . . ugh:

Code: Select all

sudo rpi-update bdb151a

[aBUGSworstnightmare]

That issue was found here viewtopic.php?t=347860. It looks like screen rotation is no longer working on devices with less than 2GB RAM because of a glamor related problem/setting (also see https://github.com/RPi-Distro/repo/issues/324)

In order to figure out the issue with screen rotation I've prepared a 2GB Pi4 with latest OS. DUT uses a DPI screen, rotated it to right.
I've also tried below command on the PI4 DUT as I've seen that failing on Pi3 yesterday as well

Code: Select all

xrandr --output DPI-1 --primary --scale-from 1024x768

Code: Select all

pi@PiScope:~ $ cat /proc/cpuinfo | grep Revision
Revision	: b03115
pi@PiScope:~ $ vcgencmd get_config total_mem
total_mem=2048
pi@PiScope:~ $ xrandr --output DPI-1 --primary --scale-from 1024x768
pi@PiScope:~ $ kmsprint -m
Connector 2 (46) DPI-1 (connected)
   0 640x480@60.00     25.200 640/16/10/134/-    480/32/2/11/-      60 (60.00) P|D   
pi@PiScope:~ $ xrandr --verbose
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 7680 x 7680
HDMI-1 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x45
	Timestamp:  245749
	Subpixel:   unknown
	Clones:    
	CRTCs:      3
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	max bpc: 8 
		range: (8, 12)
	bottom margin: 0 
		range: (0, 100)
	top margin: 0 
		range: (0, 100)
	right margin: 0 
		range: (0, 100)
	left margin: 0 
		range: (0, 100)
	Colorspace: Default 
		supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 32 
		supported: 32
	non-desktop: 0 
		range: (0, 1)
HDMI-2 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x46
	Timestamp:  245749
	Subpixel:   unknown
	Clones:    
	CRTCs:      4
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	max bpc: 8 
		range: (8, 12)
	bottom margin: 0 
		range: (0, 100)
	top margin: 0 
		range: (0, 100)
	right margin: 0 
		range: (0, 100)
	left margin: 0 
		range: (0, 100)
	Colorspace: Default 
		supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 41 
		supported: 41
	non-desktop: 0 
		range: (0, 1)
DPI-1 connected primary 1024x768+0+0 (0x49) normal (normal left inverted right x axis y axis) 0mm x 0mm
	Identifier: 0x47
	Timestamp:  245749
	Subpixel:   unknown
	Gamma:      1.0:1.0:1.0
	Brightness: 1.0
	Clones:    
	CRTC:       0
	CRTCs:      0
	Transform:  1.599991 0.000000 0.000000
	            0.000000 1.599991 0.000000
	            0.000000 0.000000 1.000000
	           filter: bilinear
	panel orientation: Normal 
		supported: Normal, Upside Down, Left Side Up, Right Side Up
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 46 
		supported: 46
	non-desktop: 0 
		range: (0, 1)
  640x480 (0x49) 25.200MHz -HSync -VSync *current +preferred
        h: width   640 start  656 end  666 total  800 skew    0 clock  31.50KHz
        v: height  480 start  512 end  514 total  525           clock  60.00Hz
pi@PiScope:~ $ 

Moving that uSD to a Pi3B will result in a flickering screen during boot. X will not get started but I can Ssh into the device

Code: Select all

pi@PiScope:~ $ sudo cat /sys/kernel/debug/device_component/gpu
cat: /sys/kernel/debug/device_component/gpu: No such file or directory
pi@PiScope:~ $ sudo cat /sys/kernel/debug/devices_deferred
pi@PiScope:~ $ raspinfo 
System Information
------------------

Raspberry Pi 3 Model B Rev 1.2
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"

Raspberry Pi reference 2023-02-21
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 25e2319effa91eb95edd9d9209eb9f8a584d67be, stage4

Linux PiScope 6.1.19-v8+ #1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023 aarch64 GNU/Linux
Revision	: a02082
Serial		: 0000000094bfaf94
Model		: Raspberry Pi 3 Model B Rev 1.2
Throttled flag  : throttled=0x50000
Camera          : supported=0 detected=0, libcamera interfaces=0

Videocore information
---------------------

Mar 17 2023 10:52:42 
Copyright (c) 2012 Broadcom
version 82f3750a65fadae9a38077e3c2e217ad158c8d54 (clean) (release) (start)

alloc failures:     0
compactions:        0
legacy block fails: 0

Filesystem information
----------------------
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/root       30449908 3566816  25587560  13% /
devtmpfs          332560       0    332560   0% /dev
tmpfs             465712       0    465712   0% /dev/shm
tmpfs             186288    1080    185208   1% /run
tmpfs               5120       4      5116   1% /run/lock
/dev/mmcblk0p1    261108   32406    228702  13% /boot
tmpfs              93140      16     93124   1% /run/user/1000
tmpfs              93140      16     93124   1% /run/user/110

Filename				Type		Size		Used	Priority
/var/swap                               file		102396		0	-2

Package version information
---------------------------
raspberrypi-ui-mods:
  Installed: 1.20230127
raspberrypi-sys-mods:
  Installed: 20221019
openbox:
  Installed: 3.6.1-9+rpt1+deb11u1
lxpanel:
  Installed: 0.10.1-2+rpt19
pcmanfm:
  Installed: 1.3.2-1+rpt9
rpd-plym-splash:
  Installed: 0.32

Networking Information
----------------------

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether m.m.m.m  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet x.x.x.x  netmask x.x.x.x
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 30  bytes 2890 (2.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 30  bytes 2890 (2.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet x.x.x.x  netmask x.x.x.x  broadcast x.x.x.x
        inet6 y::y.y.y.y  prefixlen 64  scopeid 0x20<link>
        ether m.m.m.m  txqueuelen 1000  (Ethernet)
        RX packets 841  bytes 132610 (129.5 KiB)
        RX errors 0  dropped 4  overruns 0  frame 0
        TX packets 318  bytes 100667 (98.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


USB Information
---------------

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
        |__ Port 3: Dev 4, If 0, Class=Vendor Specific Class, Driver=rtl8192cu, 480M
        |__ Port 5: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M

Display Information
-------------------

Running (F)KMS, console

/sys/class/drm/card0-DPI-1

/sys/class/drm/card0-HDMI-A-1

/sys/class/drm/card0-Writeback-1


Connector 0 (32) HDMI-A-1 (disconnected)
  Encoder 0 (31) TMDS
Connector 1 (42) DPI-1 (connected)
  Encoder 1 (41) DPI
    Crtc 1 (71) 640x480@60.00 25.200 640/16/10/134/- 480/32/2/11/- 60 (60.00) P|D 
      Plane 1 (61) fb-id: 294 (crtcs: 1) 0,0 640x480 -> 0,0 640x480 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12)
        FB 294 640x480 RG16

Connector 1 (42) DPI-1 (connected)
   0 640x480@60.00     25.200 640/16/10/134/-    480/32/2/11/-      60 (60.00) P|D   


/sys/kernel/debug/dri/0/state:
plane[44]: plane-0
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=0
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[61]: plane-1
	crtc=pixelvalve-0
	fb=294
		allocated by = [fbcon]
		refcount=2
		format=RG16 little-endian (0x36314752)
		modifier=0x0
		size=640x480
		layers:
			size[0]=640x480
			pitch[0]=1280
			offset[0]=0
			obj[0]:
				name=0
				refcount=3
				start=00100000
				size=614400
				imported=no
	crtc-pos=640x480+0+0
	src-pos=640.000000x480.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=0
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[72]: plane-2
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=0
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[83]: plane-3
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=0
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[94]: plane-4
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=1
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[104]: plane-5
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=2
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[114]: plane-6
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=3
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[124]: plane-7
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=4
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[134]: plane-8
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=5
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[144]: plane-9
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=6
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[154]: plane-10
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=7
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[164]: plane-11
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=8
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[174]: plane-12
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=9
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[184]: plane-13
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=a
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[194]: plane-14
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=b
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[204]: plane-15
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=c
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[214]: plane-16
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=d
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[224]: plane-17
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=e
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[234]: plane-18
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=f
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[244]: plane-19
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=10
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[254]: plane-20
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=11
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[264]: plane-21
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=11
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[274]: plane-22
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=11
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
plane[284]: plane-23
	crtc=(null)
	fb=0
	crtc-pos=0x0+0+0
	src-pos=0.000000x0.000000+0.000000+0.000000
	rotation=1
	normalized-zpos=11
	color-encoding=ITU-R BT.709 YCbCr
	color-range=YCbCr limited range
crtc[54]: txp
	enable=0
	active=0
	self_refresh_active=0
	planes_changed=0
	mode_changed=0
	active_changed=0
	connectors_changed=0
	color_mgmt_changed=0
	plane_mask=0
	connector_mask=0
	encoder_mask=0
	mode: "": 0 0 0 0 0 0 0 0 0 0 0x0 0x0
crtc[71]: pixelvalve-0
	enable=1
	active=1
	self_refresh_active=0
	planes_changed=1
	mode_changed=0
	active_changed=0
	connectors_changed=0
	color_mgmt_changed=0
	plane_mask=2
	connector_mask=2
	encoder_mask=2
	mode: "640x480": 60 25200 640 656 666 800 480 512 514 525 0x48 0xa
crtc[82]: pixelvalve-1
	enable=0
	active=0
	self_refresh_active=0
	planes_changed=0
	mode_changed=0
	active_changed=0
	connectors_changed=0
	color_mgmt_changed=0
	plane_mask=0
	connector_mask=0
	encoder_mask=0
	mode: "": 0 0 0 0 0 0 0 0 0 0 0x0 0x0
crtc[93]: pixelvalve-2
	enable=0
	active=0
	self_refresh_active=0
	planes_changed=0
	mode_changed=0
	active_changed=0
	connectors_changed=0
	color_mgmt_changed=0
	plane_mask=0
	connector_mask=0
	encoder_mask=0
	mode: "": 0 0 0 0 0 0 0 0 0 0 0x0 0x0
connector[32]: HDMI-A-1
	crtc=(null)
	self_refresh_aware=0
connector[42]: DPI-1
	crtc=pixelvalve-0
	self_refresh_aware=0
connector[60]: Writeback-1
	crtc=(null)
	self_refresh_aware=0



config.txt
----------

aphy_params_current=819
arm_64bit=1
arm_freq=1200
arm_freq_min=600
audio_pwm_mode=514
camera_auto_detect=-1
config_hdmi_boost=5
core_freq=400
desired_osc_freq=0x387520
disable_commandline_tags=2
disable_l2cache=1
disable_overscan=1
disable_poe_fan=1
display_hdmi_rotate=-1
display_lcd_rotate=-1
dphy_params_current=547
dtdebug=1
dvfs=3
enable_tvout=1
force_pwm_open=1
framebuffer_ignore_alpha=1
framebuffer_swap=1
gpu_freq=300
init_uart_clock=0x2dc6c00
lcd_framerate=60
mask_gpu_interrupt0=3072
mask_gpu_interrupt1=26370
max_framebuffers=2
over_voltage=5
over_voltage_avs=0x23186
pause_burst_frames=1
program_serial_random=1
sdram_freq=450
total_mem=1024
hdmi_force_cec_address:0=65535
hdmi_force_cec_address:1=65535
hdmi_pixel_freq_limit:0=0x9a7ec80
device_tree=-
overlay_prefix=overlays/
hdmi_cvt:0=
hdmi_cvt:1=
hdmi_edid_filename:0=
hdmi_edid_filename:1=
hdmi_timings:0=
hdmi_timings:1=

cmdline.txt
-----------
coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=0 snd_bcm2835.enable_headphones=0 video=Composite-1:720x480@60i vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=f0cc52e8-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles

raspi-gpio settings
-------------------

BANK0 (GPIO 0 to 27):
GPIO 0: level=1 fsel=6 alt=2 func=PCLK
GPIO 1: level=0 fsel=6 alt=2 func=DE
GPIO 2: level=1 fsel=6 alt=2 func=LCD_VSYNC
GPIO 3: level=1 fsel=6 alt=2 func=LCD_HSYNC
GPIO 4: level=1 fsel=6 alt=2 func=DPI_D0
GPIO 5: level=0 fsel=6 alt=2 func=DPI_D1
GPIO 6: level=0 fsel=6 alt=2 func=DPI_D2
GPIO 7: level=0 fsel=6 alt=2 func=DPI_D3
GPIO 8: level=0 fsel=6 alt=2 func=DPI_D4
GPIO 9: level=0 fsel=6 alt=2 func=DPI_D5
GPIO 10: level=0 fsel=0 func=INPUT
GPIO 11: level=0 fsel=0 func=INPUT
GPIO 12: level=0 fsel=6 alt=2 func=DPI_D8
GPIO 13: level=0 fsel=6 alt=2 func=DPI_D9
GPIO 14: level=0 fsel=6 alt=2 func=DPI_D10
GPIO 15: level=0 fsel=6 alt=2 func=DPI_D11
GPIO 16: level=0 fsel=6 alt=2 func=DPI_D12
GPIO 17: level=0 fsel=6 alt=2 func=DPI_D13
GPIO 18: level=0 fsel=0 func=INPUT
GPIO 19: level=1 fsel=2 alt=5 func=PWM1
GPIO 20: level=0 fsel=6 alt=2 func=DPI_D16
GPIO 21: level=0 fsel=6 alt=2 func=DPI_D17
GPIO 22: level=0 fsel=6 alt=2 func=DPI_D18
GPIO 23: level=0 fsel=6 alt=2 func=DPI_D19
GPIO 24: level=0 fsel=6 alt=2 func=DPI_D20
GPIO 25: level=0 fsel=6 alt=2 func=DPI_D21
GPIO 26: level=0 fsel=0 func=INPUT
GPIO 27: level=0 fsel=0 func=INPUT
BANK1 (GPIO 28 to 45):
GPIO 28: level=0 fsel=0 func=INPUT
GPIO 29: level=1 fsel=0 func=INPUT
GPIO 30: level=0 fsel=0 func=INPUT
GPIO 31: level=0 fsel=0 func=INPUT
GPIO 32: level=1 fsel=7 alt=3 func=TXD0
GPIO 33: level=1 fsel=7 alt=3 func=RXD0
GPIO 34: level=0 fsel=7 alt=3 func=SD1_CLK
GPIO 35: level=1 fsel=7 alt=3 func=SD1_CMD
GPIO 36: level=1 fsel=7 alt=3 func=SD1_DAT0
GPIO 37: level=1 fsel=7 alt=3 func=SD1_DAT1
GPIO 38: level=1 fsel=7 alt=3 func=SD1_DAT2
GPIO 39: level=1 fsel=7 alt=3 func=SD1_DAT3
GPIO 40: level=0 fsel=4 alt=0 func=PWM0
GPIO 41: level=1 fsel=4 alt=0 func=PWM1
GPIO 42: level=0 fsel=4 alt=0 func=GPCLK1
GPIO 43: level=1 fsel=4 alt=0 func=GPCLK2
GPIO 44: level=1 fsel=0 func=INPUT
GPIO 45: level=1 fsel=0 func=INPUT
BANK2 (GPIO 46 to 53):
GPIO 46: level=1 fsel=0 func=INPUT
GPIO 47: level=1 fsel=1 func=OUTPUT
GPIO 48: level=0 fsel=4 alt=0 func=SD0_CLK
GPIO 49: level=1 fsel=4 alt=0 func=SD0_CMD
GPIO 50: level=1 fsel=4 alt=0 func=SD0_DAT0
GPIO 51: level=1 fsel=4 alt=0 func=SD0_DAT1
GPIO 52: level=1 fsel=4 alt=0 func=SD0_DAT2
GPIO 53: level=1 fsel=4 alt=0 func=SD0_DAT3

vcdbg log messages
------------------


dmesg log
---------

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.1.19-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023
[    0.000000] random: crng init done
[    0.000000] Machine model: Raspberry Pi 3 Model B Rev 1.2
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x000000001ec00000, size 256 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000000000-0x000000003b3fffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x000000003b3fffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003b3fffff]
[    0.000000] On node 0, zone DMA: 19456 pages in unavailable ranges
[    0.000000] percpu: Embedded 29 pages/cpu s78504 r8192 d32088 u118784
[    0.000000] pcpu-alloc: s78504 r8192 d32088 u118784 alloc=29*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: kernel page table isolation forced ON by KASLR
[    0.000000] CPU features: detected: Kernel page table isolation (KPTI)
[    0.000000] CPU features: detected: ARM erratum 843419
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] alternatives: applying boot alternatives
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 238896
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=0 snd_bcm2835.enable_headphones=0 video=Composite-1:720x480@60i vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=f0cc52e8-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    0.000000] Unknown kernel command line parameters "splash", will be passed to user space.
[    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 665124K/970752K available (11776K kernel code, 2106K rwdata, 3688K rodata, 4160K init, 1077K bss, 43484K reserved, 262144K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 39741 entries in 156 pages
[    0.000000] ftrace: allocated 156 pages with 4 groups
[    0.000000] trace event string verifier disabled
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu: 	RCU event tracing is enabled.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000] 	Trampoline variant of Tasks RCU enabled.
[    0.000000] 	Rude variant of Tasks RCU enabled.
[    0.000000] 	Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] Root IRQ handler: bcm2836_arm_irqchip_handle_irq
[    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000001] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000393] Console: colour dummy device 80x25
[    0.000478] printk: console [tty1] enabled
[    0.000549] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=76800)
[    0.000588] pid_max: default: 32768 minimum: 301
[    0.000774] LSM: Security Framework initializing
[    0.001043] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.001088] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.002947] cgroup: Disabling memory control group subsystem
[    0.006307] cblist_init_generic: Setting adjustable number of callback queues.
[    0.006332] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.006605] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.006883] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.007536] rcu: Hierarchical SRCU implementation.
[    0.007555] rcu: 	Max phase no-delay instances is 1000.
[    0.009435] EFI services will not be available.
[    0.010193] smp: Bringing up secondary CPUs ...
[    0.011798] Detected VIPT I-cache on CPU1
[    0.011997] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.013833] Detected VIPT I-cache on CPU2
[    0.013985] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.015724] Detected VIPT I-cache on CPU3
[    0.015868] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.016103] smp: Brought up 1 node, 4 CPUs
[    0.016135] SMP: Total of 4 processors activated.
[    0.016155] CPU features: detected: 32-bit EL0 Support
[    0.016171] CPU features: detected: 32-bit EL1 Support
[    0.016191] CPU features: detected: CRC32 instructions
[    0.016370] CPU: All CPU(s) started at EL2
[    0.016403] alternatives: applying system-wide alternatives
[    0.019016] devtmpfs: initialized
[    0.044216] Enabled cp15_barrier support
[    0.044273] Enabled setend support
[    0.044614] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.044662] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.056673] pinctrl core: initialized pinctrl subsystem
[    0.058028] DMI not present or invalid.
[    0.059069] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.071055] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
[    0.071498] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.073052] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.073222] audit: initializing netlink subsys (disabled)
[    0.073649] audit: type=2000 audit(0.072:1): state=initialized audit_enabled=0 res=1
[    0.074684] thermal_sys: Registered thermal governor 'step_wise'
[    0.074819] cpuidle: using governor menu
[    0.075577] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.075881] ASID allocator initialised with 32768 entries
[    0.076178] Serial: AMBA PL011 UART driver
[    0.094695] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.099154] platform panel: Fixed dependency cycle(s) with /soc/dpi@7e208000
[    0.117247] raspberrypi-firmware soc:firmware: Attached to firmware from 2023-03-17T10:52:42, variant start
[    0.121266] raspberrypi-firmware soc:firmware: Firmware hash is 82f3750a65fadae9a38077e3c2e217ad158c8d54
[    0.134555] KASLR enabled
[    0.184409] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
[    0.191506] SCSI subsystem initialized
[    0.191884] usbcore: registered new interface driver usbfs
[    0.191981] usbcore: registered new interface driver hub
[    0.192090] usbcore: registered new device driver usb
[    0.192786] usb_phy_generic phy: supply vcc not found, using dummy regulator
[    0.193141] usb_phy_generic phy: dummy supplies not allowed for exclusive requests
[    0.193590] pps_core: LinuxPPS API ver. 1 registered
[    0.193609] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.193655] PTP clock support registered
[    0.195504] vgaarb: loaded
[    0.196801] clocksource: Switched to clocksource arch_sys_counter
[    0.197828] VFS: Disk quotas dquot_6.6.0
[    0.197948] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.198250] FS-Cache: Loaded
[    0.198539] CacheFiles: Loaded
[    0.215200] NET: Registered PF_INET protocol family
[    0.216010] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.218684] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
[    0.218738] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.218777] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.218911] TCP bind hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    0.219291] TCP: Hash tables configured (established 8192 bind 8192)
[    0.219561] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[    0.219630] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[    0.219985] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.221108] RPC: Registered named UNIX socket transport module.
[    0.221131] RPC: Registered udp transport module.
[    0.221149] RPC: Registered tcp transport module.
[    0.221166] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.221205] PCI: CLS 0 bytes, default 64
[    0.224275] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[    0.224692] kvm [1]: IPA Size Limit: 40 bits
[    0.226609] kvm [1]: Hyp mode initialized successfully
[    2.016367] Initialise system trusted keyrings
[    2.017028] workingset: timestamp_bits=46 max_order=18 bucket_order=0
[    2.029872] zbud: loaded
[    2.034521] NFS: Registering the id_resolver key type
[    2.034593] Key type id_resolver registered
[    2.034612] Key type id_legacy registered
[    2.034795] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    2.034822] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    2.037100] Key type asymmetric registered
[    2.037127] Asymmetric key parser 'x509' registered
[    2.037253] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    2.037668] io scheduler mq-deadline registered
[    2.037695] io scheduler kyber registered
[    2.050008] simple-framebuffer 3eaa9000.framebuffer: framebuffer at 0x3eaa9000, 0x151800 bytes
[    2.050051] simple-framebuffer 3eaa9000.framebuffer: format=a8r8g8b8, mode=720x480x32, linelength=2880
[    2.050715] Console: switching to colour frame buffer device 90x30
[    2.053839] simple-framebuffer 3eaa9000.framebuffer: fb0: simplefb registered!
[    2.065467] bcm2835-rng 3f104000.rng: hwrng registered
[    2.066712] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    2.069140] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    2.089939] brd: module loaded
[    2.103936] loop: module loaded
[    2.105189] Loading iSCSI transport class v2.0-870.
[    2.112989] usbcore: registered new interface driver r8152
[    2.113108] usbcore: registered new interface driver lan78xx
[    2.113208] usbcore: registered new interface driver smsc95xx
[    2.114033] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    2.844100] Core Release: 2.80a
[    2.844151] Setting default values for core params
[    2.844187] Finished setting default values for core params
[    3.044721] Using Buffer DMA mode
[    3.044740] Periodic Transfer Interrupt Enhancement - disabled
[    3.044757] Multiprocessor Interrupt Enhancement - disabled
[    3.044793] OTG VER PARAM: 0, OTG VER FLAG: 0
[    3.044818] Dedicated Tx FIFOs mode

[    3.049898] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = ffffffc008459000 dma = 0x00000000df000000 len=9024
[    3.049946] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    3.049971] dwc_otg: Microframe scheduler enabled

[    3.050059] WARN::hcd_init_fiq:497: MPHI regs_base at ffffffc00806d000
[    3.050163] dwc_otg 3f980000.usb: DWC OTG Controller
[    3.050209] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    3.050276] dwc_otg 3f980000.usb: irq 74, io mem 0x00000000
[    3.050342] Init: Port Power? op_state=1
[    3.050360] Init: Power Port (0)
[    3.050911] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[    3.050941] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.050966] usb usb1: Product: DWC OTG Controller
[    3.050988] usb usb1: Manufacturer: Linux 6.1.19-v8+ dwc_otg_hcd
[    3.051010] usb usb1: SerialNumber: 3f980000.usb
[    3.052143] hub 1-0:1.0: USB hub found
[    3.052269] hub 1-0:1.0: 1 port detected
[    3.053688] dwc_otg: FIQ enabled
[    3.053708] dwc_otg: NAK holdoff enabled
[    3.053725] dwc_otg: FIQ split-transaction FSM enabled
[    3.053757] Module dwc_common_port init
[    3.054600] usbcore: registered new interface driver uas
[    3.054756] usbcore: registered new interface driver usb-storage
[    3.055174] mousedev: PS/2 mouse device common for all mice
[    3.062677] sdhci: Secure Digital Host Controller Interface driver
[    3.062705] sdhci: Copyright(c) Pierre Ossman
[    3.063686] sdhci-pltfm: SDHCI platform and OF driver helper
[    3.067988] ledtrig-cpu: registered to indicate activity on CPUs
[    3.068626] hid: raw HID events driver (C) Jiri Kosina
[    3.069045] usbcore: registered new interface driver usbhid
[    3.069067] usbhid: USB HID core driver
[    3.078041] NET: Registered PF_PACKET protocol family
[    3.078239] Key type dns_resolver registered
[    3.080605] registered taskstats version 1
[    3.080725] Loading compiled-in X.509 certificates
[    3.082182] Key type .fscrypt registered
[    3.082204] Key type fscrypt-provisioning registered
[    3.109178] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    3.109411] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 99, base_baud = 0) is a PL011 rev2
[    3.115847] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    3.116550] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    3.119952] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    3.119984] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
[    3.147281] sdhost: log_buf @ 00000000a179cc4e (c251a000)
[    3.161069] Indeed it is in host mode hprt0 = 00021501
[    3.205227] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    3.212408] of_cfs_init
[    3.212637] of_cfs_init: OK
[    3.214323] Waiting for root device PARTUUID=f0cc52e8-02...
[    3.239455] mmc0: host does not support reading read-only switch, assuming write-enable
[    3.243037] mmc0: new high speed SDHC card at address 59b4
[    3.244651] mmcblk0: mmc0:59b4 5WCGP 29.8 GiB 
[    3.249549]  mmcblk0: p1 p2
[    3.250466] mmcblk0: mmc0:59b4 5WCGP 29.8 GiB
[    3.283391] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
[    3.283532] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    3.285023] devtmpfs: mounted
[    3.302036] Freeing unused kernel memory: 4160K
[    3.302281] Run /sbin/init as init process
[    3.302300]   with arguments:
[    3.302315]     /sbin/init
[    3.302330]     splash
[    3.302346]   with environment:
[    3.302360]     HOME=/
[    3.302376]     TERM=linux
[    3.352863] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    3.353125] Indeed it is in host mode hprt0 = 00001101
[    3.561417] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
[    3.561463] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.562729] hub 1-1:1.0: USB hub found
[    3.562951] hub 1-1:1.0: 5 ports detected
[    3.852910] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    3.953516] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[    3.953564] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.956942] smsc95xx v2.0.0
[    3.985379] systemd[1]: System time before build time, advancing clock.
[    4.148959] SMSC LAN8700 usb-001:003:01: attached PHY driver (mii_bus:phy_addr=usb-001:003:01, irq=184)
[    4.150290] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, m.m.m.m
[    4.228928] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
[    4.274264] NET: Registered PF_INET6 protocol family
[    4.277149] Segment Routing with IPv6
[    4.277217] In-situ OAM (IOAM) with IPv6
[    4.330924] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8178, bcdDevice= 2.00
[    4.330973] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.330999] usb 1-1.3: Product: 802.11n WLAN Adapter
[    4.331021] usb 1-1.3: Manufacturer: Realtek
[    4.331042] usb 1-1.3: SerialNumber: 00e04c000001
[    4.368417] systemd[1]: systemd 247.3-7+deb11u1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[    4.370095] systemd[1]: Detected architecture arm64.
[    4.377543] systemd[1]: Set hostname to <PiScope>.
[    4.416881] usb 1-1.5: new low-speed USB device number 5 using dwc_otg
[    4.524373] usb 1-1.5: New USB device found, idVendor=093a, idProduct=2510, bcdDevice= 1.00
[    4.524428] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.524454] usb 1-1.5: Product: USB Optical Mouse
[    4.524476] usb 1-1.5: Manufacturer: PixArt
[    4.532196] input: PixArt USB Optical Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:093A:2510.0001/input/input0
[    4.533305] hid-generic 0003:093A:2510.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-3f980000.usb-1.5/input0
[    5.377023] systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    5.633498] systemd[1]: Queued start job for default target Graphical Interface.
[    5.655381] systemd[1]: Created slice system-getty.slice.
[    5.657678] systemd[1]: Created slice system-modprobe.slice.
[    5.659410] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    5.660665] systemd[1]: Created slice User and Session Slice.
[    5.661557] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    5.663258] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    5.664001] systemd[1]: Reached target Slices.
[    5.664171] systemd[1]: Reached target Swap.
[    5.665791] systemd[1]: Listening on Syslog Socket.
[    5.666889] systemd[1]: Listening on fsck to fsckd communication Socket.
[    5.667480] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    5.669552] systemd[1]: Listening on Journal Audit Socket.
[    5.670845] systemd[1]: Listening on Journal Socket (/dev/log).
[    5.672305] systemd[1]: Listening on Journal Socket.
[    5.675832] systemd[1]: Listening on udev Control Socket.
[    5.677260] systemd[1]: Listening on udev Kernel Socket.
[    5.678774] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[    5.705604] systemd[1]: Mounting POSIX Message Queue File System...
[    5.713306] systemd[1]: Mounting RPC Pipe File System...
[    5.721963] systemd[1]: Mounting Kernel Debug File System...
[    5.731052] systemd[1]: Mounting Kernel Trace File System...
[    5.731776] systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
[    5.744483] systemd[1]: Starting Restore / save the current clock...
[    5.752741] systemd[1]: Starting Set the console keyboard layout...
[    5.761698] systemd[1]: Starting Create list of static device nodes for the current kernel...
[    5.770731] systemd[1]: Starting Load Kernel Module configfs...
[    5.781141] systemd[1]: Starting Load Kernel Module drm...
[    5.790419] systemd[1]: Starting Load Kernel Module fuse...
[    5.796181] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[    5.811697] systemd[1]: Starting File System Check on Root Device...
[    5.831214] systemd[1]: Starting Journal Service...
[    5.886272] systemd[1]: Starting Load Kernel Modules...
[    5.895107] systemd[1]: Starting Coldplug All udev Devices...
[    5.928330] fuse: init (API version 7.37)
[    5.931386] systemd[1]: Mounted POSIX Message Queue File System.
[    5.932643] systemd[1]: Mounted RPC Pipe File System.
[    5.934012] systemd[1]: Mounted Kernel Debug File System.
[    5.935137] systemd[1]: Mounted Kernel Trace File System.
[    5.938495] systemd[1]: Finished Restore / save the current clock.
[    5.946236] systemd[1]: Finished Create list of static device nodes for the current kernel.
[    5.949725] systemd[1]: modprobe@configfs.service: Succeeded.
[    5.952080] systemd[1]: Finished Load Kernel Module configfs.
[    5.957246] systemd[1]: modprobe@fuse.service: Succeeded.
[    5.959731] systemd[1]: Finished Load Kernel Module fuse.
[    5.997832] systemd[1]: Mounting FUSE Control File System...
[    6.028451] systemd[1]: Mounting Kernel Configuration File System...
[    6.037662] systemd[1]: Started File System Check Daemon to report status.
[    6.051094] systemd[1]: Mounted FUSE Control File System.
[    6.052175] systemd[1]: Mounted Kernel Configuration File System.
[    6.097339] i2c_dev: i2c /dev entries driver
[    6.100456] systemd[1]: modprobe@drm.service: Succeeded.
[    6.103052] systemd[1]: Finished Load Kernel Module drm.
[    6.130578] systemd[1]: Finished Load Kernel Modules.
[    6.171700] systemd[1]: Starting Apply Kernel Variables...
[    6.250827] systemd[1]: Finished Apply Kernel Variables.
[    6.305109] systemd[1]: Finished File System Check on Root Device.
[    6.337297] systemd[1]: Starting Remount Root and Kernel File Systems...
[    6.365982] systemd[1]: Started Journal Service.
[    6.667214] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.
[    6.816753] systemd-journald[141]: Received client request to flush runtime journal.
[    6.852745] systemd-journald[141]: File /var/log/journal/5e4d9ccbc0654469967e95ef8b1e7f4e/system.journal corrupted or uncleanly shut down, renaming and replacing.
[    8.660582] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[    8.663501] mc: Linux media interface: v0.10
[    8.694431] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    8.694482] [vc_sm_connected_init]: start
[    8.705739] [vc_sm_connected_init]: installed successfully
[    8.852706] videodev: Linux video capture interface: v2.00
[    8.884373] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    8.965480] pwm-backlight backlight_pwm: supply power not found, using dummy regulator
[    8.966130] pwm-backlight backlight_pwm: invalid default brightness level: 16, using 15
[    8.967683] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    8.968151] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    8.969144] panel-simple panel: supply power not found, using dummy regulator
[    8.999716] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[    9.011177] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    9.024864] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[    9.026041] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[    9.026777] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[    9.027306] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[    9.027360] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[    9.027398] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[    9.027428] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[    9.027459] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[    9.032051] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    9.037703] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video20
[    9.038435] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video21
[    9.038772] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[    9.038956] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[    9.038980] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video22
[    9.039513] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video23
[    9.039557] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[    9.039594] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[    9.039625] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[    9.039655] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[    9.040035] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[    9.057974] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[    9.058064] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[    9.066896] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[    9.067022] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[    9.071291] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    9.076374] bcm2835-codec bcm2835-codec: Device registered as /dev/video18
[    9.076481] bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx
[    9.086221] bcm2835-codec bcm2835-codec: Device registered as /dev/video31
[    9.086334] bcm2835-codec bcm2835-codec: Loaded V4L2 encode_image
[   10.191932] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   10.271200] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.287282] Console: switching to colour dummy device 80x25
[   10.301302] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[   10.315411] Registered IR keymap rc-cec
[   10.315771] rc rc0: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0
[   10.316184] input: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0/input1
[   10.333134] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
[   10.333759] vc4-drm soc:gpu: bound 3f208000.dpi (ops vc4_dpi_ops [vc4])
[   10.334387] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4])
[   10.335011] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
[   10.335572] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
[   10.336121] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
[   10.336538] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
[   10.348727] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0
[   10.390606] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
[   10.470484] Console: switching to colour frame buffer device 80x30
[   10.470617] vc4-drm soc:gpu: [drm] fb0: vc4drmfb frame buffer device
[   11.663650] rtl8192cu: Chip version 0x11
[   11.997055] rtl8192cu: Board Type 0
[   11.997466] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[   11.997632] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[   11.998174] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[   12.002737] usbcore: registered new interface driver rtl8192cu
[   12.173599] uart-pl011 3f201000.serial: no DMA platform data
[   12.273159] 8021q: 802.1Q VLAN Support v1.8
[   12.382924] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[   12.690098] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   12.695408] smsc95xx 1-1.1:1.0 eth0: Link is Down
[   13.048324] rtl8192cu: MAC auto ON okay!
[   13.148345] rtl8192cu: Tx queue select: 0x05
[   15.273070] hwmon hwmon1: Undervoltage detected!
[   15.742359] wlan0: authenticate with m.m.m.m
[   15.742444] wlan0: 80 MHz not supported, disabling VHT
[   15.772061] wlan0: send auth to m.m.m.m (try 1/3)
[   15.782986] wlan0: authenticated
[   15.784881] wlan0: associate with m.m.m.m (try 1/3)
[   15.821616] wlan0: RX AssocResp from m.m.m.m (capab=0x1431 status=0 aid=4)
[   15.831101] wlan0: associated
[   15.852124] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by m.m.m.m
[   16.634195] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   19.211684] Bluetooth: Core ver 2.22
[   19.211841] NET: Registered PF_BLUETOOTH protocol family
[   19.211851] Bluetooth: HCI device and connection manager initialized
[   19.211878] Bluetooth: HCI socket layer initialized
[   19.211894] Bluetooth: L2CAP socket layer initialized
[   19.211922] Bluetooth: SCO socket layer initialized
[   19.229055] Bluetooth: HCI UART driver ver 2.3
[   19.229101] Bluetooth: HCI UART protocol H4 registered
[   19.229232] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   19.229636] Bluetooth: HCI UART protocol Broadcom registered
[   19.943772] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   19.943820] Bluetooth: BNEP filters: protocol multicast
[   19.943866] Bluetooth: BNEP socket layer initialized
[   19.961179] Bluetooth: MGMT ver 1.22
[   20.002510] NET: Registered PF_ALG protocol family
[   23.065278] Bluetooth: RFCOMM TTY layer initialized
[   23.065338] Bluetooth: RFCOMM socket layer initialized
[   23.065379] Bluetooth: RFCOMM ver 1.11
[   25.348962] hwmon hwmon1: Voltage normalised
[   27.365103] hwmon hwmon1: Undervoltage detected!
[   33.412929] hwmon hwmon1: Voltage normalised
[   35.428957] hwmon hwmon1: Undervoltage detected!
[   39.460947] hwmon hwmon1: Voltage normalised
[  135.557049] wlan0: AP m.m.m.m changed bandwidth, new config is 2412.000 MHz, width 2 (2422.000/0 MHz)
[  157.880332] wlan0: AP m.m.m.m changed bandwidth, new config is 2412.000 MHz, width 1 (2412.000/0 MHz)
pi@PiScope:~ $ 

Yes, there are some undevoltage warnings; they are related to the fact that I've used a Powerbank for this first brief test. They are not related to the issue as X will also crash when I change PSU.

What looks strange in

Code: Select all

pi@PiScope:~ $ sudo cat /sys/kernel/debug/device_component/gpu
cat: /sys/kernel/debug/device_component/gpu: No such file or directory
pi@PiScope:~ $ sudo cat /sys/kernel/debug/devices_deferred
pi@PiScope:~ $

Trying to reboot the device results in the same effect: flickering screen with blinking cursor. Using raspi-config from SSH for enabling glamor and rebooting bring up X, showing the rotated desktop.

Glamor wasn't needed on 5.15.xx for getting the desktop rotated! Why is it mandatory on 6.1.x?

EDIT:
trying to use below on a Pi3B

Code: Select all

xrandr --output DPI-1 --primary --scale-from 1024x768

result in a restart of X (login screen get's shown, command fails) on a Pi3 with 5.15.84 kernel (fresh 21st Feb 64bit image)

Code: Select all

pi@PiScope:~ $ uname -a
Linux PiScope 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux

result on 6.1.19 is the same when trying to use xrandr for scaling the desktop -> X fails and login screen will be shown

Code: Select all

pi@PiScope:~ $ uname -a
Linux PiScope 6.1.19-v8+ #1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023 aarch64 GNU/Linux

[dom]

Meanwhile setting `arm_64bit=0` results in an unstable system (possibly caused by https://github.com/raspberrypi/linux/issues/5395 ?).

Are you getting the same symptoms as that thread (reports of out-of-memory in dmesg?)
If so, you can disable MGLRU and report if that helps:

Code: Select all

echo 0 | sudo tee /sys/kernel/mm/lru_gen/enabled

Code: Select all

sudo rpi-update bdb151a

Yes, that should get you back to 5.15 kernel.

[dom]

Glamor wasn't needed on 5.15.xx for getting the desktop rotated! Why is it mandatory on 6.1.x?

I don't think this is related to 6.1 kernel. It is probably the update to xserver-xorg-core
to enable GL content in windows without glamor. We've reported the behaviour to authors of that patch.

[aBUGSworstnightmare]

Glamor wasn't needed on 5.15.xx for getting the desktop rotated! Why is it mandatory on 6.1.x?

I don't think this is related to 6.1 kernel. It is probably the update to xserver-xorg-core
to enable GL content in windows without glamor. We've reported the behaviour to authors of that patch.

Hi Dom,
thanks for informing it's not kernel related and thanks again for taking care on reporting it.

[Dianne]

I recently upgraded three Pi 4Bs and one Pi 3B+ to the 6.1 kernel. The 3B+ and two of the 4Bs are fine, but the last 4B kept throwing OOM-killer errors and eventually locked up, so I had to revert.

The bad 4B is running a lot of things: Asterisk, Postfix, OpenVPN, matterircd, PiHole and so forth, so possibly something related to how busy it is has tickled a bug.

I realize this is not a particularly helpful bug report as it's likely impossible to replicate.

[PhilE]

I realize this is not a particularly helpful bug report as it's likely impossible to replicate.

Fortunately for you, other users are reporting the same issue, and it's being discussed on GitHub: https://github.com/raspberrypi/linux/issues/5395

Are you setting arm_64bit in config.txt?

The suggestion is to run the following before starting any memory-intensive tasks:

Code: Select all

echo 0 | sudo tee /sys/kernel/mm/lru_gen/enabled

(if running as root this can be simplified to "echo 0 > /sys/kernel/mm/lru_gen/enabled")

[Dianne]

Fortunately for you, other users are reporting the same issue, and it's being discussed on GitHub: https://github.com/raspberrypi/linux/issues/5395

Wow, amazing! That's very helpful; I did not expect such a great result so quickly.

Are you setting arm_64bit in config.txt?

Only on one of the Pi 4s. That one doesn't have issues... but then again, neither does one of the ones without it set.

Anyway, thanks for the link to the GitHub issue and the recommended fix!

Regards,

Dianne.

[navels]

Meanwhile setting `arm_64bit=0` results in an unstable system (possibly caused by https://github.com/raspberrypi/linux/issues/5395 ?).

Are you getting the same symptoms as that thread (reports of out-of-memory in dmesg?)
If so, you can disable MGLRU and report if that helps:

Code: Select all

echo 0 | sudo tee /sys/kernel/mm/lru_gen/enabled

Thanks, will report back if I can ever get past the rainbow screen, but my first step will be to revert the kernel. Going forward I'll hopefully remember to never do a kernel upgrade without spending a few hours in the forums assessing potential impacts.

[dom]

I don't think this is related to 6.1 kernel. It is probably the update to xserver-xorg-core
to enable GL content in windows without glamor. We've reported the behaviour to authors of that patch.

An update to:

Code: Select all

xserver-common/stable 2:1.20.11-1+rpt3+deb11u6 all [upgradable from: 2:1.20.11-1+rpt2+deb11u5]
xserver-xorg-core/stable 2:1.20.11-1+rpt3+deb11u6 armhf [upgradable from: 2:1.20.11-1+rpt2+deb11u5]

should be rolling out. I've confirmed it fixes rotated screen on Pi3 (without glamor enabled), which previosly for me resulted in a black screen.

[aBUGSworstnightmare]

I don't think this is related to 6.1 kernel. It is probably the update to xserver-xorg-core
to enable GL content in windows without glamor. We've reported the behaviour to authors of that patch.

An update to:

Code: Select all

xserver-common/stable 2:1.20.11-1+rpt3+deb11u6 all [upgradable from: 2:1.20.11-1+rpt2+deb11u5]
xserver-xorg-core/stable 2:1.20.11-1+rpt3+deb11u6 armhf [upgradable from: 2:1.20.11-1+rpt2+deb11u5]

should be rolling out. I've confirmed it fixes rotated screen on Pi3 (without glamor enabled), which previosly for me resulted in a black screen.

i will test that tomorrow and report back. Thanks for letting us know a fix is on it's way.

EDIT: tested it this morning, starting from a fresh OS install.
Updates have fixed the issues on my DUT (Pi3B).

[navels]

I was unable to get past the rainbow screen and had to wipe my SSD and reinstall the OS. Was able to rollback the kernel. Next is reinstalling HomeAssistant and everything else I had running on this thing. What a royal pain in the neck this has been.

[dom]

I was unable to get past the rainbow screen and had to wipe my SSD and reinstall the OS. Was able to rollback the kernel. Next is reinstalling HomeAssistant and everything else I had running on this thing. What a royal pain in the next this has been.

If you want help, then more info would be needed.
Are you saying the reinstalled OS didn't work until you rollbacked the kernel? What version had a problem and what version worked?