Processed: reassign 1063879 to nvidia-kernel-dkms, forcibly merging 1062932 1063879

[Debian Bug Tracking System]

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

> reassign 1063879 nvidia-kernel-dkms
Bug #1063879 [src:linux] linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 
do not compile against linux-image 6.1.0-18
Bug reassigned from package 'src:linux' to 'nvidia-kernel-dkms'.
No longer marked as found in versions linux/6.1.76-1.
Ignoring request to alter fixed versions of bug #1063879 to the same values 
previously set
> forcemerge 1062932 1063879
Bug #1062932 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: dkms module won't build against linux-image-6.1.0-18-amd64 
(6.1.76-1)
Bug #1063668 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues
Bug #1063689 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU
Bug #1063713 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports 
problem with building modules
Bug #1063717 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
cuda-drivers: Build of module nvidia.ko fails
Bug #1063729 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot
Bug #1063731 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Kernel panic after update from Debian 12.4 to 12.5 in command line
Bug #1063780 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Package: linux-image-6.1.0-18-amd64, linux-headers-6.1.0-18-amd64, and 
nvidia-kernel-dkms v525.147.05-4~deb12u1
Bug #1063879 [nvidia-kernel-dkms] linux-image-6.1.0-18-amd64: nvidia-drivers 
525.147.05 do not compile against linux-image 6.1.0-18
Severity set to 'grave' from 'serious'
1063879 was not blocked by any bugs.
1063879 was not blocking any bugs.
Added blocking bug(s) of 1063879: 1063675
Marked Bug as done
Marked as fixed in versions nvidia-graphics-drivers/535.54.03-1, 
nvidia-graphics-drivers/525.147.05-6, and 
nvidia-graphics-drivers/525.147.05-6~deb12u1.
Marked as found in versions nvidia-graphics-drivers/525.147.05-4~deb12u1.
Added tag(s) patch.
Bug #1063668 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues
Bug #1063689 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU
Bug #1063713 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports 
problem with building modules
Bug #1063717 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
cuda-drivers: Build of module nvidia.ko fails
Bug #1063729 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot
Bug #1063731 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Kernel panic after update from Debian 12.4 to 12.5 in command line
Bug #1063780 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Package: linux-image-6.1.0-18-amd64, linux-headers-6.1.0-18-amd64, and 
nvidia-kernel-dkms v525.147.05-4~deb12u1
Merged 1062932 1063668 1063689 1063713 1063717 1063729 1063731 1063780 1063879
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
1063668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063668
1063689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063689
1063713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063713
1063717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063717
1063729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063729
1063731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063731
1063780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063780
1063879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063879: linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image 6.1.0-18

[Peter Hyman]

Package: src:linux
Version: 6.1.76-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the 
past)


Dear Maintainer,

Upgrading from linux-image 6.1.0-17 to 6.1.0-18 fails to complete due to 
nvidia

compile error.

ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_unlock'

* What led up to the situation?
routine kernel upgrade using meta package linux-image-amd64
* What exactly did you do (or not do) that was effective (or
ineffective)?
used synaptic. Also attempted on commandline
$ apt install linux-image-amd64
* What was the outcome of this action?
Cleaning build area...
env NV_VERBOSE=1 make -j8 modules
KERNEL_UNAME=6.1.0-18-amd64..(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more
information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
...
dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-6.1.0-18-amd64
linux-headers-6.1.0-18-amd64
linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
* What outcome did you expect instead?
kernel upgraded


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

** Model information
sys_vendor: HP
product_name: HP Pavilion Laptop 15-cs3xxx
product_version: Type1ProductConfigId
chassis_vendor: HP
chassis_version: Chassis Version
bios_vendor: Insyde
bios_version: F.21
board_vendor: HP
board_name: 86E2
board_version: 95.36

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Ice Lake-LP Processor Host 
Bridge/DRAM Registers [8086:8a12] (rev 03)
Subsystem: Hewlett-Packard Company Ice Lake-LP Processor Host 
Bridge/DRAM Registers [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0
IOMMU group: 1
Capabilities: 
Kernel driver in use: icl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Plus 
Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller])

Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86e2]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 139
IOMMU group: 0
Region 0: Memory at 601600 (64-bit, non-prefetchable) [size=16M]
Region 2: Memory at 40 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 8000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Processor 
Power and Thermal Controller [8086:8a03] (rev 03)
Subsystem: Hewlett-Packard Company Processor Power and Thermal 
Controller [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0
Interrupt: pin A routed to IRQ 16
IOMMU group: 2
Region 0: Memory at 601710 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:14.0 USB controller [0c03]: Intel Corporation Ice Lake-LP USB 3.1 
xHCI Host Controller [8086:34ed] (rev 30) (prog-if 30 [XHCI])
Subsystem: Hewlett-Packard Company Ice Lake-LP USB 3.1 xHCI Host 
Controller [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Latency: 0
Interrupt: pin A routed to IRQ 127
IOMMU group: 3
Region 0: Memory at 5600 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 RAM memory [0500]: Intel Corporation Ice Lake-LP DRAM Controller 
[8086:34ef] (rev 30)

Subsystem: Hewlett-Packard Company Ice Lake-LP DRAM Controller [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0, Cache Line Size: 64 bytes
IOMMU group: 3
Region 0: Memory at 6017118000 (64-bit, non-prefetchable) [size=8K]
Region 2: Memory at 601712 (64-bit, non-prefetchable) [size=4K]
Capabilities: 

00:14.3 Network controller [0280]: Intel Corporation Ice Lake-LP PCH 
CNVi WiFi [8086:34f0] (rev 30)

DeviceName: Intel Wireless-WiFi 6 AX201 Dual Band 2x2 WiFi + BT 5
Subsystem: Intel 

Re: Bug#1062678: amd64-microcode: Package upstream's amdtee dir in amd64-microcode?

[Mario Limonciello]

'amdtee' is the one thing right now, but soon (TM) the IPU/NPU binaries
will go to linux-firmware.git and then where do those go?


My (current) thinking is to have 2 categories:
- AMD CPU related
- AMD GPU/graphics related


Current products only put the IPU/NPU in APU chips, but who is to stay;
those might end up in SoCs without graphics in the future too.


I think it's important to facilitate people having f.e. the following combos:
- Intel CPU with AMD GPU
- AMD CPU with Nvidia GPU
- AMD CPU with AMD GPU (discrete or integrated)

Preferably without having to install 100s of MB of firmware files of which 95%
the user doesn't actually need. (See f.e. https://bugs.debian.org/1057786)


You don't currently split up the AMD APU integrated graphics and dGPU, 
and I doing this is a bad idea as it's possible to reuse IP versions on 
APU and dGPU hardware.  If they are the same then they would use the 
same firmware binaries.


For reference on the size:

$ du -sh amdgpu
60M amdgpu

$ du -sh du -sh amdtee/
20K amdtee/

$ du -sh amd-ucode/
112Kamd-ucode/

$ du -sh amd
268Kamd

These aren't yet upstream, but so you can see the size:

$ du -sh amdnpu/
3.3Mamdnpu/




How would you feel about making a master "amd" metapackage that pulls
them all?  You can split as you see fit then and people who want the
'easy button' can just install that package.


I'm not much of a fan of such metapackages. I think it mostly indicates that
the purpose of the various packages isn't clear, so let's install all of them.
Clarifying the purpose better is a better solution imo.
I'm aware others feel different: https://bugs.debian.org/522415

I prefer to keep that discussion out of this bug though, feel free to open a
new bug for that if you do want it.


I think your suggestion to combine all the non graphics related binaries 
to a single package and all graphics related binaries to another is fine.

Re: Bug#1062678: amd64-microcode: Package upstream's amdtee dir in amd64-microcode?

[Diederik de Haas]

On Tuesday, 13 February 2024 17:59:55 CET Mario Limonciello wrote:
> > I think it's important to facilitate people having f.e. the following
> > combos: 
> > - Intel CPU with AMD GPU
> > - AMD CPU with Nvidia GPU
> > - AMD CPU with AMD GPU (discrete or integrated)
> > 
> > Preferably without having to install 100s of MB of firmware files of which
> > 95% the user doesn't actually need. (See f.e.
> > https://bugs.debian.org/1057786)
> You don't currently split up the AMD APU integrated graphics and dGPU,
> and I doing this is a bad idea as it's possible to reuse IP versions on
> APU and dGPU hardware.  If they are the same then they would use the
> same firmware binaries.

I have/had no plan to make a split for iGPU and dGPU, both would need to 
install the `firmware-amd-graphics` package.

For the 3 scenario's above:
- `intel-microcode` + `firmware-amd-graphics`
- `amd64-microcode` + `firmware-nvidia`*
- `amd64-microcode` + `firmware-amd-graphics`

AMD APU's would fall into scenario 3.

*) If my MR gets accepted, otherwise `firmware-misc-nonfree`

> For reference on the size:
> 
> $ du -sh amdgpu
> 60M amdgpu
> 
> $ du -sh du -sh amdtee/
> 20K amdtee/
> 
> $ du -sh amd-ucode/
> 112Kamd-ucode/
> 
> $ du -sh amd
> 268Kamd

What I want(ed) to prevent is that for scenario 2, the user should NOT have to 
install the `firmware-amd-graphics` package to get the amdtee firmware.

> These aren't yet upstream, but so you can see the size:
> 
> $ du -sh amdnpu/
> 3.3Mamdnpu/

And that seems like a future candidate too for amd64-microcode package.

> I think your suggestion to combine all the non graphics related binaries
> to a single package and all graphics related binaries to another is fine.

Excellent, then I think we're all in agreement :)

I'll add the `amdtee` dir to `Files-Excluded` in firmware-nonfree and Henrique 
can add those files to the amd64-microcode package.

Cheers,
  Diederik

signature.asc
Description: This is a digitally signed message part.

Bug#1063775: initramfs-tools, and cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead

[Wesley Schwengle]

Small update on the previous message.

It's the same as Debian #1055694, which is upstream bug

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572


Cheers,
Wesley

--
Wesley Schwengle
E: wes...@schwengle.net

Bug#1063775: initramfs-tools, and cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead

[Jeffrey Walton]

This issue is likely Debian Bug #62572. Also see
.

(Thanks Wesley).

Bug#1058890: new try

[Dr . André Desgualdo Pereira]

Adding "intel_iommu=off" to kernel boot does NOT change anything.