The pinetab cannot boot with kernel version 6.1. It ends with a 'list_add corruption' and the boot process dies (look at attached log file).
boot-pt-6.1-loglevel7.txt
edit: It is not a mobian only problem - same on postmarketos.
I was using a self built u-boot for 'pinetab Early Adopters'. Because there is no tow-boot for the pinetab.
I was able (with help from https://wiki.debian.org/Teams/Mobian/KernelBuild) to build a custom kernel for 5.15 and 6.1. The 5.15. boots without problems, the 6.1 dies on boot.
I tried to play with kernel config parameters using a diff between 5.15 and 6.1. but had no luck.
Other things, like kernel hacking, are beyond my skills. I realy don't know where to start to search.
But I can build from branches and test things.
Edited
Designs
Child items
...
Linked items
0
Link issues together to show that they're related.
Learn more.
one step forward: after changing DRM_PANEL_ILITEK_ILI9881C from intern (y) to module (m) the 6.1 kernel boots on Pinetab.
Made this 2 changes:
CONFIG_DRM_PANEL_ILITEK_ILI9881C=m
CONFIG_DRM_PANEL_SITRONIX_ST7703 is not set
Maybe a later load of the module does not cause the 'list_add corruption'. Maybe I'm wrong, because I'm a noob, would be nice a kernel expert can read this an think about.
edit20230719(next level):
to fix the
[ 5.499080] lima 1c40000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found
I had to make a change inside 'sun50i-a64.dtsi'. I had to replace the line
This way I get a more clean log and can boot the kernel 6.1 on the pinetab.
Enter choice: 1: Mobian GNU/Linux 6.1.37-sunxi64-frankRetrieving file: /vmlinuz-6.1.37-sunxi64-frankRetrieving file: /initrd.img-6.1.37-sunxi64-frankappend: root=UUID=b45b3f0c-ee8b-499c-8051-af7188faa65b consoleblank=0 loglevel=7 fbcon=rotate:1 ro quiet plymouth.ignore-serial-consoles vt.global_cursor_default=0Retrieving file: /dtb-6.1.37-sunxi64-frank/allwinner/sun50i-a64-pinetab-early-adopter.dtb Uncompressing Kernel ImageMoving Image from 0x40080000 to 0x40200000, end=41670000## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000Working FDT set to 4fa00000 Loading Ramdisk to 45098000, end 49fffdda ... OK Loading Device Tree to 000000004508c000, end 0000000045097624 ... OKWorking FDT set to 4508c000Starting kernel ...[ 17.735392] debugfs: File 'AIF3 Playback' in directory 'dapm' already present![ 17.753325] debugfs: File 'AIF3 Capture' in directory 'dapm' already present!Debian GNU/Linux 12 pt ttyS0pt login:
Making the ili9881c a module and making some changes inside the .dts and .dtsi files lets the Pinetab boot. The changes on the way to make the Pinephone better, never found their way to the Pinetab HW description files.
The way I did it on testing will impact the Pinephone that uses 'sun50i-a64.dtsi' too.
This seems to be an upstream issue and the best way is to do a git bisect to find the commit which broke it.
See https://wiki.debian.org/DebianKernel/GitBisect for instructions on how to do that
It says:
a Probe_DEFER error that happens because the kernel tries to probe too early the DSI.
Maybe something similar to this error, because compiling the './drivers/gpu/drm/panel/panel-ilitek-ili9881c.c ' as a module still fixes it for me. How can the timings for the probe be changed?