Re: Odroid U2 Kernel 4.7rc7+ Hang on reboot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/19/2016 01:29 PM, Krzysztof Kozlowski wrote:
> 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):

I dig a little bit and emergency reboot on Odroid U3 (and family) is not
solvable in an easy and clean way.

The problem is: reset is a software reset of AP which means that clocks
go to default values. If cpufreq is active and CPU regulator voltage is
low, then it will fail to boot because clock frequency is high but
voltage is low, too low.

Possible solutions would be:
1. Reset PMIC values. This does not happen on software reset. I tried
also hardware reset through watchdog - also nothing.

2. Set regulator to safe value (same as for suspend, opp-suspend). This
cannot be used in emergency path because it is a sleeping, long
operation. I even wrote simpler cpufreq restart handler but still this
is not accepted sleeping operation. Also on Odroid U3 the CPU regulator
voltage cannot be controlled through GPIO/DVS because... they are wired
to VDD.

3. Extend emergency reboot path with execution of some new
syscore_emergency_shutdown() op. That is quite intrusive and requires
changing in many archs... Not really applicable.

4. Change the minimum voltage of buck2 to 1.0V on Odroid. Set is as
constrain, always. Not nice, but should help... Is it worth the effort?

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



[Index of Archives]     [Linux SoC Development]     [Linux Rockchip Development]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Linux SCSI]     [Yosemite News]

  Powered by Linux