OrangepiZero2 Builds Starting kernel ... panic #4892
Comments
So not a building issue which this issue tracker is intended for. Please use forums for issues running Armbian |
|
There no point in discussing this in the forums. |
|
Since basically all bugs found in Armbian when running images need code adjustment there would be no point to have forums at all following that logic. However we are on our way to move development related discussions entirely to Github but this will take a while to get there. Probably not before 23.05 release: https://armbian.atlassian.net/browse/AR-1529 Side questions: Did this work with old master? |
|
Thanks Werner, yes look Ive applied and Igor accepted for me to help maintain Zero2. I believe something is happening in the build system and am trying to figure it out. Incidentally the released CI test images boot no problem I just tried that right now again, so it not my system or running problem. https://forum.armbian.com/topic/26661-armbian-2302-quoll-testings/ Yes I will go back to master, its on list to rule out. I must also re-test booting minimal that built a couple of days back again. I don't think I've been on boarded quite yet and cant log into armbian Jira etc, so maybe I can message you on the forum about that. Thanks for answering. |
|
Feel free to re-open if it works on master since then definitely something is fishy ;) |
|
@AGM1968 can you try stopping boot like you did, but then pasting the bootscript (.cmd / scr) line by line and seeing what the output is? My guess uImage will gag... |
|
Suspected it might well be, will do so and report.. |
|
Output as requested @rpardini |
|
To start, from what I can see the script doesn't load from
then
|
|
It's seem like that |
|
yes I agree, constant error there.. (am only investigating uboot specific atm, zero2 seems always in trouble) |
|
Further info - in process |
|
|
|
|
Yeah, when stopping boot, distroboot is only partially ran, so you need to set the values of the devtype / devnum and prefix manually so it you can reproduce manually. This varies per uboot version too... |
|
Thanks - still uncertain of a few things. |
|
Armbian_23.05.0-trunk_Orangepizero2_bullseye_edge_6.2.2_minimal.img NOW BOOTING - must of been something to check with dtb? Dunno, -- thanks for the suggestions! Will start with the patches been working on for 6.2.2 |
|
Apologies for the continued long posts here! Unfortunately adding patches in In order to prove/disprove theories, had to reset my master branch as follows: Then update remote/pull locally to include the depreciation note: Clone to VM and configure for building from master branch, all resulting in bootable image. Walk through set-up completes Welcome to ARMBIAN! Updates are available! UPDATES: complete and reboot FAIL BOOT: device tree, boot scr errors, forces network boot |
|
Package repositories
|
IMO this is the core of the problem - why this is not defined in u-boot / lost in some way. |
|
Using this image: Can't reproduce :( |
|
To be honest I really don't know other than sometimes it works other times not so. |
|
Will investigate further this evening, thanks for having a look |
|
Still looking. I forgot to run upgrade ... |
|
Ja I saw that>>>> hahaha |
|
I'll also venture to be a bit bolder in agreement and say that the fdt address is the common problem .. (kernel) |
|
For clarification purpose updating from master fails. From main there is less likely a problem, I cant test the update because of build failure. on main 'wireless drivers' bluetooth specific are problematic. The patching in my case, that working through is failing on both main and master This is a separate issue that I will have to solve and is unrelated to boot issues |
|
Thanks all concerned @ #4913 (comment) main is building now - will do so more digging over the weekend |
|
I think original issues were possibly caused by directories not cleaning, despite not using So here is where we are today, I cannot upgrade on my user account (root updates and reboots). Moreover the area that I'm working through has issues, 6.1 & 6.2. in that regard 5.19.17 does not have these problems. Still plenty to work on for Zero2. Noted on 6.1 & 6.2 kernel (#4935) Noted thermal failure on 6.1 & 6.2 kernels Noted cpu backtrace on 6.2 kernels |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Builds complete without reporting failures..... Do not move beyond Starting kernel ...
STATUS: Investigating possible causes!
=> booti ${kernel_addr_r} - ${fdtcontroladdr}etcHow to reproduce?
Both Standard and Minimal builds are failing
./compile.sh BOARD=orangepizero2 BRANCH=edge RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,imgBranch
main (main development branch)
On which host OS are you observing this problem?
bullseye
Relevant log output
https://paste.next.armbian.com/uvenaxekunThe text was updated successfully, but these errors were encountered: