Bug#1021391: marked as done (Kernel Exception at BananaPi M2 Ultra)
Your message dated Fri, 30 Dec 2022 16:25:50 + with message-id <224e7a8db88151a8cb34e4e08249d1859f6fdf4f.ca...@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 ow...@bugs.debian.org immediately.) -- 1021391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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: > > [ 102.815102] 1fc0: > > [ 102.823272] 1fe0: 0013 > [ 102.829880] ---[ end trace ]--- > [ 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 U-Boot SPL 2022.10+dfsg-1 (Oct 04 2022 - 00:06:38 +) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2022.10+dfsg-1 (Oct 04 2022 - 00:06:38 +) Allwinner Technology CPU: Allwinner R40 (SUN8I 1701) Model: Banana Pi BPI-M2-Ultra DRAM: 2 GiB Core: 65 devices, 22 uclasses, devicetree: separate WDT: Not starting watchdog@1c20c90 MMC: mmc@1c0f000: 0, mmc@1c1: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In:serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: eth0: ethernet@1c5 starting USB... Bus usb@1c19000:
Bug#1027325: /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found
Hi,
Thanks Diederik.
On Fri, Dec 30, 2022 at 01:01:55PM +0100, Diederik de Haas wrote:
> On Friday, 30 December 2022 12:42:53 CET Thorsten Glaser wrote:
> > I think I reported the same thing against experimental some time ago,
> > but it now is a regression in stable. Building kernel modules shows:
> >
> > tglase@tglase-edge:~/lnx/master/janz $ make
> > make -C '/lib/modules/5.10.0-20-amd64/build'
> > M='/home/tglase/lnx/master/janz' modules make[1]: Entering directory
> > '/usr/src/linux-headers-5.10.0-20-amd64' W: /bin/sh:
> > /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh:
> > inaccessible or not found
>
> That's likely https://bugs.debian.org/1008501 that was fixed here:
> https://salsa.debian.org/kernel-team/linux/-/commit/ee29a5e231886d26cef901285bf46a1f929ad4eb
Upstream commit c5006abb80e2 ("kbuild: Unify options for BTF
generation for vmlinux and modules") was as well backported in the
last rounds to 5.10.151, so yes we need the same fix for bullseye as
well.
Have added it to the bullseye branch for the next upload.
Regards,
Salvatore
Processed: forcibly merging 1008501 1027325
Processing commands for cont...@bugs.debian.org:
> forcemerge 1008501 1027325
Bug #1008501 {Done: Salvatore Bonaccorso } [src:linux]
pahole-flags.sh: inaccessible or not found
Bug #1027325 [src:linux]
/usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible
or not found
Marked Bug as done
Marked as fixed in versions linux/5.17.3-1.
Marked as found in versions linux/5.16.18-1 and linux/5.17~rc8-1~exp1.
Bug #1008501 {Done: Salvatore Bonaccorso } [src:linux]
pahole-flags.sh: inaccessible or not found
Marked as found in versions linux/5.10.158-1.
Added tag(s) confirmed.
Merged 1008501 1027325
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1008501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008501
1027325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1027325 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1027325 src:linux 5.10.158-1 Bug #1027325 [linux-headers-5.10.0-20-common] /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found Bug reassigned from package 'linux-headers-5.10.0-20-common' to 'src:linux'. No longer marked as found in versions linux/5.10.158-2. Ignoring request to alter fixed versions of bug #1027325 to the same values previously set Bug #1027325 [src:linux] /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found Marked as found in versions linux/5.10.158-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): unarchiving 1008501, forcibly merging 1008501 1027325, found 1008501 in 5.10.158-1
Processing commands for cont...@bugs.debian.org:
> unarchive 1008501
Bug #1008501 {Done: Salvatore Bonaccorso } [src:linux]
pahole-flags.sh: inaccessible or not found
Unarchived Bug 1008501
> forcemerge 1008501 1027325
Bug #1008501 {Done: Salvatore Bonaccorso } [src:linux]
pahole-flags.sh: inaccessible or not found
Unable to merge bugs because:
package of #1027325 is 'linux-headers-5.10.0-20-common' not 'src:linux'
Failed to forcibly merge 1008501: Did not alter merged bugs.
> found 1008501 5.10.158-1
Failed to add found on 1008501: failed to get lock on
/srv/bugs.debian.org/spool/lock/1008501 -- Unable to lock
/srv/bugs.debian.org/spool/lock/1008501 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1008501 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1008501 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1008501 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1008501 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1008501 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1008501 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1008501 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1008501 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1008501 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1008501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008501
1027325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1027325
Processing commands for cont...@bugs.debian.org: > tags 1027325 + confirmed Bug #1027325 [linux-headers-5.10.0-20-common] /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027325: /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found
On Friday, 30 December 2022 12:42:53 CET Thorsten Glaser wrote: > I think I reported the same thing against experimental some time ago, > but it now is a regression in stable. Building kernel modules shows: > > tglase@tglase-edge:~/lnx/master/janz $ make > make -C '/lib/modules/5.10.0-20-amd64/build' > M='/home/tglase/lnx/master/janz' modules make[1]: Entering directory > '/usr/src/linux-headers-5.10.0-20-amd64' W: /bin/sh: > /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: > inaccessible or not found That's likely https://bugs.debian.org/1008501 that was fixed here: https://salsa.debian.org/kernel-team/linux/-/commit/ee29a5e231886d26cef901285bf46a1f929ad4eb signature.asc Description: This is a digitally signed message part.
Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang
On Friday, 30 December 2022 01:48:53 CET Stefan Pietsch wrote: > >> Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and > >> linux-image-5.6.0-2-amd64 (5.6.14-1).> > > This also affects 5.5.0-rc5-amd64. > > > > (https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/l > > inux/) > > > > The kernel boot option "intel_iommu=igfx_off" prevents the error message. > > This seems to be resolved in newer kernel versions. > I'm not able to reproduce this with kernel version 5.14.0-4-amd64 > (5.14.16-1). Great that it is resolved :-) As many people are affected and the Stable kernel version still seems to exhibit the problem, I want to ask a question: Are you willing to help out to narrow down as much as possible which version introduced the error and in which is was fixed? Wrt the latter, does 5.14.12-1 still show the issue? Via https://snapshot.debian.org/binary/linux-image-amd64/ you get (easily) get all the kernel versions that were released. If we know a (reasonably) small range of kernel versions in which it surfaced and a small range in which it was fixed, then we could make some educated guesses as to which commit caused the issue in the first place. TIA, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1027325: /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found
Package: linux-headers-5.10.0-20-common Version: 5.10.158-2 Severity: normal X-Debbugs-Cc: t...@mirbsd.de I think I reported the same thing against experimental some time ago, but it now is a regression in stable. Building kernel modules shows: tglase@tglase-edge:~/lnx/master/janz $ make make -C '/lib/modules/5.10.0-20-amd64/build' M='/home/tglase/lnx/master/janz' modules make[1]: Entering directory '/usr/src/linux-headers-5.10.0-20-amd64' W: /bin/sh: /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found W: /bin/sh: /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found CC [M] /home/tglase/lnx/master/janz/sch_janz.o CC [M] /home/tglase/lnx/master/janz/sch_janzdbg.o W: /bin/sh: /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found MODPOST /home/tglase/lnx/master/janz/Module.symvers CC [M] /home/tglase/lnx/master/janz/sch_janz.mod.o LD [M] /home/tglase/lnx/master/janz/sch_janz.ko CC [M] /home/tglase/lnx/master/janz/sch_janzdbg.mod.o LD [M] /home/tglase/lnx/master/janz/sch_janzdbg.ko make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-20-amd64' -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-20-amd64 (SMP w/3 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) -- no debconf information
Processed: forcibly merging 1027304 1027306
Processing commands for cont...@bugs.debian.org: > forcemerge 1027304 1027306 Bug #1027304 [linux-kbuild-6.0] linux-kbuild-6.0: missing `resolve_btfids` and some scripts Bug #1027306 [linux-kbuild-6.0] linux-kbuild-6.0: missing `resolve_btfids` and some scripts Merged 1027304 1027306 > thanks Stopping processing here. Please contact me if you need assistance. -- 1027304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027304 1027306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962003: marked as done (Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang)
Your message dated Fri, 30 Dec 2022 09:04:03 +0100 with message-id and subject line Re: Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang has caused the Debian Bug report #962003, regarding Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang 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 ow...@bugs.debian.org immediately.) -- 962003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-amd64 Version: 5.6.14-1 Starting with Linux kernel package linux-image-5.6.0-1-amd64 (5.6.7-1) I get the following error message that is repeating every few seconds: kernel: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang. Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and linux-image-5.6.0-2-amd64 (5.6.14-1). The error message does not appear with linux-image-5.4.0-4-amd64 (5.4.19-1). Hardware is a Lenovo T410 with integrated Intel graphics controller. --- End Message --- --- Begin Message --- Source: linux Source-Version: 5.14.16-1 Hi Stefan, On Fri, Dec 30, 2022 at 12:48:53AM +, Stefan Pietsch wrote: > On 07.06.20 08:48, Stefan Pietsch wrote: > > On 2020-06-01 20:44, Stefan Pietsch wrote: > > > > > Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and > > > linux-image-5.6.0-2-amd64 (5.6.14-1). > > > > This also affects 5.5.0-rc5-amd64. > > > > (https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/linux/) > > > > The kernel boot option "intel_iommu=igfx_off" prevents the error message. > > This seems to be resolved in newer kernel versions. > I'm not able to reproduce this with kernel version 5.14.0-4-amd64 (5.14.16-1). Thanks for bisecting/investigating. In this case let's for version tracking mark the bug as fixed with 5.14.16-1. This leaves open yet if a fix for 5.10.y can be isolated to have the fix as well in bullseye. Regards, Salvatore--- End Message ---
