From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: Odroid-C2 solid green screen on "echo c > /proc/sysrq-trigger" on Arch 4.16/4.17rc6
Date: Fri, 25 May 2018 09:53:56 +0200 [thread overview]
Message-ID: <5d1512ae-51eb-7e05-ad8b-b8e851aee90e@baylibre.com> (raw)
In-Reply-To: <84bc747f58f648e1b209bc0005804bc5@wppexc12.purdue.lcl>
Hi,
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.
Neil
>
> 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.
>
> Thanks,
>
> Matthew
>
>
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>
next prev parent reply other threads:[~2018-05-25 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 2:19 Swabey, Matthew A
2018-05-25 7:53 ` Neil Armstrong [this message]
[not found] ` <CAERgokn-JU9JxHibaWF8w9-roz-wVukey2c7RKVNJoSV=Y+Q3g@mail.gmail.com>
2018-05-26 2:36 ` Swabey, Matthew A
2018-05-26 3:49 ` Swabey, Matthew A
2018-05-26 8:33 ` Neil Armstrong
2018-05-26 8:49 ` Michał Zegan
2018-05-26 22:20 ` Swabey, Matthew A
2018-06-04 21:22 ` Swabey, Matthew A
2018-06-05 9:17 ` Neil Armstrong
2018-06-05 13:48 ` Swabey, Matthew A
2018-06-05 16:07 ` Jerome Brunet
2018-06-05 16:25 ` Neil Armstrong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d1512ae-51eb-7e05-ad8b-b8e851aee90e@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®