Kernel panic
drtyhlpr opened this issue · comments
RPI_MODEL=3
RELEASE=stretch
BUILD_KERNEL=true
ENABLE_CRYPTFS=true
CRYPTFS_PASSWORD=...
ENABLE_VIDEOCORE=false
ENABLE_WIRELESS=true
system boots to kernel panic . needs investigation
even without ENABLE_CRYPTFS=true, CRYPTFS_PASSWORD=... I run into a kernel panic. hm shit @burnbabyburn can you please verify?
I encountered the same issue with model rpi3P and both stretch and buster releases. it involved a bcm module.
even without ENABLE_CRYPTFS=true, CRYPTFS_PASSWORD=... I run into a kernel panic. hm shit @burnbabyburn can you please verify?
ofc i am
i checked out c5881a5 and do some testing now. If it works ill compare/diff the logs.
hm fuck no. even with checkout back to c5881a5. still kernel panic. well lets I give qemu a try.
kernel,dtb etc. configurations are quite the same no matter if i chose RPI_MODEL 3 or 3P right?
the kernel panic comes from a reverse partition layout on sd card
rootfs is on part0 and /boot is on part1
atleast thats my experience :)
kernel,dtb etc. configurations are quite the same no matter if i chose RPI_MODEL 3 or 3P right?
yes it's just wlan firmware that makes a major difference
hm? was it changed?
not on purpose. probably some "fun" from reverting to bin/sh or escaping from shellcheck. i can boot cryptfs builds too, if i correct bootcmd to point to the right partition.
I'll revert the shellcheck changes around ROOT_OFFSET in rpi23-gen-sh and build an new one
hm the generated images look like they have the right disk layout:
fdisk -l ..
2048 64M Win95 FA
231345 Linux
i assumed that because of ordering in windows. checking it with fdisk gives me the same ouput :/
hm the 1st part should be windows to let the raspberry load and boot .txt files and bins. the root= should be the root partition of the linux partition and linux should be 2nd. hm I just removed the escapes from the shellcheck and currently building the test image.
this should be the correct hm .. root=/dev/mmcblk0p2 rootfstype=ext4
ref+fix branch of mine successfully build
SET_ARCH=64
RPI_MODEL=3P
RELEASE=buster
ENABLE_CRYPTFS=true
CRYPTFS_PASSWORD=password
Also cryptfs expand seems to work:
filesystem size used avaible % mountpoint
/dev/mapper/secure 3,6G 589M 2,8G 18% /
hm i will try 64 bit now. for default 32 bit I tested to set root to 1 partition and it did not work
ps. i tried to compile a default 32 bit kernel with the removed escapes from shellcheck still same problem
ENABLE_CONSOLE=false should fix the current problem
i think it's this line:
# Add serial console support
if [ "$ENABLE_CONSOLE" = true ] ; then
CMDLINE="${CMDLINE} console=ttyAMA0,115200 kgdboc=ttyAMA0,115200"
fi
after i removed it it from cmdline, my kernel panic was gone. #166 (comment) after i added it again. the panic was back
/dev/ttyAMA0 /dev/ttyS0 and /dev/ttyprintk were present on the system
i used default rpi3buster template
what about /dev/serial via raspberry-sys-mods package
it is needed for bluetooth. Is it also a nice to have with ENABLE_CONSOLE ?
€ the line is for old debian versions only. and that's from a 2013 pov
https://hallard.me/enable-serial-port-on-raspberry-pi/
should be fixed