Processed: Reassign 1050315 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1050315 src:linux Bug #1050315 [fb-modules-6.4.0-3-arm64-di] Please include sun8i-drm-hdmi module in installer Bug reassigned from package 'fb-modules-6.4.0-3-arm64-di' to 'src:linux'. No longer marked as found in versions linux-signed-arm64/6.4.11+1. Ignoring request to alter fixed versions of bug #1050315 to the same values previously set > stop Stopping processing here. Please contact me if you need assistance. -- 1050315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1042753: nouveau bug in linux/6.1.38-2
Processing control commands: > tags -1 + fixed-upstream Bug #1042753 [src:linux] nouveau: Screen remains black. Added tag(s) fixed-upstream. -- 1042753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042753: nouveau bug in linux/6.1.38-2
Control: tags -1 + fixed-upstream On Sat, Aug 05, 2023 at 12:40:24PM +0200, Diederik de Haas wrote: > Control: forwarded -1 > https://lore.kernel.org/dri-devel/20be6650-5db3-b72a-a7a8-5e817113c...@kravcenko.com/ > > https://lore.kernel.org/dri-devel/20230805101813.2603989-1-kher...@redhat.com/ > Control: tag -1 - moreinfo > > On Saturday, 5 August 2023 11:44:22 CEST Olaf Skibbe wrote: > > On Sat, 5 Aug 2023 at 01:09, Karol Herbst wrote: > > > Mind checking if instead of reverting the entire commit that this is > > > enough to fix it as well? > > > > > > https://gitlab.freedesktop.org/karolherbst/nouveau/-/commit/f99ae069876f7f > > > feb6368da0381485e8c3adda43.patch > > This patch does fix the problem as well: Screen works. > > And this caused a patch proposal fixing the issue \o/ > https://lore.kernel.org/dri-devel/20230805101813.2603989-1-kher...@redhat.com/ For reference: https://git.kernel.org/linus/d5712cd22b9cf109fded1b7f178f4c1888c8b84b in 6.5-rc6 got then backported to 6.4.11 and 6.1.46. So next upload with rebase of 6.1.y will contain the fix. Regards, Salvatore
Processed: reassign 1043404 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1043404 src:linux Bug #1043404 [linux-image-6.4.0-1-amd64] with linux 6.4.4 mariadbd is at 100% wait for one cpu Warning: Unknown package 'linux-image-6.4.0-1-amd64' Bug reassigned from package 'linux-image-6.4.0-1-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/6.4.4+2. Ignoring request to alter fixed versions of bug #1043404 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1043404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
linux-signed-arm64_6.5~rc7+1~exp1_source.changes ACCEPTED into experimental
Thank you for your contribution to Debian. Mapping rc-buggy to experimental. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 21 Aug 2023 21:49:11 +0200 Source: linux-signed-arm64 Architecture: source Version: 6.5~rc7+1~exp1 Distribution: rc-buggy Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-arm64 (6.5~rc7+1~exp1) experimental; urgency=medium . * Sign kernel from linux 6.5~rc7-1~exp1 . * New upstream release candidate . [ Salvatore Bonaccorso ] * linux-image: bug: Update taint list and use upstream descriptions * [rt] Refresh "serial: 8250: implement non-BKL console" . [ Miguel Bernal Marin ] * [amd64] mm: Enable MEMORY_HOTPLUG_DEFAULT_ONLINE: Enable Online the newly added memory blocks by default (Closes: #1049901) . [ Helge Deller ] * [hppa] Add build-dependency on binutils-dev to get bfd.h and thus allow disassembly of jitted programs in bpftool Checksums-Sha1: 7f8599342f11ab3fa8b32182f3749b3a3899dc97 7407 linux-signed-arm64_6.5~rc7+1~exp1.dsc d601fb5ad1425377307b17b7a5c8b362977d3e5e 2860500 linux-signed-arm64_6.5~rc7+1~exp1.tar.xz Checksums-Sha256: 6fc1cc4d2bb82ac9ec8b58ad99c17351dc9679cb28211263e01b72c479ccefe5 7407 linux-signed-arm64_6.5~rc7+1~exp1.dsc df79fbeada6f10869e0cddcc04fa453c238543d1d546ef4882ef8827c1f9836b 2860500 linux-signed-arm64_6.5~rc7+1~exp1.tar.xz Files: 6bec81e312987bb825ab4a1b76f450c6 7407 kernel optional linux-signed-arm64_6.5~rc7+1~exp1.dsc 088d18a05bd295fed2fa165006087371 2860500 kernel optional linux-signed-arm64_6.5~rc7+1~exp1.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmTnuiwACgkQi0FRiLdO NzbufQ/9GMtr09drrJQdANdXR+3ckuAelyqQilboiBn8h/oH3ORU2e3ZqwWxakP3 W63rXRVTnTVmMZb2a9tah2InfRyH4Xjvi1rbGAJRdLnCs0yjmAqT3QLJQnSqTKp9 t1D0PjcvR7epddFfw7FY3CrvJW4dLNSJxXVCxUethKBDEyTm+SC0P94g+D4Yptey HIYp/wdahYt1vPx5ycPKbar5FNp9HFCM3F7tFTEZfy4WIUwDVDEmmAhP5xA50cJs Ic9PmHcsHulLPMSmXAZlBDoCLTqflCG/O/KkSO8gDCh2uPGAJiN+LUTcJtskluMk LTUfatvOEobMml+0KuOmag5Mc5qvvU7itD32lteH2Xik9Lh8kTbDzbpWWrXFV/cY R4EqP4FRCDlCJYRMHXCUE9ZfQ1I3TeeHxq81tX2359IoP9lYi+tsq1uwonahR3UQ U8SX1vtpMV42tP/ws9ldTyUYcDn8LJkt94pyYv9+IJeFc+rLlyfVow7OXci7H3G0 DyaDdUbwNNXZ9nMrit3WmSExFFR8/OAWQB1tEgGR/931VAisdyHLU+aBjHnDDCVO SSUo0/M2qFhNMEPZVUu5gEv6zZvhSOm0/zJZ6J4e+WC87CgnIMf1NjK/IAUjEgz6 chEARrqz7VC8+JU4qmlFztqo1k1bcPiCI9LBemHncFaAVZ7jS80= =dPlQ -END PGP SIGNATURE-
Processing of linux-signed-arm64_6.5~rc7+1~exp1_source.changes
linux-signed-arm64_6.5~rc7+1~exp1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_6.5~rc7+1~exp1.dsc linux-signed-arm64_6.5~rc7+1~exp1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1050460: linux-image-6.4.0-3-amd64: Unable to start in graphic mode with a nvidia card (nouveau driver)
Package: src:linux Version: 6.4.11-1 Severity: important Dear Maintainer, * What led up to the situation? Normal system update, then reboot with new kernel and it apparently stops loading; from syslog i can see it crashes video module. I'm using nouveau driver * What exactly did you do (or not do) that was effective (or ineffective)? Tried to boot with nomodeset but X fails to start; booting with parameters "nomodeset xforcevesa" system starts but it keeps resolution of 800x600. When started normally computer is accessible only via ssh and there is no way to use it via its display. Now i'm writing from previous kernel version. Consider routing the bug to nouveau video package if you think it's needed Attached there is a part of kernel log related to the issue. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Hewlett-Packard product_name: HP Z210 Workstation product_version: chassis_vendor: Hewlett-Packard chassis_version: bios_vendor: Hewlett-Packard bios_version: J51 v01.55 board_vendor: Hewlett-Packard board_name: 1587h board_version: ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 Processor Family DRAM Controller [8086:0108] (rev 09) Subsystem: Hewlett-Packard Company Xeon E3-1200 Processor Family DRAM Controller [103c:1587] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ie31200_edac Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal decode]) Subsystem: Hewlett-Packard Company Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [103c:1587] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:06.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:010d] (rev 09) (prog-if 00 [Normal decode]) Subsystem: Hewlett-Packard Company Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [103c:1587] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller [103c:1587] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:16.2 IDE interface [0101]: Intel Corporation 6 Series/C200 Series Chipset Family IDE-r Controller [8086:1c3c] (rev 04) (prog-if 85 [PCI native mode-only controller, supports bus mastering]) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family IDE-r Controller [103c:1587] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ata_generic Kernel modules: ata_generic 00:16.3 Serial controller [0700]: Intel Corporation 6 Series/C200 Series Chipset Family KT Controller [8086:1c3d] (rev 04) (prog-if 02 [16550]) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family KT Controller [103c:1587] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: serial 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) [8086:1502] (rev 04) DeviceName: Onboard LAN Subsystem: Hewlett-Packard Company 82579LM Gigabit Network Connection (Lewisville) [103c:1587] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB
[bts-link] source package src:linux
# # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #1039029 (http://bugs.debian.org/1039029) # Bug title: linux-signed-amd64: Core frequencies do not float correctly on AMD Ryzen 7 5700U when running on battery # * http://bugzilla.kernel.org/show_bug.cgi?id=217809 # * remote status changed: (?) -> NEW usertags 1039029 + status-NEW thanks
Bug#1050446: nfs over rdma between debian12 client and debian11 server can cause data corruption
Package: nfs-common,rdma-core I've been testing the upgrade of a compute node from Debian11 to Debian12. That node was connected through nfs with rdma protocol to a zfs-storage server running on Debian11. The compute node and the storage server are part of a high-performance compute cluster, connected over infiniband. Not sure whether this is important, but the storage server is using zfs. After the upgrade of the compute node (node client) to Debian 12, this machine could not correctly read a few (small) files. The files were correctly shown with "ls", and the size matched as well. However the content was corrupted (looked like random garbage). In one case the .ssh/authorized_keys was corrupted, in some other case the "version.lua" from the lmod system was affected, rendering lmod unusable. Interestingly, only very few files seemed to be affected. Most files were correctly retrieved. So this is a very subtle error, and not obvious. When retrieving these files, no error was reported, but data of the expected size was retrieved. Effectively, the retrieved data was corrupted, and could lead to potential data loss. The compute node on Debian12 had ii libnfsidmap1:amd641:2.6.2-4 amd64NFS idmapping library ii nfs-common1:2.6.2-4 amd64NFS support files common to client and server ii librdmacm1:amd64 44.0-2 amd64Library for managing RDMA connections ii rdma-core 44.0-2 amd64RDMA core userspace infrastructure and documentation ii rdmacm-utils 44.0-2 amd64Examples for the librdmacm library The storage server on Debian11 had ii nfs-common 1:1.3.4-6 amd64 NFS support files common to client and server ii nfs-kernel-server 1:1.3.4-6 amd64 support for NFS kernel server ii librdmacm1:amd64 33.2-1 amd64 Library for managing RDMA connections The problem went away, when changing nfs mount protocal from proto=rdma to proto=tcp. I tried to learn about this incompatibility, but did not find any information. I'm also curious whether an nfs 2.6 server would correctly talk to an nfs 1.3 client over rdma ? Can anyone provide more information on that topic ?
Bug#1050442: iproute2: [INTL:sv] Swedish translation of debconf messages
Package: iproute2 Version: 6.4.0-1 Severity: wishlist Tags: l10n patch X-Debbugs-Cc: peterkvilleg...@posteo.net Dear Maintainer, Please copy the attachment into debian/po/sv.po It's been reviewed by the Swedish translation team, tested with msgfmt -c -v -o /dev/null sv.po, and is in UTF-8. Regards, Peter Kvillegård # Swedish translation of iproute2 debconf messages # Copyright (C) The iproute2 package copyright holders # This file is distributed under the same license as the iproute2 package. # Peter Kvillegård , 2023. # msgid "" msgstr "" "Project-Id-Version: iproute2 6.4.0-1\n" "Report-Msgid-Bugs-To: iprou...@packages.debian.org\n" "POT-Creation-Date: 2018-04-12 12:01+0100\n" "PO-Revision-Date: 2023-08-21 19:02+0200\n" "Last-Translator: Peter Kvillegård \n" "Language-Team: Swedish \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Poedit 3.2.2\n" #. Type: boolean #. Description #: ../iproute2.templates:1001 msgid "Allow ordinary users to run ip vrf exec using capabilities?" msgstr "" "Tillåt vanliga användare att köra ip vrf exec genom att använda förmågor " "(capabilities)?" #. Type: boolean #. Description #: ../iproute2.templates:1001 msgid "" "iproute2 can be used to configure and use Virtual Routing and Forwarding " "(VRF) functionality in the kernel. This normally requires root permissions, " "but sometimes it's useful to allow ordinary users to execute commands from " "inside a virtual routing and forwarding domain. E.g. ip vrf exec examplevrf " "ping 10.0.0.1" msgstr "" "iproute2 kan användas för att konfigurera och använda kärnans funktioner för " "virtuell dirigering och vidarebefordran (Virtual Routing and Forwarding " "(VRF)). Detta kräver vanligen root-rättigheter, men ibland är det användbart " "att tillåta vanliga användare att köra kommandon inifrån en domän för " "virtuell dirigering och vidarebefordran. Till exempel ip vrf exec exempelvrf " "ping 10.0.0.1" #. Type: boolean #. Description #: ../iproute2.templates:1001 msgid "" "The ip command supports dropping capabilities, making an exception for ip " "vrf exec. The drawback of setting the permissions is that if in the unlikely " "case of a security critical bug being found before the ip command has " "dropped capabilities then it could be used by an attacker to gain root " "permissions. It's up to you to decide about the trade-offs and select the " "best setting for your system. This will give cap_dac_override, cap_net_admin " "and cap_sys_admin to /bin/ip." msgstr "" "Kommandot ip stödjer att ta bort förmågor (capabilities) med undantag för ip " "vrf exec. Nackdelen med att ställa in rättigheterna är att i den osannolika " "händelsen av att ett kritiskt säkerhetsfel hittas innan ip har tagit bort " "förmågor, så kan det användas av en angripare för att få root-rättigheter. " "Det är upp till dig att göra en avvägning och välja vad som passar bäst för " "ditt system. Detta kommer att ge förmågorna cap_dac_override, cap_net_admin, " "och cap_sys_admin till /bin/ip." #. Type: boolean #. Description #: ../iproute2.templates:1001 msgid "" "More information about VRF can be found at: https://www.kernel.org/doc/; "Documentation/networking/vrf.txt" msgstr "" "Mer information om virtuell dirigering och vidarebefordran (VRF) kan hittas " "på https://www.kernel.org/doc/Documentation/networking/vrf.txt;
Bug#1050352: backside USB-ports stop working after some time
On another disk I installed bookworm and upgraded to testing. With testing the problem is also there.
Processed: reassign 1050406 to virtualbox-dkms
Processing commands for cont...@bugs.debian.org: > reassign 1050406 virtualbox-dkms Bug #1050406 [linux-headers-6.4.0-3-amd64] linux-headers-6.4.0-3-amd64: cannot install because of dkms problem Bug reassigned from package 'linux-headers-6.4.0-3-amd64' to 'virtualbox-dkms'. No longer marked as found in versions linux/6.4.11-1. Ignoring request to alter fixed versions of bug #1050406 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1050406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1049885: overlayfs: cannot rename symlink if lower filesystem is NFS
Processing control commands: > tags -1 + moreinfo Bug #1049885 [src:linux] overlayfs: cannot rename symlink if lower filesystem is NFS Added tag(s) moreinfo. -- 1049885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1049885: overlayfs: cannot rename symlink if lower filesystem is NFS
Control: tags -1 + moreinfo
Hi Guido,
On Wed, Aug 16, 2023 at 03:34:45PM +0200, Guido Berhoerster wrote:
> Package: linux-image-6.1.0-10-amd64
> Version: 6.1.38-2
>
> rename(2) on a symlink on an overlayfs where the lower filesystem is NFS
> fails with ENXIO.
>
> It can be reproduced as follows:
>
> lower=/nfs/lower # /nfs should be an nfs mount
> mkdir -p "${lower}" /upper /work /merged
> touch "${lower}"/foo
> ln -s foo "${lower}"/bar
> mount -t overlay overlay -o lowerdir="${lower}",upperdir=/upper,workdir=/work
> /merged
> mv /merged/bar /merged/baz
>
> If $lower is e.g. ext4 this works. This is a regression over kernel
> 5.10 in bullseye. It affects ltsp causing booting into root fs on NFS
> to fail due to an initrd script which temporarily renames the /sbin/init
> symlink, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049397
Did you check, does that affect current stable versions upstream or
mainline?
Were you able to bisect the breaking change?
In both cases, it would be great it you can report this upstream and
keep us in the loop.
Regards,
Salvatore
Bug#1050406: linux-headers-6.4.0-3-amd64: cannot install because of dkms problem
Package: linux-headers-6.4.0-3-amd64 Version: 6.4.11-1 Severity: normal At install time I get following error, which prevents installation (and yes I need virtualbox) Setting up linux-headers-6.4.0-3-amd64 (6.4.11-1) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.4.0-3-amd64. Sign command: /lib/modules/6.4.0-3-amd64/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j8 KERNELRELEASE=6.4.0-3-amd64 -C /lib/modules/6.4.0-3-amd64/build M=/var/lib/dkms/virtualbox/7.0.10/build(bad exit status: 2) Error! Bad return status for module build on kernel: 6.4.0-3-amd64 (x86_64) Consult /var/lib/dkms/virtualbox/7.0.10/build/make.log for more information. dkms autoinstall on 6.4.0-3-amd64/x86_64 failed for virtualbox(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.4.0-3-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.4.0-3-amd64.postinst line 11. dpkg: error processing package linux-headers-6.4.0-3-amd64 (--configure): installed linux-headers-6.4.0-3-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-amd64: linux-headers-amd64 depends on linux-headers-6.4.0-3-amd64 (= 6.4.11-1); however: Package linux-headers-6.4.0-3-amd64 is not configured yet. dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured Setting up linux-image-6.4.0-3-amd64 (6.4.11-1) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.4.0-3-amd64. Sign command: /lib/modules/6.4.0-3-amd64/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j8 KERNELRELEASE=6.4.0-3-amd64 -C /lib/modules/6.4.0-3-amd64/build M=/var/lib/dkms/virtualbox/7.0.10/build(bad exit status: 2) Error! Bad return status for module build on kernel: 6.4.0-3-amd64 (x86_64) Consult /var/lib/dkms/virtualbox/7.0.10/build/make.log for more information. dkms autoinstall on 6.4.0-3-amd64/x86_64 failed for virtualbox(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.4.0-3-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.4.0-3-amd64 (--configure): installed linux-image-6.4.0-3-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-amd64: linux-image-amd64 depends on linux-image-6.4.0-3-amd64 (= 6.4.11-1); however: Package linux-image-6.4.0-3-amd64 is not configured yet. dpkg: error processing package linux-image-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-6.4.0-3-amd64 linux-headers-amd64 linux-image-6.4.0-3-amd64 linux-image-amd64 -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (900, 'stable-updates'), (900, 'testing'), (800, 'stable-security'), (500, 'proposed-updates'), (500, 'unstable'), (400, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-headers-6.4.0-3-amd64 depends on: ii linux-compiler-gcc-13-x86 6.4.11-1 ii linux-headers-6.4.0-3-common 6.4.11-1 ii linux-kbuild-6.4.0-3 6.4.11-1 linux-headers-6.4.0-3-amd64 recommends no packages. linux-headers-6.4.0-3-amd64 suggests no packages. Other package implied : ii virtualbox-dkms7.0.10-dfsg-2 amd64 -- no debconf information
Bug#939170: linux: does not suspend completely, locks up
The reason for the change may be due to the way some new motherboards are designed with accessory plug-able trusted platform modules or TMP 2 for short. And Window 11 requirements. More about tmp2 on linux and windows 11 https://paolozaino.wordpress.com/2021/02/21/linux-configure-and-use-your-tpm-2-0-module-on-linux/ https://www.pcmag.com/news/what-is-a-tpm-and-why-do-i-need-one-for-windows-11 hope this is helpful !Billy
Bug#1050352: backside USB-ports stop working after some time
I have just installed bullseye on another disk. It has the same problem. I do not know why I did not run in this problem when bullseye was stable and I used it.
