[yocto] Intermittent Kernel Boot Hang 4.8/Intel Z5 Atom

[Chris Trobridge]

Advice on how to proceed with this?

Current Yocto (morty) kernels include 4.1, 4.4 that work and 4.8 that doesn't.

Intermittent hang during power-on kernel boots before/without any diagnostic output.  Can I compile the kernel to output more than boot options allow?

I could fix this BSP to 4.4 (if that will hang around) and this is old hardware so it won't hang around for more than a few years.

I can't find anything that appears related to this on the web.  Not sure about going through intermediate kernel versions with yocto other than going back to older versions of poky for ones that are missing.  I thought about the Linux kernel site but nothing in bugzilla or archives and this may not be of sufficient interest without more information.

Thanks,
Chris

From: yocto-bounces at yoctoproject.org <yocto-bounces at yoctoproject.org> on behalf of Chris Trobridge <christrobridge at hotmail.com>
Sent: 24 February 2017 12:10
To: Yocto List
Subject: [yocto] Intermittent Kernel Boot Hang 4.8/Intel Z5 Atom
    
Since switching kernel to 4.8 (Morty) I have noticed that sometimes my Intel Atom hardware (Pokini) doesn't boot Linux.

Specifically, syslinux runs fine and starts the kernel but this then hangs immediately after displaying "Booting the kernel.", producing no further output.

This is typical output, with one of my attempts to produce more output from the kernel via serial:

> /vmlinuz initrd=/initrd LABEL=boot root=/dev/ram0  video=efifb:off video=640x480 console=ttyS0,115200 verbose

Loading /vmlinuz... ok
Loading /initrd...ok

The issue seem to occur with some probability after powering the hardware but I've not seen it occur after a reboot.

4.1 and 4.4.36 are reliable and do not have any issues booting.

I've been looking through bugs/issue but not found anything relevant.  Does anyone know of issues that I might not have found that would apply?

I've also been looking at how to get more diagnostics out of the boot.  I've tried a few suggested kernel boot parameters but nothing has helped so far.   It seems to go wrong too early.  Do I need to re-build the kernel to produce more output at the early  stage it fails?

Thanks,
Chris
-- 
_______________________________________________
yocto mailing list
yocto at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


yocto Info Page
lists.yoctoproject.org
Discussion of all things about the Yocto Project. Read our Community Guidelines or learn more about how to participate in other community discussions.