From: Marian Mihailescu <mihailescu2m@gmail.com>
To: linux-samsung-soc@vger.kernel.org
Subject: Re: Odroid U2 Kernel 4.7rc7+ Hang on reboot
Date: Sat, 16 Jul 2016 13:53:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20160716T153429-759@post.gmane.org> (raw)
In-Reply-To: 1468527750.4843.7.camel@gmail.com
I can provide more information, i've been battling with this for a long time.
Tried on U3 and U3+ with similar results:
1) samsung tizen 4.1 kernel reboots OK.
2) i tried 4.4, 4.6, 4.7 (from Tobias's repository) all have the reboot issue.
i've put some printk in the syscon reboot. it looks like it gets registered,
but i never saw the printk put in the actual notifier function.
3) the issue is the same for emmc and sd-card, i've tried both
4) IT'S VERY RANDOM
* i've got sysrq rebooting OK, i've got sysrq ending in a kernel crash
(like Nicolas above)
* I've got rebooting working ok sometimes, but only from tty1 console or
sometimes ssh - NEVER from ttySAC1 serial console.
rebooting from serial console always resulted in hang after systemd stops.
* after switching from emmc to sd-card, there are always problems.
i had sd-card rebooting ok (from tty1) for a few hours, then after i put in
an emmc card => hell broke loose. putting sd-card back => still had issues,
although sd was fine before.
* many times, after reboot hang or switching from emmc to sd
or the other way around => kernel would crash on boot for a few times.
I reverted the SYSCON driver changes, and went back to the reboot code
in the exynos pmu.c file like 4.1 kernel => got the same issues.
I thought it's a systemd issue (after seeing echo b > /proc/sysrq-trigger
working ok) and tried the kernel on a ubuntu 14.04 image (with upstart)
=> got the same issues.
I think it might be u-boot.
PS: please keep me in the CC from here on as well.
prev parent reply other threads:[~2016-07-16 14:10 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
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 [this message]
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.20160716T153429-759@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