Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #76445 > unrolled thread

Bug#1021391: Kernel Exception at BananaPi M2 Ultra

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1021391: Kernel Exception at BananaPi M2 Ultra Bernhard <bernhard.woerner@posteo.de> - 2022-10-07 14:00 +0200
    Bug#1021391: Kernel Exception at BananaPi M2 Ultra Diederik de Haas <didi.debian@cknow.org> - 2022-10-07 15:40 +0200
    Processed: Re: Bug#1021391: Kernel Exception at BananaPi M2 Ultra "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-10-07 15:40 +0200
    Bug#1021391: Possible solution with kernel 6.0.11 Bernhard <bernhard.woerner@posteo.de> - 2022-12-05 13:30 +0100
      Bug#1021391: Possible solution with kernel 6.0.11 Salvatore Bonaccorso <carnil@debian.org> - 2022-12-05 22:10 +0100
    Bug#1021391: Possible solved with kernel 6.0.12 Bernhard <bernhard.woerner@posteo.de> - 2022-12-26 17:40 +0100
      Bug#1021391: Possible solved with kernel 6.0.12 Salvatore Bonaccorso <carnil@debian.org> - 2022-12-27 09:40 +0100
    Bug#1021391: marked as done (Kernel Exception at BananaPi M2 Ultra) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-12-30 17:30 +0100

#76445 — Bug#1021391: Kernel Exception at BananaPi M2 Ultra

[Multipart message — attachments visible in raw view] — view raw

Package: src:linux
Severity: normal
Version: 5.19.11-1

Hello,

I installed with the daily images "testing, bookworm" to Banana Pi M2 Ultra.
After poweroff, there is a kernel exception regarding i2c:

> Last login: Fri Oct  7 13:02:50 CEST 2022 on ttyS0
> [?2004hroot@Banana-Test:~# poweroff
> [?2004l
> Failed to connect to bus: No such file or directory
> [   92.114464] reboot: Power down
> [   94.163385] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
> [  102.615362] ------------[ cut here ]------------
> [  102.619982] WARNING: CPU: 0 PID: 13 at kernel/irq_work.c:134 irq_work_queue_on+0x104/0x108
> [  102.628259] Modules linked in: hci_uart btqca btrtl btbcm btintel bluetooth jitterentropy_rng sha512_generic sha512_arm snd_soc_hdmi_codec dw_hdmi_cec dw_hdmi_i2s_audio evdev sun8i_drm_hdmi
> aes_arm_bs crypto_simd dw_hdmi cryptd drbg axp20x_adc drm_display_helper industrialio cec ansi_cprng brcmfmac brcmutil axp20x_pek sun4i_i2s lima ecdh_generic gpu_sched ecc drm_shmem_helper sunxi_cir
> snd_soc_core snd_pcm_dmaengine sunxi_cedrus(C) snd_pcm rc_core v4l2_mem2mem snd_timer sun8i_thermal sunxi_wdt cfg80211 snd videobuf2_dma_contig soundcore videobuf2_memops videobuf2_v4l2
> videobuf2_common rfkill videodev mc leds_gpio sun6i_dma display_connector fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic realtek ahci_sunxi libahci_platform
> dwmac_sun8i libahci stmmac_platform axp20x_regulator stmmac pcs_xpcs phylink mdio_mux of_mdio fixed_phy fwnode_mdio libphy ptp libata pps_core i2c_mv64xxx ehci_platform ohci_platform ohci_hcd
> phy_sun4i_usb ehci_hcd sun4i_drm scsi_mod
> [  102.628661]  sun4i_frontend usbcore sunxi_mmc sun8i_mixer scsi_common sun4i_tcon sun8i_tcon_top drm_cma_helper drm_kms_helper drm
> [  102.727286] CPU: 0 PID: 13 Comm: rcu_sched Tainted: G         C        5.19.0-2-armmp-lpae #1  Debian 5.19.11-1
> [  102.737367] Hardware name: Allwinner sun8i Family
> [  102.742078]  unwind_backtrace from show_stack+0x18/0x1c
> [  102.747314]  show_stack from dump_stack_lvl+0x40/0x4c
> [  102.752374]  dump_stack_lvl from __warn+0xd0/0x134
> [  102.757176]  __warn from warn_slowpath_fmt+0x80/0xbc
> [  102.762145]  warn_slowpath_fmt from irq_work_queue_on+0x104/0x108
> [  102.768242]  irq_work_queue_on from rcu_implicit_dynticks_qs+0x200/0x330
> [  102.774951]  rcu_implicit_dynticks_qs from force_qs_rnp+0x154/0x250
> [  102.781223]  force_qs_rnp from rcu_gp_fqs_loop+0x224/0x320
> [  102.786714]  rcu_gp_fqs_loop from rcu_gp_kthread+0x110/0x174
> [  102.792377]  rcu_gp_kthread from kthread+0xd8/0xf4
> [  102.797174]  kthread from ret_from_fork+0x14/0x34
> [  102.801881] Exception stack(0xf0851fb0 to 0xf0851ff8)
> [  102.806932] 1fa0:                                     00000000 00000000 00000000 00000000
> [  102.815102] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> [  102.823272] 1fe0: 00000000 00000000 00000000 00000000 00000013 0000000
0
> [  102.829880] ---[ end trace 0000000000000000 ]---
> [  113.127339] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
> [  113.133263] rcu: 	3-O..0: (1 GPs behind) idle=7ad/0/0x1 softirq=4245/4248 fqs=1219 
> [  113.140921] 	(detected by 0, t=5255 jiffies, g=2641, q=52 ncpus=4)
> [  113.147098] rcu: Offline CPU 3 blocking current GP.
> 

The complete log from RS232 is attached.
Hopefully it helps.

If i can do some other tests, please let me know.

Best regards and thank you for your support.
Bernhard

[toc] | [next] | [standalone]

#76446

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On vrijdag 7 oktober 2022 13:50:46 CEST Bernhard wrote:
> The complete log from RS232 is attached.

> Starting kernel ...
> 
> [    0.003958] /cpus/cpu@0 missing clock-frequency property
> [    0.003995] /cpus/cpu@1 missing clock-frequency property
> [    0.004012] /cpus/cpu@2 missing clock-frequency property
> [    0.004029] /cpus/cpu@3 missing clock-frequency property

That looks bad.
It is that you already said that the *complete* log was attached, otherwise 
I'd have asked whether you filtered it for errors as (pretty much) every line 
looks troublesome :-O

> If i can do some other tests, please let me know.

Knowing if it worked before is rather useful and if so, with which kernel 
version that would be. I don't know if installing a different kernel version 
would automatically update the dtbs that are used, so please verify that.

And I think it would also be good to verify things with u-boot package from 
testing (version 2022.04+dfsg-2)

[toc] | [prev] | [next] | [standalone]

#76447 — Processed: Re: Bug#1021391: Kernel Exception at BananaPi M2 Ultra

Processing control commands:

> tag -1 moreinfo
Bug #1021391 [src:linux] Kernel Exception at BananaPi M2 Ultra
Added tag(s) moreinfo.

-- 
1021391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021391
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#77434 — Bug#1021391: Possible solution with kernel 6.0.11

[Multipart message — attachments visible in raw view] — view raw

Hello Salvatore

It is possible, that kernel 6.0.11 solves the Bug #1021391 because of

>>>
- [arm64,armhf] bus: sunxi-rsb: Remove the shutdown callback
    - [arm64,armhf] bus: sunxi-rsb: Support atomic transfers
<<<

If i have a look at the ARM kernel mailinglist, there are bugfixes for this I2C:

>>>
Shutting down the RSB controller prevents communicating with a PMIC
inside pm_power_off(), so it breaks system poweroff on some boards.
<<<

>>>
This series fixes a couple of issues that occur when powering off a
board using a PMIC attached to the RSB bus.

These issues only affected 32-bit platforms, because 64-bit platforms
use PSCI for pm_power_off(), and the PSCI firmware reinitializes the
RSB controller.
<<<

>>>
When communicating with a PMIC during system poweroff (pm_power_off()),
IRQs are disabled and we are in a RCU read-side critical section, so we
cannot use wait_for_completion_io_timeout(). Instead, poll the status
register for transfer completion.
<<<

Is it planned, to release this kernel in the next days?
I'm really very interested in testing.

Best regards and thank you for the very great support.
Bernhard

[toc] | [prev] | [next] | [standalone]

#77454 — Bug#1021391: Possible solution with kernel 6.0.11

Hi Bernhard,

On Mon, Dec 05, 2022 at 12:21:48PM +0000, Bernhard wrote:
> Hello Salvatore
> 
> It is possible, that kernel 6.0.11 solves the Bug #1021391 because of
> 
> >>>
> - [arm64,armhf] bus: sunxi-rsb: Remove the shutdown callback
>     - [arm64,armhf] bus: sunxi-rsb: Support atomic transfers
> <<<
> 
> If i have a look at the ARM kernel mailinglist, there are bugfixes for this I2C:
> 
> >>>
> Shutting down the RSB controller prevents communicating with a PMIC
> inside pm_power_off(), so it breaks system poweroff on some boards.
> <<<
> 
> >>>
> This series fixes a couple of issues that occur when powering off a
> board using a PMIC attached to the RSB bus.
> 
> These issues only affected 32-bit platforms, because 64-bit platforms
> use PSCI for pm_power_off(), and the PSCI firmware reinitializes the
> RSB controller.
> <<<
> 
> >>>
> When communicating with a PMIC during system poweroff (pm_power_off()),
> IRQs are disabled and we are in a RCU read-side critical section, so we
> cannot use wait_for_completion_io_timeout(). Instead, poll the status
> register for transfer completion.
> <<<
> 
> Is it planned, to release this kernel in the next days?
> I'm really very interested in testing.

I was pondering it actually, and the changes are waiting in the sid
branch, but wanted to include the changes of upcoming 6.0.12 as well
in the next update.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#77730 — Bug#1021391: Possible solved with kernel 6.0.12

[Multipart message — attachments visible in raw view] — view raw

Hello all

It seems, with Kernel 6.0.12 this problem is solved.
This problem was never shown with kernel 6.0.12.

I'll have a further look for the next days.
After that, i'll close this bug.

Best regards and thank you for the great work.
Bernhard

[toc] | [prev] | [next] | [standalone]

#77742 — Bug#1021391: Possible solved with kernel 6.0.12

Hi Bernhard,

On Mon, Dec 26, 2022 at 04:37:48PM +0000, Bernhard wrote:
> Hello all
> 
> It seems, with Kernel 6.0.12 this problem is solved.
> This problem was never shown with kernel 6.0.12.
> 
> I'll have a further look for the next days.
> After that, i'll close this bug.

Many thanks for reporting back. If it does not show furthr up in the
next few days then please do close it as you said, add please a
corresponding fixed version to 6.0.12-1.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#77774 — Bug#1021391: marked as done (Kernel Exception at BananaPi M2 Ultra)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Fri, 30 Dec 2022 16:25:50 +0000
with message-id <224e7a8db88151a8cb34e4e08249d1859f6fdf4f.camel@posteo.de>
and subject line Misbehaviour was never shown after kernel update
has caused the Debian Bug report #1021391,
regarding Kernel Exception at BananaPi M2 Ultra
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1021391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021391
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web