13420 2019-06-26 13:22:19 +0000 When moving from linux-yocto 5.0.7 to linux-yocto 5.0.13, kernel boot hangs after "Starting kernel ..." 2019-07-25 14:50:46 +0000 1 1 6 Yocto Project Subprojects Kernel linux-yocto 2.7.2 Other arm64 RESOLVED INVALID Medium major 2.8 1 matthias.schoepfer matthias.schoepfer kevin.tian randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 84318 0 matthias.schoepfer 2019-06-26 13:22:19 +0000 We are using yocto with the dragonboard 410c. Linux-yocto works with version 5.0.7, but when updating poky to commit 0cc214e2d25eb59ef36fa39145097f7dcc30830a and beyond, the resulting Kernel will hang right after u-boot passed the control to the kernel (last message is "Starting kernel ..." I am well aware, that this might be an upstream bug in the kernel?! 84323 1 matthias.schoepfer 2019-06-27 14:22:16 +0000 Okay, so, if I devtool modify linux-yocto, the kernel will run. If I do not do it, kernel will hang. Must have to do with some of the magic with yocto-kernel-cache, I guess? 84442 2 bruce.ashfield 2019-07-17 14:20:30 +0000 I honestly don't have any ideas about this. I'm not seeing any boot issues on any of my boards. devtool modify + rebuild shouldn't have had an impact. If you are still seeing this behaviour, can you provide a diff of the configs that are produced ? 84481 3 matthias.schoepfer 2019-07-23 11:50:30 +0000 Actually, I am quite puzzled. I have spend a week with this. Kernel size from devtool or regular build match, difference is only few bytes, that are for example build time or a path. Same with the fitImage. But there must be something broken right when the jump into the kernel happens, as not a single line of kernel messages is printed. Basically, I sticked to 5.0.7 for now, need to get some other work done before. Its okay with me if you close this issue. If I ever can come up with more insight, I will add a comment here... 84489 4 randy.macleod 2019-07-25 14:50:46 +0000 Closing as per Mattias's suggestion. Reopen if the situation become more clear.