Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
Hi, Could you please provide a full boot log with that? I notice that the kernel is tained with TAINT_OOT_MODULE, so please try to boot without loading of those OOT modules, what is the outcome? Regards, Salvatore
HI, Please see bug report 1088524, Its the same but with more information. Please see attached boot log. Benjamin
Hi Benjamin, Thanks for providing the full log. As I understand from the subject this is only aproblem with 3 screens. So if this is correct and with two screens all is green, do boot please with two screens and attach this full boot logs as well for comparision. In meanwhile there is as well newer kernel available, please upgrade to 6.1.129-1 and report back if the problem persist with the nwer kernel as well. Ideally if yes, then testing newer kernel from unstable or experimental would be great to determine if the issue is fixed. Thanks already. Regards,
HI Salvatore, On my current install I have installed NVIDIA drivers to be able to work with the 3 screens. I did a fresh install of Debian 12 on a different ssd to do the test. Attached are the two boot logs one with 3 screens connected and turned on, and one with 2 screens connected and turned on. This is a fresh install of Debian 12.10. Regards, Benjamin
Thank-you for the boot logs Benjamin. The 3-monitor log initially confused me since it started with the 2-monitor log and looked identical. Once I'd figured it contained multiple boots and cleaned it I compared differences using: diff -u <( sed -n '/kernel:/ s/^.*kernel: \(nouveau.*\)/\1/p' /tmp/bootlog_2_screens.log ) <( sed -n '/kernel:/ s/^.*kernel: \(nouveau.*\)/\1/p' /tmp/bootlog_3_screens.log ) --- /dev/fd/63 2025-04-03 18:21:05.169414147 +0100 +++ /dev/fd/62 2025-04-03 18:21:05.169414147 +0100 @@ -44,18 +44,303 @@ nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies nouveau 0000:01:00.0: sec2: cmdq: timeout waiting for queue ready nouveau 0000:01:00.0: gr: init failed, -110 -nouveau 0000:01:00.0: DRM: allocated 2560x1440 fb: 0x200000, bo 0000000094c55ef2 +nouveau 0000:01:00.0: DRM: allocated 2560x1440 fb: 0x200000, bo 00000000afe506a5 nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device nouveau 0000:01:00.0: DRM: Disabling PCI power management to avoid bug nouveau 0000:01:00.0: gr: fecs falcon already acquired by gr! nouveau 0000:01:00.0: gr: init failed, -16 +nouveau 0000:01:00.0: Xorg[734]: failed to idle channel 2 [Xorg[734]] nouveau 0000:01:00.0: gr: fecs falcon already acquired by gr! nouveau 0000:01:00.0: gr: init failed, -16 +nouveau 0000:01:00.0: Xorg[734]: failed to idle channel 2 [Xorg[734]] +nouveau 0000:01:00.0: i2c: aux 0004: magic wait 00009000 +nouveau 0000:01:00.0: i2c: aux 0004: magic wait 00009000 +nouveau 0000:01:00.0: i2c: aux 0004: magic wait 00009000 ... After looking at other logs and reports it seems the "sec2" and "gr" messages are expected for the TU117 models. The important part here is "failed to idle channel 2". Based on my experience using an Nvidia Quadro NVS420 that contains 2 GPUs and has 4 outputs I *think* the channels are paired such that: Channel Pair Monitor 0 1 A 1 1 B 2 2 C 3 2 D It may be the case that for the GPU model here there is a problem in operating the second pair (channel 2 in your case). I've skimmed through the nouveau commit history from v6.1 up to current master but could not see anything obvious related to this, but then again the code is extremely complex and covers so many models I suspect it needs someone intimately familiar with the hardware and code to know what to look for. I'd recommend the following in an attempt to narrow down the cause and possibly identify a fix: 1) Test a recent mainline kernel [0] (if building a kernel is a problem maybe try a pre-built kernel from experimental [1]). If the issue is resolved we can try to identify where the fix is either through commit history or a git bisect. Note however even if a fix is found it may not be possible to back-port it to v6.1 since the code has undergone some large recfactors between these versions. 2) Whether or not you can identify a fixed version report this to the nouveau developers via their issue tracker [2] since they're best placed to know what is going on and suggest further steps. I did browse through closed and open reports for something similar that might shed light but the single report there has no follow-up. I was going to recommend reporting to their mailing list [3] as well but, at least for me, their mail archive web-site is unreachable. [0] https://www.kernel.org/ [1] https://tracker.debian.org/pkg/linux [2] https://gitlab.freedesktop.org/drm/nouveau [3] https://lists.freedesktop.org/archives/nouveau/
Hi, Sorry for not responding earlier, I was waiting for a reply in my email. Today I checked on bugs.debian.org and I saw your reply below. Please see attached log, this is with the Debian 13 (Trixie), I get the same results as with Debian 12. With 3 monitors it locks up (just the monitors or the graphics card, not the computer, I can still login with ssh), and with 2 monitors it works. It does look like the the error is different in the logs. I think it is the actual graphics card that is "locking up" because I can turn off the monitors and turn them on again and they will still display that same thing as before. The only way to get out of this is to reboot the computer. Boot 1 is at the beginning of the log file and it is with the 3 screens turned on. Boot 2 starts at Jun-24 20:19:25 and is with 2 screens I was really hoping that we could get this fixed before Trixie becomes stable. As I really wanted to update my main computer to Trixie, when it becomes stable. I had one guy look at this problem and he thinks that it is the "plymouth service" that is causing this problem. He was unable to troubleshoot it any further as he said it is almost imposible to remove plymouth from Debian and still have a working system. I have tested with the latest Fedora +KDE and all 3 screens works great, no problems whatsoever. Currently Fedora is using kernel 6.15** But I remember checking back when Fedora was still on the same kernel version as Trixie and it was working then as well. So this has me believe that it is not in the kernel but something that is added by Debian. If you want I can send you a boot log from Fedora so that you can compare it with Debian. I have tested this on Ubuntu, POP OS and a few other OS based on Debian and they are all the same. Fedora is the only non Debian OS that I have tried. Regards, Benjamin. On Thu, 03 Apr 2025 18:46:41 +0100 Tj <tj.iam.tj@proton.me> wrote: > Package: linux-image-6.13.1+debian+tj > Followup-For: Bug #1088522 > X-Debbugs-Cc: tj.iam.tj@proton.me > > Thank-you for the boot logs Benjamin. The 3-monitor log initially > confused me since it started with the 2-monitor log and looked > identical. Once I'd figured it contained multiple boots and cleaned it I > compared differences using: > > diff -u <( sed -n '/kernel:/ s/^.*kernel: \(nouveau.*\)/\1/p' /tmp/bootlog_2_screens.log ) <( sed -n '/kernel:/ s/^.*kernel: \(nouveau.*\)/\1/p' /tmp/bootlog_3_screens.log ) > > --- /dev/fd/63 2025-04-03 18:21:05.169414147 +0100 > +++ /dev/fd/62 2025-04-03 18:21:05.169414147 +0100 > @@ -44,18 +44,303 @@ > nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies > nouveau 0000:01:00.0: sec2: cmdq: timeout waiting for queue ready > nouveau 0000:01:00.0: gr: init failed, -110 > -nouveau 0000:01:00.0: DRM: allocated 2560x1440 fb: 0x200000, bo 0000000094c55ef2 > +nouveau 0000:01:00.0: DRM: allocated 2560x1440 fb: 0x200000, bo 00000000afe506a5 > nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device > nouveau 0000:01:00.0: DRM: Disabling PCI power management to avoid bug > nouveau 0000:01:00.0: gr: fecs falcon already acquired by gr! > nouveau 0000:01:00.0: gr: init failed, -16 > +nouveau 0000:01:00.0: Xorg[734]: failed to idle channel 2 [Xorg[734]] > nouveau 0000:01:00.0: gr: fecs falcon already acquired by gr! > nouveau 0000:01:00.0: gr: init failed, -16 > +nouveau 0000:01:00.0: Xorg[734]: failed to idle channel 2 [Xorg[734]] > +nouveau 0000:01:00.0: i2c: aux 0004: magic wait 00009000 > +nouveau 0000:01:00.0: i2c: aux 0004: magic wait 00009000 > +nouveau 0000:01:00.0: i2c: aux 0004: magic wait 00009000 > ... > > After looking at other logs and reports it seems the "sec2" and "gr" > messages are expected for the TU117 models. The important part here is > "failed to idle channel 2". > > Based on my experience using an Nvidia Quadro NVS420 that contains 2 > GPUs and has 4 outputs I *think* the channels are paired such that: > > Channel Pair Monitor > 0 1 A > 1 1 B > 2 2 C > 3 2 D > > It may be the case that for the GPU model here there is a problem in > operating the second pair (channel 2 in your case). > > I've skimmed through the nouveau commit history from v6.1 up to current > master but could not see anything obvious related to this, but then > again the code is extremely complex and covers so many models I suspect > it needs someone intimately familiar with the hardware and code to know > what to look for. > > I'd recommend the following in an attempt to narrow down the cause and > possibly identify a fix: > > 1) Test a recent mainline kernel [0] (if building a kernel is a problem > maybe try a pre-built kernel from experimental [1]). If the issue is > resolved we can try to identify where the fix is either through commit
Hello Benjamin, That would be great, ideally with similar kernels. Given that Fedora is at 6.15, can you try with Debian's 6.15 kernel from experimental to compare? Also I wouldn't be surprised if userspace also plays a role here. So creating a monolithic kernel for your system and booting that once with Debian and once with Fedora would probably also help. That would be done using something like: git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git cd linux-stable git checkout v6.15.4 cp /boot/config-$(uname -r) arch/x86/configs/my_defconfig make my_defconfig make localmodconfig make localyesconfig make -j 12 make install Best regards Uwe
Hi, Uwe, I tried to run the commands you gave on my Fedora install but was met with errors when running the make commands, I did not try it on my Debian install. Please see attached boot logs of Fedora, and Debian with kernel 6.15 installed. There are 3 boot sessions in the Debian boot log. First was with 2 monitors, 2nd was with all 3 connected (it failed), and 3rd was with 2 connected. Fedora was with all 3 connected. Regards, Benjamin
Hello, journalctl -b -k to only contain the kernel logs. That makes it a bit easier on the receiving end. Comparing the 2nd Debian log with the fedora one I don't spot the problem. Debian has a message nouveau 0000:01:00.0: pmu: firmware unavailable which might be a hint that the relevant hint is related to firmware. There are a few more differences: Debian has several lines nouveau 0000:01:00.0: i2c: aux 0004: magic wait 00008000 and timeout messages: nouveau 0000:01:00.0: sec2:cmdq: timeout waiting for reply nouveau 0000:01:00.0: gr: init failed, -110 nouveau 0000:01:00.0: timeout WARNING: CPU: 2 PID: 932 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:841 gf100_gr_fecs_bind_pointer+0x123/0x140 [nouveau] ee1004 wmi_bmof snd_hwdep snd_pcm pcspkr intel_uncore snd_timer snd mei_me mei soundcore intel_pch_thermal raid6_pq joydev intel_pmc_core pmt_telemetry pmt_class intel_vsec acpi_pad evdev sg msr parport_pc ppdev lp parport configfs efi_pstore nfnetlink efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nouveau uas usb_storage mxm_wmi drm_gpuvm gpu_sched sd_mod drm_ttm_helper ttm drm_exec drm_display_helper cec rc_core drm_client_lib drm_kms_helper ahci libahci xhci_pci libata drm nvme xhci_hcd iTCO_wdt scsi_mod intel_pmc_bxt igb iTCO_vendor_support nvme_core watchdog usbcore i2c_algo_bit e1000e nvme_keyring dca nvme_auth i2c_i801 usb_common video i2c_smbus scsi_common fan wmi button RIP: 0010:gf100_gr_fecs_bind_pointer+0x123/0x140 [nouveau] gf100_grctx_generate+0x2c4/0x720 [nouveau] gf100_gr_chan_new+0x458/0x490 [nouveau] nvkm_cgrp_ectx_get+0x154/0x1e0 [nouveau] nvkm_cgrp_vctx_get+0xf7/0x2b0 [nouveau] nvkm_chan_cctx_get+0x125/0x220 [nouveau] nvkm_uchan_object_new+0xd3/0x1e0 [nouveau] nvkm_ioctl_new+0x141/0x220 [nouveau] ? __pfx_nvkm_uchan_object_new+0x10/0x10 [nouveau] ? __pfx_gf100_gr_object_new+0x10/0x10 [nouveau] nvkm_ioctl+0xbc/0x190 [nouveau] nvif_object_ctor+0x121/0x1a0 [nouveau] nouveau_abi16_ioctl+0x4fa/0x5b0 [nouveau] nouveau_drm_ioctl+0xa2/0xb0 [nouveau] nouveau 0000:01:00.0: gr: failed to construct context nouveau 0000:01:00.0: fifo:000000:0003:[Xorg[932]] ectx 0[gr]: -110 nouveau 0000:01:00.0: fifo:000000:0003:0003:[Xorg[932]] vctx 0[gr]: -110 Can you please compare the used firmware blobs between Debian and fedora? And maybe try booting the Debian system with the fedora kernel (and vice versa). For the latter I'd copy fedora's /lib/modules/6.15.4-200.fc42.x86_64 into the Debian rootfs and then edit fedora's grub boot entry to use root=UUID=6c47cad0-3157-4246-94b0-1985db645ff0 instead of root=UUID=9445de78-114f-4960-9823-cefaa8824cf1 rootflags=subvol=root resume=UUID=ae6b6cd8-1d85-4f26-b7e6-ce442951cc79 . If you spot a difference in the firmware files it might also be worth to boot Debian with fedora's firmware blobs. Best regards Uwe
Hi, Please provide complete file paths to check the firmware files. If I copy /lib/modules/6.15.4-200.fc42.x86_64 from Fedora into Debian's /lib/modules/, can I use "sudo update-grub" to update the grub boot entry or do I need to manually edit the entry? regards, Benjamin
Hello Benjamin, There are quite a lot, I think the relevant files are: $ /sbin/modinfo nouveau | grep firmware | grep tu117 firmware: nvidia/tu117/acr/ucode_ahesasc.bin firmware: nvidia/tu117/acr/bl.bin firmware: nvidia/tu117/acr/ucode_asb.bin firmware: nvidia/tu117/acr/ucode_unload.bin firmware: nvidia/tu117/acr/unload_bl.bin firmware: nvidia/tu117/nvdec/scrubber.bin firmware: nvidia/tu117/gsp/gsp-535.113.01.bin firmware: nvidia/tu117/gsp/bootloader-535.113.01.bin firmware: nvidia/tu117/gsp/booter_unload-535.113.01.bin firmware: nvidia/tu117/gsp/booter_load-535.113.01.bin firmware: nvidia/tu117/gr/sw_veid_bundle_init.bin firmware: nvidia/tu117/gr/sw_method_init.bin firmware: nvidia/tu117/gr/sw_bundle_init.bin firmware: nvidia/tu117/gr/sw_nonctx.bin firmware: nvidia/tu117/gr/sw_ctx.bin firmware: nvidia/tu117/gr/gpccs_sig.bin firmware: nvidia/tu117/gr/gpccs_data.bin firmware: nvidia/tu117/gr/gpccs_inst.bin firmware: nvidia/tu117/gr/gpccs_bl.bin firmware: nvidia/tu117/gr/fecs_sig.bin firmware: nvidia/tu117/gr/fecs_data.bin firmware: nvidia/tu117/gr/fecs_inst.bin firmware: nvidia/tu117/gr/fecs_bl.bin firmware: nvidia/tu117/sec2/sig.bin firmware: nvidia/tu117/sec2/image.bin firmware: nvidia/tu117/sec2/desc.bin These should be in /lib/firmware. I'm not sure if it does the right thing. Certainly it would need copying the kernel to /boot, too and then maybe `update-initramfs -k all -u` does the right thing. If it works that would result in the fedora kernel being booted with Debian firmware files only. Might be worth a try. But my thought was to edit the grub menulist item, in the assumption that your machine has both fedora and Debian installed without swapping harddisks. The above test is maybe more sensible, because when booting the fedora kernel+initramfs with Debian rootfs it's not entirely clear without further checking how relevant the firmware files are that might be in the fedora initramfs. Best regards Uwe
HI, I ran the this command on both installs, and both are the same, see attached screen shot. If I go in the /lib/firmware/nvidia/gsp/, There are a few differences there, see attached screenshot. All the rest of the files under tu117 are the same. The Fedora folder nvidia has quite a few more folders than the Debian. See attached. As far as the other things you wanted me to try, Sorry, I am not sure I understand. If you can explain them in layman terms with each step and command laid out. I will give it a try. All I know is that the GPU is getting some bad commands or info and it puts it in a locked up state. Usually some frozen artifacts on the screen. Not necessarily text, though it can be text sometimes. Best Regard, Benjamin
Hello Benjamin, I didn't check in detail, having more files can be beneficial, or not matter at all. The easy and quick test would be: mv /lib/firmware/nvidia /lib/firmware/nvidia.bak cp -a /path/to/fedora/mount/lib/firmware/nvidia /lib/firmware/nvidia update-initramfs -u -k $(uname -r) and then reboot. After the test restore the original /lib/firmware/nvidia to not confuse dpkg. Best regards Uwe
Hi Uwe, I tried this, but it did not help. with 3 monitors it still locks up. With 2 monitors it works and I can get to the desktop. Please see attached log. Regards, Benjamin
Hi Uwe, I forgot to mention that the Fedora firmware files were all compressed. Maybe that is the reason for the firmware errors in the log. Where as the Debian files are not compressed. Regards Benjamin.
Hello Benjamin, kernel patched for that. It seems I was wrong. Given that Debian can do two monitors without firmware: I wonder what Fedora does without firmware. Does Fedora still boot if you do mv /lib/firmware/nvidia /lib/firmware/nvidia.bak plus the Fedora equivalent of update-initramfs? Best regards Uwe
Hello Uwe, I changed the NVIDIA file to .bak and then updated the initramfs with Fedora's command. With 3 monitors connected I got a black screen, the monitors were turned on, but black. See log for 3 monitors. With 2 monitors I was able to login and get to the desktop but was unable to use it. It was very very sluggish, the mouse cursor was about 5 seconds behind my actions. The CPU fan was on high about the whole time, indicating high CPU usage. I think that this is because of Wayland. On Debian I am using X11. See log for two monitors. I had to use the rescue kernel to login and revert the changes. Another thing I noticed is the GPU fan, On Debian I can always hear it, its not high, but audible, With Fedora, when the firmware files load on boot, I can hear that fan slow down to an unnoticeable level. However when booting Fedora without the firmware files I could hear the GPU fan, the same as Debian. It never slowed down like before. So to me, this makes it clear that Debian needs to update its NVIDIA firmware files in the kernel. Is this something that could get pushed into Trixie yet? I doubt it, but I guess maybe a patch could be made that I could install locally. Regards, Benjamin
monitors on DisplayPort and one on HDMI. My mouse was also sluggish. And in certain modeset settings, I'd get a blinking cursor in the upper left corner and nothing else. All when using Wayland. I ended up connecting all three monitors as display port to one card: NVIDIA GeForce RTX 5070 Ti. I have this nvidia driver installed: 575.64.03 I think the key point though is I switched away from Wayland back to X11. Everything is responsive again. As much as I'd like to run Wayland, it does seem to have some shortcomings. You can choose X11 mode in Trixie with KDE (assuming that is what you are using), but choosing the renderer in the lower left corner prior to logging in. Hope this helps.
Hello Raymond, If you're using the proprietary driver, all comparison is moot. Best regards Uwe
I suspect that the Debian kernel can load the compressed firmware and just emits a misleading error message about the non-existing uncompressed files before it finds the compressed ones. (That would be easily verifiable by moving the Debian files out of /lib/firmware/nvidia without placing the compressed Fedora files there. If it behaves differently than with the compressed files, they are used.) Either that or Fedora has driver or config changes on top of the nouveau driver that are missing in Debian. Yesterday I tried to find the Fedora kernel sources archive, but I only found something older. Do you happen to know where to look for these? If it was only firmware files then it had to be good with Debian kernel + the Fedora firmware versions. If you want to you can test with the Fedora tree and run: find /lib/firmware -name \*.xz -print0 | unxz --files0 (untested, the intention is to uncompress all files). My expectation would be that this behaves in the same way as with the compressed Fedora firmware files, just without the error messages. The difficulty with firmware updates is that the changes introduced with updating are not transparent. So even if an update helps you, it might break someone else's setup ... But sure, a local modification is possible once we found the culprit. Best regards Uwe
Hi Uwe, So with no NVIDIA files or with the uncompressed Fedora files, everything is the same, see attached logs. With 2 monitors I can get to the desktop, with 3 monitors the GPU freezes. In all the test that we have done, it doesn't seem to make a difference what we do with the firmware files, all seems the same, so it seems that Debian is not evening using the firmware files to boot. And that is the reason that it is locking up with 3 monitors. Why it works with 2 monitors, I don't know. The one difference I can see in the logs between 3 or 2 monitors is that with 3 monitors we get the magic wait error, I think this has something to do with the GPU being locked up. When running the decompression command, it skipped al the files that had symbolic links. Is this what you are looking for on the Fedora kernel? >> https://koji.fedoraproject.org/koji/buildinfo?buildID=2750317 Regards, Benjamin
I've had some time to come back to this now there's a lot of to-and-fro with more data. Looking at https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=1088522;filename=Debian6.15boot.log;msg=63 that contains three boots: 1. 2 monitors 2. 3 monitors 3. 2 monitors I think the cause is pretty obvious. Nouveau needs to ask the GPU how many outputs it has and query each for monitor capabilities. That is done over i2c. It looks to me as if an incorrect i2c auxiliary channel is being used. I further suspect commit 752a281032b2 may give us a lead to what is going on here. Note its commit message specifically calls out crashing GPUs that have off-chip Display Port. I scanned the bug messages but didn't find any detail about how the monitors are connected (also, some adapters use DP internally but expose the output via HDMI). So let's also get the exact make/model of the GPU adapter.
Hi Tj, This is the GPU >> https://www.techpowerup.com/gpu-specs/t400.c3808 The 3 monitors are : Dell U2722DE connected to DP 1 Dell U2722D connected to DP 2 and 3 All monitors are connected with mini display port to normal display port cables. Both monitors models have DP pass-through, meaning each monitor also has a display port output. (This only works if the GPU supports that, I do not know if my GPU (the Nvidia T400) supports DP pass-through. Best Regards, Benjamin
The kernel logs show the Device Control Block [0] reported as: DRM: DCB version 4.1 DRM: DCB outp 00: 01800f46 04600020 DRM: DCB outp 01: 01000f42 00020020 DRM: DCB outp 02: 01811f36 04600010 DRM: DCB outp 03: 01011f32 00020010 DRM: DCB outp 04: 02822f66 04600020 DRM: DCB outp 05: 02022f62 00020020 DRM: DCB conn 00: 00002046 DRM: DCB conn 01: 00001146 DRM: DCB conn 02: 00020246 sec2: unhandled intr 00000010 DRM: MM: using COPY for buffer copies The table is printed in drivers/gpu/drm/nouveau/nouveau_bios.c::parse_db_entry() using NV_INFO(drm, "DCB outp %02d: %08x %08x\n", idx, conn, conf); Each entry can be decoded using [1]. `conn` above is the Display Path Information that parse_dcb20_entry() decodes into 'entry'. I suspect the entries for the 3rd output connector are wrong. I don't know how to determine that though. drivers/gpu/drm/nouveau/nouveau_bios.c::apply_dcb_encoder_quirks() is where fix-ups are done and contains quirks for several devices so we have something to work from. Using the attached shell script nvidia_dcb_decode.bash I've decoded the above table using: $ ./nvidia_dcb_decode.bash <<< "DRM: DCB outp 00: 01800f46 04600020 DRM: DCB outp 01: 01000f42 00020020 DRM: DCB outp 02: 01811f36 04600010 DRM: DCB outp 03: 01011f32 00020010 DRM: DCB outp 04: 02822f66 04600020 DRM: DCB outp 05: 02022f62 00020020 DRM: DCB conn 00: 00002046 DRM: DCB conn 01: 00001146 DRM: DCB conn 02: 00020246" Note that "EDID Port" is an index into a Communications Control Block [2] and that is where the information about I2C is stored. As far as I can tell so far we don't have that exposed via the kernel log so would have to add some debug code to a custom kernel build to obtain it. DRM: DCB outp 00: 01800f46 04600020 Type: DisplayPort EDID Port: 0x4 Heads: 0: 1 1: 1 2: 1 3: 1 Connector: 0 Bus: 0 Location: On Chip (internal) TV encoder, internal TMDS encoder BDR: This device is allowed to boot if detected BBDR: This device is not allowed to boot, even if detected Output: 0: 1 1: 0 2: 0 3: 0 Virtual: 0 Reserved: 0x0 DRM: DCB outp 01: 01000f42 00020020 Type: TMDS EDID Port: 0x4 Heads: 0: 1 1: 1 2: 1 3: 1 Connector: 0 Bus: 0 Location: On Chip (internal) TV encoder, internal TMDS encoder BDR: This device is allowed to boot if detected BBDR: This device is allowed to boot if no devices are detected Output: 0: 1 1: 0 2: 0 3: 0 Virtual: 0 Reserved: 0x0 DRM: DCB outp 02: 01811f36 04600010 Type: DisplayPort EDID Port: 0x3 Heads: 0: 1 1: 1 2: 1 3: 1 Connector: 1 Bus: 1 Location: On Chip (internal) TV encoder, internal TMDS encoder BDR: This device is allowed to boot if detected BBDR: This device is not allowed to boot, even if detected Output: 0: 1 1: 0 2: 0 3: 0 Virtual: 0 Reserved: 0x0 DRM: DCB outp 03: 01011f32 00020010 Type: TMDS EDID Port: 0x3 Heads: 0: 1 1: 1 2: 1 3: 1 Connector: 1 Bus: 1 Location: On Chip (internal) TV encoder, internal TMDS encoder BDR: This device is allowed to boot if detected BBDR: This device is allowed to boot if no devices are detected Output: 0: 1 1: 0 2: 0 3: 0 Virtual: 0 Reserved: 0x0 DRM: DCB outp 04: 02822f66 04600020 Type: DisplayPort EDID Port: 0x6 Heads: 0: 1 1: 1 2: 1 3: 1 Connector: 2 Bus: 2 Location: On Chip (internal) TV encoder, internal TMDS encoder BDR: This device is allowed to boot if detected BBDR: This device is not allowed to boot, even if detected Output: 0: 0 1: 1 2: 0 3: 0 Virtual: 0 Reserved: 0x0 DRM: DCB outp 05: 02022f62 00020020 Type: TMDS EDID Port: 0x6 Heads: 0: 1 1: 1 2: 1 3: 1 Connector: 2 Bus: 2 Location: On Chip (internal) TV encoder, internal TMDS encoder BDR: This device is allowed to boot if detected BBDR: This device is allowed to boot if no devices are detected Output: 0: 0 1: 1 2: 0 3: 0 Virtual: 0 Reserved: 0x0 DRM: DCB conn 00: 00002046 (ignored) DRM: DCB conn 01: 00001146 (ignored) DRM: DCB conn 02: 00020246 (ignored) [0] https://http.download.nvidia.com/open-gpu-doc/DCB/1/DCB-4.0-Specification.html [1] https://http.download.nvidia.com/open-gpu-doc/DCB/1/DCB-4.0-Specification.html#_dcb_device_entries [2] https://http.download.nvidia.com/open-gpu-doc/DCB/1/DCB-4.0-Specification.html#_communications_control_block
Hi, Did you need more information from me or were you working on a custom kernel patch? Regards Benjamin.
Hello, I have the impression we're in need of someone with a deeper understanding of the nouveau driver. @Tj, do you agree? In that case we should bring this problem to upstream's attention. Best regards Uwe
Hi, Any more info on this bug? Regards, Benjamin
I'll do some more investigation and consider a patched kernel. Are you able to build a kernel locally if I provide a patch or would you prefer a binary kernel .deb package? @Uwe: do we have a mechanism to offer 'trusted' custom builds via Debian infrastructure?
I can definitely try to build a kernel with a patch, if step by step instruction are provided or a link to an online tutorial . A .deb package may be preferred. Would this patch get pushed upstream for testing and then released in a future kernel update? Regards, Benjamin.
Today I've spent a few hours minutely examining the differences in the logs you provided for v6.15 for Fedora and Debian in message #63, looking for differences in the kernel configs for each, and comparing the source-code between mainline, Fedora and Debian for clues. Since there were no differences in nouveau across all three I worked to understand why the initialisation of the GPU results in different messages between the two distros. In the v6.15 logs Fedora's nouveau does NOT report what Debian does "drm: BIT table 'A' not found" and "drm: BIT table 'A' not found" nor does it report the earlier "pmu: firmware unavailable". I strongly suspect this is because Fedora config sets CONFIG_DRM_NOUVEAU_GSP_DEFAULT=y (and we don't). This tells the driver to use the GPU's system processor to do all the initialisation after loading the requisite firmware. As we see in message #80 Fedora ship "nvidia/tu117/gsp/gsp-535.113.01.bin" whereas in Debian we do not, or if we do, I can't find it ( I can see some gsp*.bin up to tu116, but not tu117 ). I'm going to consult with the other kernel team members on the best way to have you test this and if proved correct what we need to do in our kernel and firmware to fix this, and for which releases. For your testing I think it'll be sufficient to build a kernel with CONFIG_DRM_NOUVEAU_GSP_DEFAULT=y since it should pick up the firmware file provided by Fedora (if you do/have copy/copied it from the Fedora install to Debian).
I was attempting to figure out how the Fedora nvidia-gpu-firmware package creates what seem to be sym-links from the various model directories to the single instance of the GSP firmware version file. In the Fedora install can you report what this reports (adjust the path prefix if that file-system is mounted somewhere else) ? find /lib/firmware/nvidia/tu117 -ls I'm expecting to see symbolic links for the gsp.*.bin files to another directory. With this information I can give you instructions on duplicating the layout in the Debian install, but even without it I think this is what you'll need to do (in the running Debian instance): # this may already be installed sudo apt install firmware-nvidia-graphics # this may already exist sudo mkdir --parents /usr/lib/firmware/nvidia/tu117/gsp # this is the vital symbolic link sudo ln -s ../../tu116/gsp/gsp-535.113.01.bin /usr/lib/firmware/nvidia/tu117/gsp/ The kernel build is ready. I've used v6.15.6 with the config patch since it will be easy to compare its log against the Debian v6.15.6 log you've already shared and we can see if it matches the Fedora log of their v6.15.4. Here's confirmation the config option is in this kernel: $ dpkg-deb --fsys-tarfile ../../builds/linux-image-6.15.6_6.15.6-318_amd64.deb | tar -x -f - --to-stdout | grep DRM_NOUVEAU_GSP_DEFAULT CONFIG_DRM_NOUVEAU_GSP_DEFAULT=y The kernel package is in my Proton Drive at: https://drive.proton.me/urls/MN32XF7V30#2v1RKvNvLLUA The sha256.sum file is there also (ffd663ea8fbb33342857279f497f6513fefd5e5127f858e92acf839e054ac081). Download both files to the same directory then do: sha256sum -c sha256.sum That should report: linux-image-6.15.6_6.15.6-318_amd64.deb: OK Now install the kernel with: sudo apt install ./linux-image-6.15.6_6.15.6-318_amd64.deb Once/if we've sorted out the GSP firmware file and required sym-links you can go ahead and boot into this kernel to test. Please report back and share the boot log whether it works or not; e.g: sudo journalctl --dmesg > /tmp/dmesg-v6.15.6+debian_tj.log Note: as well as the Nvidia config change this kernel includes a handful of my own patches that I apply to all my builds. One of them reports all firmware files that are loaded and hopefully - if nouveau is using the firmware loader library - it'll tell us for sure which firmware files are being loaded. The patch stack on top of v6.15.6 mainline in this kernel is: $ git l -n 10 fd77d0df971df 2025-08-07 13:47:07 +0000 N Tj config: Debian v6.15.6 enable DRM_NOUVEAU_GSP_DEFAULT 18fc0cd28e807 2025-08-07 13:45:53 +0000 N Tj config: import Debian v6.15.6 config ca23184e137d6 2025-08-07 13:42:42 +0000 N Tj defconfig: add debian+tj v6.15 30e1edbe28128 2025-08-07 13:42:42 +0000 N Tj ath: add module_param country_default for regulatory domain control 852c7433a5467 2025-08-07 13:42:42 +0000 N Tj cfg80211: suppress regdom warning when phy not ready 39c61beb7d2ec 2025-08-07 13:42:42 +0000 N Tj debian: call linux-update-symlinks from postinst (v6.14+) 9ea18f3b0a5d4 2025-08-07 13:42:42 +0000 N Tj debian: no -dbg package using KDEB_NO_DBG=1 55762f40f581c 2025-08-07 13:42:42 +0000 N Tj firmware: report each loaded firmware file 1562d94823254 2025-07-10 16:08:55 +0200 N Greg Kroah-Hartman Linux 6.15.6 62901034ddc8a 2025-07-10 16:08:55 +0200 N Borislav Petkov (AMD) x86/process: Move the buffer clearing before MONITOR
HI, Please see attached file. I got an error on this one saying the file already existed. Connected the 3 screens and rebooted and it worked!!! YEA!!! And as soon as the driver loaded the GPU fan speed slowed down too, just like in Fedora. See attached log. So is this something that can be pushed in an update to the kernel in Trixie? I am not planning to install Trixie right away as my daily runner. So if this could be available in a few months I might just wait till this patch has been applied. Thank you both TJ and Uwe for your time and effort in this. Regards, Benjamin
hello, so the TL;DR; of this bug is that we just need to enable DRM_NOUVEAU_GSP_DEFAULT + maybe take care that the matching firmware is packaged, right? Maybe the same effect can be achieved by using nouveau.config=NvGspRm=1 on the kernel command-line. Best regards Uwe
Yes, although we should document this and stipulate this will only work for kernel v6.6+ I think we should enable GSP by default as Fedora did [0] for v6.14+ [1]. For firmware-nonfree from what I can see linux-firmware's copy-firmware.sh via WHENCE already installs the correct links for TU117: creating link nvidia/tu117/gsp -> ../tu116/gsp ... creating link nvidia/tu116/gsp/gsp-535.113.01.bin -> ../../tu102/gsp/gsp-535.113.01.bin [0] https://gitlab.com/cki-project/kernel-ark/-/commit/0995cb5643bf77ec1d5ada23e2860d836b9e19b9 [1] https://kojipkgs.fedoraproject.org//packages/kernel/6.14.0/63.fc42/x86_64/kernel-core-6.14.0-63.fc42.x86_64.rpm
Benjamin, could you do a test for us (with my custom kernel build) ?
We want to determine what happens when this option is enabled but the firmware cannot be found. I tried to determine it from the source-code but there are so many levels of indirection it will be easier to simply test.
The firmware for TU117 GSP is sym-linked to the TU116, that is in turn sym-linked to TU102 files. So, to *temporarily, for this test only* prevent that firmware being found do:
$ sudo mv /usr/lib/firmware/nvidia/tu102/gsp/gsp-535.113.01.bin{,.disabled}
Then check the tu117 sym-link is now broken:
$ realpath -e /usr/lib/firmware/nvidia/tu117/gsp/gsp-535.113.01.bin
realpath: /usr/lib/firmware/nvidia/tu117/gsp/gsp-535.113.01.bin: No such file or directory
Reboot and share the kernel log. I'm hoping it falls back to the VBIOSInit routine and you see the same messages we saw originally, with those "table '*' not found" messages.
To reinstate the firmware file do:
$ sudo mv /usr/lib/firmware/nvidia/tu102/gsp/gsp-535.113.01.bin{.disabled,}
$ realpath -e /usr/lib/firmware/nvidia/tu117/gsp/gsp-535.113.01.bin
/usr/lib/firmware/nvidia/tu102/gsp/gsp-535.113.01.bin
TJ, Please see attached. From what I could tell it still loaded the firmware. The 3 monitors worked correctly. I did a simular test with my Fedora install, see message 112. (I renamed the nvidia folder .) Regards Benjamin
As you say, the firmware was loaded (thank goodness for my 'firmware loaded' patch): nouveau 0000:01:00.0: Firmware loaded: nvidia/tu117/gsp/gsp-535.113.01.bin I, of course, forgot that the driver and firmware are in the initial ramdisk! So, would you mind repeating the experiment but after confirming the sym-link is broken, as a last step before booting into this kernel doing: $ sudo update-initramfs -u -v -k 6.15.6 Capture and share the kernel log as before and report whether the 3rd output (monitor) was activated. And of course, to undo this deliberate break, after reinstating the firmware file regenerating the initrd again: $ sudo update-initramfs -u -v -k 6.15.6
Please see attached, this time it acted the same as before we applied the patch. 3 monitors > GPU locked up 2 monitors > Was able to boot, but subpar performance. Regards Benjamin
Thank-you. That confirms that with just the GSP firmware file unavailable the driver falls back to its own initialisation functions and we see the same messages as originally about table A, etc. The fix has been added to v6.16 in experimental and backported to v6.12.40 that will be in trixie-security shortly.
I would be interested if the unfixed kernel can be repaired when you have nouveau.config=NvGspRm=1 in the kernel command line. If this is confirmed I'd care to add this info to the help text of CONFIG_DRM_NOUVEAU_GSP_DEFAULT. Best regards Uwe
I did a fresh install of Trixie on my test drive, and this morning installed security update 6.12.41 and rebooted, everything is working good with the 3 monitors. Thanks again. Benjamin.
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 1088522@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso <carnil@debian.org> (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 ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Sat, 16 Aug 2025 09:09:54 +0200 Source: linux Architecture: source Version: 6.16.1-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org> Changed-By: Salvatore Bonaccorso <carnil@debian.org> Closes: 1088522 1110511 1110679 1111017 Changes: linux (6.16.1-1~exp1) experimental; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.16.1 . [ Salvatore Bonaccorso ] * net: Enable OVPN (OpenVPN data channel offload) as module (Closes: #1110511) * d/c/defines.toml: Bump abi_suffix to +deb14 for unstable releases * d/c/defines.toml: Define the Debian forky release * d/c/defines.toml: Define the Debian trixie-backports release * btrfs: fix log tree replay failure due to file with 0 links and extents (Closes: #1110679) * netlink: avoid infinite retry looping in netlink_unicast() (Closes: #1111017) * [amd64] udeb: kernel-image: Include SPI drivers . [ Tj ] * drivers/gpu/drm/nouveau: Enable DRM_NOUVEAU_GSP_DEFAULT (Closes: #1088522) . [ Uwe Kleine-König ] * [armhf] Add phy-gmii-sel module to nic-shared-modules udeb for ti/omap/am335x based machines (e.g. BeagleBone black). . [ Ben Hutchings ] * linux-misc-tools: Fix FTBFS on sparc64: - tools/bootconfig: Cleanup bootconfig footer size calculations - bootconfig: Fix unaligned access when building footer . [ Bastian Blank ] * [amd64, arm64] Enable MANA_INFINIBAND. Checksums-Sha1: 3fe755e9a0724ff80d9834b6f62429a7e88882d0 192581 linux_6.16.1-1~exp1.dsc 6c3b7dee664b18f90058ebf957d4a9a7b718767b 155630760 linux_6.16.1.orig.tar.xz 733d9cfbc4e66afabe22b9dbb700c43213335d8a 1534552 linux_6.16.1-1~exp1.debian.tar.xz 6d6732311b5d08ff6abd6491b88bb9bc2f371d16 6714 linux_6.16.1-1~exp1_source.buildinfo Checksums-Sha256: fef311d6f33eb642bf6a5a55d77cf8118b611e9e6a26bd4555fecccaf8e9130e 192581 linux_6.16.1-1~exp1.dsc 309034f1f996252052e9d5dba51f930fb80c4449f50004c85aed925a38ed6dc7 155630760 linux_6.16.1.orig.tar.xz 779776d60e2163a64de9bd4c89500caf42be1ed2b65b5ad3004bfcda084cecc5 1534552 linux_6.16.1-1~exp1.debian.tar.xz 1ae28353728ad8c23772a9b4c12c6a75165afb0448bc519b3e75f8e9a775096f 6714 linux_6.16.1-1~exp1_source.buildinfo Files: b5610596c534bf9b3134df62a32489bc 192581 kernel optional linux_6.16.1-1~exp1.dsc f6f3df7dbf804b4473133ea6335eb80b 155630760 kernel optional linux_6.16.1.orig.tar.xz 6b654b5cfa777300caec3a71842bfbc2 1534552 kernel optional linux_6.16.1-1~exp1.debian.tar.xz 2a5883101ee6beebde2834b22e0f24ea 6714 kernel optional linux_6.16.1-1~exp1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmigL2VfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EG7gP/0+7BlQPb7/FkTQn4ud7BuwML/SYkxf/ g7Nr6oBpb8YVcMIBgtRTpPVMG9Wrq0trj3sNbVa4s7OFsTnSR85g5BjbO4cOlWlM RwSYxGK1gpqVc18WWTlaOlnk+MLsA+NlLyL0y1bKtXtvJYxFZYnx6Vct56YjLcul /bnQsewh4EWb7w+v2cmI9I53ldCKkx2sNH7Q5UGt58WqKCQOWtjPEKG997w99PO9 w2v6SBltgLFHGlFAFtitXSnXrT2TNo7sxe1dket8toax5sdfkBVK6S0Tvao8GJVj crOozcTaYLI6hUlKaa1sPKJyH3dPiFOCZO1lKJETWDls8Z67pcFOi5VCaWBdVF/U 3o7X7cHvjtkrN9kvc6zOwN238DDeO5aJ+uQwnEW4kjXqGBJ997uOIc7LjahlaZUY A+joB4cUlRoG6B3WPCmhZIfw69VVPLbSMG0ZP347JP6HaaHnrE+SmNeyyudkCy7t Zzj0VoTe0uEKnvGoFpXHD6jY57LpUdVZHf9C/bOjnP3+RI3/vb5qPR4mR6Uhs0Gq Yt03QFZY7P59gKV9FgxQx8DvtyRJxnwvxgx+tstfXHs7FMkwcysQu80v4NMQkeiO oibB2A8JaKcdeAHob73eik9FN8H4d4XSCngi5OYiYxfSJ3sQYPOR6D6OFuNYAVsW F18Id+anZyS0 =yH23 -----END PGP SIGNATURE-----
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 1088522@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso <carnil@debian.org> (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 ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Tue, 12 Aug 2025 05:28:04 +0200 Source: linux Architecture: source Version: 6.12.41-1 Distribution: trixie-security Urgency: high Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org> Changed-By: Salvatore Bonaccorso <carnil@debian.org> Closes: 1088522 1108430 1109344 1109676 1109734 1109799 Changes: linux (6.12.41-1) trixie-security; urgency=high . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.39 - eventpoll: don't decrement ep refcount while still holding the ep mutex (CVE-2025-38349) - drm/amdgpu/discovery: use specific ip_discovery.bin for legacy asics - drm/amdgpu/ip_discovery: add missing ip_discovery fw - [s390x] crypto: s390/sha - Fix uninitialized variable in SHA-1 and SHA-2 - drm/amdgpu: Replace Mutex with Spinlock for RLCG register access to avoid Priority Inversion in SRIOV (CVE-2025-38104) - [amd64] ASoC: Intel: SND_SOC_INTEL_SOF_BOARD_HELPERS select SND_SOC_ACPI_INTEL_MATCH - [amd64] ASoC: Intel: soc-acpi: arl: Correct naming of a cs35l56 address struct - [amd64] ASoC: Intel: soc-acpi: arl: Add match entries for new cs42l43 laptops - [amd64] ASoC: soc-acpi: add get_function_tplg_files ops - [amd64] ASoC: Intel: add sof_sdw_get_tplg_files ops - [amd64] ASoC: Intel: soc-acpi-intel-arl-match: set get_function_tplg_files ops - [amd64] ASoC: Intel: soc-acpi: arl: Correct order of cs42l43 matches - perf/core: Fix the WARN_ON_ONCE is out of lock protected region - irqchip/irq-msi-lib: Select CONFIG_GENERIC_MSI_IRQ - sched/core: Fix migrate_swap() vs. hotplug - perf: Revert to requiring CAP_SYS_ADMIN for uprobes - ASoC: cs35l56: probe() should fail if the device ID is not recognized - Bluetooth: hci_sync: Fix not disabling advertising instance - Bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected - pinctrl: amd: Clear GPIO debounce for suspend - fix proc_sys_compare() handling of in-lookup dentries - sched/deadline: Fix dl_server runtime calculation formula - bnxt_en: eliminate the compile warning in bnxt_request_irq due to CONFIG_RFS_ACCEL - [arm64] poe: Handle spurious Overlay faults - [arm64] net: phy: qcom: move the WoL function to shared library - [arm64] net: phy: qcom: qca808x: Fix WoL issue by utilizing at8031_set_wol() - netlink: Fix wraparounds of sk->sk_rmem_alloc. - vsock: fix `vsock_proto` declaration - tipc: Fix use-after-free in tipc_conn_close(). - tcp: Correct signedness in skb remaining space calculation - vsock: Fix transport_{g2h,h2g} TOCTOU - vsock: Fix transport_* TOCTOU - vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local` - net: stmmac: Fix interrupt handling for level-triggered mode in DWC_XGMAC2 - net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap - net: phy: smsc: Force predictable MDI-X state on LAN87xx - net: phy: smsc: Fix link failure in forced mode with Auto-MDIX - atm: clip: Fix potential null-ptr-deref in to_atmarpd(). - atm: clip: Fix memory leak of struct clip_vcc. - atm: clip: Fix infinite recursive call of clip_push(). - atm: clip: Fix NULL pointer dereference in vcc_sendmsg() - [arm64] net: ethernet: ti: am65-cpsw-nuss: Fix skb size by accounting for skb_shared_info - net/sched: Abort __tc_modify_qdisc if parent class does not exist - rxrpc: Fix bug due to prealloc collision - rxrpc: Fix oops due to non-existence of prealloc backlog struct - ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() - [amd64] x86/mce/amd: Add default names for MCA banks and blocks - [amd64] x86/mce/amd: Fix threshold limit reset - [amd64] x86/mce: Don't remove sysfs if thresholding sysfs init fails - [amd64] x86/mce: Ensure user polling settings are honored when restarting timer - [amd64] x86/mce: Make sure CMCI banks are cleared during shutdown on Intel - [amd64] KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table. - [amd64] KVM: SVM: Add missing member in SNP_LAUNCH_START command structure - [amd64] KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight - KVM: Allow CPU to reschedule while setting per-page memory attributes - ASoC: fsl_sai: Force a software reset when starting in consumer mode - gre: Fix IPv6 multicast route creation. (Closes: #1108430) - md/md-bitmap: fix GPF in bitmap_get_stats() (Closes: #1109734) - [arm64] pinctrl: qcom: msm: mark certain pins as invalid for interrupts - pwm: Fix invalid state detection - pwm: mediatek: Ensure to disable clocks in error path - wifi: prevent A-MSDU attacks in mesh networks (CVE-2025-27558) - wifi: mwifiex: discard erroneous disassoc frames on STA interface - wifi: mt76: mt7921: prevent decap offload config before STA initialization - wifi: mt76: mt7925: prevent NULL pointer dereference in mt7925_sta_set_decap_offload() - wifi: mt76: mt7925: fix the wrong config for tx interrupt - wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan - drm/imagination: Fix kernel crash when hard resetting the GPU - drm/amdkfd: Don't call mmput from MMU notifier callback - drm/gem: Acquire references on GEM handles for framebuffers - drm/sched: Increment job count before swapping tail spsc queue - drm/ttm: fix error handling in ttm_buffer_object_transfer - drm/gem: Fix race in drm_gem_handle_create_tail() - drm/xe/bmg: fix compressed VRAM handling - Revert "drm/xe/xe2: Enable Indirect Ring State support for Xe2" - usb: gadget: u_serial: Fix race condition in TTY wakeup - Revert "usb: gadget: u_serial: Add null pointer check in gs_start_io" - drm/framebuffer: Acquire internal references on GEM handles - drm/xe: Allocate PF queue size on pow2 boundary - Revert "ACPI: battery: negate current when discharging" (Closes: #1109344) - Revert "PCI/ACPI: Fix allocated memory release on error in pci_acpi_scan_root()" - kallsyms: fix build without execinfo - maple_tree: fix mt_destroy_walk() on root leaf node - mm: fix the inaccurate memory statistics issue for users - mm/vmalloc: leave lazy MMU mode on PTE mapping error - lib/alloc_tag: do not acquire non-existent lock in alloc_tag_top_users() - [amd64] x86/rdrand: Disable RDSEED on AMD Cyan Skillfish - [amd64] x86/mm: Disable hugetlb page table sharing on 32-bit - [arm64] clk: scmi: Handle case where child clocks are initialized before their parents - smb: server: make use of rdma_destroy_qp() - ksmbd: fix a mount write count leak in ksmbd_vfs_kern_path_locked() - erofs: fix to add missing tracepoint in erofs_read_folio() - erofs: address D-cache aliasing - [amd64] ASoC: Intel: sof-function-topology-lib: Print out the unsupported dmic count - netlink: Fix rmem check in netlink_broadcast_deliver(). - netlink: make sure we allow at least one dump skb - netfs: Fix ref leak on inserted extra subreq in write retry - wifi: cfg80211: fix S1G beacon head validation in nl80211 - wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() - drm/tegra: nvdec: Fix dma_alloc_coherent error check - md/raid1: Fix stack memory use after return in raid1_reshape - raid10: cleanup memleak at raid10_make_request - wifi: mac80211: correctly identify S1G short beacon - wifi: mac80211: fix non-transmitted BSSID profile search - wifi: rt2x00: fix remove callback type mismatch - drm/nouveau/gsp: fix potential leak of memory used during acpi init - wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() - nbd: fix uaf in nbd_genl_connect() error path - drm/xe/pf: Clear all LMTT pages on alloc - erofs: free pclusters if no cached folio is attached - erofs: get rid of `z_erofs_next_pcluster_t` - erofs: tidy up zdata.c - erofs: refine readahead tracepoint - erofs: fix to add missing tracepoint in erofs_readahead() - netfilter: flowtable: account for Ethernet header in nf_flow_pppoe_proto() - net: appletalk: Fix device refcount leak in atrtr_create() - ibmvnic: Fix hardcoded NUM_RX_STATS/NUM_TX_STATS with dynamic sizeof - net: phy: microchip: Use genphy_soft_reset() to purge stale LPA bits - net: phy: microchip: limit 100M workaround to link-down events on LAN88xx - drm/xe/pm: Correct comment of xe_pm_set_vram_threshold() - can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level - net/mlx5e: Fix race between DIM disable and net_dim() - net/mlx5e: Add new prio for promiscuous mode - net: ll_temac: Fix missing tx_pending check in ethtools_set_ringparam() - bnxt_en: Fix DCB ETS validation - bnxt_en: Set DMA unmap len correctly for XDP_REDIRECT - ublk: sanity check add_dev input for underflow - atm: idt77252: Add missing `dma_map_error()` - ASoC: SOF: Intel: hda: Use devm_kstrdup() to avoid memleak. - [amd64] ALSA: hda/realtek: Add mic-mute LED setup for ASUS UM5606 - io_uring: make fallocate be hashed work - [amd64] ASoC: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic - ALSA: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 - ALSA: hda/realtek: Add quirks for some Clevo laptops - net: usb: qmi_wwan: add SIMCom 8230C composition - driver: bluetooth: hci_qca:fix unable to load the BT driver - HID: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 - net: mana: Record doorbell physical address in PF mode - btrfs: fix assertion when building free space tree - vt: add missing notification when switching back to text mode - bpf: Adjust free target to avoid global starvation of LRU map - [riscv64] vdso: Exclude .rodata from the PT_DYNAMIC segment - HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY - HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras - HID: nintendo: avoid bluetooth suspend/resume stalls - erofs: fix rare pcluster memory leak after unmounting - net: wangxun: revert the adjustment of the IRQ vector sequence - kasan: remove kasan_find_vm_area() to prevent possible deadlock - ksmbd: fix potential use-after-free in oplock/lease break ack - [arm64] Filter out SME hwcaps when FEAT_SME isn't implemented - crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (CVE-2025-37984) - rseq: Fix segfault on registration when rseq_cs is non-zero (CVE-2025-38067) - [amd64] KVM: SVM: Set synthesized TSA CPUID flags https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.40 - USB: serial: option: add Telit Cinterion FE910C04 (ECM) composition - USB: serial: option: add Foxconn T99W640 - USB: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI - usb: musb: fix gadget state on disconnect - [arm*] usb: dwc2: gadget: Fix enter to hibernation for UTMI+ PHY - usb: gadget: configfs: Fix OOB read on empty string write - [armhf] i2c: stm32: fix the device used for the DMA map - [armhf] i2c: stm32f7: unmap DMA mapped buffer - [amd64] thunderbolt: Fix wake on connect at runtime - [amd64] thunderbolt: Fix bit masking in tb_dp_port_set_hops() - Revert "staging: vchiq_arm: Create keep-alive thread during probe" - nvmem: imx-ocotp: fix MAC address byte length - nvmem: layouts: u-boot-env: remove crc32 endianness conversion - Input: xpad - set correct controller type for Acer NGR200 - pch_uart: Fix dma_sync_sg_for_device() nents value - spi: Add check for 8-bit transfer with 8 IO mode support - dm-bufio: fix sched in atomic context - HID: core: ensure the allocated report buffer can contain the reserved report ID - HID: core: ensure __hid_request reserves the report ID as the first byte - HID: core: do not bypass hid_hw_raw_request - tracing/probes: Avoid using params uninitialized in parse_btf_arg() - tracing: Add down_write(trace_event_sem) when adding trace event - tracing/osnoise: Fix crash in timerlat_dump_stack() - drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume - drm/amdgpu: Increase reset counter only on success - drm/amd/display: Disable CRTC degamma LUT for DCN401 - drm/amd/display: Free memory allocation - ALSA: hda/realtek - Fix mute LED for HP Victus 16-r0xxx - ALSA: hda/realtek: Add quirk for ASUS ROG Strix G712LWS - io_uring/poll: fix POLLERR handling - mptcp: make fallback action and fallback decision atomic - mptcp: plug races between subflow fail and subflow creation - mptcp: reset fallback status gracefully at disconnect() time - phonet/pep: Move call to pn_skb_get_dst_sockaddr() earlier in pep_sock_accept() - net/mlx5: Update the list of the PCI supported devices - [arm64] dts: imx8mp-venice-gw74xx: fix TPM SPI frequency - [arm64] dts: add big-endian property back into watchdog node - [arm64] dts: freescale: imx8mm-verdin: Keep LDO5 always on - [arm64] dts: imx8mp-venice-gw71xx: fix TPM SPI frequency - [arm64] dts: imx8mp-venice-gw72xx: fix TPM SPI frequency - [arm64] dts: imx8mp-venice-gw73xx: fix TPM SPI frequency - [arm64] dts: rockchip: use cs-gpios for spi1 on ringneck - af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() - af_packet: fix soft lockup issue caused by tpacket_snd() - Bluetooth: btintel: Check if controller is ISO capable on btintel_classify_pkt_type - cpuidle: psci: Fix cpuhotplug routine with PREEMPT_RT=y - isofs: Verify inode mode when loading from disk - memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() - [arm*] mmc: bcm2835: Fix dma_unmap_sg() nents value - mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models - [arm64] mmc: sdhci_am654: Workaround for Errata i2312 - [amd64] net: stmmac: intel: populate entire system_counterval_t in get_time_fn() callback - pmdomain: governor: Consider CPU latency tolerance from pm_domain_cpu_gov - [s390x] bpf: Fix bpf_arch_text_poke() with new_addr == NULL again - smb: client: fix use-after-free in crypt_message when using async crypto - [armhf] soc: aspeed: lpc-snoop: Cleanup resources in stack-order - [armhf] soc: aspeed: lpc-snoop: Don't disable channels that aren't enabled - iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush - iio: adc: axp20x_adc: Add missing sentinel to AXP717 ADC channel maps - iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] - iio: adc: max1363: Reorder mode_list[] entries - iio: adc: stm32-adc: Fix race in installing chained IRQ handler - iio: backend: fix out-of-bound write - iio: common: st_sensors: Fix use of uninitialize device structs - [arm64] dts: rockchip: Add cd-gpios for sdcard detect on Cool Pi CM5 - [arm64] dts: rockchip: Add cd-gpios for sdcard detect on Cool Pi 4B - [arm64] dts: imx95: Correct the DMA interrupter number of pcie0_ep - bpf: Reject %p% format string in bprintf-like helpers - cachefiles: Fix the incorrect return value in __cachefiles_write() - block: fix kobject leak in blk_unregister_queue - net/sched: sch_qfq: Fix race condition on qfq_aggregate - rpl: Fix use-after-free in rpl_do_srh_inline(). - smb: client: fix use-after-free in cifs_oplock_break - fix a leak in fcntl_dirnotify() - nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() - nvme: fix endianness of command word prints in nvme_log_err_passthru() - smc: Fix various oops due to inet_sock type confusion. - net: phy: Don't register LEDs for genphy - nvme: fix misaccounting of nvme-mpath inflight I/O - nvmet-tcp: fix callback lock for TLS handshake - wifi: cfg80211: remove scan request n_channels counted_by - [amd64] hwmon: (corsair-cpro) Validate the size of the received input buffer - ice: add NULL check in eswitch lag check - ice: check correct pointer in fwlog debugfs - usb: net: sierra: check for no status endpoint - loop: use kiocb helpers to fix lockdep warning - [riscv64] Enable interrupt during exception handling - [riscv64] traps_misaligned: properly sign extend value in misaligned load handler - Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() - Bluetooth: hci_sync: fix connectable extended advertising when using static random address - Bluetooth: SMP: If an unallowed command is received consider it a failure - Bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout - Bluetooth: hci_core: add missing braces when using macro parameters - Bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID - net/mlx5: Correctly set gso_size when LRO is used - ipv6: mcast: Delay put pmc->idev in mld_del_delrec() - net: fix segmentation after TCP/UDP fraglist GRO - netfilter: nf_conntrack: fix crash due to removal of uninitialised entry - drm/xe/pf: Sanitize VF scratch registers on FLR - drm/xe/pf: Move VFs reprovisioning to worker - drm/xe/pf: Prepare to stop SR-IOV support prior GT reset - Bluetooth: L2CAP: Fix attempting to adjust outgoing MTU - [amd64,arm64] hv_netvsc: Set VF priv_flags to IFF_NO_ADDRCONF before open to prevent IPv6 addrconf - virtio-net: fix recursived rtnl_lock() during probe() - tls: always refresh the queue when reading sock - net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime - net: bridge: Do not offload IGMP/MLD messages - net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree - rxrpc: Fix recv-recv race of completed call - rxrpc: Fix transmission of an abort in response to an abort - Revert "cgroup_freezer: cgroup_freezing: Check if not frozen" - drm/mediatek: Add wait_event_timeout when disabling plane - drm/mediatek: only announce AFBC if really supported - libbpf: Fix handling of BPF arena relocations - efivarfs: Fix memory leak of efivarfs_fs_info in fs_context error paths - sched: Change nr_uninterruptible type to unsigned long - clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns - btrfs: fix block group refcount race in btrfs_create_pending_block_groups() (CVE-2025-22115) - usb: hub: fix detection of high tier USB3 devices behind suspended hubs - usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm - usb: hub: Fix flushing of delayed work used for post resume purposes - usb: hub: Don't try to recover devices lost during warm reset. - [arm64] usb: dwc3: qcom: Don't leave BCR asserted - [arm64,armhf] i2c: omap: Add support for setting mux - [arm64,armhf] i2c: omap: Fix an error handling path in omap_i2c_probe() - [arm64,armhf] i2c: omap: Handle omap_i2c_init() errors in omap_i2c_probe() - [arm64,armhf] i2c: omap: fix deprecated of_property_read_bool() use - sched,freezer: Remove unnecessary warning in __thaw_task - drm/xe/mocs: Initialize MOCS index early - drm/xe: Move page fault init after topology init - smb: client: let smbd_post_send_iter() respect the peers max_send_size and transmit all data - [amd64] iommu/vt-d: Fix misplaced domain_attached assignment (Closes: #1109676) - [amd64] KVM: x86/xen: Fix cleanup logic in emulation of Xen schedop poll hypercalls https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.41 - [amd64] x86/traps: Initialize DR7 by writing its architectural reset value - Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (CVE-2025-38335) - virtio_net: Enforce minimum TX ring size for reliability - virtio_ring: Fix error reporting in virtqueue_resize - regulator: core: fix NULL dereference on unbind due to stale coupling data - [amd64] platform/x86: asus-nb-wmi: add DMI quirk for ASUS Zenbook Duo UX8406CA - RDMA/core: Rate limit GID cache warning messages - [arm64] interconnect: qcom: sc7280: Add missing num_links to xm_pcie3_1 node - iio: adc: ad7949: use spi_is_bpw_supported() - regmap: fix potential memory leak of regmap_bus - [amd64] x86/hyperv: Fix usage of cpu_online_mask to get valid cpu - [amd64] platform/x86: Fix initialization order for firmware_attributes_class - [arm*] staging: vchiq_arm: Make vchiq_shutdown never fail - xfrm: state: initialize state_ptrs earlier in xfrm_state_find - xfrm: state: use a consistent pcpu_id in xfrm_state_find - xfrm: Set transport header to fix UDP GRO handling - xfrm: interface: fix use-after-free after changing collect_md xfrm interface - [arm64] net: ti: icssg-prueth: Fix buffer allocation for ICSSG - net/mlx5: Fix memory leak in cmd_exec() - net/mlx5: E-Switch, Fix peer miss rules to use peer eswitch - i40e: report VF tx_dropped with tx_errors instead of tx_discards - i40e: When removing VF MAC filters, only check PF-set MAC - net: appletalk: Fix use-after-free in AARP proxy probe - net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class - can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode - [arm64] drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() - ALSA: hda/realtek: Fix mute LED mask on HP OMEN 16 laptop - [s390x] ism: fix concurrency management in ism_cmd() - [arm64] net: hns3: fix concurrent setting vlan filter issue - [arm64] net: hns3: disable interrupt when ptp init failed - [arm64] net: hns3: fixed vf get max channels bug - [arm64] net: hns3: default enable tx bounce buffer when smmu enabled - [amd64] platform/x86: ideapad-laptop: Fix FnLock not remembered among boots - [amd64] platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots - drm/amdgpu: Reset the clear flag in buddy during resume - drm/sched: Remove optimization that causes hang when killing dependent jobs - mm/ksm: fix -Wsometimes-uninitialized from clang-21 in advisor_mode_show() - timekeeping: Zero initialize system_counterval when querying time from phc drivers - [arm64] i2c: qup: jump out of the loop in case of timeout - [arm64,armhf] i2c: tegra: Fix reset error handling with ACPI - i2c: virtio: Avoid hang by using interruptible completion wait - bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() - sprintf.h requires stdarg.h - ALSA: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx - ALSA: hda/realtek - Add mute LED support for HP Victus 15-fa0xxx - [arm64] entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack() - [arm64] dpaa2-eth: Fix device reference count leak in MAC endpoint handling - e1000e: disregard NVM checksum on tgp when valid checksum bit is not set - e1000e: ignore uninitialized checksum word on tgp - gve: Fix stuck TX queue for DQ queue format - ice: Fix a null pointer dereference in ice_copy_and_init_pkg() - nilfs2: reject invalid file types when reading inodes - resource: fix false warning in __request_region() - mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list - mm/zsmalloc: do not pass __GFP_MOVABLE if CONFIG_COMPACTION=n - [amd64,arm64] usb: typec: tcpm: allow to use sink in accessory mode - [amd64,arm64] usb: typec: tcpm: allow switching to mode accessory to mux properly - [amd64,arm64] usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach - spi: cadence-quadspi: fix cleanup of rx_chan on failure paths - [amd64] x86/bugs: Fix use of possibly uninit value in amd_check_tsa_microcode() - jfs: reject on-disk inodes of an unsupported type (CVE-2025-37925) - [amd64] comedi: comedi_test: Fix possible deletion of uninitialized timers - [arm64] dts: qcom: x1e78100-t14s: mark l12b and l15b always-on - erofs: simplify z_erofs_load_compact_lcluster() - erofs: refine z_erofs_get_extent_compressedlen() - erofs: use Z_EROFS_LCLUSTER_TYPE_MAX to simplify switches - erofs: simplify tail inline pcluster handling - erofs: clean up header parsing for ztailpacking and fragments - erofs: fix large fragment handling - ext4: don't explicit update times in ext4_fallocate() - ext4: refactor ext4_punch_hole() - ext4: refactor ext4_zero_range() - ext4: refactor ext4_collapse_range() - ext4: refactor ext4_insert_range() - ext4: factor out ext4_do_fallocate() - ext4: move out inode_lock into ext4_fallocate() - ext4: move out common parts into ext4_fallocate() - ext4: fix incorrect punch max_end - ext4: correct the error handle in ext4_fallocate() - ext4: fix out of bounds punch offset - [amd64] KVM: x86: drop x86.h include from cpuid.h - [amd64] KVM: x86: Route non-canonical checks in emulator through emulate_ops - [amd64] KVM: x86: Add X86EMUL_F_MSR and X86EMUL_F_DT_LOAD to aid canonical checks - [amd64] KVM: x86: model canonical checks more precisely - [amd64] KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush (CVE-2025-38351) - [amd64] x86/hyperv: Fix APIC ID and VP index confusion in hv_snp_boot_ap() - [arm64] dts: qcom: x1-crd: Fix vreg_l2j_1p2 voltage - Revert "wifi: mt76: mt7925: Update mt7925_mcu_uni_[tx,rx]_ba for MLO" - wifi: mt76: mt7925: adjust rm BSS flow to prevent next connection failure - iio: hid-sensor-prox: Restore lost scale assignments - iio: hid-sensor-prox: Fix incorrect OFFSET calculation - [amd64,arm64] Drivers: hv: Make the sysfs node size for the ring buffer dynamic - ALSA: hda/tegra: Add Tegra264 support - ALSA: hda: Add missing NVIDIA HDA codec IDs - [amd64] drm/i915/dp: Fix 2.7 Gbps DP_LINK_BW value on g4x - Revert "drm/xe/gt: Update handling of xe_force_wake_get return" (Closes: #1109799) - Revert "drm/xe/tests/mocs: Update xe_force_wake_get() return handling" - Revert "drm/xe/devcoredump: Update handling of xe_force_wake_get return" - Revert "drm/xe/forcewake: Add a helper xe_force_wake_ref_has_domain()" - [amd64] KVM: x86: Free vCPUs before freeing VM state - mm: khugepaged: fix call hpage_collapse_scan_file() for anonymous vma . [ Bastian Blank ] * Store build time signing key encrypted. * Enable CRYPTO_ECDSA. . [ Aurelien Jarno ] * Fix installation of DTB files . [ Tj ] * drivers/gpu/drm/nouveau: Enable DRM_NOUVEAU_GSP_DEFAULT (Closes: #1088522) . [ Uwe Kleine-König ] * [armhf] Add phy-gmii-sel module to nic-shared-modules udeb for ti/omap/am335x based machines (e.g. BeagleBone black). . [ Salvatore Bonaccorso ] * d/salsa-ci.yml: Update for trixie: Set RELEASE to trixie Checksums-Sha1: 4c27cc03165101daa02730a246b5db5edfd2578e 219407 linux_6.12.41-1.dsc accbbe886f7ee7058c827f6ea981e6c57fca8285 151148292 linux_6.12.41.orig.tar.xz 9580fbacfe8e5e345f4770237739808dfcc6af45 1672664 linux_6.12.41-1.debian.tar.xz fba82022a1f26b217e65612bfc2686a3fe0ec4c4 6694 linux_6.12.41-1_source.buildinfo Checksums-Sha256: 65bbf4e35635465326c9470605da1886ce3d3cf7e2a6d93392c4c6245d895b34 219407 linux_6.12.41-1.dsc 78afa637ca891174c22b332e4c1f87cf6aaa81861a6cca3b529e861843fa2fd3 151148292 linux_6.12.41.orig.tar.xz b62680107fc155ad3d2c421ba0af1d5848812674fe767fcd40ba81a414e4ce2a 1672664 linux_6.12.41-1.debian.tar.xz 59c0b9af69e550237710e6c56c67f7d9f62f35283af553196a4d0a1ec1ced78c 6694 linux_6.12.41-1_source.buildinfo Files: 26aa7b0334cd1d40085838b157601a02 219407 kernel optional linux_6.12.41-1.dsc a005fb8810c0ef34fc27bc5edf92d128 151148292 kernel optional linux_6.12.41.orig.tar.xz fa713a42314b7a9d99fb1e053e9fc824 1672664 kernel optional linux_6.12.41-1.debian.tar.xz 1ae397aa6aee8bfccf80d08c11fd330b 6694 kernel optional linux_6.12.41-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmiatddfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EqiUP/RMw7zcTvXowime5vF7mRR9pK5UWBUtT RwIKg8OtrO7GYc22RJUTZrBeAH0YS7vN5/89h38i0EUElv02S0YgRSxZJ8rYmNnF yhaskB+OZ/uu5AOMHukBO7CTxu8eTlEWfZ5x47xfl9Dm5EgCzD+Sy+KK72A8ORe9 6se6QjUlpY6+LfcMjWjdojAmAdFDR49AT63yWQAyD7PcE42puh/1CPNB64XB/DCL Q8zGC8VtOAa/VWb7Fxi0HVA1tBwQWXyYZNl+ssrqlxPpO3zKZsrS/hxYgo1G/1QL 22Hu5ljImERn/m9uooqX32+btycv8xuH0lFkprKUpbLmoJmwEto6tfkb//S6xwLw m8Qg6r2gPTphQv/be3zA2pSJYFEd5+altLqOXrZjV0X/xIm+dKN5ksCh1UOMOQ6j wkfBl2DHKd4Q+gmEdrMhiZ/aERjQwmngiImhlOvCSkHRFdKZg2p1o9EHoGUt2RPN t6ygp4H/cLKHkwBJsmlx4UW5MtnhB+7ZjMMjyqgHeMkTxkhW8slDEhmW6dVQAuvY e5H45fFoS+dpDDhtJU22UghalXV9KX3icyvrerAOtcORVR43ZXQSNZAFqfWxyEmw 8AnweMKUWLJ5QidZedu7ELlMD2I6qUpKyAJyEN5LGB9/AYSjcIROEnpJThJvomK4 7VbBVT3mM5dF =LGVy -----END PGP SIGNATURE-----