mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: maswabey@purdue.edu (Swabey, Matthew A)
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 02:19:46 +0000	[thread overview]
Message-ID: <84bc747f58f648e1b209bc0005804bc5@wppexc12.purdue.lcl> (raw)

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

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: linux-aarch64-rc.tar.bz2
Type: application/octet-stream
Size: 103472 bytes
Desc: linux-aarch64-rc.tar.bz2
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20180525/3c7014c1/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linux-aarch64.tar.bz2
Type: application/octet-stream
Size: 99947 bytes
Desc: linux-aarch64.tar.bz2
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20180525/3c7014c1/attachment-0001.obj>

             reply	other threads:[~2018-05-25  2:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25  2:19 Swabey, Matthew A [this message]
2018-05-25  7:53 ` Neil Armstrong
     [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=84bc747f58f648e1b209bc0005804bc5@wppexc12.purdue.lcl \
    --to=maswabey@purdue.edu \
    --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®