Banana Pi don't shutdown - kernel panic

[Tone]

My Banana Pi get a kernel panic if I try to shut it down as you can see in the picture.

How can I fix this?

I'm using 

Armbian 22.02.1 with Linux 5.15.25-sunxi

 

http://ix.io/3VHA

 

sudo i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

[Werner]

Moved to P2P help.

[Myron]

I've noticed this too on my BananaPi Pro board too.   From my board the armbianmonitor diagnostics is here: http://ix.io/3VH9

 

Here is what I get:

root@loki:~# poweroff
[503985.574336] reboot: Power down
[503985.612166] ------------[ cut here ]------------
[503985.668455] WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.h:41 i2c_transfer+0x93/0xbc
[503985.764283] No atomic I2C transfer handler for 'i2c-1'
[503985.826794] Modules linked in: tun cmac nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs overlay xt_multiport l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_recent xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter evdev axp20x_adc brcmfmac lima gpu_sched sun4i_gpadc_iio industrialio brcmutil cfg80211 sun4i_ts sunxi_cir rfkill sunxi_cedrus(C) v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common display_connector uio_pdrv_genirq uio cpufreq_dt binfmt_misc sch_fq_codel sunrpc ip_tables x_tables autofs4 pwrseq_simple sun4i_gpadc realtek
[503986.634338] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G         C        5.15.32-sunxi #trunk
[503986.740544] Hardware name: Allwinner sun7i (A20) Family
[503986.804106] [<c010cea9>] (unwind_backtrace) from [<c01095b9>] (show_stack+0x11/0x14)
[503986.897846] [<c01095b9>] (show_stack) from [<c09cc035>] (dump_stack_lvl+0x2b/0x34)
[503986.989505] [<c09cc035>] (dump_stack_lvl) from [<c011b5a9>] (__warn+0xad/0xc0)
[503987.076999] [<c011b5a9>] (__warn) from [<c09c5c23>] (warn_slowpath_fmt+0x5f/0x7c)
[503987.167615] [<c09c5c23>] (warn_slowpath_fmt) from [<c0795a5f>] (i2c_transfer+0x93/0xbc)
[503987.264472] [<c0795a5f>] (i2c_transfer) from [<c0795ac3>] (i2c_transfer_buffer_flags+0x3b/0x50)
[503987.369648] [<c0795ac3>] (i2c_transfer_buffer_flags) from [<c0697577>] (regmap_i2c_write+0x13/0x24)
[503987.478985] [<c0697577>] (regmap_i2c_write) from [<c0694023>] (_regmap_raw_write_impl+0x48b/0x560)
[503987.587282] [<c0694023>] (_regmap_raw_write_impl) from [<c0694139>] (_regmap_bus_raw_write+0x41/0x5c)
[503987.698697] [<c0694139>] (_regmap_bus_raw_write) from [<c06939b1>] (_regmap_write+0x35/0xc8)
[503987.800753] [<c06939b1>] (_regmap_write) from [<c06948b5>] (regmap_write+0x29/0x3c)
[503987.893443] [<c06948b5>] (regmap_write) from [<c069e723>] (axp20x_power_off+0x23/0x30)
[503987.989261] [<c069e723>] (axp20x_power_off) from [<c0137ded>] (__do_sys_reboot+0xf5/0x16c)
[503988.089238] [<c0137ded>] (__do_sys_reboot) from [<c0100061>] (ret_fast_syscall+0x1/0x52)
[503988.187132] Exception stack(0xc1557fa8 to 0xc1557ff0)
[503988.248616] 7fa0:                   4321fedc be8b0aa8 fee1dead 28121969 4321fedc 00000000
[503988.347544] 7fc0: 4321fedc be8b0aa8 be8b0aa4 00000058 be8b0aa8 be8b0aa4 fffff000 be8b0aac
[503988.446465] 7fe0: 00000058 be8b0a1c b6f381b5 b6eb67e6
[503988.507941] ---[ end trace 7944c4f50e61189e ]---
[503989.583768] i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0
[503990.191744] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
[503990.284440] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G        WC        5.15.32-sunxi #trunk
[503990.390645] Hardware name: Allwinner sun7i (A20) Family
[503990.454205] [<c010cea9>] (unwind_backtrace) from [<c01095b9>] (show_stack+0x11/0x14)
[503990.547955] [<c01095b9>] (show_stack) from [<c09cc035>] (dump_stack_lvl+0x2b/0x34)
[503990.639611] [<c09cc035>] (dump_stack_lvl) from [<c09c5a4d>] (panic+0xc1/0x238)
[503990.727108] [<c09c5a4d>] (panic) from [<c011fd5d>] (complete_and_exit+0x1/0x18)
[503990.815643] [<c011fd5d>] (complete_and_exit) from [<fee1dead>] (0xfee1dead)
[503990.900024] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000 ]---

 

@Tone please provide logs for your board

 

Provide logs with 

armbianmonitor -u

 

[Tone]

I tried that to the time I created this post, but ix.io was down or something..

however, now it works again:

http://ix.io/3VHA

 

I also don't understand why armbian tells me in the motd I'm in a beta:

[ General system configuration (beta): armbian-config ]

[Myron]

52 minutes ago, Tone said:

I also don't understand why armbian tells me in the motd I'm in a beta:

[ General system configuration (beta): armbian-config ]

That's just for the armbian-config utility.

[Tone]

vor 14 Stunden schrieb Myron:

That's just for the armbian-config utility.

ah ok thank you!

 

Whats also strange to me, the last successful log is 

finished power-off
reached target power-off

so that means to me the power-off is finished, how can I get an kernel-panic after that? 

Tries the board to reboot? 

 

[Myron]

It's a guess. What the Kernel may be trying to so is to set the power controller to actually power-down the board, but that final function is turning it off is failing.

 

Seems like it is a very old bug and not just affecting the BananaPi Pro.

Ref: https://www.spinics.net/lists/linux-i2c/msg42348.html