From: Marian Mihailescu <mihailescu2m@gmail.com>
To: linux-samsung-soc@vger.kernel.org
Subject: Re: Odroid U2 Kernel 4.7rc7+ Hang on reboot
Date: Wed, 20 Jul 2016 23:56:13 +0000 (UTC) [thread overview]
Message-ID: <loom.20160721T015558-545@post.gmane.org> (raw)
In-Reply-To: 578E0F28.6010600@samsung.com
Krzysztof Kozlowski <k.kozlowski <at> samsung.com> writes:
>
> On 07/15/2016 05:56 PM, Nicolas Dufresne wrote:
> > Le vendredi 15 juillet 2016 à 16:33 +0200, Tobias Jakobi a écrit :
> >> I can confirm that this indeed doesn't work.
> >>
> >> chidori ~ # echo 1 > /proc/sys/kernel/sysrq
> >> chidori ~ # echo s > /proc/sysrq-trigger
> >> chidori ~ # echo u > /proc/sysrq-trigger
> >> chidori ~ # echo b > /proc/sysrq-trigger
> >> <board hangs, only red power LED on>
> >>
> >> I guess Nicolas is seeing a different or another problem here
though.
> >
> > Well for me both method hangs. On an extra note, reset inside Uboot
> > works, but reboot in Linux hang. I tried adding a trace
> > in syscon_restart_handle(), but the trace is never displayed. I'm
> > wondering if that handler is ever called, or if it's just that the
> > serial console was shut down already.
> >
> > Any idea what else should I trace ?
>
> This is weird... reboot should work. Just to confirm it - can you test
> following patch in both scenarios (this should fix both of them... at
> least on Odroid U3 but your board might have different SPL/BL1):
>
Hi Krzysztof,
Thanks for looking into this.
While Nicolas is away, I can do whatever testing you need.
I can confirm that with this patch, I can now reboot both from tty1 and
ttySAC1. I haven't done any extensive testing, but I could reboot
without issues several times in a row.
I do remember with previous kernels (even 3.x) there would be issues
with reboot if the governor was anything else than performance. This is
why my config only has performance enabled - but I was still having
reboot issues. Do you expect using performance gov + this patch to fully
solve the reboot issue?
Thanks,
Marian
next prev parent reply other threads:[~2016-07-20 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1468525055.4843.4.camel@ndufresne.ca>
2016-07-14 19:45 ` Odroid U2 Kernel 4.7rc7+ Hang on reboot Nicolas Dufresne
2016-07-14 20:01 ` Tobias Jakobi
2016-07-14 20:33 ` Nicolas Dufresne
2016-07-15 7:55 ` Krzysztof Kozlowski
2016-07-15 11:35 ` Krzysztof Kozlowski
2016-07-15 13:15 ` Tobias Jakobi
2016-07-15 13:20 ` Krzysztof Kozlowski
2016-07-15 13:23 ` Tobias Jakobi
2016-07-15 13:25 ` Krzysztof Kozlowski
2016-07-15 14:33 ` Tobias Jakobi
2016-07-15 15:56 ` Nicolas Dufresne
2016-07-19 11:29 ` Krzysztof Kozlowski
2016-07-20 12:29 ` Krzysztof Kozlowski
2016-07-20 12:53 ` Nicolas Dufresne
2016-07-20 23:56 ` Marian Mihailescu [this message]
2016-07-15 13:24 ` Krzysztof Kozlowski
2016-07-15 13:50 ` Nicolas Dufresne
2016-07-14 20:22 ` Nicolas Dufresne
2016-07-16 13:53 ` Marian Mihailescu
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=loom.20160721T015558-545@post.gmane.org \
--to=mihailescu2m@gmail.com \
--cc=linux-samsung-soc@vger.kernel.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