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 > -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html