Bug#1015167: CPU stall while running fwupdmgr
On Aug 13, Salvatore Bonaccorso wrote: > Do you still experience this problem with the latest kernel in > unstable or experimental? No, but IIRC the bug was not deterministic and a later update with the same kernel did not actually trigger it. -- ciao, Marco signature.asc Description: PGP signature
Upcoming oldstable point release (10.13)
Hi, The next - and final - point release for "buster" (10.13) is scheduled for Saturday, September 10th. Processing of new uploads into buster- proposed-updates will be frozen during the weekend of August 27th. Regards, Adam
Upcoming stable point release (11.5)
Hi, The next point release for "bullseye" (11.5) is scheduled for Saturday, September 10th. Processing of new uploads into bullseye-proposed- updates will be frozen during the preceding weekend. Regards, Adam
Processed: Re: Bug#1016317: linux-image-5.10.0-16-armmp: insecure W+X mapping
Processing control commands: > tags -1 + moreinfo Bug #1016317 [src:linux] linux-image-5.10.0-16-armmp: insecure W+X mapping Added tag(s) moreinfo. -- 1016317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016317: linux-image-5.10.0-16-armmp: insecure W+X mapping
Control: tags -1 + moreinfo
On Fri, Jul 29, 2022 at 08:04:56PM +0200, Rainer Dorsch wrote:
> Package: src:linux
> Version: 5.10.127-2
> Severity: normal
>
> Dear Maintainer,
>
> I just noticed after booting into the kernel 5.10.0-16-armmp #1 SMP Debian
> 5.10.127-2 (2022-07-23) armv7l GNU/Linux (on a SolidRun Cubox-i with an NXP
> iMX6) that I get an
>
> insecure W+X mapping at address 0xf0879000
>
> on a serial console and a backtrace during the boot process:
>
> [5.377591] Registering SWP/SWPB emulation handler
> [5.382640] registered taskstats version 1
> [5.386784] Loading compiled-in X.509 certificates
> [5.787454] Loaded X.509 cert 'Debian Secure Boot CA:
> 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1'
> [5.796311] Loaded X.509 cert 'Debian Secure Boot Signer 2021 - linux:
> 4b6ef5abca669825178e052c84667ccbc0531f8c'
> [5.806849] zswap: loaded using pool lzo/zbud
> [5.812253] Key type ._fscrypt registered
> [5.816352] Key type .fscrypt registered
> [5.820314] Key type fscrypt-provisioning registered
> [5.825722] AppArmor: AppArmor sha1 policy hashing enabled
> [5.865627] vcc_3v3: supplied by v_5v0
> [5.895845] Freeing unused kernel memory: 2048K
> [5.913843] [ cut here ]
> [5.918527] WARNING: CPU: 0 PID: 1 at arch/arm/mm/dump.c:248
> note_page+0x3d0/0x3dc
> [5.926143] arm/mm: Found insecure W+X mapping at address 0xf0879000
> [5.932529] Modules linked in:
> [5.935629] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.0-16-armmp #1
> Debian 5.10.127-2
> [5.943912] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
> [5.950457] Backtrace:
> [5.952938] [] (dump_backtrace) from []
> (show_stack+0x20/0x24)
> [5.960532] r7:00f8 r6:6013 r5: r4:c14cdda8
> [5.966215] [] (show_stack) from []
> (dump_stack+0xc8/0xdc)
> [5.973469] [] (dump_stack) from [] (__warn+0xfc/0x158)
> [5.980449] r7:00f8 r6:0009 r5:c031fa38 r4:c0fbe5c8
> [5.986130] [] (__warn) from []
> (warn_slowpath_fmt+0xa4/0xe4)
> [5.993633] r7:c031fa38 r6:00f8 r5:c0fbe5c8 r4:c0fbe594
> [5.999311] [] (warn_slowpath_fmt) from []
> (note_page+0x3d0/0x3dc)
> [6.007251] r8: r7: r6:0005 r5:c140c4e0 r4:c197ff28
> [6.013971] [] (note_page) from []
> (walk_pmd+0xe8/0x1a4)
> [6.021042] r10:c197ff28 r9:c0207c20 r8:c1900800 r7: r6:c0fbe610
> r5:f087b000
> [6.02] r4:c19001ec
> [6.031437] [] (walk_pmd) from []
> (ptdump_check_wx+0x88/0x104)
> [6.039030] r10: r9: r8: r7: r6:c0208000
> r5:f080
> [6.046878] r4:c0207c28
> [6.049435] [] (ptdump_check_wx) from []
> (mark_rodata_ro+0x3c/0x40)
> [6.057459] r6: r5:c0d092cc r4:
> [6.062103] [] (mark_rodata_ro) from []
> (kernel_init+0x44/0x130)
> [6.069873] [] (kernel_init) from []
> (ret_from_fork+0x14/0x2c)
> [6.077459] Exception stack(0xc197ffb0 to 0xc197fff8)
> [6.082528] ffa0:
>
> [6.090726] ffc0:
>
> [6.098924] ffe0: 0013
> [6.105553] r5:c0d092cc r4:
> [6.109187] ---[ end trace 36d095f56a800b3c ]---
> [6.114076] Checked W+X mappings: FAILED, 1 W+X pages found
> [6.119751] Run /init as init process
> [6.847313] gpio_mxc: module verification failed: signature and/or
> required
> key missing - tainting kernel
> [6.859257] vdd1p1: supplied by regulator-dummy
> [6.871900] v_usb2: supplied by v_5v0
> [6.876972] vdd3p0: supplied by regulator-dummy
> [6.882630] vdd2p5: supplied by regulator-dummy
> [6.887949] vddarm: supplied by regulator-dummy
> [6.893661] vddpu: supplied by regulator-dummy
> [6.898847] vddsoc: supplied by regulator-dummy
>
> I do not observe any functional issue so far though.
>
> Since I have not checked the output of the serial console for a while, I
> cannot tell when
> the issue started to appear.
>
> There is a similar report for the same hardware platform, but is reported on
> a 5.13 kernel:
> https://lore.kernel.org/all/yun2qpc5ibaiv...@shell.armlinux.org.uk/T/
>
> I am not sure if it was already present in 5.10, if it got backported or if
> it is
> entirely unrelated.
>
> Many thanks for the great support of many hardware platforms
Would it be possible that you try to cherry-pick upstream 4aede550f104
("ARM: imx6: mark OCRAM mapping read-only") to see if it solves the
issue?
Can you alternatively test the package from bullseye-backports which
would have the fix included and see if the issue goes away?
Regards,
Salvatore
Processed: reassign 1015167 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1015167 src:linux 5.18.5-1 Bug #1015167 [src:linux] CPU stall while running fwupdmgr Ignoring request to reassign bug #1015167 to the same package Bug #1015167 [src:linux] CPU stall while running fwupdmgr Marked as found in versions linux/5.18.5-1; no longer marked as found in versions linux/5.10.127-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1015004 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1015004 src:linux 5.18.5-1 Bug #1015004 [linux-source] No "beep" after a reboot (system restart) Bug reassigned from package 'linux-source' to 'src:linux'. No longer marked as found in versions linux/5.18.5-1. Ignoring request to alter fixed versions of bug #1015004 to the same values previously set Bug #1015004 [src:linux] No "beep" after a reboot (system restart) Marked as found in versions linux/5.18.5-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1015295: linux-image-5.10.0-16-arm64: Unbootable system due to F2FS sanity_check_inode errors after upgrading kernel
Processing control commands: > tags -1 + moreinfo Bug #1015295 [src:linux] linux-image-5.10.0-16-arm64: Unbootable system due to F2FS sanity_check_inode errors after upgrading kernel Added tag(s) moreinfo. -- 1015295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015295: linux-image-5.10.0-16-arm64: Unbootable system due to F2FS sanity_check_inode errors after upgrading kernel
Control: tags -1 + moreinfo On Tue, Jul 19, 2022 at 05:50:13AM +0200, Lukasz K. wrote: > Package: linux-image-5.10.0-16-arm64 > Severity: critical > Justification: breaks the whole system > X-Debbugs-Cc: mov...@cryptolab.net > > Dear Maintainer, > > After upgrading kernel from linux-image-5.10.0-14-arm64 to > linux-image-5.10.0-16-arm64 my system became unbootable due to F2FS > sanity_check_inode errors. > > Going back to previous kernel fixed the issue. > > This does not appear to be limited only to Debian, as could be seen in this > thread: > https://github.com/raspberrypi/linux/issues/5068 > > Error messages are (aside from different device) the same as in the linked > thread above: > [ 10.395372] F2FS-fs (mmcblk0p2): sanity_check_inode: inode (ino=85f5, > mode=33188) should not have inline_data, run fsck to fix > [...] > > I am using F2FS for my root partition with zstd compression enabled. > > Partition was created with: > mkfs.f2fs -f -O > extra_attr,inode_checksum,sb_checksum,compression,quota,encrypt DEVICE > > And is mounted with: > flush_merge,data_flush,compress_algorithm=zstd > > Compression was explicitly enabled for entire root partition during > installation > with: > mount -t f2fs -o flush_merge,data_flush,compress_algorithm=zstd DEVICE /target > chattr -R -V +c /target > > Linked thread also mentions that this was fixed upstream. The referenced commit seems to have actually landed in 5.10.127 upstream. So this probably needs more investigation. Can you for your device test upstrema kernels and test if 5.10.136 upstream fixes the issue? Can you bisect the breaking commit upstream between the two versions working in Debian and breaking? Regards, Salvatore
Processed: Re: Bug#1015167: CPU stall while running fwupdmgr
Processing control commands: > tags -1 + moreinfo Bug #1015167 [src:linux] CPU stall while running fwupdmgr Added tag(s) moreinfo. -- 1015167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015167: CPU stall while running fwupdmgr
Control: tags -1 + moreinfo Hi Marco, On Sun, Jul 17, 2022 at 01:49:12AM +0200, Marco d'Itri wrote: > On Jul 17, Diederik de Haas wrote: > > > On Sunday, 17 July 2022 01:34:08 CEST Marco d'Itri wrote: > > > Source: linux > > > Version: 5.10.127-1 > > > Severity: normal > ... > > > Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) > > > > Why is this bug filed against kernel version 5.10.127-1 and not 5.18.5-1? > I wondered myself, but I do not know why reportbug choose the version of > the stable package. > > ii linux-image-5.18.0-2-amd64 5.18.5-1 amd64Linux 5.18 for > 64-bit > > > 5.18.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.5-1 (2022-06-16) x86_64 > GNU/Linux Do you still experience this problem with the latest kernel in unstable or experimental? Regards, Salvatore
Processed: closing 983818
Processing commands for cont...@bugs.debian.org: > close 983818 5.18.14-1 Bug #983818 [src:linux] linux-image-5.10.0-3-arm64: often fails to bring up ethernet / dwmac_rk module on rockpro64 Marked as fixed in versions linux/5.18.14-1. Bug #983818 [src:linux] linux-image-5.10.0-3-arm64: often fails to bring up ethernet / dwmac_rk module on rockpro64 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 983818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014793: linux-image-5.10.0-16-amd64: Kernel crashes while serving NFS
Hi Arne,
On Fri, Jul 22, 2022 at 10:18:56AM +0200, Arne Nordmark wrote:
> Den 2022-07-15 kl. 21:58, skrev Salvatore Bonaccorso:
> > I would be interested to either pinpoint the regressing commit
> > upstream beween 5.10.120 and 5.10.127 or conversely the fixing commit
> > beween 5.10.127 upstream and 5.10.130 where you are not able anymore
> > to reproduce the error. What I can say, I have already imported
> > 5.10.130 for furture upload (cf.
> > https://salsa.debian.org/kernel-team/linux/-/merge_requests/506).
>
> Bisection for the regression proved too hard.
>
> Bisection for the fix went better, I can get a crash with 5.10.128-00010 but
> not yet with 5.10.128-00011. This indicates that the fixing commit was
> probably:
>
> commit 6a0b9512a6aa7b7835d8138f5ffdcb4789c093d4
> Author: Chuck Lever
> Date: Thu Jun 30 16:48:18 2022 -0400
>
> SUNRPC: Fix READ_PLUS crasher
>
> which indeed seems to touch code involved in NFS service.
>
> Consequently, the breaking commit was probably:
>
> 6c254bf3b637 ("SUNRPC: Fix the calculation of xdr->end in
> xdr_get_next_encode_buffer()")
Thank you and apologies for the delay! The next upload for
bullseye(-security) will contain that fix and will close the bug with
that upload.
Thanks a lot for your investigtive work and bisection to the fix!
Regards,
Salvatore
