Bug#1098661: fixed in linux 6.13.5-1~exp1

[Bastian Blank]

On Fri, Feb 28, 2025 at 09:14:33PM +0100, Salvatore Bonaccorso wrote:
> > I suggest that "flash-kernel" should be updated if zboot is to be enabled 
> > again in the future.
> Can you please fill a bug aainst frash-kernel as well (as Bastian
> cloned this one for grub as well?)

I'm trying to write those bugs.  There are more targets that needs them.
And we may want to start to use usertags for them.

Right now on my list is:
- flash-kernel
- raspi-firmware
- qemu (https://gitlab.com/qemu-project/qemu/-/issues/2810)

Any more?

Do we want to provide a tool for that?  Doing it in shell is cumbersome.

Bastian

-- 
There are certain things men must do to remain men.
-- Kirk, "The Ultimate Computer", stardate 4929.4

Processing of linux-signed-arm64_6.13.5+1~exp1_source.changes

[Debian FTP Masters]

linux-signed-arm64_6.13.5+1~exp1_source.changes uploaded successfully to 
localhost
along with the files:
  linux-signed-arm64_6.13.5+1~exp1.dsc
  linux-signed-arm64_6.13.5+1~exp1.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1099138: linux: CVE-2024-45001 in bookworm

[Noah Meyerhans]

Source: linux
Version: 6.1.128-1
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

I believe CVE-2024-45001 (RX buf alloc_size alignment and atomic op 
panic) is miscategorized as not impacting bookworm.  The issue is with 
the net/ethernet/microsoft/mana driver and was introduced in linux 6.10,
which is likely why the security-tracker contains the note "Vulnerable 
code not present" for bookworm.  However, bookworm contains a backported
version of this driver from 6.10 in
debian/patches/features/all/ethernet-microsoft. [1] [2]

The upstream fix applies on top of our patched 6.1 kernel with an 
offset. [3]

I didn't propose a fix to the security-tracker data because I don't know
the file format well enough.

I can prepare a merge request to the kernel package if that would help.

Thanks
noah

1. https://security-tracker.debian.org/tracker/CVE-2024-45001
2. 
https://salsa.debian.org/kernel-team/linux/-/tree/debian/6.1/bookworm/debian/patches/features/all/ethernet-microsoft?ref_type=heads
3. 
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=32316f676b4ee87c0404d333d248ccf777f739bc

Bug#1098706: /bin/sh: 1: /usr/src/linux-headers-6.13-amd64/tools/bpf/resolve_btfids/resolve_btfids: not found

[Salvatore Bonaccorso]

Control: tags -1 + unreproducible moreinfo

Hi Andreas,

On Sat, Mar 01, 2025 at 02:12:16AM +0100, Andreas Beckmann wrote:
> Control: found -1 6.13.5-1~exp1
> 
> with pahole available, the next script is missing:
> /usr/src/linux-headers-@KVERS@/tools/bpf/resolve_btfids/resolve_btfids
> 
> DKMS (dkms-3.1.5) make.log for dkms_test/1.0 for kernel 6.13-amd64 (x86_64)
> Sat Mar  1 01:09:31 UTC 2025
> 
> Building module(s)
> # command: make -j14 KERNELRELEASE=6.13-amd64 -C 
> /lib/modules/6.13-amd64/build M=/var/lib/dkms/dkms_test/1.0/build
> make: Entering directory '/usr/src/linux-headers-6.13-amd64'
> make[1]: Entering directory '/var/lib/dkms/dkms_test/1.0/build'
>   CC [M]  dkms_test.o
>   MODPOST Module.symvers
>   CC [M]  dkms_test.mod.o
>   CC [M]  .module-common.o
>   LD [M]  dkms_test.ko
>   BTF [M] dkms_test.ko
> /bin/sh: 1: 
> /usr/src/linux-headers-6.13-amd64/tools/bpf/resolve_btfids/resolve_btfids: 
> not found
> make[3]: *** 
> [/usr/src/linux-headers-6.13-common/scripts/Makefile.modfinal:59: 
> dkms_test.ko] Error 127
> make[3]: *** Deleting file 'dkms_test.ko'
> make[2]: *** [/usr/src/linux-headers-6.13-common/Makefile:1939: modules] 
> Error 2
> make[1]: *** [/usr/src/linux-headers-6.13-common/Makefile:263: __sub-make] 
> Error 2
> make[1]: Leaving directory '/var/lib/dkms/dkms_test/1.0/build'
> make: *** [/usr/src/linux-headers-6.13-common/Makefile:263: __sub-make] Error 
> 2
> make: Leaving directory '/usr/src/linux-headers-6.13-amd64'
> 
> # exit code: 2
> # elapsed time: 00:00:02
> 

I cannot reproduce your issue. The resolve_btfids was already included
earlier, and triggered without the pahole dependency the problem.

[...]
Setting up bpftool (7.6.0+6.13.5-1~exp1) ...
Setting up linux-libc-dev (6.13.5-1~exp1) ...
Setting up linux-headers-6.13-common (6.13.5-1~exp1) ...
Setting up linux-image-6.13-amd64 (6.13.5-1~exp1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.12.16-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.12.16-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.13-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.13-amd64
/etc/kernel/postinst.d/dkms:

Sign command: /lib/modules/6.13-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module dkms_test/1.0 for kernel 6.13-amd64 (x86_64)
Cleaning build area... done.
Building module(s)... done.
Signing module /var/lib/dkms/dkms_test/1.0/build/dkms_test.ko
Cleaning build area... done.
Installing /lib/modules/6.13-amd64/updates/dkms/dkms_test.ko.xz
Running depmod... done.

Autoinstall on 6.13-amd64 succeeded for module(s) dkms_test.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.13-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.13-amd64
Found initrd image: /boot/initrd.img-6.13-amd64
Found linux image: /boot/vmlinuz-6.12.16-amd64
Found initrd image: /boot/initrd.img-6.12.16-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up linux-perf (6.13.5-1~exp1) ...
Setting up pahole (1.29-2) ...
Setting up dkms-test-dkms (3.1.5-1) ...
Removing old dkms_test/1.0 DKMS files...
Module dkms_test/1.0 for kernel 6.13-amd64 (x86_64):
Before uninstall, this module version was ACTIVE on this kernel.
Deleting /lib/modules/6.13-amd64/updates/dkms/dkms_test.ko.xz
Running depmod... done.

Deleting module dkms_test/1.0 completely from the DKMS tree.
Loading new dkms_test/1.0 DKMS files...
Building for 6.12.16-amd64 and 6.13-amd64

Building initial module dkms_test/1.0 for 6.12.16-amd64
Done.
Installing /lib/modules/6.12.16-amd64/updates/dkms/dkms_test.ko.xz
Running depmod... done.

Building initial module dkms_test/1.0 for 6.13-amd64
Done.
Installing /lib/modules/6.13-amd64/updates/dkms/dkms_test.ko.xz
Running depmod... done.
Setting up linux-image-amd64 (6.13.5-1~exp1) ...
Setting up linux-kbuild-6.13 (6.13.5-1~exp1) ...
Setting up linux-headers-6.13-amd64 (6.13.5-1~exp1) ...
Setting up linux-headers-amd64 (6.13.5-1~exp1) ...
Processing triggers for man-db (2.13.0-1) ...

I would like to see this fixed ASAP for unstable but I have now
postponed my 6.12.17-1 upload. It would be great if you can confirm if
there was just a local problem.

# dpkg -S resolve_btfids/resolve_btfids
linux-kbuild-6.12.16: 
/usr/lib/linux-kbuild-6.12.16/tools/bpf/resolve_btfids/resolve_btfids
linux-kbuild-6.13: 
/usr/lib/linux-kbuild-6.13/tools/bpf/resolve_btfids/resolve_btfids

Regards,
Salvatore

linux-signed-arm64_6.13.5+1~exp1_source.changes ACCEPTED into experimental

[Debian FTP Masters]

Thank you for your contribution to Debian.

Mapping rc-buggy to experimental.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Feb 2025 12:01:10 +0100
Source: linux-signed-arm64
Architecture: source
Version: 6.13.5+1~exp1
Distribution: rc-buggy
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-arm64 (6.13.5+1~exp1) experimental; urgency=medium
 .
   * Sign kernel from linux 6.13.5-1~exp1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.13.5
 .
   [ Salvatore Bonaccorso ]
   * kbuild: Add Depends on pahole (Closes: #1098706)
   * [arm64] phy: rockchip: naneng-combphy: compatible reset with old DT
 (Closes: #1095745, #1098250, #1098354)
 .
   [ Uwe Kleine-König ]
   * Revert to disabled EFI_ZBOOT for the time being (Closes: #1098661)
 .
   [ Steev Klimaszewski ]
   * [arm64] Enable modules for Thinkpad X13s webcam
 .
   [ Alper Nebi Yasak ]
   * [arm64] Enable modules for Qualcomm SC7180 Chromebooks
 - Enable SC_GPUCC_7180 and INTERCONNECT_QCOM_SC7180 as modules
 - Enable SC_DISPCC_7180, SC_VIDEOCC_7180 and SC_CAMCC_7180 as modules
 - Enable SC_LPASS_CORECC_7180, SND_SOC_ADAU7002, SND_SOC_SC7180 as modules
 - Enable IIO_CROS_EC_SENSORS_LID_ANGLE and CROS_EC_MKBP_PROXIMITY as 
modules
 - Enable EDAC_QCOM and SPI_QCOM_QSPI as modules
   * [arm64] udeb: Add modules fo Qualcomm SC7180 Chromebooks
 - Add gcc-sc7180 and qnoc-sc7180 to kernel-image
 - Add dispcc-sc7180 and gpucc-sc7180 to fb-modules
   * [arm64] Enable SC_LPASSCC_7280 as module
Checksums-Sha1:
 9b26a172653bdd68c3dd00cc50a0760240d2e9be 9469 
linux-signed-arm64_6.13.5+1~exp1.dsc
 f72327283adb649cd1e7ff93b0515dd8448e9571 692448 
linux-signed-arm64_6.13.5+1~exp1.tar.xz
Checksums-Sha256:
 01358d4fea7b9af8dacde901bb3ac339efcfdb03e4455afe497da126881077c0 9469 
linux-signed-arm64_6.13.5+1~exp1.dsc
 a8762c0052280cb760cd329e0d6e9d66027bd3068fa2b410d6171bc46336a72a 692448 
linux-signed-arm64_6.13.5+1~exp1.tar.xz
Files:
 8b5ee8de1366f1cfcc2d1c799b5a4393 9469 kernel optional 
linux-signed-arm64_6.13.5+1~exp1.dsc
 659faf3b0a63c79b5431fc7a5eae496c 692448 kernel optional 
linux-signed-arm64_6.13.5+1~exp1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmfCw2IACgkQi0FRiLdO
NzbyMRAAjubordSWhtsibmD1vTTsd6hkOtVr84rj+Fc9FzFWY544oXa8JENcVr1T
ToTJmHuohqfaq2preN2LioTHVA8YkqRb1V+BoFBe00d6XJjW0VTnp0qfbpHB8U0V
/HQi+M+Bhp+7jSRjWlvIsgEdi2XV1tT94JXGZ1qYhw57czx+J1jqG8IC91dDRbMb
ZeJ2aCXmHDfmDTsaa00mN/AQVHw1hEqT/HZDd3T8gSWGW8P3etFlT57Wt1PYfkLu
B10aFxZhP2YA5zGroMbmud0pJxHicvvhWOzFDnsSB7Zs7s1zSIAChCGmpiOda+iQ
qEknZRrmsx63goFSosRGOF1lqacLzv3OYcTCZfCBT0NitmFa4UdQRbSDyQp0YStM
+g5+TN+vI1JPMfjvYxA/eI6JEhDcAzpdPrm+xrvISEg8YOePZJlu2RynwImBei+J
WUhVXEBwMwypk7g7dN5Y38DnVtGVDhfxlp0VJuznowfaaHvFvZ1SpvincuEsQaTu
zQccsrmuEQbzJjhsH49etBkaYTHzIk1fyVooMC6iXaqT0kn6jwo0afl+p52QHKDR
ylxL+lag3tfFkmj52lk3Js9+/l10BlsvnwKNspT7X74Qxl133A4ahUtiH3Sxe3UU
PhLyGc4YWHTkngIP6AJjdxc3Vaehk7Esj0TbnbqsCYDcRFQdrOg=
=9zOc
-END PGP SIGNATURE-



pgpgiPXtlEsDv.pgp
Description: PGP signature

Processed: limit source to linux, tagging 1099146, tagging 1099143, tagging 1099145, tagging 1099144

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'

> tags 1099146 + pending
Bug #1099146 [src:linux] Enable Intel IDPF on cloud arm64
Added tag(s) pending.
> tags 1099143 + pending
Bug #1099143 [src:linux] Enable Intel IDPF on amd64
Added tag(s) pending.
> tags 1099145 + pending
Bug #1099145 [src:linux] Enable Intel IDPF on arm64
Added tag(s) pending.
> tags 1099144 + pending
Bug #1099144 [src:linux] Enable Intel IDPF on cloud amd64
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1099143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099143
1099144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099144
1099145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099145
1099146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1098706: /bin/sh: 1: /usr/src/linux-headers-6.13-amd64/tools/bpf/resolve_btfids/resolve_btfids: not found

[Andreas Beckmann]

Control: notfound -1 6.13.5-1~exp1
Control: fixed -1 6.13.5-1~exp1
Control: tag -1 - moreinfo unreproducible

On 3/1/25 07:57, Salvatore Bonaccorso wrote:

I would like to see this fixed ASAP for unstable but I have now
postponed my 6.12.17-1 upload. It would be great if you can confirm if
there was just a local problem.


Please go ahead. It works in a clean chroot ... but not in my
existing one with all^Wmost *-dkms installed ...


# dpkg -S resolve_btfids/resolve_btfids
linux-kbuild-6.12.16: 
/usr/lib/linux-kbuild-6.12.16/tools/bpf/resolve_btfids/resolve_btfids
linux-kbuild-6.13: 
/usr/lib/linux-kbuild-6.13/tools/bpf/resolve_btfids/resolve_btfids


Darn experimental at pin priority 1 ... upgraded only the packages I explicitly 
selected

iU  linux-headers-6.13-amd64  6.13.5-1~exp1 
amd64Header files for Linux 6.13-amd64
ii  linux-kbuild-6.13 6.13.2-1~exp1 
amd64Kbuild infrastructure for Linux 6.13

No resolve_btfids in that old versions ...

Shouldn't linux-headers-X.Y[.Z]-$flavor have a more strict
Depends: linux-kbuild-X.Y[.Z] (= ${binary:Version}) ?

Probably only matters in experimental which omits .Z


Andreas

PS: after upgrading linux-kbuild-6.13 the modules seem to build fine

Processed: Re: /bin/sh: 1: /usr/src/linux-headers-6.13-amd64/tools/bpf/resolve_btfids/resolve_btfids: not found

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 6.13.5-1~exp1
Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: 
not found
Bug #1098737 [src:linux] virtualbox-dmks: possible missing dependency on pahole
Bug #1098739 [src:linux] vhba-dkms fails to build with linux-image-6.12.16-amd64
Bug #1098742 [src:linux] nvidia-driver 535.216.03-2 and 
linux-image-6.12.16-amd64 won't compile - missing `pahole`
Bug #1098771 [src:linux] dkms: fails to build modules
Bug #1098779 [src:linux] zfs-dkms: zfs/2.3.0 fails to build with kenel 
6.12.16-amd64
Bug #1098782 [src:linux] Bug: nvidia-driver missing dependency on dwarves 
(pahole required for DKMS build)
Bug #1098786 [src:linux] dkms: needs pahole but doesn't depend on it
Bug #1098789 [src:linux] "pahole" dependency missing
Bug #1098794 [src:linux] FTBFS: pahole Build-Deps might be missing?
Bug #1098814 [src:linux] linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad 
return status for module build on kernel
Bug #1098840 [src:linux] virtualbox-dkms: Doesn't build with kernel 6.12.16
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
No longer marked as found in versions linux/6.13.5-1~exp1.
> fixed -1 6.13.5-1~exp1
Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: 
not found
Bug #1098737 [src:linux] virtualbox-dmks: possible missing dependency on pahole
Bug #1098739 [src:linux] vhba-dkms fails to build with linux-image-6.12.16-amd64
Bug #1098742 [src:linux] nvidia-driver 535.216.03-2 and 
linux-image-6.12.16-amd64 won't compile - missing `pahole`
Bug #1098771 [src:linux] dkms: fails to build modules
Bug #1098779 [src:linux] zfs-dkms: zfs/2.3.0 fails to build with kenel 
6.12.16-amd64
Bug #1098782 [src:linux] Bug: nvidia-driver missing dependency on dwarves 
(pahole required for DKMS build)
Bug #1098786 [src:linux] dkms: needs pahole but doesn't depend on it
Bug #1098789 [src:linux] "pahole" dependency missing
Bug #1098794 [src:linux] FTBFS: pahole Build-Deps might be missing?
Bug #1098814 [src:linux] linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad 
return status for module build on kernel
Bug #1098840 [src:linux] virtualbox-dkms: Doesn't build with kernel 6.12.16
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as fixed in versions linux/6.13.5-1~exp1.
> tag -1 - moreinfo unreproducible
Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: 
not found
Bug #1098737 [src:linux] virtualbox-dmks: possible missing dependency on pahole
Bug #1098739 [src:linux] vhba-dkms fails to build with linux-image-6.12.16-amd64
Bug #1098742 [src:linux] nvidia-driver 535.216.03-2 and 
linux-image-6.12.16-amd64 won't compile - missing `pahole`
Bug #1098771 [src:linux] dkms: fails to build modules
Bug #1098779 [src:linux] zfs-dkms: zfs/2.3.0 fails to build with kenel 
6.12.16-amd64
Bug #1098782 [src:linux] Bug: nvidia-driver missing dependency on dwarves 
(pahole required for DKMS build)
Bug #1098786 [src:linux] dkms: needs pahole but doesn't depend on it
Bug #1098789 [src:linux] "pahole" dependency missing
Bug #1098794 [src:linux] FTBFS: pahole Build-Deps might be missing?
Bug #1098814 [src:linux] linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad 
return status for module build on kernel
Bug #1098840 [src:linux] virtualbox-dkms: Doesn't build with kernel 6.12.16
Removed tag(s) moreinfo and unreproducible.
Removed tag(s) unreproducible and moreinfo.
Removed tag(s) unreproducible and moreinfo.
Removed tag(s) moreinfo and unreproducible.
Removed tag(s) moreinfo and unreproducible.
Removed tag(s) moreinfo and unreproducible.
Removed tag(s) unreproducible and moreinfo.
Removed tag(s) moreinfo and unreproducible.
Removed tag(s) unreproducible and moreinfo.
Removed tag(s) moreinfo and unreproducible.
Removed tag(s) moreinfo and unreproducible.
Removed tag(s) unreproducible and moreinfo.

-- 
1098706: https://bugs.debian.org/cgi-bin/bu

Processed: retitle 1099138 to linux: Backports for fixes for CVE-2024-42069 and CVE-2024-45001 in bookworm

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1099138 linux: Backports for fixes for CVE-2024-42069 and 
> CVE-2024-45001 in bookworm
Bug #1099138 [src:linux] linux: CVE-2024-45001 in bookworm
Changed Bug title to 'linux: Backports for fixes for CVE-2024-42069 and 
CVE-2024-45001 in bookworm' from 'linux: CVE-2024-45001 in bookworm'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1099138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 1098698 in 6.12~rc6-1~exp1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1098698 6.12~rc6-1~exp1
Bug #1098698 [src:linux] linux: Segfault and system hang on larger network file 
transfers
Marked as found in versions linux/6.12~rc6-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1098698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1098698

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1098698 - moreinfo
Bug #1098698 [src:linux] linux: Segfault and system hang on larger network file 
transfers
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1098698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1098698 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1098698 + upstream
Bug #1098698 [src:linux] linux: Segfault and system hang on larger network file 
transfers
Ignoring request to alter tags of bug #1098698 to the same tags previously set
> forwarded 1098698 
> https://lore.kernel.org/netfs/cakpou+_4muwygqtrtbxcmi+-k3pgvlysnpadkmhoyb7gz0i...@mail.gmail.com/
Bug #1098698 [src:linux] linux: Segfault and system hang on larger network file 
transfers
Set Bug forwarded-to-address to 
'https://lore.kernel.org/netfs/cakpou+_4muwygqtrtbxcmi+-k3pgvlysnpadkmhoyb7gz0i...@mail.gmail.com/'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1098698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processing of linux_6.12.17-1_source.changes

[Debian FTP Masters]

linux_6.12.17-1_source.changes uploaded successfully to localhost
along with the files:
  linux_6.12.17-1.dsc
  linux_6.12.17.orig.tar.xz
  linux_6.12.17-1.debian.tar.xz
  linux_6.12.17-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Processed: affects 1098706

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1098706 lime-forensics-dkms
Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: 
not found
Bug #1098737 [src:linux] virtualbox-dmks: possible missing dependency on pahole
Bug #1098739 [src:linux] vhba-dkms fails to build with linux-image-6.12.16-amd64
Bug #1098742 [src:linux] nvidia-driver 535.216.03-2 and 
linux-image-6.12.16-amd64 won't compile - missing `pahole`
Bug #1098771 [src:linux] dkms: fails to build modules
Bug #1098779 [src:linux] zfs-dkms: zfs/2.3.0 fails to build with kenel 
6.12.16-amd64
Bug #1098782 [src:linux] Bug: nvidia-driver missing dependency on dwarves 
(pahole required for DKMS build)
Bug #1098786 [src:linux] dkms: needs pahole but doesn't depend on it
Bug #1098789 [src:linux] "pahole" dependency missing
Bug #1098794 [src:linux] FTBFS: pahole Build-Deps might be missing?
Bug #1098814 [src:linux] linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad 
return status for module build on kernel
Bug #1098840 [src:linux] virtualbox-dkms: Doesn't build with kernel 6.12.16
Added indication that 1098706 affects lime-forensics-dkms
Added indication that 1098737 affects lime-forensics-dkms
Added indication that 1098739 affects lime-forensics-dkms
Added indication that 1098742 affects lime-forensics-dkms
Added indication that 1098771 affects lime-forensics-dkms
Added indication that 1098779 affects lime-forensics-dkms
Added indication that 1098782 affects lime-forensics-dkms
Added indication that 1098786 affects lime-forensics-dkms
Added indication that 1098789 affects lime-forensics-dkms
Added indication that 1098794 affects lime-forensics-dkms
Added indication that 1098814 affects lime-forensics-dkms
Added indication that 1098840 affects lime-forensics-dkms
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
1098737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098737
1098739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098739
1098742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098742
1098771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098771
1098779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098779
1098782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098782
1098786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098786
1098789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098789
1098794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098794
1098814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098814
1098840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1099158 to src:linux

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1099158 src:linux 6.12.12-1
Bug #1099158 [linux-image-6.12.12-amd64] linux-image-6.12.12-amd64: Please 
enable CONFIG_VIRTIO_IOMMU for IOMMU in virtual machines
Bug reassigned from package 'linux-image-6.12.12-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/6.12.12+1.
Ignoring request to alter fixed versions of bug #1099158 to the same values 
previously set
Bug #1099158 [src:linux] linux-image-6.12.12-amd64: Please enable 
CONFIG_VIRTIO_IOMMU for IOMMU in virtual machines
Marked as found in versions linux/6.12.12-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1099158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1098706: /bin/sh: 1: /usr/src/linux-headers-6.13-amd64/tools/bpf/resolve_btfids/resolve_btfids: not found

[Salvatore Bonaccorso]

Hi Andreas,

Thanks for your time re-checking!

On Sat, Mar 01, 2025 at 02:02:13PM +0100, Andreas Beckmann wrote:
> Control: notfound -1 6.13.5-1~exp1
> Control: fixed -1 6.13.5-1~exp1
> Control: tag -1 - moreinfo unreproducible
> 
> On 3/1/25 07:57, Salvatore Bonaccorso wrote:
> > I would like to see this fixed ASAP for unstable but I have now
> > postponed my 6.12.17-1 upload. It would be great if you can confirm if
> > there was just a local problem.
> 
> Please go ahead. It works in a clean chroot ... but not in my
> existing one with all^Wmost *-dkms installed ...

Ack in this case I proceed finalizing the unstable upload.

> 
> > # dpkg -S resolve_btfids/resolve_btfids
> > linux-kbuild-6.12.16: 
> > /usr/lib/linux-kbuild-6.12.16/tools/bpf/resolve_btfids/resolve_btfids
> > linux-kbuild-6.13: 
> > /usr/lib/linux-kbuild-6.13/tools/bpf/resolve_btfids/resolve_btfids
> 
> Darn experimental at pin priority 1 ... upgraded only the packages I 
> explicitly selected
> 
> iU  linux-headers-6.13-amd64  6.13.5-1~exp1   
>   amd64Header files for Linux 6.13-amd64
> ii  linux-kbuild-6.13 6.13.2-1~exp1   
>   amd64Kbuild infrastructure for Linux 6.13
> 
> No resolve_btfids in that old versions ...
> 
> Shouldn't linux-headers-X.Y[.Z]-$flavor have a more strict
> Depends: linux-kbuild-X.Y[.Z] (= ${binary:Version}) ?
> 
> Probably only matters in experimental which omits .Z

yes you are right for experimental the version is capped, cf.
https://salsa.debian.org/kernel-team/linux/-/commit/3282bf29846a0c47a8e01c60c038d29ad17c573d#1deb02069d878e54cd8cdfff584dfd6215f9b13f_648_639
.

So 6.12.17-1 should follow ASAP, working on it now finalizing it.

Again thanks for your time, much appreciated.

Regards,
Salvatore

Bug#1099138: linux: CVE-2024-45001 in bookworm

[Noah Meyerhans]

On Sat, Mar 01, 2025 at 02:15:43PM +0100, Salvatore Bonaccorso wrote:
> > > Source: linux
> > > Version: 6.1.128-1
> > > Severity: important
> > > Tags: security
> > > X-Debbugs-Cc: Debian Security Team 
> > > 
> > > I believe CVE-2024-45001 (RX buf alloc_size alignment and atomic op 
> > > panic) is miscategorized as not impacting bookworm.  The issue is with 
> > > the net/ethernet/microsoft/mana driver and was introduced in linux 6.10,
> > > which is likely why the security-tracker contains the note "Vulnerable 
> > > code not present" for bookworm.  However, bookworm contains a backported
> > > version of this driver from 6.10 in
> > > debian/patches/features/all/ethernet-microsoft. [1] [2]
> > > 
> > > The upstream fix applies on top of our patched 6.1 kernel with an 
> > > offset. [3]
> > > 
> > > I didn't propose a fix to the security-tracker data because I don't know
> > > the file format well enough.
> > > 
> > > I can prepare a merge request to the kernel package if that would help.
> > 
> > Thanks I will shortly have a look at that as I'm rebasing 6.1.y for
> > bookworm for the next upload.
> 
> Investigating this further I believe we have the same problem as well
> for CVE-2024-42069.

Yes, that seems likely.

noah

Bug#1098698: linux: Segfault and system hang on larger network file transfers

[Paul DeKraker]

Here is a log collected via netconsole.

Thanks,
Paul

On Thu, Feb 27, 2025 at 11:39 AM Salvatore Bonaccorso 
wrote:

> Hi Paul,
>
> On Mon, Feb 24, 2025 at 09:12:43PM -0500, Paul DeKraker wrote:
> > I just tried 6.12.16 and as with 6.12.15 the system locks up / becomes
> > completely unresponsive and needs to be hard reset when attempting a
> large
> > transfer from a network share to the local computer, so this probably is
> a
> > separate issue. If there is something more I can do to capture this
> > behavior please let me know.
>
> Thanks for confirming. Yes now we have to get to fresh logs. As I
> understand you cannot access the system (not even remotely via SSH) to
> gather the kernel logs after the issue appears?
>
> In this case we might be successfull if you attach a netconsole and
> have another system available which can capture the logs.
> Documentation can be found here:
>
> https://www.kernel.org/doc/html/latest/networking/netconsole.html#netconsole
>
> Would you be able to try that and provide fresh logs for the recent
> 6.12.y kernels?
>
> Regards,
> Salvatore
>


log
Description: Binary data

Bug#1099138: linux: CVE-2024-45001 in bookworm

[Salvatore Bonaccorso]

Control: linux: Backports for fixes for CVE-2024-42069 and CVE-2024-45001 in 
bookworm

Hi Noah,

On Fri, Feb 28, 2025 at 08:30:27PM +0100, Salvatore Bonaccorso wrote:
> Hi Noah,
> 
> On Fri, Feb 28, 2025 at 01:58:18PM -0500, Noah Meyerhans wrote:
> > Source: linux
> > Version: 6.1.128-1
> > Severity: important
> > Tags: security
> > X-Debbugs-Cc: Debian Security Team 
> > 
> > I believe CVE-2024-45001 (RX buf alloc_size alignment and atomic op 
> > panic) is miscategorized as not impacting bookworm.  The issue is with 
> > the net/ethernet/microsoft/mana driver and was introduced in linux 6.10,
> > which is likely why the security-tracker contains the note "Vulnerable 
> > code not present" for bookworm.  However, bookworm contains a backported
> > version of this driver from 6.10 in
> > debian/patches/features/all/ethernet-microsoft. [1] [2]
> > 
> > The upstream fix applies on top of our patched 6.1 kernel with an 
> > offset. [3]
> > 
> > I didn't propose a fix to the security-tracker data because I don't know
> > the file format well enough.
> > 
> > I can prepare a merge request to the kernel package if that would help.
> 
> Thanks I will shortly have a look at that as I'm rebasing 6.1.y for
> bookworm for the next upload.

Investigating this further I believe we have the same problem as well
for CVE-2024-42069.

Regards,
Salvatore

Processed: tagging 1098706

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1098706 + pending
Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: 
not found
Bug #1098737 [src:linux] virtualbox-dmks: possible missing dependency on pahole
Bug #1098739 [src:linux] vhba-dkms fails to build with linux-image-6.12.16-amd64
Bug #1098742 [src:linux] nvidia-driver 535.216.03-2 and 
linux-image-6.12.16-amd64 won't compile - missing `pahole`
Bug #1098771 [src:linux] dkms: fails to build modules
Bug #1098779 [src:linux] zfs-dkms: zfs/2.3.0 fails to build with kenel 
6.12.16-amd64
Bug #1098782 [src:linux] Bug: nvidia-driver missing dependency on dwarves 
(pahole required for DKMS build)
Bug #1098786 [src:linux] dkms: needs pahole but doesn't depend on it
Bug #1098789 [src:linux] "pahole" dependency missing
Bug #1098794 [src:linux] FTBFS: pahole Build-Deps might be missing?
Bug #1098814 [src:linux] linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad 
return status for module build on kernel
Bug #1098840 [src:linux] virtualbox-dkms: Doesn't build with kernel 6.12.16
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
1098737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098737
1098739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098739
1098742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098742
1098771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098771
1098779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098779
1098782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098782
1098786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098786
1098789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098789
1098794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098794
1098814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098814
1098840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)

[Eric]

Hi for what it's worth the problem is reproduced on each new kernel 
version up to now (6.12.12-1).


I understand the bug is marked for upstream, are we just waiting for 
them to get back to us ? I am not trying to rush people here, just 
making sure I have not missed something I should do.



Thanks for your work


Eric

Processed: notfound 1098706 in 6.12~rc6-1~exp1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # copy paste error doing bts triage
> notfound 1098706 6.12~rc6-1~exp1
Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: 
not found
Bug #1098737 [src:linux] virtualbox-dmks: possible missing dependency on pahole
Bug #1098739 [src:linux] vhba-dkms fails to build with linux-image-6.12.16-amd64
Bug #1098742 [src:linux] nvidia-driver 535.216.03-2 and 
linux-image-6.12.16-amd64 won't compile - missing `pahole`
Bug #1098771 [src:linux] dkms: fails to build modules
Bug #1098779 [src:linux] zfs-dkms: zfs/2.3.0 fails to build with kenel 
6.12.16-amd64
Bug #1098782 [src:linux] Bug: nvidia-driver missing dependency on dwarves 
(pahole required for DKMS build)
Bug #1098786 [src:linux] dkms: needs pahole but doesn't depend on it
Bug #1098789 [src:linux] "pahole" dependency missing
Bug #1098794 [src:linux] FTBFS: pahole Build-Deps might be missing?
Bug #1098814 [src:linux] linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad 
return status for module build on kernel
Bug #1098840 [src:linux] virtualbox-dkms: Doesn't build with kernel 6.12.16
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
No longer marked as found in versions linux/6.12~rc6-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
1098737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098737
1098739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098739
1098742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098742
1098771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098771
1098779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098779
1098782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098782
1098786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098786
1098789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098789
1098794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098794
1098814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098814
1098840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

linux_6.12.17-1_source.changes is NEW

[Debian FTP Masters]

binary:affs-modules-6.12.17-5kc-malta-di is NEW.
binary:affs-modules-6.12.17-loongson-3-di is NEW.
binary:affs-modules-6.12.17-mips64r2el-di is NEW.
binary:affs-modules-6.12.17-mips64r6el-di is NEW.
binary:affs-modules-6.12.17-octeon-di is NEW.
binary:ata-modules-6.12.17-5kc-malta-di is NEW.
binary:ata-modules-6.12.17-armmp-di is NEW.
binary:ata-modules-6.12.17-loongson-3-di is NEW.
binary:ata-modules-6.12.17-mips64r2el-di is NEW.
binary:ata-modules-6.12.17-mips64r6el-di is NEW.
binary:ata-modules-6.12.17-octeon-di is NEW.
binary:ata-modules-6.12.17-powerpc64le-di is NEW.
binary:ata-modules-6.12.17-riscv64-di is NEW.
binary:btrfs-modules-6.12.17-5kc-malta-di is NEW.
binary:btrfs-modules-6.12.17-armmp-di is NEW.
binary:btrfs-modules-6.12.17-loongson-3-di is NEW.
binary:btrfs-modules-6.12.17-mips64r2el-di is NEW.
binary:btrfs-modules-6.12.17-mips64r6el-di is NEW.
binary:btrfs-modules-6.12.17-octeon-di is NEW.
binary:btrfs-modules-6.12.17-powerpc64le-di is NEW.
binary:btrfs-modules-6.12.17-riscv64-di is NEW.
binary:btrfs-modules-6.12.17-s390x-di is NEW.
binary:cdrom-core-modules-6.12.17-5kc-malta-di is NEW.
binary:cdrom-core-modules-6.12.17-armmp-di is NEW.
binary:cdrom-core-modules-6.12.17-loongson-3-di is NEW.
binary:cdrom-core-modules-6.12.17-mips64r2el-di is NEW.
binary:cdrom-core-modules-6.12.17-mips64r6el-di is NEW.
binary:cdrom-core-modules-6.12.17-octeon-di is NEW.
binary:cdrom-core-modules-6.12.17-powerpc64le-di is NEW.
binary:cdrom-core-modules-6.12.17-riscv64-di is NEW.
binary:cdrom-core-modules-6.12.17-s390x-di is NEW.
binary:crypto-dm-modules-6.12.17-5kc-malta-di is NEW.
binary:crypto-dm-modules-6.12.17-armmp-di is NEW.
binary:crypto-dm-modules-6.12.17-loongson-3-di is NEW.
binary:crypto-dm-modules-6.12.17-mips64r2el-di is NEW.
binary:crypto-dm-modules-6.12.17-mips64r6el-di is NEW.
binary:crypto-dm-modules-6.12.17-octeon-di is NEW.
binary:crypto-dm-modules-6.12.17-powerpc64le-di is NEW.
binary:crypto-dm-modules-6.12.17-riscv64-di is NEW.
binary:crypto-dm-modules-6.12.17-s390x-di is NEW.
binary:crypto-modules-6.12.17-5kc-malta-di is NEW.
binary:crypto-modules-6.12.17-armmp-di is NEW.
binary:crypto-modules-6.12.17-loongson-3-di is NEW.
binary:crypto-modules-6.12.17-mips64r2el-di is NEW.
binary:crypto-modules-6.12.17-mips64r6el-di is NEW.
binary:crypto-modules-6.12.17-octeon-di is NEW.
binary:crypto-modules-6.12.17-powerpc64le-di is NEW.
binary:crypto-modules-6.12.17-riscv64-di is NEW.
binary:crypto-modules-6.12.17-s390x-di is NEW.
binary:dasd-extra-modules-6.12.17-s390x-di is NEW.
binary:dasd-modules-6.12.17-s390x-di is NEW.
binary:drm-core-modules-6.12.17-5kc-malta-di is NEW.
binary:drm-core-modules-6.12.17-armmp-di is NEW.
binary:drm-core-modules-6.12.17-loongson-3-di is NEW.
binary:drm-core-modules-6.12.17-mips64r2el-di is NEW.
binary:drm-core-modules-6.12.17-mips64r6el-di is NEW.
binary:drm-core-modules-6.12.17-octeon-di is NEW.
binary:drm-core-modules-6.12.17-powerpc64le-di is NEW.
binary:drm-core-modules-6.12.17-riscv64-di is NEW.
binary:ext4-modules-6.12.17-5kc-malta-di is NEW.
binary:ext4-modules-6.12.17-armmp-di is NEW.
binary:ext4-modules-6.12.17-loongson-3-di is NEW.
binary:ext4-modules-6.12.17-mips64r2el-di is NEW.
binary:ext4-modules-6.12.17-mips64r6el-di is NEW.
binary:ext4-modules-6.12.17-octeon-di is NEW.
binary:ext4-modules-6.12.17-powerpc64le-di is NEW.
binary:ext4-modules-6.12.17-riscv64-di is NEW.
binary:ext4-modules-6.12.17-s390x-di is NEW.
binary:f2fs-modules-6.12.17-5kc-malta-di is NEW.
binary:f2fs-modules-6.12.17-armmp-di is NEW.
binary:f2fs-modules-6.12.17-loongson-3-di is NEW.
binary:f2fs-modules-6.12.17-mips64r2el-di is NEW.
binary:f2fs-modules-6.12.17-mips64r6el-di is NEW.
binary:f2fs-modules-6.12.17-octeon-di is NEW.
binary:f2fs-modules-6.12.17-powerpc64le-di is NEW.
binary:f2fs-modules-6.12.17-riscv64-di is NEW.
binary:f2fs-modules-6.12.17-s390x-di is NEW.
binary:fat-modules-6.12.17-5kc-malta-di is NEW.
binary:fat-modules-6.12.17-armmp-di is NEW.
binary:fat-modules-6.12.17-loongson-3-di is NEW.
binary:fat-modules-6.12.17-mips64r2el-di is NEW.
binary:fat-modules-6.12.17-mips64r6el-di is NEW.
binary:fat-modules-6.12.17-octeon-di is NEW.
binary:fat-modules-6.12.17-powerpc64le-di is NEW.
binary:fat-modules-6.12.17-riscv64-di is NEW.
binary:fat-modules-6.12.17-s390x-di is NEW.
binary:fb-modules-6.12.17-5kc-malta-di is NEW.
binary:fb-modules-6.12.17-armmp-di is NEW.
binary:fb-modules-6.12.17-loongson-3-di is NEW.
binary:fb-modules-6.12.17-mips64r2el-di is NEW.
binary:fb-modules-6.12.17-mips64r6el-di is NEW.
binary:fb-modules-6.12.17-octeon-di is NEW.
binary:fb-modules-6.12.17-powerpc64le-di is NEW.
binary:fb-modules-6.12.17-riscv64-di is NEW.
binary:firewire-core-modules-6.12.17-5kc-malta-di is NEW.
binary:firewire-core-modules-6.12.17-loongson-3-di is NEW.
binary:firewire-core-modules-6.12.17-mips64r2el-di is NEW.
binary:firewire-core-modules-6.12.17-mips64r6el-di is NEW.
binary:firewire-core-modules-6.12.17-octeon-di is NEW.
binary:firewire-core-modules-6.12.17-powerpc64le

Bug#1099214: linux-source: Carefully use CPUID instruction in Intel machine.

[Corcodel Marian]

Package: linux-source
Severity: normal
X-Debbugs-Cc: corcodel.mar...@gmail.com

Hi, according to the Intel manual 325462-sdm-vol-1-2abcd-3abcd-4-1.pdf page
409, 17.3.9.1 Instruction Based Considerations CPUID and other instructions
instructions will abort transactional execution on any implementation.
Conclusion,  exesive usage just to linux kernel an cat /proc/cpuinfo can result
data loss?
Just ask.


-- System Information:
Debian Release: 12.9
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.5+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source depends on:
pn  linux-source-6.1  

linux-source recommends no packages.

linux-source suggests no packages.

Bug#1099214: Still can avoid this isuue

[Marian Corcodel]

People can remove cover from the box and inspect code of cpu and build
sistem acording to that code and use cpuid durring compilation process
but again sistem is unsure, ha, ha!

Bug#1098698: linux: Segfault and system hang on larger network file transfers

[Salvatore Bonaccorso]

Hi Paul,

On Sat, Mar 01, 2025 at 08:21:58AM -0500, Paul DeKraker wrote:
> Here is a log collected via netconsole.
> 
> Thanks,
> Paul
> 
> On Thu, Feb 27, 2025 at 11:39 AM Salvatore Bonaccorso 
> wrote:
> 
> > Hi Paul,
> >
> > On Mon, Feb 24, 2025 at 09:12:43PM -0500, Paul DeKraker wrote:
> > > I just tried 6.12.16 and as with 6.12.15 the system locks up / becomes
> > > completely unresponsive and needs to be hard reset when attempting a
> > large
> > > transfer from a network share to the local computer, so this probably is
> > a
> > > separate issue. If there is something more I can do to capture this
> > > behavior please let me know.
> >
> > Thanks for confirming. Yes now we have to get to fresh logs. As I
> > understand you cannot access the system (not even remotely via SSH) to
> > gather the kernel logs after the issue appears?
> >
> > In this case we might be successfull if you attach a netconsole and
> > have another system available which can capture the logs.
> > Documentation can be found here:
> >
> > https://www.kernel.org/doc/html/latest/networking/netconsole.html#netconsole
> >
> > Would you be able to try that and provide fresh logs for the recent
> > 6.12.y kernels?

Thanks a lot for the log, this was very helpful. At first glance it
looks like this issue:
https://lore.kernel.org/netfs/cakpou+_4muwygqtrtbxcmi+-k3pgvlysnpadkmhoyb7gz0i...@mail.gmail.com/

There is a submitted patch but it does not look like it got applied
already, checking.

Might you be able to test the patch from
https://lore.kernel.org/netfs/20250210191118.316-1-max.kellerm...@ionos.com/
to see if it fixes the issue?

You can follow the procedure in
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
to do the "simple patching and building".

Regards,
Salvatore

Processed: found 1098706 in 6.12~rc6-1~exp1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1098706 6.12~rc6-1~exp1
Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: 
not found
Bug #1098737 [src:linux] virtualbox-dmks: possible missing dependency on pahole
Bug #1098739 [src:linux] vhba-dkms fails to build with linux-image-6.12.16-amd64
Bug #1098742 [src:linux] nvidia-driver 535.216.03-2 and 
linux-image-6.12.16-amd64 won't compile - missing `pahole`
Bug #1098771 [src:linux] dkms: fails to build modules
Bug #1098779 [src:linux] zfs-dkms: zfs/2.3.0 fails to build with kenel 
6.12.16-amd64
Bug #1098782 [src:linux] Bug: nvidia-driver missing dependency on dwarves 
(pahole required for DKMS build)
Bug #1098786 [src:linux] dkms: needs pahole but doesn't depend on it
Bug #1098789 [src:linux] "pahole" dependency missing
Bug #1098794 [src:linux] FTBFS: pahole Build-Deps might be missing?
Bug #1098814 [src:linux] linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad 
return status for module build on kernel
Bug #1098840 [src:linux] virtualbox-dkms: Doesn't build with kernel 6.12.16
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
Marked as found in versions linux/6.12~rc6-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
1098737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098737
1098739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098739
1098742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098742
1098771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098771
1098779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098779
1098782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098782
1098786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098786
1098789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098789
1098794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098794
1098814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098814
1098840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1099261: marked as done (nvidia-graphics-drivers: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-graphics-drivers: FTBFS: /bin/sh: 1: pahole: not found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-graphics-drivers
Version: 535.216.03-2
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{535.216.03}g;' \
-e 's{#MAJOR#}{535}g;' \
-e 's{#NVIDIA#}{nvidia}g;' \
-e 's{#VARIANT#}{}g;' \
-e 's{#CURRENT#}{current}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-kernel}g;' \

[... snipped ...]

/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011951rm+0x4e: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011846rm+0x1aa: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039290rm+0x16: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011948rm+0x47: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011927rm+0x16: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011936rm+0x2e: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039296rm+0x2e: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011933rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039285rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039294rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011930rm+0x32: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv038815rm+0xac: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv038839rm+0xbb: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039328rm+0xcc9: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012037rm+0x18d: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012039rm+0x184: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012030rm+0x34c: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012023rm+0x333: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012025rm+0x33c: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012019rm+0x2dd: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012027rm+0x33d: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011853rm+0xe9c: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012055rm+0x199: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012043rm+0x3f2: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011842rm+0x5b: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011839rm+0x51: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012006rm+0x225: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012021rm+0x2dd: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011808rm+0x1e8: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: obj

Bug#1099259: marked as done (nvidia-graphics-drivers-tesla-535: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-graphics-drivers-tesla-535: FTBFS: /bin/sh: 1: pahole: not 
found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-graphics-drivers-tesla-535
Version: 535.216.03-1
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{535.216.03}g;' \
-e 's{#MAJOR#}{535}g;' \
-e 's{#NVIDIA#}{nvidia-tesla-535}g;' \
-e 's{#VARIANT#}{-tesla-535}g;' \
-e 's{#CURRENT#}{tesla-535}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-tesla-535-kernel}g;' \

[... snipped ...]

/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011951rm+0x4e: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011846rm+0x1aa: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039290rm+0x16: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011948rm+0x47: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011927rm+0x16: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011936rm+0x2e: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039296rm+0x2e: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011933rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039285rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039294rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011930rm+0x32: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv038815rm+0xac: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv038839rm+0xbb: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv039328rm+0xcc9: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012037rm+0x18d: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012039rm+0x184: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012030rm+0x34c: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012023rm+0x333: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012025rm+0x33c: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012019rm+0x2dd: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012027rm+0x33d: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011853rm+0xe9c: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012055rm+0x199: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012043rm+0x3f2: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011842rm+0x5b: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011839rm+0x51: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012006rm+0x225: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv012021rm+0x2dd: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011808rm+0x1e8: 'naked' return found in MITIGATION_RETHU

Bug#1099256: marked as done (nvidia-graphics-drivers-tesla-418: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-graphics-drivers-tesla-418: FTBFS: /bin/sh: 1: pahole: not 
found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-graphics-drivers-tesla-418
Version: 418.226.00-17
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{418.226.00}g;' \
-e 's{#MAJOR#}{418}g;' \
-e 's{#NVIDIA#}{nvidia-tesla-418}g;' \
-e 's{#VARIANT#}{-tesla-418}g;' \
-e 's{#CURRENT#}{tesla-418}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-tesla-418-kernel}g;' \

[... snipped ...]

/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x330: data relocation to !ENDBR: _nv037589rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x338: data relocation to !ENDBR: _nv037588rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x340: data relocation to !ENDBR: _nv037604rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x348: data relocation to !ENDBR: _nv037467rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x350: data relocation to !ENDBR: _nv037603rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x358: data relocation to !ENDBR: _nv037466rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x360: data relocation to !ENDBR: _nv037480rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x368: data relocation to !ENDBR: _nv037481rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x370: data relocation to !ENDBR: _nv037572rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x378: data relocation to !ENDBR: _nv037573rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x380: data relocation to !ENDBR: _nv037502rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x388: data relocation to !ENDBR: _nv037498rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x390: data relocation to !ENDBR: _nv037489rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x398: data relocation to !ENDBR: _nv037494rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3a0: data relocation to !ENDBR: _nv037505rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3a8: data relocation to !ENDBR: _nv037501rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3b0: data relocation to !ENDBR: _nv037490rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3b8: data relocation to !ENDBR: _nv037495rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3c0: data relocation to !ENDBR: _nv037504rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3c8: data relocation to !ENDBR: _nv037500rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3d0: data relocation to !ENDBR: _nv037503rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3d8: data relocation to !ENDBR: _nv037499rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3e0: data relocation to !ENDBR: _nv037492rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3e8: data relocation to !ENDBR: _nv037496rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3f0: data relocation to !ENDBR: _nv037493rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x3f8: data relocation to !ENDBR: _nv037497rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x400: data relocation to !ENDBR: _nv037548rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x408: data relocation to !ENDBR: _nv037549rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x410: data relocation to !ENDBR: _nv037550rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv037664rm+0x418: data relocation to !ENDBR: _nv037551rm+0x0
/<>/ker

Bug#1099258: marked as done (nvidia-graphics-drivers-tesla-460: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-graphics-drivers-tesla-460: FTBFS: /bin/sh: 1: pahole: not 
found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-graphics-drivers-tesla-460
Version: 460.106.00-19
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{460.106.00}g;' \
-e 's{#MAJOR#}{460}g;' \
-e 's{#NVIDIA#}{nvidia-tesla-460}g;' \
-e 's{#VARIANT#}{-tesla-460}g;' \
-e 's{#CURRENT#}{tesla-460}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-tesla-460-kernel}g;' \

[... snipped ...]

/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3b0: data relocation to !ENDBR: _nv041868rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3b8: data relocation to !ENDBR: _nv041873rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3c0: data relocation to !ENDBR: _nv041882rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3c8: data relocation to !ENDBR: _nv041878rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3d0: data relocation to !ENDBR: _nv041881rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3d8: data relocation to !ENDBR: _nv041877rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3e0: data relocation to !ENDBR: _nv041870rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3e8: data relocation to !ENDBR: _nv041874rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3f0: data relocation to !ENDBR: _nv041871rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x3f8: data relocation to !ENDBR: _nv041875rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x400: data relocation to !ENDBR: _nv041926rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x408: data relocation to !ENDBR: _nv041927rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x410: data relocation to !ENDBR: _nv041928rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x418: data relocation to !ENDBR: _nv041929rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x420: data relocation to !ENDBR: _nv042018rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x428: data relocation to !ENDBR: _nv042019rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x430: data relocation to !ENDBR: _nv042022rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x438: data relocation to !ENDBR: _nv042030rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x440: data relocation to !ENDBR: _nv041908rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x448: data relocation to !ENDBR: _nv041917rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x450: data relocation to !ENDBR: _nv041909rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x458: data relocation to !ENDBR: _nv041919rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x460: data relocation to !ENDBR: _nv041918rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x468: data relocation to !ENDBR: _nv041886rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x470: data relocation to !ENDBR: _nv041922rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x478: data relocation to !ENDBR: _nv041960rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x480: data relocation to !ENDBR: _nv041925rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x488: data relocation to !ENDBR: _nv042025rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x490: data relocation to !ENDBR: _nv042027rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv042040rm+0x498: data relocation to !ENDBR: _nv042024rm+0x0
/<>/ker

Bug#1099143: marked as done (Enable Intel IDPF on amd64)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1099143: fixed in linux 6.12.17-1
has caused the Debian Bug report #1099143,
regarding Enable Intel IDPF on amd64
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.)


-- 
1099143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 6.12.12-1
Severity: wishlist

Intel's IDPF network interface driver is available in 6.12 and
required by current GCE bare metal machine families.

Please add CONFIG_IDPF=m to Linux kernel configuration to enable this driver.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1099...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit FW version string length
 - [amd64] accel/ivpu: Add coredump support
 - [amd64] accel/ivpu: Add FW state dump on TDR
 - [amd64] accel/ivpu: Fix error handling in recovery/reset
 - drm/amdkfd: Move gfx12 trap handler to separate file
 - drm/amdkfd: Ensure consistent barrier state saved in gfx12 trap handler
 - tracing: Switch trace.c code over to use guard()
 - tracing: Have the error of __tracing_resize_ring_buffer() passed to user
 - USB: gadget: f_midi: f_midi_complete to call queue_work
 - sched_ext: 

Bug#1099253: nvidia-graphics-drivers-legacy-340xx: FTBFS: /bin/sh: 1: pahole: not found

[Santiago Vila]

El 1/3/25 a las 22:37, Andreas Beckmann escribió:

Please clean up all the 'pahole: not found' bugs, that's #1098706 in src:linux 
and an upload for that is on the way to sid.


Ok, done.

Bug#1098739: marked as done (vhba-dkms fails to build with linux-image-6.12.16-amd64)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding vhba-dkms fails to build with linux-image-6.12.16-amd64
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vhba-dkms
Version: 20240917-1
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: debian-am...@lists.debian.org
User: debian-am...@lists.debian.org
Usertags: amd64

Hey.

Fails to build with 6.12.16, oddly enough, it still worked wiht 6.12.15.

Cheers,
Chris.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vhba-dkms depends on:
ii  dkms  3.1.5-1

vhba-dkms recommends no packages.

vhba-dkms suggests no packages.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit

Bug#1098250: marked as done (linux-image-arm64: USB and PCIe broken on rk356x devices)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098354: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098354,
regarding linux-image-arm64: USB and PCIe broken on rk356x devices
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.)


-- 
1098354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 6.12.8-1
Severity: important
Tags: upstream patch
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: arm64

https://lore.kernel.org/linux-rockchip/df8e0ff8-355b-4c18-9349-0f04ae16e...@kwiboo.se/:

  Upstream commit fbcbffbac994 ("phy: rockchip: naneng-combphy: fix phy reset")
  broke backwards compatibly with old DTs and has already been backported
  breaking i.e. PCIe and USB on Rockchip RK356x boards on stable and
  longterm kernels.

That thread is about a patch which fixes that backward compatibility.
Further down in that thread mentioned the following:

  Trying to boot into Linux v6.1.123+, v6.6.69+ and v6.12.8+ using the
  U-Boot bundled DT for RK356x boards now result in broken PCIe, SATA and
  USB

This issue results in the following kernel errors:

  [6.075822] rockchip-naneng-combphy fe83.phy: error -ENOENT: failed to 
get phy reset
  [6.076599] rockchip-naneng-combphy fe83.phy: probe with driver 
rockchip-naneng-combphy failed with error -2
  [6.078649] rockchip-naneng-combphy fe84.phy: error -ENOENT: failed to 
get phy reset
  [6.079420] rockchip-naneng-combphy fe84.phy: probe with driver 
rockchip-naneng-combphy failed with error -2

It doesn't affect kernel 6.13 (and higher) though.

The patch has been accepted by the upstream maintainer and can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/log/?h=fixes
But it hasn't been sent 'further up the chain' just yet (right now).

This means that currently USB and PCIe is broken for rk356x devices for
both Stable/Bookworm and Testing/Trixie (and Sid).

Attached you'll find the commit from the linux-phy git repo.
I haven't added the 'fixed-upstream' tag as I wasn't sure if it needed
to be accepted 'further up the chain' for that.

HTH,
  Diederik


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 6.12.8-arm64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
From: Chukun Pan 
Date: Mon, 6 Jan 2025 18:00:01 +0800
Subject: phy: rockchip: naneng-combphy: compatible reset with old DT
Origin: 
https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/commit?id=3126ea9be66b53e607f87f067641ba724be24181

The device tree of RK3568 did not specify reset-names before.
So add fallback to old behaviour to be compatible with old DT.

Fixes: fbcbffbac994 ("phy: rockchip: naneng-combphy: fix phy reset")
Cc: Jianfeng Liu 
Signed-off-by: Chukun Pan 
Reviewed-by: Jonas Karlman 
Link: https://lore.kernel.org/r/2025010611.1344418-2-amad...@jmu.edu.cn
Signed-off-by: Vinod Koul 
---
 drivers/phy/rockchip/phy-rockchip-naneng-combphy.c | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c 
b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
index a1532ef8bbe9..8c3ce57f8915 100644
--- a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
+++ b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
@@ -324,7 +324,10 @@ static int rockchip_combphy_parse_dt(struct device *dev, 
struct rockchip_combphy
 
priv->ext_refclk = device_property_present(dev, "rockchip,ext-refclk");
 
-   priv->phy_rst = devm_reset_control_get(dev, "phy");
+   priv->phy_rst = devm_reset_control_get_exclusive(dev, "phy");
+   /* fallback to old behaviour */
+   if (PTR_ERR(priv->phy_rst) == -ENOENT)
+   priv->phy_rst = devm_reset_control_array_get_exclusive(dev);
if (IS_ERR(priv->phy_rst))
return dev_err_probe(dev, PTR_ERR(priv->phy_rst), "failed to 
get phy reset\n");
 
-- 
2.47.2

--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between thi

Bug#1098737: marked as done (virtualbox-dmks: possible missing dependency on pahole)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding virtualbox-dmks: possible missing dependency on pahole
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-dkms
Version: 7.0.20-dfsg-1.2
Severity: serious
Justification: missing declared dependency

On today's apt upgrade, the virtualbox dkms driver failed to compile,
with the error: 

/bin/sh: 1: pahole: not found

Aftet installing pahole, the installation suceeds.

Attached the complete make.log

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.13-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox-dkms depends on:
ii  dkms  3.1.5-1

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  7.0.20-dfsg-1.2

virtualbox-dkms suggests no packages.

-- no debconf information
DKMS (dkms-3.1.5) make.log for virtualbox/7.0.20 for kernel 6.12.16-amd64 
(x86_64)
So 23. Feb 16:32:25 CET 2025
Cleaning build area
# command: rm -f *.*o

# exit code: 0
# elapsed time: 00:00:00
Building module(s)
# command: make -j8 KERNELRELEASE=6.12.16-amd64 -C 
/lib/modules/6.12.16-amd64/build M=/var/lib/dkms/virtualbox/7.0.20/build
make: Entering directory '/usr/src/linux-headers-6.12.16-amd64'
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/SUPLibAll.o
  CC [M]  
/var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/common/string/strformatrt.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/combined-agnostic1.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/combined-agnostic2.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/combined-os-specific.o
  LD [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/vboxdrv.o
/var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/vboxdrv.o: warning: objtool: 
rtThreadCtxHooksLnxSchedOut+0x23: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/vboxdrv.o: warning: objtool: 
rtThreadCtxHooksLnxSchedIn+0x2d: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/vboxdrv.o: warning: objtool: 
VBoxHost_RTR0MemKernelCopyTo+0x17: redundant CLD
/var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/vboxdrv.o: warning: objtool: 
VBoxHost_RTR0MemKernelCopyFrom+0x17: redundant CLD
/var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/vboxdrv.o: warning: objtool: 
supdrvTracerCommonDeregisterImpl+0x3c: relocation to !ENDBR: 
supdrvTracerProbeFireStub+0x0
/var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/vboxdrv.o: warning: objtool: 
.export_symbol+0x518: data relocation to !ENDBR: SUPR0TracerFireProbe+0x0
/var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/vboxdrv.o: warning: objtool: 
g_aFunctions+0xea0: data relocation to !ENDBR: SUPR0TracerFireProbe+0x0
/var/lib/dkms/virtualbox/7.0.20/build/vboxdrv/vboxdrv.o: warning: objtool: 
g_pfnSupdrvProbeFireKernel+0x0: data relocation to !ENDBR: 
supdrvTracerProbeFireStub+0x0
  CC [M]  
/var/lib/dkms/virtualbox/7.0.20/build/vboxnetflt/linux/VBoxNetFlt-linux.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxnetflt/VBoxNetFlt.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxnetflt/SUPR0IdcClient.o
  CC [M]  
/var/lib/dkms/virtualbox/7.0.20/build/vboxnetflt/SUPR0IdcClientComponent.o
  CC [M]  
/var/lib/dkms/virtualbox/7.0.20/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
  LD [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxnetflt/vboxnetflt.o
  CC [M]  
/var/lib/dkms/virtualbox/7.0.20/build/vboxnetadp/linux/VBoxNetAdp-linux.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxnetadp/VBoxNetAdp.o
  LD [M]  /var/lib/dkms/virtualbox/7.0.20/build/vboxnetadp/vboxnetadp.o
  MODPOST /var/lib/dkms/virtualbox/7.0.20/build/Module.symvers
  CC [M]  /var/lib/dkms/vi

Bug#1098706: marked as done (linux: building out-of-tree modules fails with pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding linux: building out-of-tree modules fails with pahole: not found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 6.12.16-1
Severity: serious

Hi,

the last linux upload causes regressions building (probably) all
out-of-tree dkms modules, e.g.

DKMS (dkms-3.1.5) make.log for dkms_test/1.0 for kernel 6.12.16-amd64 (x86_64)
Sun Feb 23 00:18:07 UTC 2025

Building module(s)
# command: make -j14 KERNELRELEASE=6.12.16-amd64 -C 
/lib/modules/6.12.16-amd64/build M=/var/lib/dkms/dkms_test/1.0/build
make: Entering directory '/usr/src/linux-headers-6.12.16-amd64'
  CC [M]  /var/lib/dkms/dkms_test/1.0/build/dkms_test.o
  MODPOST /var/lib/dkms/dkms_test/1.0/build/Module.symvers
  CC [M]  /var/lib/dkms/dkms_test/1.0/build/dkms_test.mod.o
  CC [M]  /var/lib/dkms/dkms_test/1.0/build/.module-common.o
  LD [M]  /var/lib/dkms/dkms_test/1.0/build/dkms_test.ko
  BTF [M] /var/lib/dkms/dkms_test/1.0/build/dkms_test.ko
/bin/sh: 1: pahole: not found
make[2]: *** 
[/usr/src/linux-headers-6.12.16-common/scripts/Makefile.modfinal:64: 
/var/lib/dkms/dkms_test/1.0/build/dkms_test.ko] Error 127
make[2]: *** Deleting file '/var/lib/dkms/dkms_test/1.0/build/dkms_test.ko'
make[1]: *** [/usr/src/linux-headers-6.12.16-common/Makefile:1890: modules] 
Error 2
make: *** [/usr/src/linux-headers-6.12.16-common/Makefile:236: __sub-make] 
Error 2
make: Leaving directory '/usr/src/linux-headers-6.12.16-amd64'

# exit code: 2
# elapsed time: 00:00:03



Andreas
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support 

Processed: closing 1099214

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1099214
Bug #1099214 [linux-source] linux-source: Carefully use CPUID instruction in 
Intel machine.
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1099214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 1099300

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1099300
Bug #1099300 [linux-source] linux-source: Iteration MODULE_DEVICE_TABLE seem do 
not is safe
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1099300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 1099302

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1099302
Bug #1099302 [linux-source] linux-source: People still can avoid multiple 
definitions symbol on loader.
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1099302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1098250: marked as done (linux-image-arm64: USB and PCIe broken on rk356x devices)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1095745: fixed in linux 6.12.17-1
has caused the Debian Bug report #1095745,
regarding linux-image-arm64: USB and PCIe broken on rk356x devices
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.)


-- 
1095745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 6.12.8-1
Severity: important
Tags: upstream patch
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: arm64

https://lore.kernel.org/linux-rockchip/df8e0ff8-355b-4c18-9349-0f04ae16e...@kwiboo.se/:

  Upstream commit fbcbffbac994 ("phy: rockchip: naneng-combphy: fix phy reset")
  broke backwards compatibly with old DTs and has already been backported
  breaking i.e. PCIe and USB on Rockchip RK356x boards on stable and
  longterm kernels.

That thread is about a patch which fixes that backward compatibility.
Further down in that thread mentioned the following:

  Trying to boot into Linux v6.1.123+, v6.6.69+ and v6.12.8+ using the
  U-Boot bundled DT for RK356x boards now result in broken PCIe, SATA and
  USB

This issue results in the following kernel errors:

  [6.075822] rockchip-naneng-combphy fe83.phy: error -ENOENT: failed to 
get phy reset
  [6.076599] rockchip-naneng-combphy fe83.phy: probe with driver 
rockchip-naneng-combphy failed with error -2
  [6.078649] rockchip-naneng-combphy fe84.phy: error -ENOENT: failed to 
get phy reset
  [6.079420] rockchip-naneng-combphy fe84.phy: probe with driver 
rockchip-naneng-combphy failed with error -2

It doesn't affect kernel 6.13 (and higher) though.

The patch has been accepted by the upstream maintainer and can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/log/?h=fixes
But it hasn't been sent 'further up the chain' just yet (right now).

This means that currently USB and PCIe is broken for rk356x devices for
both Stable/Bookworm and Testing/Trixie (and Sid).

Attached you'll find the commit from the linux-phy git repo.
I haven't added the 'fixed-upstream' tag as I wasn't sure if it needed
to be accepted 'further up the chain' for that.

HTH,
  Diederik


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 6.12.8-arm64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
From: Chukun Pan 
Date: Mon, 6 Jan 2025 18:00:01 +0800
Subject: phy: rockchip: naneng-combphy: compatible reset with old DT
Origin: 
https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/commit?id=3126ea9be66b53e607f87f067641ba724be24181

The device tree of RK3568 did not specify reset-names before.
So add fallback to old behaviour to be compatible with old DT.

Fixes: fbcbffbac994 ("phy: rockchip: naneng-combphy: fix phy reset")
Cc: Jianfeng Liu 
Signed-off-by: Chukun Pan 
Reviewed-by: Jonas Karlman 
Link: https://lore.kernel.org/r/2025010611.1344418-2-amad...@jmu.edu.cn
Signed-off-by: Vinod Koul 
---
 drivers/phy/rockchip/phy-rockchip-naneng-combphy.c | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c 
b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
index a1532ef8bbe9..8c3ce57f8915 100644
--- a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
+++ b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
@@ -324,7 +324,10 @@ static int rockchip_combphy_parse_dt(struct device *dev, 
struct rockchip_combphy
 
priv->ext_refclk = device_property_present(dev, "rockchip,ext-refclk");
 
-   priv->phy_rst = devm_reset_control_get(dev, "phy");
+   priv->phy_rst = devm_reset_control_get_exclusive(dev, "phy");
+   /* fallback to old behaviour */
+   if (PTR_ERR(priv->phy_rst) == -ENOENT)
+   priv->phy_rst = devm_reset_control_array_get_exclusive(dev);
if (IS_ERR(priv->phy_rst))
return dev_err_probe(dev, PTR_ERR(priv->phy_rst), "failed to 
get phy reset\n");
 
-- 
2.47.2

--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between thi

Bug#1098354: marked as done (linux-image-6.1.0: FriendlyElec R5S, one Ethernet-Port / PCI-Device missing on Kernels beyond 6.1.0-28-arm64)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1095745: fixed in linux 6.12.17-1
has caused the Debian Bug report #1095745,
regarding linux-image-6.1.0: FriendlyElec R5S, one Ethernet-Port / PCI-Device 
missing on Kernels beyond 6.1.0-28-arm64
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.)


-- 
1095745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.124-1
Severity: important
File: linux-image-6.1.0
X-Debbugs-Cc: m...@gosmooth.de

lspci on system affected
root@takashi:~# lspci 
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)
0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
2.5GbE Controller (rev 05)
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)

lspci on system not affected
root@kiyoko:~# lspci 
:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)
:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
2.5GbE Controller (rev 05)
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)
0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
2.5GbE Controller (rev 05)
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)

System is unaffected if running older kernel. I have two systems. They both
work if running the older kernel, both don't when running the newer kernel.

Older kernel:
root@kiyoko:~# cat /proc/version 
Linux version 6.1.0-28-arm64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 
6.1.119-1 (2024-11-22)

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
Device Tree model: FriendlyElec NanoPi R5S

** PCI devices:
0001:00:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3568 Remote 
Signal Processor [1d87:3566] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA 
PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Address:   Data: 
Capabilities: [70] Express (v2) Root Port (Slot-), MSI 08
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
LnkCap: Port #0, Speed 8GT/s, Width x1, ASPM L1, Exit Latency 
L1 <64us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x1
TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt+
RootCap: CRSVisible+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ 
CRSVisible+
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+ 
NROPrPrP+ LTR+
 10BitTagComp- 10BitTagReq- OBFF Via message/WAKE#, 
ExtFmt- EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- 
ARIFwd-
 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 
10BitTagReq- OBFF Disabled, ARIFwd-
 AtomicOpsCtl: ReqEn- EgressBlck-
LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 
2Retimers- DRS-
LnkCtl2: Target Link Speed: 8GT/s,

Bug#1098250: marked as done (linux-image-arm64: USB and PCIe broken on rk356x devices)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098250: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098250,
regarding linux-image-arm64: USB and PCIe broken on rk356x devices
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.)


-- 
1098250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 6.12.8-1
Severity: important
Tags: upstream patch
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: arm64

https://lore.kernel.org/linux-rockchip/df8e0ff8-355b-4c18-9349-0f04ae16e...@kwiboo.se/:

  Upstream commit fbcbffbac994 ("phy: rockchip: naneng-combphy: fix phy reset")
  broke backwards compatibly with old DTs and has already been backported
  breaking i.e. PCIe and USB on Rockchip RK356x boards on stable and
  longterm kernels.

That thread is about a patch which fixes that backward compatibility.
Further down in that thread mentioned the following:

  Trying to boot into Linux v6.1.123+, v6.6.69+ and v6.12.8+ using the
  U-Boot bundled DT for RK356x boards now result in broken PCIe, SATA and
  USB

This issue results in the following kernel errors:

  [6.075822] rockchip-naneng-combphy fe83.phy: error -ENOENT: failed to 
get phy reset
  [6.076599] rockchip-naneng-combphy fe83.phy: probe with driver 
rockchip-naneng-combphy failed with error -2
  [6.078649] rockchip-naneng-combphy fe84.phy: error -ENOENT: failed to 
get phy reset
  [6.079420] rockchip-naneng-combphy fe84.phy: probe with driver 
rockchip-naneng-combphy failed with error -2

It doesn't affect kernel 6.13 (and higher) though.

The patch has been accepted by the upstream maintainer and can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/log/?h=fixes
But it hasn't been sent 'further up the chain' just yet (right now).

This means that currently USB and PCIe is broken for rk356x devices for
both Stable/Bookworm and Testing/Trixie (and Sid).

Attached you'll find the commit from the linux-phy git repo.
I haven't added the 'fixed-upstream' tag as I wasn't sure if it needed
to be accepted 'further up the chain' for that.

HTH,
  Diederik


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 6.12.8-arm64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
From: Chukun Pan 
Date: Mon, 6 Jan 2025 18:00:01 +0800
Subject: phy: rockchip: naneng-combphy: compatible reset with old DT
Origin: 
https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git/commit?id=3126ea9be66b53e607f87f067641ba724be24181

The device tree of RK3568 did not specify reset-names before.
So add fallback to old behaviour to be compatible with old DT.

Fixes: fbcbffbac994 ("phy: rockchip: naneng-combphy: fix phy reset")
Cc: Jianfeng Liu 
Signed-off-by: Chukun Pan 
Reviewed-by: Jonas Karlman 
Link: https://lore.kernel.org/r/2025010611.1344418-2-amad...@jmu.edu.cn
Signed-off-by: Vinod Koul 
---
 drivers/phy/rockchip/phy-rockchip-naneng-combphy.c | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c 
b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
index a1532ef8bbe9..8c3ce57f8915 100644
--- a/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
+++ b/drivers/phy/rockchip/phy-rockchip-naneng-combphy.c
@@ -324,7 +324,10 @@ static int rockchip_combphy_parse_dt(struct device *dev, 
struct rockchip_combphy
 
priv->ext_refclk = device_property_present(dev, "rockchip,ext-refclk");
 
-   priv->phy_rst = devm_reset_control_get(dev, "phy");
+   priv->phy_rst = devm_reset_control_get_exclusive(dev, "phy");
+   /* fallback to old behaviour */
+   if (PTR_ERR(priv->phy_rst) == -ENOENT)
+   priv->phy_rst = devm_reset_control_array_get_exclusive(dev);
if (IS_ERR(priv->phy_rst))
return dev_err_probe(dev, PTR_ERR(priv->phy_rst), "failed to 
get phy reset\n");
 
-- 
2.47.2

--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between thi

Bug#1095745: marked as done (rockchip: NVMe unavailable on rk3568 platform)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1095745: fixed in linux 6.12.17-1
has caused the Debian Bug report #1095745,
regarding rockchip: NVMe unavailable on rk3568 platform
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.)


-- 
1095745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-image-arm64
Version: 6.1.123-1
Source: linux
Tags: patch

Dear maintainers,

Commit fd3ac6e80497 ("phy: rockchip: naneng-combphy: fix phy reset") 
introduced an issue that breaks NVMe support on rk3568 based systems 
(e.g. radxa ropck 3A).


There is an patch available upstream [1] that we applied to debian 
kernel 6.1.128-1 (6.1.0-31) and can confirm that it fixes this issue.


Thanks for your work,
Valentin

[1] 
https://lore.kernel.org/lkml/2025010611.1344418-2-amad...@jmu.edu.cn/
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1095...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit FW version string length
 - [amd64] accel/ivpu: Add coredump support
 - [amd64] accel/ivpu: Add FW state dump on TDR
 - [amd64] accel/ivpu: Fix error handling in recovery/reset
 - drm/amdkfd: Move gfx12 trap handler to separate file
 - drm/amdkfd: Ensure con

Bug#1099254: marked as done (nvidia-graphics-drivers-legacy-390xx: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-graphics-drivers-legacy-390xx: FTBFS: /bin/sh: 1: pahole: not 
found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-graphics-drivers-legacy-390xx
Version: 390.157-11
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build --with dkms
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{390.157}g;' \
-e 's{#MAJOR#}{390}g;' \
-e 's{#NVIDIA#}{nvidia-legacy-390xx}g;' \
-e 's{#VARIANT#}{-legacy-390xx}g;' \
-e 's{#CURRENT#}{legacy-390xx}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-legacy-390xx-kernel}g;' \

[... snipped ...]

/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2b0: data relocation to !ENDBR: _nv035290rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2b8: data relocation to !ENDBR: _nv035286rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2c0: data relocation to !ENDBR: _nv035265rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2c8: data relocation to !ENDBR: _nv035268rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2d0: data relocation to !ENDBR: _nv035271rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2d8: data relocation to !ENDBR: _nv035267rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2e0: data relocation to !ENDBR: _nv035275rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2e8: data relocation to !ENDBR: _nv035266rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2f0: data relocation to !ENDBR: _nv035274rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x2f8: data relocation to !ENDBR: _nv035269rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x300: data relocation to !ENDBR: _nv035293rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x308: data relocation to !ENDBR: _nv035277rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x310: data relocation to !ENDBR: _nv035156rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x318: data relocation to !ENDBR: _nv035156rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x320: data relocation to !ENDBR: _nv035315rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x328: data relocation to !ENDBR: _nv035316rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x330: data relocation to !ENDBR: _nv035280rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x338: data relocation to !ENDBR: _nv035279rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x340: data relocation to !ENDBR: _nv035295rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x348: data relocation to !ENDBR: _nv035158rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x350: data relocation to !ENDBR: _nv035294rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x358: data relocation to !ENDBR: _nv035157rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x360: data relocation to !ENDBR: _nv035171rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x368: data relocation to !ENDBR: _nv035172rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x370: data relocation to !ENDBR: _nv035263rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x378: data relocation to !ENDBR: _nv035264rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x380: data relocation to !ENDBR: _nv035193rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x388: data relocation to !ENDBR: _nv035189rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x390: data relocation to !ENDBR: _nv035180rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv035355rm+0x398: data relocation to !ENDBR:

Bug#1098771: marked as done (dkms: fails to build modules)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding dkms: fails to build modules
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dkms
Version: 3.1.5-1
Severity: important
Tags: ftbfs

Dear Maintainer,

today, when upgrading my kernel, the two DKMS modules i have enabled on my
machine both failed to build.
inspecting the logs shows, that the build tries to run a 'pahole' command which
does not exist on my machine.
after installing the 'pahole' package, the build of the DKMS packages succeeds
and 'apt full-upgrade' finishes successfully.

incidentally i'm also maintainer of the 'src:v4l2loopback' package that comes
with a 'v4l2loopback-dkms' package, for which i pushed a few commits to salsa
today, triggering the CI.
So you can see the build-failure in action on
 

(the missing dependency on 'pahole' could as well be in the linux-header
package; please redirect this bug-report if this is the case)

cheers


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.15-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dkms depends on:
ii  build-essential  12.12
ii  dpkg-dev 1.22.15
ii  kmod 33+20240816-2
ii  lsb-release  12.1-1
ii  make 4.4.1-1
ii  patch2.7.6-7

Versions of packages dkms recommends:
ii  clang-18 [c-compiler]  1:18.1.8-16
ii  clang-19 [c-compiler]  1:19.1.7-1+b1
ii  fakeroot   1.37-1
ii  gcc [c-compiler]   4:14.2.0-1
ii  gcc-13 [c-compiler]13.3.0-12
ii  gcc-14 [c-compiler]14.2.0-17
ii  sudo   1.9.16p2-1

Versions of packages dkms suggests:
ii  e2fsprogs  1.47.2-1
pn  menu   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed

Bug#1099145: marked as done (Enable Intel IDPF on arm64)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1099145: fixed in linux 6.12.17-1
has caused the Debian Bug report #1099145,
regarding Enable Intel IDPF on arm64
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.)


-- 
1099145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-arm64
Version: 6.12.12-1
Severity: wishlist

Intel's IDPF network interface driver is available in 6.12 and
required by current GCE bare metal machine families.

Please add CONFIG_IDPF=m to Linux kernel configuration to enable this driver.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1099...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit FW version string length
 - [amd64] accel/ivpu: Add coredump support
 - [amd64] accel/ivpu: Add FW state dump on TDR
 - [amd64] accel/ivpu: Fix error handling in recovery/reset
 - drm/amdkfd: Move gfx12 trap handler to separate file
 - drm/amdkfd: Ensure consistent barrier state saved in gfx12 trap handler
 - tracing: Switch trace.c code over to use guard()
 - tracing: Have the error of __tracing_resize_ring_buffer() passed to user
 - USB: gadget: f_midi: f_midi_complete to call queue_work
 - sched_ext: 

Bug#1099144: marked as done (Enable Intel IDPF on cloud amd64)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1099144: fixed in linux 6.12.17-1
has caused the Debian Bug report #1099144,
regarding Enable Intel IDPF on cloud amd64
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.)


-- 
1099144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-cloud-amd64
Version: 6.12.12-1
Severity: wishlist

Intel's IDPF network interface driver is available in 6.12 and
required by current GCE bare metal machine families.

Please add CONFIG_IDPF=m to Linux kernel configuration to enable this driver.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1099...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit FW version string length
 - [amd64] accel/ivpu: Add coredump support
 - [amd64] accel/ivpu: Add FW state dump on TDR
 - [amd64] accel/ivpu: Fix error handling in recovery/reset
 - drm/amdkfd: Move gfx12 trap handler to separate file
 - drm/amdkfd: Ensure consistent barrier state saved in gfx12 trap handler
 - tracing: Switch trace.c code over to use guard()
 - tracing: Have the error of __tracing_resize_ring_buffer() passed to user
 - USB: gadget: f_midi: f_midi_complete to call queue_work
 -

Bug#1098840: marked as done (virtualbox-dkms: Doesn't build with kernel 6.12.16)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding virtualbox-dkms: Doesn't build with kernel 6.12.16
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-dkms
Version: 7.0.20-dfsg-1.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-am...@lists.debian.org
User: debian-am...@lists.debian.org
Usertags: amd64

Dear Maintainer,

   * What led up to the situation? During upgrade DKMS failed to compile the
module from the sources (not only virtual box but v4l2 when I retried )
   * What exactly did you do (or not do) that was effective (or
 ineffective)? I did red the logs and saw => /bin/sh: 1: pahole: not found
=> So I installed pahole
   * What was the outcome of this action? Now it's compiling
   * So there is a missing dependency in DKMS for newer kernel than 6.12.15
that required pahole


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox-dkms depends on:
ii  dkms  3.1.5-1

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  7.0.20-dfsg-1.2

virtualbox-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to sup

Bug#1099302: People still can avoid multiple ...cont

[Marian Corcodel]

People can build a list in format .txt in kernel with reserved names used around
MODULE_DEVICE_TABLE, relative to names used by pci_id to avoid
duplicates, repeat ,loader
program is good make good job against this situation, seems random
number generator have
some issuess, or just voluntary just remove pci_id from kernel and let
developersto chose his name, and result double guards agains stringfy
problems.

Bug#1099146: Enable Intel IDPF on cloud arm64

[Andrew Jorgensen]

Package: linux-image-cloud-arm64
Version: 6.12.12-1
Severity: wishlist

Intel's IDPF network interface driver is available in 6.12 and
required by current GCE bare metal machine families.

Please add CONFIG_IDPF=m to Linux kernel configuration to enable this driver.

Bug#1099302: linux-source: People still can avoid multiple definitions symbol on loader.

[Corcodel Marian]

Package: linux-source
Severity: normal
Tags: patch
X-Debbugs-Cc: corcodel.mar...@gmail.com

Hi
Bellow i explain simple method used only for research purpose used as
countermeasure in order to run MODULE_DEVICE_TABLE macro whithout .ko file,
just fixing stringfy problems ,like:

ld: drivers/usb/host/ehci-pci.o:(.rodata+0x0): multiple definition of
`__mod_pci__pci_ids_device_table';
drivers/tty/serial/8250/8250_mid.o:(.rodata+0x0): first defined here
ld: drivers/usb/host/ohci-pci.o:(.rodata+0x0): multiple definition of
`__mod_pci__pci_ids_device_table';
drivers/tty/serial/8250/8250_mid.o:(.rodata+0x0): first defined here


-- System Information:
Debian Release: 12.9
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.5+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source depends on:
pn  linux-source-6.1  

linux-source recommends no packages.

linux-source suggests no packages.
>From 50aca464b8042c0805431cf1bd6ea9dc946ee481 Mon Sep 17 00:00:00 2001
From: Corcodel Marian 
Date: Sat, 1 Mar 2025 23:56:17 +0100
Subject: [PATCH] Avoid multiple definition on loader

Short example how to avoid multiple definition on loader, problems stringfy.
---
 drivers/tty/serial/8250/8250_lpss.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/tty/serial/8250/8250_lpss.c 
b/drivers/tty/serial/8250/8250_lpss.c
index 776ec1ef2..05aebfdc5 100644
--- a/drivers/tty/serial/8250/8250_lpss.c
+++ b/drivers/tty/serial/8250/8250_lpss.c
@@ -402,7 +402,7 @@ static const struct lpss8250_board qrk_board = {
.exit = qrk_serial_exit,
 };
 
-static const struct pci_device_id pci_ids[] = {
+static const struct pci_device_id pci_idsa[] = {
{ PCI_DEVICE_DATA(INTEL, QRK_UARTx, &qrk_board) },
{ PCI_DEVICE_DATA(INTEL, EHL_UART0, &ehl_board) },
{ PCI_DEVICE_DATA(INTEL, EHL_UART1, &ehl_board) },
@@ -418,11 +418,11 @@ static const struct pci_device_id pci_ids[] = {
{ PCI_DEVICE_DATA(INTEL, BDW_UART2, &byt_board) },
{ }
 };
-MODULE_DEVICE_TABLE(pci, pci_ids);
+MODULE_DEVICE_TABLE(pci, pci_idsa);
 
 static struct pci_driver lpss8250_pci_driver = {
.name   = "8250_lpss",
-   .id_table   = pci_ids,
+   .id_table   = pci_idsa,
.probe  = lpss8250_probe,
.remove = lpss8250_remove,
 };
-- 
2.39.5

Bug#1098354: marked as done (linux-image-6.1.0: FriendlyElec R5S, one Ethernet-Port / PCI-Device missing on Kernels beyond 6.1.0-28-arm64)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098250: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098250,
regarding linux-image-6.1.0: FriendlyElec R5S, one Ethernet-Port / PCI-Device 
missing on Kernels beyond 6.1.0-28-arm64
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.)


-- 
1098250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.124-1
Severity: important
File: linux-image-6.1.0
X-Debbugs-Cc: m...@gosmooth.de

lspci on system affected
root@takashi:~# lspci 
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)
0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
2.5GbE Controller (rev 05)
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)

lspci on system not affected
root@kiyoko:~# lspci 
:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)
:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
2.5GbE Controller (rev 05)
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)
0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
2.5GbE Controller (rev 05)
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)

System is unaffected if running older kernel. I have two systems. They both
work if running the older kernel, both don't when running the newer kernel.

Older kernel:
root@kiyoko:~# cat /proc/version 
Linux version 6.1.0-28-arm64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 
6.1.119-1 (2024-11-22)

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
Device Tree model: FriendlyElec NanoPi R5S

** PCI devices:
0001:00:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3568 Remote 
Signal Processor [1d87:3566] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA 
PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Address:   Data: 
Capabilities: [70] Express (v2) Root Port (Slot-), MSI 08
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
LnkCap: Port #0, Speed 8GT/s, Width x1, ASPM L1, Exit Latency 
L1 <64us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x1
TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt+
RootCap: CRSVisible+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ 
CRSVisible+
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+ 
NROPrPrP+ LTR+
 10BitTagComp- 10BitTagReq- OBFF Via message/WAKE#, 
ExtFmt- EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- 
ARIFwd-
 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 
10BitTagReq- OBFF Disabled, ARIFwd-
 AtomicOpsCtl: ReqEn- EgressBlck-
LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 
2Retimers- DRS-
LnkCtl2: Target Link Speed: 8GT/s,

Bug#1098354: marked as done (linux-image-6.1.0: FriendlyElec R5S, one Ethernet-Port / PCI-Device missing on Kernels beyond 6.1.0-28-arm64)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098354: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098354,
regarding linux-image-6.1.0: FriendlyElec R5S, one Ethernet-Port / PCI-Device 
missing on Kernels beyond 6.1.0-28-arm64
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.)


-- 
1098354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.124-1
Severity: important
File: linux-image-6.1.0
X-Debbugs-Cc: m...@gosmooth.de

lspci on system affected
root@takashi:~# lspci 
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)
0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
2.5GbE Controller (rev 05)
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)

lspci on system not affected
root@kiyoko:~# lspci 
:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)
:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
2.5GbE Controller (rev 05)
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)
0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 
2.5GbE Controller (rev 05)
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal 
Processor (rev 01)

System is unaffected if running older kernel. I have two systems. They both
work if running the older kernel, both don't when running the newer kernel.

Older kernel:
root@kiyoko:~# cat /proc/version 
Linux version 6.1.0-28-arm64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 
6.1.119-1 (2024-11-22)

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
Device Tree model: FriendlyElec NanoPi R5S

** PCI devices:
0001:00:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3568 Remote 
Signal Processor [1d87:3566] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA 
PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Address:   Data: 
Capabilities: [70] Express (v2) Root Port (Slot-), MSI 08
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
LnkCap: Port #0, Speed 8GT/s, Width x1, ASPM L1, Exit Latency 
L1 <64us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x1
TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt+
RootCap: CRSVisible+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ 
CRSVisible+
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+ 
NROPrPrP+ LTR+
 10BitTagComp- 10BitTagReq- OBFF Via message/WAKE#, 
ExtFmt- EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- 
ARIFwd-
 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 
10BitTagReq- OBFF Disabled, ARIFwd-
 AtomicOpsCtl: ReqEn- EgressBlck-
LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 
2Retimers- DRS-
LnkCtl2: Target Link Speed: 8GT/s,

Bug#1095745: marked as done (rockchip: NVMe unavailable on rk3568 platform)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098354: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098354,
regarding rockchip: NVMe unavailable on rk3568 platform
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.)


-- 
1098354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-image-arm64
Version: 6.1.123-1
Source: linux
Tags: patch

Dear maintainers,

Commit fd3ac6e80497 ("phy: rockchip: naneng-combphy: fix phy reset") 
introduced an issue that breaks NVMe support on rk3568 based systems 
(e.g. radxa ropck 3A).


There is an patch available upstream [1] that we applied to debian 
kernel 6.1.128-1 (6.1.0-31) and can confirm that it fixes this issue.


Thanks for your work,
Valentin

[1] 
https://lore.kernel.org/lkml/2025010611.1344418-2-amad...@jmu.edu.cn/
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit FW version string length
 - [amd64] accel/ivpu: Add coredump support
 - [amd64] accel/ivpu: Add FW state dump on TDR
 - [amd64] accel/ivpu: Fix error handling in recovery/reset
 - drm/amdkfd: Move gfx12 trap handler to separate file
 - drm/amdkfd: Ensure con

Bug#1099255: marked as done (nvidia-graphics-drivers-tesla-450: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-graphics-drivers-tesla-450: FTBFS: /bin/sh: 1: pahole: not 
found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-graphics-drivers-tesla-450
Version: 450.248.02-9
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{450.248.02}g;' \
-e 's{#MAJOR#}{450}g;' \
-e 's{#NVIDIA#}{nvidia-tesla-450}g;' \
-e 's{#VARIANT#}{-tesla-450}g;' \
-e 's{#CURRENT#}{tesla-450}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-tesla-450-kernel}g;' \

[... snipped ...]

/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3b0: data relocation to !ENDBR: _nv038777rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3b8: data relocation to !ENDBR: _nv038782rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3c0: data relocation to !ENDBR: _nv038791rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3c8: data relocation to !ENDBR: _nv038787rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3d0: data relocation to !ENDBR: _nv038790rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3d8: data relocation to !ENDBR: _nv038786rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3e0: data relocation to !ENDBR: _nv038779rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3e8: data relocation to !ENDBR: _nv038783rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3f0: data relocation to !ENDBR: _nv038780rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x3f8: data relocation to !ENDBR: _nv038784rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x400: data relocation to !ENDBR: _nv038835rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x408: data relocation to !ENDBR: _nv038836rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x410: data relocation to !ENDBR: _nv038837rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x418: data relocation to !ENDBR: _nv038838rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x420: data relocation to !ENDBR: _nv038927rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x428: data relocation to !ENDBR: _nv038928rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x430: data relocation to !ENDBR: _nv038931rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x438: data relocation to !ENDBR: _nv038939rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x440: data relocation to !ENDBR: _nv038817rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x448: data relocation to !ENDBR: _nv038826rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x450: data relocation to !ENDBR: _nv038818rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x458: data relocation to !ENDBR: _nv038828rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x460: data relocation to !ENDBR: _nv038827rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x468: data relocation to !ENDBR: _nv038795rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x470: data relocation to !ENDBR: _nv038831rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x478: data relocation to !ENDBR: _nv038869rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x480: data relocation to !ENDBR: _nv038834rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x488: data relocation to !ENDBR: _nv038934rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x490: data relocation to !ENDBR: _nv038936rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv038949rm+0x498: data relocation to !ENDBR: _nv038933rm+0x0
/<>/kern

Bug#1098789: marked as done ("pahole" dependency missing)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding "pahole" dependency missing
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: evdi-dkms
Version: 1.14.8+dfsg-1
Severity: normal

I get this output in /var/lib/dkms/evdi/1.14.8+dfsg/build/make.log:

  BTF [M] /var/lib/dkms/evdi/1.14.8+dfsg/build/evdi.ko
  /bin/sh: 1: pahole: not found
  make[2]: *** 
[/usr/src/linux-headers-6.12.16-common-rt/scripts/Makefile.modfinal:64: 
/var/lib/dkms/evdi/1.14.8+dfsg/build/evdi.ko] Fehler 127


After installation building evdi works fine, please add the dependency.

Thanks!

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')

Architecture: amd64 (x86_64)

Kernel: Linux 6.12.9-rt-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages evdi-dkms depends on:
ii  dkms  3.1.5-1

Versions of packages evdi-dkms recommends:
ii  libevdi1  1.14.8+dfsg-1

evdi-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 -

Bug#1099260: marked as done (nvidia-graphics-drivers-tesla: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-graphics-drivers-tesla: FTBFS: /bin/sh: 1: pahole: not found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-graphics-drivers-tesla
Version: 525.147.05-13
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{525.147.05}g;' \
-e 's{#MAJOR#}{525}g;' \
-e 's{#NVIDIA#}{nvidia-tesla}g;' \
-e 's{#VARIANT#}{-tesla}g;' \
-e 's{#CURRENT#}{tesla}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-tesla-kernel}g;' \

[... snipped ...]

/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035748rm+0x207: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035787rm+0x6f: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035927rm+0x49: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: _nv036413rm+0xc: 
'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035955rm+0x5c: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: _nv035962rm+0x9: 
'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: _nv036407rm+0x4: 
'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: _nv036203rm+0x4: 
'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv035969rm+0x5f: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036464rm+0x12: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036273rm+0x1f: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036250rm+0x33: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036481rm+0xde: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036232rm+0x3e7: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036450rm+0x6b0: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036502rm+0xa91: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011292rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011295rm+0x28: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036372rm+0x20: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036374rm+0x32: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036383rm+0x32: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011289rm+0x56: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011184rm+0x18a: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036381rm+0x30: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011286rm+0x59: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011265rm+0x15: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036376rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv011271rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
_nv036385rm+0x24: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.

Processing of linux-signed-amd64_6.12.17+1_source.changes

[Debian FTP Masters]

linux-signed-amd64_6.12.17+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-amd64_6.12.17+1.dsc
  linux-signed-amd64_6.12.17+1.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

linux-signed-arm64_6.12.17+1_source.changes is NEW

[Debian FTP Masters]

Mapping sid to unstable.
binary:ata-modules-6.12.17-arm64-di is NEW.
binary:btrfs-modules-6.12.17-arm64-di is NEW.
binary:cdrom-core-modules-6.12.17-arm64-di is NEW.
binary:crypto-dm-modules-6.12.17-arm64-di is NEW.
binary:crypto-modules-6.12.17-arm64-di is NEW.
binary:ext4-modules-6.12.17-arm64-di is NEW.
binary:f2fs-modules-6.12.17-arm64-di is NEW.
binary:fat-modules-6.12.17-arm64-di is NEW.
binary:fb-modules-6.12.17-arm64-di is NEW.
binary:input-modules-6.12.17-arm64-di is NEW.
binary:isofs-modules-6.12.17-arm64-di is NEW.
binary:jfs-modules-6.12.17-arm64-di is NEW.
binary:kernel-image-6.12.17-arm64-di is NEW.
binary:linux-image-6.12.17-arm64 is NEW.
binary:linux-image-6.12.17-arm64-16k is NEW.
binary:linux-image-6.12.17-cloud-arm64 is NEW.
binary:linux-image-6.12.17-rt-arm64 is NEW.
binary:loop-modules-6.12.17-arm64-di is NEW.
binary:md-modules-6.12.17-arm64-di is NEW.
binary:mmc-modules-6.12.17-arm64-di is NEW.
binary:multipath-modules-6.12.17-arm64-di is NEW.
binary:nbd-modules-6.12.17-arm64-di is NEW.
binary:nic-modules-6.12.17-arm64-di is NEW.
binary:nic-shared-modules-6.12.17-arm64-di is NEW.
binary:nic-usb-modules-6.12.17-arm64-di is NEW.
binary:nic-wireless-modules-6.12.17-arm64-di is NEW.
binary:ppp-modules-6.12.17-arm64-di is NEW.
binary:sata-modules-6.12.17-arm64-di is NEW.
binary:scsi-core-modules-6.12.17-arm64-di is NEW.
binary:scsi-modules-6.12.17-arm64-di is NEW.
binary:scsi-nic-modules-6.12.17-arm64-di is NEW.
binary:sound-modules-6.12.17-arm64-di is NEW.
binary:speakup-modules-6.12.17-arm64-di is NEW.
binary:squashfs-modules-6.12.17-arm64-di is NEW.
binary:udf-modules-6.12.17-arm64-di is NEW.
binary:uinput-modules-6.12.17-arm64-di is NEW.
binary:usb-modules-6.12.17-arm64-di is NEW.
binary:usb-serial-modules-6.12.17-arm64-di is NEW.
binary:usb-storage-modules-6.12.17-arm64-di is NEW.
binary:xfs-modules-6.12.17-arm64-di is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports


pgpsBnBNDJwnY.pgp
Description: PGP signature

Processing of linux-signed-arm64_6.12.17+1_source.changes

[Debian FTP Masters]

linux-signed-arm64_6.12.17+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-arm64_6.12.17+1.dsc
  linux-signed-arm64_6.12.17+1.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Processed: merge

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1098706 1099253 1099254 1099255 1099256 1099257 1099258 1099259 
> 1099260 1099261 1099262
Bug #1098706 [src:linux] linux: building out-of-tree modules fails with pahole: 
not found
Bug #1098737 [src:linux] virtualbox-dmks: possible missing dependency on pahole
Bug #1098739 [src:linux] vhba-dkms fails to build with linux-image-6.12.16-amd64
Bug #1098742 [src:linux] nvidia-driver 535.216.03-2 and 
linux-image-6.12.16-amd64 won't compile - missing `pahole`
Bug #1098771 [src:linux] dkms: fails to build modules
Bug #1098779 [src:linux] zfs-dkms: zfs/2.3.0 fails to build with kenel 
6.12.16-amd64
Bug #1098782 [src:linux] Bug: nvidia-driver missing dependency on dwarves 
(pahole required for DKMS build)
Bug #1098786 [src:linux] dkms: needs pahole but doesn't depend on it
Bug #1098789 [src:linux] "pahole" dependency missing
Bug #1098794 [src:linux] FTBFS: pahole Build-Deps might be missing?
Bug #1098814 [src:linux] linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad 
return status for module build on kernel
Bug #1098840 [src:linux] virtualbox-dkms: Doesn't build with kernel 6.12.16
Bug #1099258 [src:linux] nvidia-graphics-drivers-tesla-460: FTBFS: /bin/sh: 1: 
pahole: not found
Added indication that 1099258 affects 
virtualbox-dkms,v4l2loopback-dkms,src:zfs-dkms,src:dkms,package,src:nvidia-driver,lime-forensics-dkms,acpi-call-dkms,src:vhba-dkms,src:evdi-dkms,broadcom-sta-dkms,src:virtualbox-dkms
Marked as fixed in versions linux/6.13.5-1~exp1.
Marked as found in versions linux/6.13.4-1~exp1 and linux/6.12.16-1.
Added tag(s) confirmed and pending.
Bug #1098742 [src:linux] nvidia-driver 535.216.03-2 and 
linux-image-6.12.16-amd64 won't compile - missing `pahole`
Removed indication that 1098742 affects broadcom-sta-dkms, virtualbox-dkms, 
package, src:evdi-dkms, src:nvidia-driver, v4l2loopback-dkms, acpi-call-dkms, 
src:zfs-dkms, lime-forensics-dkms, src:dkms, src:virtualbox-dkms, and 
src:vhba-dkms
Added indication that 1098742 affects 
virtualbox-dkms,v4l2loopback-dkms,src:zfs-dkms,src:dkms,package,src:nvidia-driver,lime-forensics-dkms,acpi-call-dkms,src:vhba-dkms,src:evdi-dkms,broadcom-sta-dkms,src:virtualbox-dkms
Removed indication that 1098706 affects src:evdi-dkms, package, 
virtualbox-dkms, broadcom-sta-dkms, src:vhba-dkms, src:virtualbox-dkms, 
lime-forensics-dkms, src:dkms, src:zfs-dkms, acpi-call-dkms, v4l2loopback-dkms, 
and src:nvidia-driver
Added indication that 1098706 affects 
virtualbox-dkms,v4l2loopback-dkms,src:zfs-dkms,src:dkms,package,src:nvidia-driver,lime-forensics-dkms,acpi-call-dkms,src:vhba-dkms,src:evdi-dkms,broadcom-sta-dkms,src:virtualbox-dkms
Removed indication that 1098737 affects src:evdi-dkms, broadcom-sta-dkms, 
virtualbox-dkms, package, src:zfs-dkms, src:dkms, lime-forensics-dkms, 
src:virtualbox-dkms, src:vhba-dkms, v4l2loopback-dkms, src:nvidia-driver, and 
acpi-call-dkms
Added indication that 1098737 affects 
virtualbox-dkms,v4l2loopback-dkms,src:zfs-dkms,src:dkms,package,src:nvidia-driver,lime-forensics-dkms,acpi-call-dkms,src:vhba-dkms,src:evdi-dkms,broadcom-sta-dkms,src:virtualbox-dkms
Removed indication that 1098739 affects src:evdi-dkms, broadcom-sta-dkms, 
package, virtualbox-dkms, src:zfs-dkms, src:virtualbox-dkms, src:vhba-dkms, 
src:dkms, lime-forensics-dkms, acpi-call-dkms, src:nvidia-driver, and 
v4l2loopback-dkms
Added indication that 1098739 affects 
virtualbox-dkms,v4l2loopback-dkms,src:zfs-dkms,src:dkms,package,src:nvidia-driver,lime-forensics-dkms,acpi-call-dkms,src:vhba-dkms,src:evdi-dkms,broadcom-sta-dkms,src:virtualbox-dkms
Removed indication that 1098771 affects v4l2loopback-dkms, src:nvidia-driver, 
acpi-call-dkms, lime-forensics-dkms, src:dkms, src:virtualbox-dkms, 
src:vhba-dkms, src:zfs-dkms, virtualbox-dkms, package, broadcom-sta-dkms, and 
src:evdi-dkms
Added indication that 1098771 affects 
virtualbox-dkms,v4l2loopback-dkms,src:zfs-dkms,src:dkms,package,src:nvidia-driver,lime-forensics-dkms,acpi-call-dkms,src:vhba-dkms,src:evdi-dkms,broadcom-sta-dkms,src:virtualbox-dkms
Removed indication that 1098779 affects acpi-call-dkms, src:nvidia-driver, 
v4l2loopback-dkms, src:zfs-dkms, src:vhba-dkms, src:virtualbox-dkms, src:dkms, 
lime-forensics-dkms, broadcom-sta-dkms, package, virtualbox-dkms, and 
src:evdi-dkms
Added indication that 1098779 affects 
virtualbox-dkms,v4l2loopback-dkms,src:zfs-dkms,src:dkms,package,src:nvidia-driver,lime-forensics-dkms,acpi-call-dkms,src:vhba-dkms,src:evdi-dkms,broadcom-sta-dkms,src:virtualbox-dkms
Removed indication that 1098782 affects package, virtualbox-dkms, 
broadcom-sta-dkms, src:evdi-dkms, acpi-call-dkms, src:nvidia-driver, 
v4l2loopback-dkms, src:vhba-dkms, src:virtualbox-dkms, src:dkms, 
lime-forensics-dkms, and src:zfs-dkms
Added indication that 1098782 affects 
virtualbox-dkms,v4l2loopback-dkms,src:zfs-dkms,src:dkms,package,src:nvidia-driver,lime-forensics-dkms,acpi-call-dkms,src:vhba-dkms,src:evdi-dkms,broadcom-sta-dkms,src:virtualbox-dkms
Removed ind

Processed: reassign

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # affects will be next if this works
> reassign 1099253 src:linux
Bug #1099253 [src:nvidia-graphics-drivers-legacy-340xx] 
nvidia-graphics-drivers-legacy-340xx: FTBFS: /bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-graphics-drivers-legacy-340xx' to 
'src:linux'.
No longer marked as found in versions 
nvidia-graphics-drivers-legacy-340xx/340.108-24.
Ignoring request to alter fixed versions of bug #1099253 to the same values 
previously set
> reassign 1099254 src:linux
Bug #1099254 [src:nvidia-graphics-drivers-legacy-390xx] 
nvidia-graphics-drivers-legacy-390xx: FTBFS: /bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-graphics-drivers-legacy-390xx' to 
'src:linux'.
No longer marked as found in versions 
nvidia-graphics-drivers-legacy-390xx/390.157-11.
Ignoring request to alter fixed versions of bug #1099254 to the same values 
previously set
> reassign 1099255 src:linux
Bug #1099255 [src:nvidia-graphics-drivers-tesla-450] 
nvidia-graphics-drivers-tesla-450: FTBFS: /bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-graphics-drivers-tesla-450' to 
'src:linux'.
No longer marked as found in versions 
nvidia-graphics-drivers-tesla-450/450.248.02-9.
Ignoring request to alter fixed versions of bug #1099255 to the same values 
previously set
> reassign 1099256 src:linux
Bug #1099256 [src:nvidia-graphics-drivers-tesla-418] 
nvidia-graphics-drivers-tesla-418: FTBFS: /bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-graphics-drivers-tesla-418' to 
'src:linux'.
No longer marked as found in versions 
nvidia-graphics-drivers-tesla-418/418.226.00-17.
Ignoring request to alter fixed versions of bug #1099256 to the same values 
previously set
> reassign 1099257 src:linux
Bug #1099257 [src:nvidia-graphics-drivers-tesla-470] 
nvidia-graphics-drivers-tesla-470: FTBFS: /bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-graphics-drivers-tesla-470' to 
'src:linux'.
No longer marked as found in versions 
nvidia-graphics-drivers-tesla-470/470.256.02-5.
Ignoring request to alter fixed versions of bug #1099257 to the same values 
previously set
> reassign 1099258 src:linux
Bug #1099258 [src:nvidia-graphics-drivers-tesla-460] 
nvidia-graphics-drivers-tesla-460: FTBFS: /bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-graphics-drivers-tesla-460' to 
'src:linux'.
No longer marked as found in versions 
nvidia-graphics-drivers-tesla-460/460.106.00-19.
Ignoring request to alter fixed versions of bug #1099258 to the same values 
previously set
> reassign 1099259 src:linux
Bug #1099259 [src:nvidia-graphics-drivers-tesla-535] 
nvidia-graphics-drivers-tesla-535: FTBFS: /bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-graphics-drivers-tesla-535' to 
'src:linux'.
No longer marked as found in versions 
nvidia-graphics-drivers-tesla-535/535.216.03-1.
Ignoring request to alter fixed versions of bug #1099259 to the same values 
previously set
> reassign 1099260 src:linux
Bug #1099260 [src:nvidia-graphics-drivers-tesla] nvidia-graphics-drivers-tesla: 
FTBFS: /bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-graphics-drivers-tesla' to 'src:linux'.
No longer marked as found in versions 
nvidia-graphics-drivers-tesla/525.147.05-13.
Ignoring request to alter fixed versions of bug #1099260 to the same values 
previously set
> reassign 1099261 src:linux
Bug #1099261 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: FTBFS: 
/bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:linux'.
No longer marked as found in versions nvidia-graphics-drivers/535.216.03-2.
Ignoring request to alter fixed versions of bug #1099261 to the same values 
previously set
> reassign 1099262 src:linux
Bug #1099262 [src:nvidia-open-gpu-kernel-modules] 
nvidia-open-gpu-kernel-modules: FTBFS: /bin/sh: 1: pahole: not found
Bug reassigned from package 'src:nvidia-open-gpu-kernel-modules' to 'src:linux'.
No longer marked as found in versions 
nvidia-open-gpu-kernel-modules/535.216.03-2.
Ignoring request to alter fixed versions of bug #1099262 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1099253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099253
1099254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099254
1099255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099255
1099256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099256
1099257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099257
1099258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099258
1099259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099259
1099260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099260
1099261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099261
1099262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099262
Debian Bug Tracki

Bug#1099257: marked as done (nvidia-graphics-drivers-tesla-470: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-graphics-drivers-tesla-470: FTBFS: /bin/sh: 1: pahole: not 
found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-graphics-drivers-tesla-470
Version: 470.256.02-5
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{470.256.02}g;' \
-e 's{#MAJOR#}{470}g;' \
-e 's{#NVIDIA#}{nvidia-tesla-470}g;' \
-e 's{#VARIANT#}{-tesla-470}g;' \
-e 's{#CURRENT#}{tesla-470}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-tesla-470-kernel}g;' \

[... snipped ...]

/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x460: data relocation to !ENDBR: _nv041177rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x468: data relocation to !ENDBR: _nv041145rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x470: data relocation to !ENDBR: _nv041181rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x478: data relocation to !ENDBR: _nv041219rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x480: data relocation to !ENDBR: _nv041184rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x488: data relocation to !ENDBR: _nv041284rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x490: data relocation to !ENDBR: _nv041286rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x498: data relocation to !ENDBR: _nv041283rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4a0: data relocation to !ENDBR: _nv041288rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4a8: data relocation to !ENDBR: _nv041282rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4b0: data relocation to !ENDBR: _nv041287rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4b8: data relocation to !ENDBR: _nv041285rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4c0: data relocation to !ENDBR: _nv041068rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4c8: data relocation to !ENDBR: _nv041081rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4d0: data relocation to !ENDBR: _nv041066rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4d8: data relocation to !ENDBR: _nv041280rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4e0: data relocation to !ENDBR: _nv041242rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4e8: data relocation to !ENDBR: _nv041224rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4f0: data relocation to !ENDBR: _nv041249rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x4f8: data relocation to !ENDBR: _nv041143rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x500: data relocation to !ENDBR: _nv041154rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x508: data relocation to !ENDBR: _nv041155rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x510: data relocation to !ENDBR: _nv041156rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x518: data relocation to !ENDBR: _nv041157rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x520: data relocation to !ENDBR: _nv041182rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x528: data relocation to !ENDBR: _nv041183rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x530: data relocation to !ENDBR: _nv041079rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x538: data relocation to !ENDBR: _nv041080rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x540: data relocation to !ENDBR: _nv041275rm+0x0
/<>/kernel-source-tree/nvidia.o: warning: objtool: 
_nv041299rm+0x548: data relocation to !ENDBR: _nv041276rm+0x0
/<>/kern

Bug#1098786: marked as done (dkms: needs pahole but doesn't depend on it)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding dkms: needs pahole but doesn't depend on it
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: dkms
Version: 3.1.5-1
Severity: grave

Dear maintainers,

It seems DKMS now uses pahole, but it's not listed as a dependency. This 
makes module build (and thus the whole upgrade) fail.


Installing pahole solves the problem.

Please update dependencies.

Regards,

--
Raphaël Halimi
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit FW version string length
 - [amd64] accel/ivpu: Add coredump support
 - [amd64] accel/ivpu: Add FW state dump on TDR
 - [amd64] accel/ivpu: Fix error handling in recovery/reset
 - drm/amdkfd: Move gfx12 trap handler to separate file
 - drm/amdkfd: Ensure consistent barrier state saved in gfx12 trap handler
 - tracing: Switch trace.c code over to use guard()
 - tracing: Have the error of __tracing_resize_ring_buffer() passed to user
 - USB: gadget: f_midi: f_m

Bug#1098814: marked as done (linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad return status for module build on kernel)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding linux-image-6.12.16-amd64: [6.12.16-amd64] Error! Bad return status 
for module build on kernel
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.12.16-1
Severity: important

Dear Maintainer,

I can’t upgrade 6.12.15 to 6.12.16.
Here is apt’s output:
Failed command:
env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=6.12.16-amd64

Error! Bad return status for module build on kernel: 6.12.16-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/535.216.03/build/make.log for more
information.

Autoinstall on 6.12.16-amd64 failed for module(s) nvidia-current(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: erreur de traitement du paquet linux-image-6.12.16-amd64 (--configure) :
 le sous-processus paquet linux-image-6.12.16-amd64 script post-installation
installé a renvoyé un état de sortie
d'erreur 1
dpkg: des problèmes de dépendances empêchent la configuration de linux-image-
amd64 :
 linux-image-amd64 dépend de linux-image-6.12.16-amd64 (= 6.12.16-1); cependant
:
 Le paquet linux-image-6.12.16-amd64 n'est pas encore configuré.

[cut]

Note that I’m not running 6.12.5 but 6.11.10.
I can’t send the make.log file here (it’s too big).

Yours,
n.


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Gigabyte Technology Co., Ltd.
product_name: B450M DS3H WIFI
product_version: -CF
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends International, LLC.
bios_version: F1
board_vendor: Gigabyte Technology Co., Ltd.
board_name: B450M DS3H WIFI-CF
board_version: x.x

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Root Complex [1022:1480]
Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root 
Complex [1022:1480]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 61)
Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001]
Contro

Bug#1098794: marked as done (FTBFS: pahole Build-Deps might be missing?)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding FTBFS: pahole Build-Deps might be missing?
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: v4l2loopback-dkms
Version: 0.13.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This is my failure log:

/var/lib/dkms/v4l2loopback/0.13.2/build/make.log


DKMS (dkms-3.1.5) make.log for v4l2loopback/0.13.2 for kernel 6.12.16-amd64 
(x86_64)
Mon 24 Feb 10:59:27 CET 2025
Cleaning build area
# command: make clean

++ To sign the  module, you must set KBUILD_SIGN_KEY/KBUILD_SIGN_CERT to 
point to the signing key/certificate!
++ For your convenience, we try to read these variables as 
'mok_signing_key' resp. 'mok_certificate' from /etc/dkms/framewo
rk.conf

++ If your certificate requires a password, pass it via the KBUILD_SIGN_PIN 
env-var!
++ E.g. using 'export KBUILD_SIGN_PIN; read -s -p "Passphrase for signing 
key : " KBUILD_SIGN_PIN; sudo --preserve-env=KBUI
LD_SIGN_PIN make sign'

rm -f *~
rm -f Module.symvers Module.markers modules.order
make -C /lib/modules/`uname -r`/build M=/var/lib/dkms/v4l2loopback/0.13.2/build 
clean
make[1]: Entering directory '/usr/src/linux-headers-6.12.10-amd64'
make[1]: Leaving directory '/usr/src/linux-headers-6.12.10-amd64'
make -C utils clean  
make[1]: Entering directory '/var/lib/dkms/v4l2loopback/0.13.2/build'
make[1]: *** utils: No such file or directory.  Stop.
make[1]: Leaving directory '/var/lib/dkms/v4l2loopback/0.13.2/build'
make: [Makefile:79: clean] Error 2 (ignored)

# exit code: 0
# elapsed time: 00:00:00
Building module(s)   
# command: make -j4 KERNELRELEASE=6.12.16-amd64 
KERNEL_DIR=/lib/modules/6.12.16-amd64/build v4l2loopback

++ To sign the  module, you must set KBUILD_SIGN_KEY/KBUILD_SIGN_CERT to 
point to the signing key/certificate!
++ For your convenience, we try to read these variables as 
'mok_signing_key' resp. 'mok_certificate' from /etc/dkms/framework.conf

++ If your certificate requires a password, pass it via the KBUILD_SIGN_PIN 
env-var!
++ E.g. using 'export KBUILD_SIGN_PIN; read -s -p "Passphrase for signing 
key : " KBUILD_SIGN_PIN; sudo --preserve-env=KBUILD_SIGN_PIN make sign'

Building v4l2-loopback driver...
make -C /lib/modules/6.12.16-amd64/build 
M=/var/lib/dkms/v4l2loopback/0.13.2/build KCPPFLAGS="" modules
make[1]: Entering directory '/usr/src/linux-headers-6.12.16-amd64'
  CC [M]  /var/lib/dkms/v4l2loopback/0.13.2/build/v4l2loopback.o
  MODPOST /var/lib/dkms/v4l2loopback/0.13.2/build/Module.symvers
  CC [M]  /var/lib/dkms/v4l2loopback/0.13.2/build/v4l2loopback.mod.o
  CC [M]  /var/lib/dkms/v4l2loopback/0.13.2/build/.module-common.o
  LD [M]  /var/lib/dkms/v4l2loopback/0.13.2/build/v4l2loopback.ko
  BTF [M] /var/lib/dkms/v4l2loopback/0.13.2/build/v4l2loopback.ko
/bin/sh: 1: pahole: not found
make[3]: *** 
[/usr/src/linux-headers-6.12.16-common/scripts/Makefile.modfinal:64: 
/var/lib/dkms/v4l2loopback/0.13.2/build/v4l2loopback.ko] Error 127
make[3]: *** Deleting file 
'/var/lib/dkms/v4l2loopback/0.13.2/build/v4l2loopback.ko'
make[2]: *** [/usr/src/linux-headers-6.12.16-common/Makefile:1890: modules] 
Error 2
make[1]: *** [/usr/src/linux-headers-6.12.16-common/Makefile:236: __sub-make] 
Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.12.16-amd64'
make: *** [Makefile:53: v4l2loopback.ko] Error 2

# exit code: 2
# elapsed time: 00:00:03


The module builds fine after installing.

~-root@io>apt-get install pahole
[...]

Need to get 258 kB of archives.
After this operation, 1,621 kB of additional disk space will be used.
Get:1 http://ftp.de.debian.org/debian sid/main amd64 pahole amd64 1.29-2 [258 
kB]
Fetched 258 kB in 0s (559 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Selecting previously unselected package pahole.
(Reading database ... 417146 files and directories currently installed.)
Preparing to unpack .../pahole_1.29-2_amd64.deb ...
Unpacking pahole (1.29-2) ...
Setting up linux-image-6.12.16-amd64 (6.12.16-1) ...
/etc/kernel/postinst.d/dkms:
Sign command: /lib/modules/6.12.16-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module nvidia-current/535.216.03

Bug#1099253: marked as done (nvidia-graphics-drivers-legacy-340xx: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-graphics-drivers-legacy-340xx: FTBFS: /bin/sh: 1: pahole: not 
found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-graphics-drivers-legacy-340xx
Version: 340.108-24
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
# LD [M]  /<>/kernel-source-tree/nvidia.ko
  x86_64-linux-gnu-ld -r -m elf_x86_64 -z noexecstack --no-warn-rwx-segments 
--build-id=sha1  -T arch/x86/module.lds -o 
/<>/kernel-source-tree/nvidia.ko 
/<>/kernel-source-tree/nvidia.o 
/<>/kernel-source-tree/nvidia.mod.o 
/<>/kernel-source-tree/.module-common.o
# BTF [M] /<>/kernel-source-tree/nvidia.ko
  if [ ! -f vmlinux ]; then printf "Skipping BTF generation for %s due to 
unavailability of vmlinux
" /<>/kernel-source-tree/nvidia.ko 1>&2; else 
LLVM_OBJCOPY="x86_64-linux-gnu-objcopy" pahole -J -j 
--btf_features=encode_force,var,float,enum64,decl_tag,type_tag,optimized_func,consistent_func,decl_tag_kfuncs
 -j --lang_exclude=rust --btf_features=distilled_base --btf_base vmlinux 
/<>/kernel-source-tree/nvidia.ko; 
./tools/bpf/resolve_btfids/resolve_btfids -b vmlinux 
/<>/kernel-source-tree/nvidia.ko; fi;
/bin/sh: 1: pahole: not found
make[8]: *** 
[/usr/src/linux-headers-6.12.16-common/scripts/Makefile.modfinal:64: 
/<>/kernel-source-tree/nvidia.ko] Error 127
make[8]: *** Deleting file '/<>/kernel-source-tree/nvidia.ko'
make[7]: *** [/usr/src/linux-headers-6.12.16-common/Makefile:1890: modules] 
Error 2
make[6]: *** [/usr/src/linux-headers-6.12.16-common/Makefile:236: __sub-make] 
Error 2
make[6]: Leaving directory '/usr/src/linux-headers-6.12.16-amd64'
make[5]: *** [Makefile:236: __sub-make] Error 2
make[5]: Leaving directory '/usr/src/linux-headers-6.12.16-common'
make[4]: *** [Makefile:217: nvidia.ko] Error 2
make[4]: Leaving directory '/<>/kernel-source-tree'
make[3]: *** [debian/rules:261: override_dh_auto_test] Error 2
make[3]: Leaving directory '/<>'
make[2]: *** [debian/rules:173: build] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:173: install] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:173: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202503/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:nvidia-graphics-drivers-legacy-340xx, so 
that this is still
visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 

Bug#1099146: marked as done (Enable Intel IDPF on cloud arm64)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1099146: fixed in linux 6.12.17-1
has caused the Debian Bug report #1099146,
regarding Enable Intel IDPF on cloud arm64
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.)


-- 
1099146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-cloud-arm64
Version: 6.12.12-1
Severity: wishlist

Intel's IDPF network interface driver is available in 6.12 and
required by current GCE bare metal machine families.

Please add CONFIG_IDPF=m to Linux kernel configuration to enable this driver.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1099...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit FW version string length
 - [amd64] accel/ivpu: Add coredump support
 - [amd64] accel/ivpu: Add FW state dump on TDR
 - [amd64] accel/ivpu: Fix error handling in recovery/reset
 - drm/amdkfd: Move gfx12 trap handler to separate file
 - drm/amdkfd: Ensure consistent barrier state saved in gfx12 trap handler
 - tracing: Switch trace.c code over to use guard()
 - tracing: Have the error of __tracing_resize_ring_buffer() passed to user
 - USB: gadget: f_midi: f_midi_complete to call queue_work
 -

linux-signed-amd64_6.12.17+1_source.changes is NEW

[Debian FTP Masters]

Mapping sid to unstable.
binary:ata-modules-6.12.17-amd64-di is NEW.
binary:btrfs-modules-6.12.17-amd64-di is NEW.
binary:cdrom-core-modules-6.12.17-amd64-di is NEW.
binary:crypto-dm-modules-6.12.17-amd64-di is NEW.
binary:crypto-modules-6.12.17-amd64-di is NEW.
binary:drm-core-modules-6.12.17-amd64-di is NEW.
binary:ext4-modules-6.12.17-amd64-di is NEW.
binary:f2fs-modules-6.12.17-amd64-di is NEW.
binary:fat-modules-6.12.17-amd64-di is NEW.
binary:fb-modules-6.12.17-amd64-di is NEW.
binary:firewire-core-modules-6.12.17-amd64-di is NEW.
binary:input-modules-6.12.17-amd64-di is NEW.
binary:isofs-modules-6.12.17-amd64-di is NEW.
binary:jfs-modules-6.12.17-amd64-di is NEW.
binary:kernel-image-6.12.17-amd64-di is NEW.
binary:linux-image-6.12.17-amd64 is NEW.
binary:linux-image-6.12.17-cloud-amd64 is NEW.
binary:linux-image-6.12.17-rt-amd64 is NEW.
binary:loop-modules-6.12.17-amd64-di is NEW.
binary:md-modules-6.12.17-amd64-di is NEW.
binary:mmc-core-modules-6.12.17-amd64-di is NEW.
binary:mmc-modules-6.12.17-amd64-di is NEW.
binary:mtd-core-modules-6.12.17-amd64-di is NEW.
binary:multipath-modules-6.12.17-amd64-di is NEW.
binary:nbd-modules-6.12.17-amd64-di is NEW.
binary:nic-modules-6.12.17-amd64-di is NEW.
binary:nic-pcmcia-modules-6.12.17-amd64-di is NEW.
binary:nic-shared-modules-6.12.17-amd64-di is NEW.
binary:nic-usb-modules-6.12.17-amd64-di is NEW.
binary:nic-wireless-modules-6.12.17-amd64-di is NEW.
binary:pata-modules-6.12.17-amd64-di is NEW.
binary:pcmcia-modules-6.12.17-amd64-di is NEW.
binary:pcmcia-storage-modules-6.12.17-amd64-di is NEW.
binary:ppp-modules-6.12.17-amd64-di is NEW.
binary:rfkill-modules-6.12.17-amd64-di is NEW.
binary:sata-modules-6.12.17-amd64-di is NEW.
binary:scsi-core-modules-6.12.17-amd64-di is NEW.
binary:scsi-modules-6.12.17-amd64-di is NEW.
binary:scsi-nic-modules-6.12.17-amd64-di is NEW.
binary:serial-modules-6.12.17-amd64-di is NEW.
binary:sound-modules-6.12.17-amd64-di is NEW.
binary:speakup-modules-6.12.17-amd64-di is NEW.
binary:squashfs-modules-6.12.17-amd64-di is NEW.
binary:udf-modules-6.12.17-amd64-di is NEW.
binary:uinput-modules-6.12.17-amd64-di is NEW.
binary:usb-modules-6.12.17-amd64-di is NEW.
binary:usb-serial-modules-6.12.17-amd64-di is NEW.
binary:usb-storage-modules-6.12.17-amd64-di is NEW.
binary:xfs-modules-6.12.17-amd64-di is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports


pgpsC9oMYwZdq.pgp
Description: PGP signature

Bug#1099300: linux-source: Iteration MODULE_DEVICE_TABLE seem do not is safe

[Corcodel Marian]

Package: linux-source
Severity: normal
X-Debbugs-Cc: corcodel.mar...@gmail.com

Hi Iteration MODULE_DEVICE_TABLE seem do not is safe, which depend by parameter
CONFIG_MODULE but is not all systems is build with modules, carefoul here.


-- System Information:
Debian Release: 12.9
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.5+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source depends on:
pn  linux-source-6.1  

linux-source recommends no packages.

linux-source suggests no packages.

Bug#1095745: marked as done (rockchip: NVMe unavailable on rk3568 platform)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098250: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098250,
regarding rockchip: NVMe unavailable on rk3568 platform
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.)


-- 
1098250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-image-arm64
Version: 6.1.123-1
Source: linux
Tags: patch

Dear maintainers,

Commit fd3ac6e80497 ("phy: rockchip: naneng-combphy: fix phy reset") 
introduced an issue that breaks NVMe support on rk3568 based systems 
(e.g. radxa ropck 3A).


There is an patch available upstream [1] that we applied to debian 
kernel 6.1.128-1 (6.1.0-31) and can confirm that it fixes this issue.


Thanks for your work,
Valentin

[1] 
https://lore.kernel.org/lkml/2025010611.1344418-2-amad...@jmu.edu.cn/
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit FW version string length
 - [amd64] accel/ivpu: Add coredump support
 - [amd64] accel/ivpu: Add FW state dump on TDR
 - [amd64] accel/ivpu: Fix error handling in recovery/reset
 - drm/amdkfd: Move gfx12 trap handler to separate file
 - drm/amdkfd: Ensure con

Bug#1099262: marked as done (nvidia-open-gpu-kernel-modules: FTBFS: /bin/sh: 1: pahole: not found)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-open-gpu-kernel-modules: FTBFS: /bin/sh: 1: pahole: not found
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nvidia-open-gpu-kernel-modules
Version: 535.216.03-2
Severity: serious
Tags: ftbfs trixie sid

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
   debian/rules build
make[2]: Entering directory '/<>'
dh build
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   debian/rules override_dh_auto_build
make[3]: Entering directory '/<>'
perl -p \
-e 's{#VERSION#}{535.216.03}g;' \
-e 's{#MAJOR#}{535}g;' \
-e 's{#NVIDIA#}{nvidia}g;' \
-e 's{#VARIANT#}{}g;' \
-e 's{#NVIDIA-KERNEL#}{nvidia-open-kernel}g;' \

[... snipped ...]

/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_write_uint24+0xe: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_append_managed_buffer+0x66: 'naked' return found in MITIGATION_RETHUNK 
build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_managed_buffer_size+0x8: 'naked' return found in MITIGATION_RETHUNK 
build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_managed_buffer+0x8: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_aead_key_size+0x23: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_aead_iv_size+0x21: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_aead_tag_size+0x1e: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_aead_encryption+0xa8: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_aead_decryption+0xa8: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_asym_func_need_hash+0x30: 'naked' return found in MITIGATION_RETHUNK 
build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_signing_context_string.constprop.0+0x3a: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_asym_verify_wrap.isra.0+0x5e: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_asym_signature_size+0x2c: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_asym_verify_hash+0x134: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_req_asym_signature_size+0x2e: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_asym_get_public_key_from_x509+0x56: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_public_key_algo_OID_len+0x3a: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_x509_certificate_check.part.0+0x8a: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_asym_get_public_key_from_x509+0x4c: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_is_root_certificate+0xb1: 'naked' return found in MITIGATION_RETHUNK 
build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_verify_certificate_chain_buffer+0x4e: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_leaf_cert_public_key_from_cert_chain+0x56: 'naked' return found in 
MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_get_dhe_pub_key_size+0x2e: 'naked' return found in MITIGATION_RETHUNK 
build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_dhe_new+0x3a: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warning: objtool: 
libspdm_dhe_generate_key+0x43: 'naked' return found in MITIGATION_RETHUNK build
/<>/test-module-build/nvidia.o: warni

Bug#1099158: marked as done (linux-image-6.12.12-amd64: Please enable CONFIG_VIRTIO_IOMMU for IOMMU in virtual machines)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:11 +
with message-id 
and subject line Bug#1099158: fixed in linux 6.12.17-1
has caused the Debian Bug report #1099158,
regarding linux-image-6.12.12-amd64: Please enable CONFIG_VIRTIO_IOMMU for 
IOMMU in virtual machines
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.)


-- 
1099158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-6.12.12-amd64
Version: 6.12.12-1
Severity: normal
X-Debbugs-Cc: debian-am...@lists.debian.org
User: debian-am...@lists.debian.org
Usertags: amd64

Incus 6.10 has enabled VirtIO IOMMU on all its virtual machines with the
next LTS point release expect to pick up this change (6.0.4 which is
aimed to be the release version for trixie).

Unfortunately the Debian kernel currently doesn't have
CONFIG_VIRTIO_IOMMU enabled, so the guest VMs don't get to benefit from
IOMMU being enabled.

It would be great if this config could be enabled in both the amd64 and
arm64 kernels as those are the architectures where virtio_iommu appears
to be functional and where we have it enabled in Incus.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.16-zabbly+ (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-6.12.12-amd64 depends on:
ii  dracut [linux-initramfs-tool]  106-5
ii  kmod   33+20240816-2
ii  linux-base 4.11

Versions of packages linux-image-6.12.12-amd64 recommends:
ii  apparmor  3.1.7-4

Versions of packages linux-image-6.12.12-amd64 suggests:
pn  debian-kernel-handbook   
pn  firmware-linux-free  
pn  grub-pc | grub-efi-amd64 | extlinux  
pn  linux-doc-6.12   
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1099...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif stat

linux_6.12.17-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm/xe/oa: Separate batch submission from waiting for completion
 - drm/xe/oa/uapi: Define and parse OA sync properties
 - drm/xe/oa: Add input fence dependencies
 - xe/oa: Fix query mode of operation for OAR/OAC
 - btrfs: do not assume the full page range is not dirty in
   extent_writepage_io()
 - btrfs: move the delalloc range bitmap search into extent_io.c
 - btrfs: mark all dirty sectors as locked inside writepage_delalloc()
 - btrfs: remove unused btrfs_folio_start_writer_lock()
 - btrfs: unify to use writer locks for subpage locking
 - btrfs: rename btrfs_folio_(set|start|end)_writer_lock()
 - btrfs: use btrfs_inode in extent_writepage()
 - btrfs: fix double accounting race when btrfs_run_delalloc_range() failed
 - btrfs: fix double accounting race when extent_writepage_io() failed
 - [amd64] KVM: x86: Get vcpu->arch.apic_base directly and drop
   kvm_get_apic_base()
 - [amd64] KVM: x86: Inline kvm_get_apic_mode() in lapic.h
 - [amd64] KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active 
w/o
   VID
 - drm/amd/display: Refactoring if and endif statements to enable DC_LOGGER
 - drm/amd/display: update dcn351 used clock offset
 - drm/amd/display: Correct register address in dcn35
 - Bluetooth: qca: Update firmware-name to support board specific nvm
 - Bluetooth: qca: Fix poor RF performance for WCN6855
 - Input: serio - define serio_pause_rx guard to pause and resume serio 
ports
 - Input: synaptics - fix crash when enabling pass-through port
   (CVE-2025-21746)
 - PCI: Make pcim_request_all_regions() a public function
 - PCI: Export pci_intx_unmanaged() and pcim_intx()
 - PCI: Remove devres from pci_intx()
 - PCI: Restore original INTX_DISABLE bit by pcim_intx()
 - [arm64] dts: mediatek: mt8183-pumpkin: add HDMI support
 - [arm64] dts: mediatek: mt8183: Disable DSI display output by default
 - [amd64] accel/ivpu: Limit FW version string length
 - [amd64] accel/ivpu: Add coredump support
 - [amd64] accel/ivpu: Add FW state dump on TDR
 - [amd64] accel/ivpu: Fix error handling in recovery/reset
 - drm/amdkfd: Move gfx12 trap handler to separate file
 - drm/amdkfd: Ensure consistent barrier state saved in gfx12 trap handler
 - tracing: Switch trace.c code over to use guard()
 - tracing: Have the error of __tracing_resize_ring_buffer() passed to user
 - USB: gadget: f_midi: f_midi_complete to call queue_work
 - sched_ext: Factor out move_task_between_dsqs() from
   scx_dispatch_from_dsq()
 - sched_ext: Fix migration disabled handling in targeted dispatches
 - [arm64] ASoC: rockchip: i2s-tdm: fix shift config for
   SND_SOC_DAIFMT_DSP_[AB]
 - [amd64] ASoC: SOF: ipc4-topology: Harden loops for looking up ALH copiers
 - [powerpc*] code-patching: Disable KASAN report during patching via
   temporary mm
 - [powerpc*] 64s: Rewrite __real_pte() and __rpte_to_hidx() as static 
inline
 - ALSA: hda/realtek: Fixup ALC225 depop procedure
 - [powerpc*] code-patching: Fix KASAN hit by not flagging text patching 
area
   as VM_ALLOC
 - [arm64] ASoC: imx-audmix: remove cpu_mclk which is from cpu dai device
 - vsock/virtio: fix variables initialization during resuming
 - geneve: Fix use-after-free in geneve_find_dev().
 - ALSA: hda/cirrus: Correct the full scale volume set logic
 - net/sched: cls_api: fix error handling causing NULL dereference
 - ALSA: seq: Drop UMP events when no UMP-conversion is set
 - [s390x] ism: add release function for struct device
 - ibmvnic: Add stat for tx direct vs tx batched
 - ibmvnic: Don't reference skb after sending to VIOS
 - sockmap, vsock: For connectible sockets allow only connected
 - vsock/bpf: Warn on socket without transport
 - tcp: adjust rcvq_space after updating scaling ratio
 - net: pse-pd: Avoid setting max_uA in regulator constraints
 - net: pse-pd: Use power limit at driver side instead of current limit
 - net: pse-pd: pd692x0: Fix power limit retrieval
 - gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl().
 - geneve: Suppress list corruption splat in geneve_destroy_tunnels().
 - flow_dissector: Fix handling of mixed port and port-range keys
 - flo

Bug#1098742: marked as done (nvidia-driver 535.216.03-2 and linux-image-6.12.16-amd64 won't compile - missing `pahole`)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding nvidia-driver 535.216.03-2 and linux-image-6.12.16-amd64 won't 
compile - missing `pahole`
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 535.216.03-2

I was doing an `apt upgrade` of linux-image from 6.12.13 to 6.12.16
and it failed. No nvidia package was updated (but some mesa packages
were).



Setting up linux-image-6.12.16-amd64 (6.12.16-1) ...
/etc/kernel/postinst.d/dkms:
Sign command: /lib/modules/6.12.16-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module nvidia-current/535.216.03 for kernel
6.12.16-amd64 (x86_64)
Cleaning build area... done.
Building module(s)(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=6.12.16-amd64

Error! Bad return status for module build on kernel: 6.12.16-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/535.216.03/build/make.log for
more information.

Autoinstall on 6.12.16-amd64 failed for module(s) nvidia-current(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-6.12.16-amd64 (--configure):
installed linux-image-6.12.16-amd64 package post-installation script
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-6.12.16-amd64:
linux-headers-6.12.16-amd64 depends on linux-image-6.12.16-amd64 (=
6.12.16-1) | linux-image-6.12.16-amd64-unsigned (= 6.12.16-1);
however:
 Package linux-image-6.12.16-amd64 is not configured yet.
 Package linux-image-6.12.16-amd64-unsigned is not installed.

dpkg: error processing package linux-headers-6.12.16-amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-headers-amd64:
linux-headers-amd64 depends on linux-headers-6.12.16-amd64 (=
6.12.16-1); however:
 Package linux-headers-6.12.16-amd64 is not configured yet.

dpkg: error processing package linux-headers-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-6.12.16-amd64
linux-headers-6.12.16-amd64
linux-headers-amd64



In the `/var/lib/dkms/nvidia-current/535.216.03/build/make.log` there
were messages (at the end) about an unknown command `pahole`. After I
installed it (`apt install pahole`), it compiled correctly (in the
pahole install command, no need for an extra one).
This problem was not on `linux-image-6.12.13-amd64` (or earlier).
I guess there is a missing dependency on the `pahole` as it is used in
the make script. But I was updating nvidia-driver recently (yesterday)
and did not notice any problem.

PS: This is my first bug report to Debian, sorry if it is incorrect.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1095745 1098250 1098354 1098706 1099143 1099144 1099145 1099146 1099158
Changes:
 linux (6.12.17-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.17
 - [arm64] mte: Do not allow PROT_MTE on MAP_HUGETLB user mappings
 - drm

Bug#1098779: marked as done (zfs-dkms: zfs/2.3.0 fails to build with kenel 6.12.16-amd64)

[Debian Bug Tracking System]

Your message dated Sun, 02 Mar 2025 00:00:10 +
with message-id 
and subject line Bug#1098706: fixed in linux 6.12.17-1
has caused the Debian Bug report #1098706,
regarding zfs-dkms: zfs/2.3.0 fails to build with kenel 6.12.16-amd64
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.)


-- 
1098706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zfs-dkms
Version: 2.3.0-1
Severity: serious
Justification: unkown

Dear Maintainer,

apt update failed to compile the zfs 2.3.0 module against 6.12.16

Manually compiling it, I get:
dkms build -m zfs -v 2.3.0 -k 6.12.16-amd64

Sign command: /lib/modules/6.12.16-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Running the pre_build script(bad exit status: 1)
Failed command:
cd /var/lib/dkms/zfs/2.3.0/build/ && /var/lib/dkms/zfs/2.3.0/build/configure
--disable-dependency-tracking --prefix=/usr --with-config=kernel --with-
linux=/lib/modules/6.12.16-amd64/source --with-linux-
obj=/lib/modules/6.12.16-amd64/build --with-qat= --host=


Again manually running it, I get:
cd /var/lib/dkms/zfs/2.3.0/build/
/var/lib/dkms/zfs/2.3.0/build/configure --disable-dependency-tracking
--prefix=/usr --with-config=kernel --with-
linux=/lib/modules/6.12.16-amd64/source --with-linux-
obj=/lib/modules/6.12.16-amd64/build --with-qat= --host=


checking whether CONFIG_MODULES is defined... no

get this:
configure: error:
*** This kernel does not include the required loadable module
*** support!
***
*** To build OpenZFS as a loadable Linux kernel module
*** enable loadable module support by setting
*** `CONFIG_MODULES=y` in the kernel configuration and run
*** `make modules_prepare` in the Linux source tree.
***
*** If you don't intend to enable loadable kernel module
*** support, please compile OpenZFS as a Linux kernel built-in.
***
*** Prepare the Linux source tree by running `make prepare`,
*** use the OpenZFS `--enable-linux-builtin` configure option,
*** copy the OpenZFS sources into the Linux source tree using
*** `./copy-builtin `,
*** set `CONFIG_ZFS=y` in the kernel configuration and compile
*** kernel as usual.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.11-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages zfs-dkms depends on:
ii  debconf [debconf-2.0]  1.5.89
ii  dkms   3.1.5-1
ii  file   1:5.45-3+b1
ii  libc6-dev [libc-dev]   2.40-7
ii  libpython3-stdlib  3.13.1-2
ii  lsb-release12.1-1

Versions of packages zfs-dkms recommends:
ii  linux-libc-dev  6.12.16-1
ii  zfs-zed 2.3.0-1
ii  zfsutils-linux  2.3.0-1

Versions of packages zfs-dkms suggests:
pn  debhelper  

-- debconf information:
  zfs-dkms/stop-build-for-32bit-kernel: true
* zfs-dkms/note-incompatible-licenses:
  zfs-dkms/stop-build-for-unknown-kernel: true
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.12.17-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1098...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Mar 2025 17:57:27 +0100
Source: linux
Architecture: source
Version: 6.12.17-1
Distribution: u