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

2024-02-12 Thread Mario Limonciello
On 2/12/2024 14:11, Diederik de Haas wrote: On Monday, 12 February 2024 19:38:12 CET Henrique de Moraes Holschuh wrote: On Fri, Feb 2, 2024, at 13:50, Diederik de Haas wrote: This is about "AMD Platform Management Framework TA", which seems to be about AMD CPU features. The first (and only)

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

2024-02-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1063780 nvidia-kernel-dkms Bug #1063780 [nvidia-kernel-dkms v525.147.05-4~deb12u1 against linux-image-6.1.0-18-amd64 and linux-headers-6.1.0-18-amd64.] Package: linux-image-6.1.0-18-amd64, linux-headers-6.1.0-18-amd64, and

Processed: reassign 1061445 to src:linux

2024-02-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1061445 src:linux Bug #1061445 [linux-image-6.7-cloud-amd64] linux-image-6.7-cloud-amd64: Built CONFIG_VIRTIO_BLK into kernel Bug reassigned from package 'linux-image-6.7-cloud-amd64' to 'src:linux'. No longer marked as found in

Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory

2024-02-12 Thread Bastian Blank
On Mon, Feb 12, 2024 at 10:26:07PM +0100, Salvatore Bonaccorso wrote: > On Mon, Feb 12, 2024 at 10:16:21PM +0100, Bastian Blank wrote: > > On Mon, Feb 12, 2024 at 10:09:41PM +0100, Salvatore Bonaccorso wrote: > > > kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64 > > > depmod: ERROR: could not

Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory

2024-02-12 Thread Salvatore Bonaccorso
Source: linux-signed-amd64 Version: 6.6.15+2 Severity: serious Justification: FTBFS X-Debbugs-Cc: car...@debian.org, wa...@debian.org, k...@debian.org The linux-signed-amd64 (and arm64 one) currently FTBFS (only filling one for amd64, as the same for arm64):

Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory

2024-02-12 Thread Marco d'Itri
On Feb 12, Salvatore Bonaccorso wrote: > --with-module-directory=/usr/lib/modules > > Looping in Marco for comments. I can revert it if it causes too much trouble, but maybe this is just the right time to switch the kernel packages to /usr/lib/modules/ as well? Please let me know if I am

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

2024-02-12 Thread Diederik de Haas
On Monday, 12 February 2024 19:38:12 CET Henrique de Moraes Holschuh wrote: > On Fri, Feb 2, 2024, at 13:50, Diederik de Haas wrote: > > This is about "AMD Platform Management Framework TA", which seems to be > > about AMD CPU features. The first (and only) commit message has this: > > > > ``` >

Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory

2024-02-12 Thread Bastian Blank
On Mon, Feb 12, 2024 at 10:09:41PM +0100, Salvatore Bonaccorso wrote: > kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64 > depmod: ERROR: could not open directory > /<>/debian/linux-image-6.6.15-amd64/usr/lib/modules/6.6.15-amd64: > No such file or directory I would say depmod changed the

Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory

2024-02-12 Thread Salvatore Bonaccorso
Hi Bastian, On Mon, Feb 12, 2024 at 10:16:21PM +0100, Bastian Blank wrote: > On Mon, Feb 12, 2024 at 10:09:41PM +0100, Salvatore Bonaccorso wrote: > > kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64 > > depmod: ERROR: could not open directory > >

Processed: Re: Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory

2024-02-12 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 kmod Bug #1063804 [src:linux-signed-amd64] FTBFS: depmod: FATAL: could not search modules: No such file or directory Bug reassigned from package 'src:linux-signed-amd64' to 'kmod'. No longer marked as found in versions linux-signed-amd64/6.6.15+2.

Bug#1063804: FTBFS: depmod: FATAL: could not search modules: No such file or directory

2024-02-12 Thread Bastian Blank
Control: reassign -1 kmod On Mon, Feb 12, 2024 at 10:37:46PM +0100, Marco d'Itri wrote: > On Feb 12, Salvatore Bonaccorso wrote: > > --with-module-directory=/usr/lib/modules > I can revert it if it causes too much trouble, but maybe this is just > the right time to switch the kernel packages to

Processed: Re: Bug#1061095: linux-image-6.6.11-amd64: 2.5gbit USB device with r8152 chipset only does 100baset

2024-02-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #1061095 [src:linux] linux-image-6.6.11-amd64: 2.5gbit USB device with r8152 chipset only does 100baset Added tag(s) moreinfo. -- 1061095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061095 Debian Bug Tracking System Contact

Bug#1061095: linux-image-6.6.11-amd64: 2.5gbit USB device with r8152 chipset only does 100baset

2024-02-12 Thread Ben Hutchings
Control: tag -1 moreinfo On Thu, 2024-01-18 at 13:42 +1100, Russell Coker wrote: > Package: src:linux > Version: 6.6.11-1 > Severity: normal > Tags: upstream > > [51076.208113] r8152-cfgselector 2-1: reset SuperSpeed USB device number 6 > using xhci_hcd > [51076.236596] r8152 2-1:1.0: firmware:

Bug#1063656: linux-image-6.1.0-18-amd64: Building nvidia modules (from Debian package) fails. Resulting kernel panics.

2024-02-12 Thread Teemu Likonen
* 2024-02-10 16:42:58+0100, Christoph Groth wrote: > Package: src:linux > Version: 6.1.76-1 This is probably the same bug as #1062932 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932 signature.asc Description: PGP signature

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

2024-02-12 Thread Diederik de Haas
On Monday, 12 February 2024 21:25:35 CET Mario Limonciello wrote: > > My logic was that this is about AMD TEE (Trusted Execution Environment), > > which I *assumed* is part of/tied to the CPU. This thought is based on > > that on ARM platforms, you also have a TEE and that is part of the CPU > >

Processed (with 2 errors): your mail

2024-02-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1063775 initramfs-tools Bug #1063775 [plymouth] Plymouth, and cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead Bug reassigned from package 'plymouth' to 'initramfs-tools'. No longer marked

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

2024-02-12 Thread Jeffrey Walton
I think I incorrectly attributed the warnings to the Plymouth package. I now think this is an issue with update-initramfs. I saw the warnings again when manually running initramfs-tools. My apologies if I got the package wrong (again). - # apt-cache show initramfs-tools Package:

Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable)

2024-02-12 Thread Arno Lehmann
Reported upstream, see https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0...@its-lehmann.de/T/#u keep your fingers crossed this will have someone interested ;-) Cheers, Arno -- Arno Lehmann IT-Service Lehmann Sandstr. 6, 49080 Osnabrück

Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable)

2024-02-12 Thread Diederik de Haas
Control: forwarded -1 https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0...@its-lehmann.de/ On Monday, 12 February 2024 12:56:45 CET Arno Lehmann wrote: > Reported upstream, see > > https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0d2a@its-lehm > ann.de/T/#u

Processed: Re: Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable)

2024-02-12 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 > https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0...@its-lehmann.de/ Bug #1060706 [src:linux] linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable Set Bug forwarded-to-address to