Odroid-C2 solid green screen on "echo c > /proc/sysrq-trigger" on Arch 4.16/4.17rc6
Swabey, Matthew A
maswabey at purdue.edu
Fri May 25 19:36:57 PDT 2018
I just had a look at the Arch linux PKGBUILD for the uboot package I am using, and it is mainline 2017.07. So I am using the mainline uboot, just a bit older.
I’ll give Armbian a try – is it the distro wit1h the most development so far? (Other than the 3.14.x releases which I would prefer not to use for now).
Dr. Matthew Swabey - Director
Bechtel Innovation Design Center - Purdue University
room: BIDC 225 phone: +1-765-494-8655
From: Tony McKahan [mailto:tonymckahan at gmail.com]
Sent: Friday, May 25, 2018 3:46 PM
To: Neil Armstrong <narmstrong at baylibre.com>
Cc: Swabey, Matthew A <maswabey at purdue.edu>; linux-amlogic at lists.infradead.org
Subject: Re: Odroid-C2 solid green screen on "echo c > /proc/sysrq-trigger" on Arch 4.16/4.17rc6
Hello Neil, Matt,
Change to 2018.03 is in Armbian's development branch, just waiting to be rolled into the master. I don't have this particular board for testing, but it should be updated soon.
On Fri, May 25, 2018, 3:57 AM Neil Armstrong <mailto:narmstrong at baylibre.com> wrote:
On 25/05/2018 04:19, Swabey, Matthew A wrote:
> Odroid-C2 solid green screen on echo c > /proc/sysrq-trigger on Arch Linux mainline 4.16/4.17rc6
> Using lightdm on xorg fb. No mali, utgard or odroid specific framebuffers. However it seems to happen on them too.
> Steps to reproduce:
> 1. Boot
> 2. Echo c > /proc/sysrq-trigger with watchdog set. Or trigger the watchdog another way, i.e. watchdogd or system.
> 3. Watchdog causes reboot
> 4. Boots with screen solid green, see photo here: https://photos.app.goo.gl/9VyiweNAIMD07VSM2
> a. No error messages visible, see attached log file bundles containing dmesg, journalctl, package list, Xorg.0.log
> b. Linux-aarch64 is 4.16
> c. Linux-aarch64-rc is 4.17rc6
> 5. Reboot - screen back to normal and working
Well, since screen goes back to normal means there is no bug on the kernel side.
This is caused by Amlogic's U-Boot.
The HW watchdog does a complete SoC reset, we cannot execute any code from kernel when the watchdog wakes up.
Please report this to Armbian and ask them to use Mainline U-Boot, this won't happen anymore.
> Thought - something about the way to trigger this reset isn't working, or a race condition is present which is being more reliably triggered? Perhaps in the dma controller or the HDMI?
> Any help to track this bug down would be very helpful, or someone else who would be interested? I can't figure out where in the stack the problem is occurring, but I guess it is the bootloader.
> linux-amlogic mailing list
> mailto:linux-amlogic at lists.infradead.org
linux-amlogic mailing list
mailto:linux-amlogic at lists.infradead.org
More information about the linux-amlogic