Hi!
Poweroff does not seem to work on Motorola droid 4 -- it reboots. It
seems to be problem "forever", 4.18 and 4.20-rc5 seem to be
affected. It is bad, because when your battery is low, you get into
reboot loop and discharge it furher, which batteries do not like.
Any ideas, or at least idea how to debug this?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
* Pavel Machek <[email protected]> [181209 12:13]:
> Hi!
>
> Poweroff does not seem to work on Motorola droid 4 -- it reboots. It
> seems to be problem "forever", 4.18 and 4.20-rc5 seem to be
> affected. It is bad, because when your battery is low, you get into
> reboot loop and discharge it furher, which batteries do not like.
>
> Any ideas, or at least idea how to debug this?
Hmm can you check if this is happening with usb unloaded or
unbind? I suspect ohci or musb..
Regards,
Tony
On Sun 2018-12-09 08:46:50, Tony Lindgren wrote:
> * Pavel Machek <[email protected]> [181209 12:13]:
> > Hi!
> >
> > Poweroff does not seem to work on Motorola droid 4 -- it reboots. It
> > seems to be problem "forever", 4.18 and 4.20-rc5 seem to be
> > affected. It is bad, because when your battery is low, you get into
> > reboot loop and discharge it furher, which batteries do not like.
> >
> > Any ideas, or at least idea how to debug this?
>
> Hmm can you check if this is happening with usb unloaded or
> unbind? I suspect ohci or musb..
Ok, let me try: musb unbound, v4.20:
root@devuan:/sys/devices/platform/44000000.ocp/4a0ab000.usb_otg_hs#
echo 4a0ab000.usb_otg_hs > driver/unbind
(I hope I did not pull the USB too late). It rebooted instead of
poweroff. Now on 4.18:
root@devuan:/sys/devices/platform/44000000.ocp/4a062000.usbhstll# echo
4a062000.usbhstll > driver/unbind
root@devuan:/sys/devices/platform/44000000.ocp/4a062000.usbhstll#
uname -a
Linux devuan 4.18.0-rc4-88970-gf075a2c-dirty #764 SMP Mon Jul 9
12:51:47 CEST 2018 armv7l GNU/Linux
I get nice oops doing that:
[ 170.705383] ------------[ cut here ]------------
[ 170.710235] WARNING: CPU: 0 PID: 2371 at drivers/clk/clk.c:697
clk_core_unpre
pare+0xcc/0xec
[ 170.718749] Unpreparing enabled l3_init_cm:clk:0048:8
[ 170.723968] Modules linked in:
root@devuan:/sys/devices/platform/44000000.ocp/4a064000.usbhshost/4a064800.ohci#
echo 4a064800.ohci > driver/unbind
..Hmm. I'm not sure how to unbind ehci. Let me try sudo
poweroff... no, it reboots, too.
Can you check if it works for you?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Sun 2018-12-09 08:46:50, Tony Lindgren wrote:
> * Pavel Machek <[email protected]> [181209 12:13]:
> > Hi!
> >
> > Poweroff does not seem to work on Motorola droid 4 -- it reboots. It
> > seems to be problem "forever", 4.18 and 4.20-rc5 seem to be
> > affected. It is bad, because when your battery is low, you get into
> > reboot loop and discharge it furher, which batteries do not like.
> >
> > Any ideas, or at least idea how to debug this?
>
> Hmm can you check if this is happening with usb unloaded or
> unbind? I suspect ohci or musb..
I tried disabling USB in the config, with v4.20-rc, and same
behaviour. sudo poweroff causes reboot.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Hi,
On Sun, Dec 09, 2018 at 01:13:18PM +0100, Pavel Machek wrote:
> Poweroff does not seem to work on Motorola droid 4 -- it reboots. It
> seems to be problem "forever", 4.18 and 4.20-rc5 seem to be
> affected. It is bad, because when your battery is low, you get into
> reboot loop and discharge it furher, which batteries do not like.
>
> Any ideas, or at least idea how to debug this?
I cannot reproduce (using 8214bdf7d3e6 + a lot of omapdrm patches,
that I'm currently testing):
droid4# poweroff
[ 1097.557434] printk: systemd-shutdow: 32 output lines suppressed due to ratelimiting
[ 1097.862670] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 1097.920715] systemd-journald[158]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 1097.973022] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 1098.027008] systemd-shutdown[1]: Unmounting file systems.
[ 1098.034057] systemd-shutdown[1]: Remounting '/' read-only with options 'errors=remount-ro'.
[ 1098.136413] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[ 1098.170623] systemd-shutdown[1]: Remounting '/' read-only with options 'errors=remount-ro'.
[ 1098.190673] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[ 1098.201324] systemd-shutdown[1]: All filesystems unmounted.
[ 1098.202148] systemd-shutdown[1]: Deactivating swaps.
[ 1098.213226] systemd-shutdown[1]: All swaps deactivated.
[ 1098.213958] systemd-shutdown[1]: Detaching loop devices.
[ 1098.240692] systemd-shutdown[1]: All loop devices detached.
[ 1098.370880] reboot: Power down
^ phone is off at this point
-- Sebastian