Source: linux Version: 4.4.6-1 Severity: normal Tags: upstream Dear Maintainer,
After upgrading from jessie to stretch, my Cubieboard (Allwinner A20) no longer powers down; instead, the machine halts with a kernel panic while continuing to be powered. I captured the following output on the serial console: # poweroff [ 654.415345] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 654.457107] systemd-journald[272]: Received SIGTERM from PID 1 (systemd-shutdow). [ 654.576175] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 654.614229] systemd-shutdown[1]: Unmounting file systems. [ 654.624854] systemd-shutdown[1]: Remounting '/' read-only with options 'ssd,discard,space_cache,subvolid=5,subvol=/'. [ 654.900813] BTRFS info (device dm-0): disk space caching is enabled [ 655.043127] systemd-shutdown[1]: Remounting '/' read-only with options 'ssd,discard,space_cache,subvolid=5,subvol=/'. [ 655.058439] BTRFS info (device dm-0): disk space caching is enabled [ 655.069255] systemd-shutdown[1]: All filesystems unmounted. [ 655.079341] systemd-shutdown[1]: Deactivating swaps. [ 655.089177] systemd-shutdown[1]: All swaps deactivated. [ 655.099060] systemd-shutdown[1]: Detaching loop devices. [ 655.109904] systemd-shutdown[1]: All loop devices detached. [ 655.120212] systemd-shutdown[1]: Detaching DM devices. [ 655.131915] systemd-shutdown[1]: Detaching DM 254:0. [ 655.141723] systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy [ 655.154470] systemd-shutdown[1]: Not all DM devices detached, 1 left. [ 655.165667] systemd-shutdown[1]: Cannot finalize remaining DM devices, continuing. [ 655.180404] systemd-shutdown[1]: Failed to finalize DM devices, ignoring [ 655.192305] systemd-shutdown[1]: Powering off. [ 655.201618] kvm: exiting hardware virtualization [ 655.211292] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 655.221730] sd 0:0:0:0: [sda] Stopping disk [ 655.323690] reboot: Power down [ 657.329374] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 657.342678] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000 [ 657.342678] [ 657.361647] CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 4.4.0-1-armmp-lpae #1 Debian 4.4.6-1 [ 657.375569] Hardware name: Allwinner sun7i (A20) Family [ 657.385995] [<c0037098>] (unwind_backtrace) from [<c00311b4>] (show_stack+0x20/0x24) [ 657.399051] [<c00311b4>] (show_stack) from [<c02fc27c>] (dump_stack+0xa0/0xb4) [ 657.411627] [<c02fc27c>] (dump_stack) from [<c0170170>] (panic+0xc0/0x258) [ 657.423871] [<c0170170>] (panic) from [<c0070b1c>] (do_exit+0xa54/0xa78) [ 657.435964] [<c0070b1c>] (do_exit) from [<c008f948>] (SyS_reboot+0x1c8/0x238) [ 657.448589] [<c008f948>] (SyS_reboot) from [<c002cbc0>] (ret_fast_syscall+0x0/0x34) [ 657.461841] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000 [ 657.461841] In order to pinpoint the kernel version that introduced the regression, I tested the following kernels from snapshot.d.o: linux-image-4.0.0-2-armmp-lpae 4.0.8-2 OK linux-image-4.1.0-2-armmp-lpae 4.1.6-1 OK linux-image-4.2.0-1-armmp-lpae 4.2.6-3 PANIC linux-image-4.3.0-1-armmp-lpae 4.3.5-1 PANIC linux-image-4.4.0-1-armmp-lpae 4.4.6-1 PANIC The regression has been introduced in Linux 4.2. I compared the serial console output of Linux 4.2/4.3/4.4, and, apart from the address offsets, the stack traces of the kernel panic are identical. Please let me know how I can help with further debugging. Regards, Peter
