From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
nicolas@ndufresne.ca,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Cc: Javier Martinez Canillas <javier@osg.samsung.com>
Subject: Re: Odroid U2 Kernel 4.7rc7+ Hang on reboot
Date: Fri, 15 Jul 2016 15:15:23 +0200 [thread overview]
Message-ID: <5788E1EB.4030003@math.uni-bielefeld.de> (raw)
In-Reply-To: <5788CA67.5090200@samsung.com>
Hey,
Krzysztof Kozlowski wrote:
> On 07/15/2016 09:55 AM, Krzysztof Kozlowski wrote:
>>>> Nicolas Dufresne wrote:
>>>>> Le jeudi 14 juillet 2016 à 15:37 -0400, Nicolas Dufresne a écrit :
>>>>>> Hi,
>>>>>>
>>>>>> I'm using the Odroid U2 to test some features implemented in
>>>>>> GStreamer.
>>>>>> The parts I need mostly works in mainline kernel, my main
>>>>>> annoyance
>>>>>> ist
>>>>>> that reboot hangs.
>>>>>>
>>>>>> Is this issue known ? I'm booting from SD card is that matters.
>>>>>> Any
>>>>>> advise would be appreciated. I'm not list member, so please keep
>>>>>> me
>>>>>> in
>>>>>> CC. I'm sharing my .config, in case that is my fault.
>>
>> First of all - use just command "reboot" to restart. It should work. If
>> it doesn't, please let us now.
>>
>> I was able to reproduce your issue - OOPS in emergency restart - also in
>> my configuration (U3 + eMMC + network boot).
>>
>> It is weird... I'll take a look at it.
>
> Actually I did not encounter OOPS of yours. I was able to reproduce a
> failure to reboot on U3. XU3 reboots fine. It might be related to pwrseq...
I'm not sure how much that helps, but I can't reproduce any of this on
my X2 (which is quite closely related to the U2/U3).
I'm only encountering non-working reboot when applying Marek's latest
IOMMU runpm patchset.
> The failure seems to be present for long time, at least since v4.2. I am
> in progress of testing more releases.
At least not for the X2, and I'm booting from a sdcard like Nicolas.
IIRC then pwrseq only plays a role for booting from eMMC.
> ext4 backtrace present in your OOPs might be related to improper reboot.
> Even for emergency reboot you should first sync, then remount ro and
> finally reboot (so sysrq: sub).
I currently don't have access to my UART adapater, but I'll try to
reproduce the Oops by issuing a reboot SysRq directly.
With best wishes,
Tobias
> Best Regards,
> Krzysztof
>
next prev parent reply other threads:[~2016-07-15 13:15 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 [this message]
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
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=5788E1EB.4030003@math.uni-bielefeld.de \
--to=tjakobi@math.uni-bielefeld.de \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=nicolas@ndufresne.ca \
/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