Bug#1069077: rockpro64: multiple kernel oops and frequent boot failures
Control: fixed -1 6.8.9-1 On Fri, 17 May 2024 12:15:55 +0200, Diederik de Haas wrote: >Kernel 6.8.9 has recently been uploaded to Unstable which has that commit. >Can you verify that it indeed fixes this bug? Indeed, it seems to be fixed there. It usually takes only one or two boots to show up, but I didn't see it in five reboots with kernel 6.8.9. This matches what I found while bisecting for the past week. Note that I have not examined the es8316 driver code or its relationship to maple_tree. I don't know if the bug was in maple_tree and now fixed, or still lurks within the driver but is now hidden as a result of the maple_tree changes. In any case, I'm happy to report that I no longer see it breaking the OS in this newer kernel.
Processed: Re: Bug#1069077: rockpro64: multiple kernel oops and frequent boot failures
Processing control commands: > fixed -1 6.8.9-1 Bug #1069077 [src:linux] es8316 driver causes kernel oops / panic on rockpro64 Marked as fixed in versions linux/6.8.9-1. -- 1069077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: ocfs2_dlmfs missing from the cloud kernel
On Fri, May 17, 2024 at 05:34:57PM +0200, Bastian Blank wrote: > > > how do I change this? > > You install the non-cloud kernel. > > The cloud kernel is limited in scope. And the decision was that not > everything you can do on platforms is in scope. To clarify the scope a bit, historically the cloud kernels have specifically targeted Amazon EC2 and Microsoft Azure. The rationale for this is that these providers present a consistent and reasonably well defined device model, meaning we can be sure what drivers and other kernel features are needed and which we can leave out. It is not intended to be usable on every cloud service. The module in question, ocfs2_dlmfs, is not, to my knowledge, generally useful in the cloud environments targeted by the cloud kernel. If we had the resources, it'd be great provide further optimized kernel builds, e.g. one for EC2 specifically, Azure specifically, GCP, and maybe some sort of OpenStack/QEMU VM definition. Unfortunately, we do not currently have those resources. So, IMO, a wishlist bug against src:linux asking for another build configuration would be a reasonable way to record an interest in such a change. The kernel team may be able to provide more context on which specific resources would be needed in order to support this. Maybe in the future it'll get implemented. noah
Re: ocfs2_dlmfs missing from the cloud kernel
On Fri, May 17, 2024 at 12:44:32PM +0200, Bastian Blank wrote: > On Fri, May 17, 2024 at 12:31:51PM +0200, Thomas Goirand wrote: > > how do I change this? > You install the non-cloud kernel. The cloud kernel is limited in scope. And the decision was that not everything you can do on platforms is in scope. So you can open a bug report, but for now I would say it is not in this scope. Cloud platforms tend to provide such things and you don't define them on your own. Bastian -- It would seem that evil retreats when forcibly confronted. -- Yarnek of Excalbia, "The Savage Curtain", stardate 5906.5
Bug#1071272: linux: building the bookworm-backports armhf kernel causes OOM on buildds
Source: linux Version: 6.7.12-1~bpo12+1 Severity: serious X-Debbugs-CC: debian-...@lists.debian.org X-Debbugs-CC: d...@debian.org Hi, armhf builds of the bookworm-backports kernel appear to have led to outages on several buildds recently. Each of arm-ubc-04, arm-ubc-05 and arm-ubc-06 (QEMU ganeti guests) stopped responding after starting to build the kernel, and had to be rebooted. The build logs stop are various points - two at different points during drivers/net, and one during the dpkg-deb runs at the end of the build. The one common factor appears to be that the system logs on each machine show the OOM killer being invoked during the build, initially killing syslog but subsequently schroot and many system processes. Each buildd has 12GB of RAM and 120GB of swap available. The issue also seems to be specific to the armhf build - arm-ubc-06 recently successfully built the armel build of the same kernel version. Please let us know if you need any further information. Regards, Adam
Bug#1071184: Kernel 6.6 and 6.7 route-leak between VRF and default leads to Time to live exceeded
On Friday, 17 May 2024 15:08:17 CEST Development EasyNet wrote: > I will try. Meanwhile I was troubleshooting this issue for some time and > I notice a change in FRRouting between 9.1 and 10.0. > Before 10.0 FRRouting was installing the routes in kernel using the > destination interface of the route. Starting from 10.0 FRRouting is > installing all routes towards the VRF interface. > > Here is my bug reported on FRRouting: > https://github.com/FRRouting/frr/issues/15909 I have no (particular) knowledge about kernel routing or FRRouting, so I can't help with that aspect. But if the problem is resolved with 6.8.9, then that seems the easiest solution and means the underlying issue is fixed. If not, it's useful to know if there is a(n older) kernel version where it does work. But given there's also a FRR 9.x -> 10.x upgrade at play, I'm not so sure the problem is actually in the kernel. signature.asc Description: This is a digitally signed message part.
Bug#1071184: Kernel 6.6 and 6.7 route-leak between VRF and default leads to Time to live exceeded
Hi Diederik, I will try. Meanwhile I was troubleshooting this issue for some time and I notice a change in FRRouting between 9.1 and 10.0. Before 10.0 FRRouting was installing the routes in kernel using the destination interface of the route. Starting from 10.0 FRRouting is installing all routes towards the VRF interface. Here is my bug reported on FRRouting: https://github.com/FRRouting/frr/issues/15909 Example: Working scenario with FRR 9.0.2 and 9.1: |root@FRR01:/opt/Kitts/frr/9.0.2# ip nexthop show id 14 dev lo scope host proto zebra id 15 dev ens33 scope host proto zebra id 16 dev ens36 scope host proto zebra id 17 dev ens37 scope host proto zebra id 18 dev ens38 scope host proto zebra id 19 dev ens33 scope link proto zebra id 21 dev ens36 scope link proto zebra id 23 dev ens37 scope link proto zebra id 25 dev ens38 scope link proto zebra id 26 dev lo3 scope link proto zebra id 30 blackhole proto zebra id 31 blackhole proto zebra id 32 via 192.168.1.1 dev ens33 scope link proto zebra id 36 dev ens37 scope host proto zebra id 37 dev lo scope host proto zebra id 38 dev ens38 scope host proto zebra root@FRR01:/opt/Kitts/frr/9.0.2# ip nexthop show vrf red id 18 dev ens38 scope host proto zebra id 25 dev ens38 scope link proto zebra id 38 dev ens38 scope host proto zebra root@FRR01:/opt/Kitts/frr/9.0.2# ip route list 10.0.0.0/30 dev ens37 proto kernel scope link src 10.0.0.1 10.0.1.0/30 nhid 38 dev ens38 proto bgp metric 20 root@FRR01:/opt/Kitts/frr/9.0.2# ip route show table local local 10.0.0.1 dev ens37 proto kernel scope host src 10.0.0.1 broadcast 10.0.0.3 dev ens37 proto kernel scope link src 10.0.0.1 local 10.100.0.1 dev lo proto kernel scope host src 10.100.0.1 broadcast 10.100.0.1 dev lo proto kernel scope link src 10.100.0.1 local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1 root@FRR01:/opt/Kitts/frr/9.0.2# ip route show vrf red blackhole default proto static metric 20 10.0.0.0/30 nhid 36 dev ens37 proto bgp metric 20 10.0.1.0/30 dev ens38 proto kernel scope link src 10.0.1.1 10.100.0.1 nhid 37 dev lo proto bgp metric 20 root@FRR01:/opt/Kitts/frr/9.0.2# ip route show table red blackhole default proto static metric 20 10.0.0.0/30 nhid 36 dev ens37 proto bgp metric 20 10.0.1.0/30 dev ens38 proto kernel scope link src 10.0.1.1 local 10.0.1.1 dev ens38 proto kernel scope host src 10.0.1.1 broadcast 10.0.1.3 dev ens38 proto kernel scope link src 10.0.1.1 10.100.0.1 nhid 37 dev lo proto bgp metric 20 root@FRR01:/opt/Kitts/frr/9.0.2# ip route show vrf red blackhole default proto static metric 20 10.0.0.0/30 nhid 36 dev ens37 proto bgp metric 20 10.0.1.0/30 dev ens38 proto kernel scope link src 10.0.1.1 10.100.0.1 nhid 37 dev lo proto bgp metric 20 root@FRR01:/opt/Kitts/frr/9.0.2# ip rule list 0: from all lookup local 1000: from all lookup [l3mdev-table] 32766: from all lookup main 32767: from all lookup default root@FRR01:/opt/Kitts/frr/9.0.2# Non-working scenario with FRR 10.0: ||root@FRR01:/# ip nexthop show id 2 dev lo0 scope link proto zebra id 4 dev lo1 scope link proto zebra id 6 dev lo2 scope link proto zebra id 8 dev lo3 scope link proto zebra id 10 dev ens36 scope host proto zebra id 17 dev ens37 scope host proto zebra id 18 dev ens38 scope host proto zebra id 19 dev lo scope host proto zebra id 20 dev ens33 scope host proto zebra id 21 blackhole proto zebra id 22 blackhole proto zebra id 24 via 192.168.1.1 dev ens33 scope link proto zebra id 32 dev ens33 scope link proto zebra id 34 dev lo scope host proto zebra id 36 dev red scope host proto zebra root@FRR01:/# ip nexthop show vrf red id 18 dev ens38 scope host proto zebra id 25 dev ens38 scope link proto zebra| |root@FRR01:/# ip route list| |10.0.0.0/30 dev ens37 proto kernel scope link src 10.0.0.1 10.0.1.0/30 nhid 36 dev red proto bgp metric 20 root@FRR01:/# ip route show table local local 10.0.0.1 dev ens37 proto kernel scope host src 10.0.0.1 broadcast 10.0.0.3 dev ens37 proto kernel scope link src 10.0.0.1 local 10.100.0.1 dev lo proto kernel scope host src 10.100.0.1 broadcast 10.100.0.1 dev lo proto kernel scope link src 10.100.0.1 local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1 root@FRR01:/# ip route show vrf red blackhole default proto static metric 20 10.0.0.0/30 nhid 34 dev lo proto bgp metric 20 10.0.1.0/30 dev ens38 proto kernel scope link src 10.0.1.1 10.100.0.1 nhid 34 dev lo proto bgp metric 20 root@FRR01:/# ip route show table red blackhole default proto static metric 20 10.0.0.0/30 nhid 34 dev lo proto bgp metric 20 10.0.1.0/30 dev ens38 proto kernel scope link src 10.0.1.1 local 10.0.1.1 dev ens38 proto kernel scope host src 10.0.1.1 broadcast 10.0.1.3 dev ens38 p
Processed: Re: Kernel 6.6 and 6.7 route-leak between VRF and default leads to Time to live exceeded
Processing control commands: > tag -1 moreinfo Bug #1071184 [src:linux] Kernel 6.6 and 6.7 route-leak between VRF and default leads to Time to live exceeded Added tag(s) moreinfo. -- 1071184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071184: Kernel 6.6 and 6.7 route-leak between VRF and default leads to Time to live exceeded
Control: tag -1 moreinfo On 15 May 2024 16:08:27 +0200 Development EasyNet wrote: > Package: linux-image > Version: 6.6.15-2 and 6.7.12-1 > > I'm facing for some time a strange behavior of the route-leak. It happen > on both IPv4 and IPv6. > Configuration used: Debian Trixie, Kernel 6.7.12 with FRRouting 10.1 - git > VRF: internet > Default: just local management Sid recently got a 6.8.9 kernel, can you test whether that fixes the issue? signature.asc Description: This is a digitally signed message part.
Processed: reassign 1071184 to src:linux, found 1071184 in 6.7.12-1, reassign 1071174 to src:onionshare ...
Processing commands for cont...@bugs.debian.org:
> reassign 1071184 src:linux 6.6.15-2
Bug #1071184 [linux-image] Kernel 6.6 and 6.7 route-leak between VRF and
default leads to Time to live exceeded
Warning: Unknown package 'linux-image'
Bug reassigned from package 'linux-image' to 'src:linux'.
Ignoring request to alter found versions of bug #1071184 to the same values
previously set
Ignoring request to alter fixed versions of bug #1071184 to the same values
previously set
Bug #1071184 [src:linux] Kernel 6.6 and 6.7 route-leak between VRF and default
leads to Time to live exceeded
Marked as found in versions linux/6.6.15-2.
> found 1071184 6.7.12-1
Bug #1071184 [src:linux] Kernel 6.6 and 6.7 route-leak between VRF and default
leads to Time to live exceeded
Marked as found in versions linux/6.7.12-1.
> reassign 1071174 src:onionshare 2.6.2-1
Bug #1071174 [src:nionshare] onionshare: runtime dependency on cython
Warning: Unknown package 'src:nionshare'
Bug reassigned from package 'src:nionshare' to 'src:onionshare'.
No longer marked as found in versions nionshare/2.6.2-1.
Ignoring request to alter fixed versions of bug #1071174 to the same values
previously set
Bug #1071174 [src:onionshare] onionshare: runtime dependency on cython
Marked as found in versions onionshare/2.6.2-1.
> close 1062444
Bug #1062444 [src:ima-evm-utils] ima-evm-utils: NMU diff for 64-bit time_t
transition
Marked Bug as done
> reassign 1071125 python3-donfig 0.8.1+dfsg-2
Bug #1071125 {Done: Antonio Valentino }
[python3-donfig,python3-nabu] python3-donfig and python3-nabu have an
undeclared file conflict on /usr/lib/python3/dist-packages/doc/conf.py
Bug reassigned from package 'python3-donfig,python3-nabu' to 'python3-donfig'.
No longer marked as found in versions 0.8.1+dfsg-2.
No longer marked as fixed in versions donfig/0.8.1+dfsg-3.
Bug #1071125 {Done: Antonio Valentino }
[python3-donfig] python3-donfig and python3-nabu have an undeclared file
conflict on /usr/lib/python3/dist-packages/doc/conf.py
Marked as found in versions donfig/0.8.1+dfsg-2.
> fixed 1071125 0.8.1+dfsg-3
Bug #1071125 {Done: Antonio Valentino }
[python3-donfig] python3-donfig and python3-nabu have an undeclared file
conflict on /usr/lib/python3/dist-packages/doc/conf.py
Marked as fixed in versions donfig/0.8.1+dfsg-3.
> retitle 1071125 python3-donfig: ships
> /usr/lib/python3/dist-packages/doc/conf.py
Bug #1071125 {Done: Antonio Valentino }
[python3-donfig] python3-donfig and python3-nabu have an undeclared file
conflict on /usr/lib/python3/dist-packages/doc/conf.py
Changed Bug title to 'python3-donfig: ships
/usr/lib/python3/dist-packages/doc/conf.py' from 'python3-donfig and
python3-nabu have an undeclared file conflict on
/usr/lib/python3/dist-packages/doc/conf.py'.
> reassign 1060134 src:busybox 1:1.30.1-6
Bug #1060134 {Done: Michael Tokarev } [kmod-udeb,busybox-udeb]
kmod-udeb vs busybox-udeb: agree on who ships depmod
Bug reassigned from package 'kmod-udeb,busybox-udeb' to 'src:busybox'.
No longer marked as found in versions kmod/28-1 and busybox/1:1.30.1-6.
No longer marked as fixed in versions busybox/1:1.36.1-7.
Bug #1060134 {Done: Michael Tokarev } [src:busybox] kmod-udeb
vs busybox-udeb: agree on who ships depmod
Marked as found in versions busybox/1:1.30.1-6.
> fixed 1060134 1:1.36.1-7
Bug #1060134 {Done: Michael Tokarev } [src:busybox] kmod-udeb
vs busybox-udeb: agree on who ships depmod
Marked as fixed in versions busybox/1:1.36.1-7.
> affects 1060134 + src:kmod
Bug #1060134 {Done: Michael Tokarev } [src:busybox] kmod-udeb
vs busybox-udeb: agree on who ships depmod
Added indication that 1060134 affects src:kmod
> fixed 1063177 1.5.0+dfsg1-4
Bug #1063177 {Done: Benjamin Drung } [src:osmo-hlr]
osmo-hlr: NMU diff for 64-bit time_t transition
Marked as fixed in versions osmo-hlr/1.5.0+dfsg1-4.
> fixed 1062984 1.18-1
Bug #1062984 {Done: Benjamin Drung } [src:timblserver]
timblserver: NMU diff for 64-bit time_t transition
Marked as fixed in versions timblserver/1.18-1.
> fixed 1062860 3.10-1
Bug #1062860 {Done: Graham Inggs } [src:mbt] mbt: NMU diff
for 64-bit time_t transition
Marked as fixed in versions mbt/3.10-1.
> notfixed 1062511 4.4.4-15.1
Bug #1062511 {Done: mwhud...@debian.org} [src:dx] dx: NMU diff for 64-bit
time_t transition
The source 'dx' and version '4.4.4-15.1' do not appear to match any binary
packages
No longer marked as fixed in versions 4.4.4-15.1.
> fixed 1062511 1:4.4.4-15.1
Bug #1062511 {Done: mwhud...@debian.org} [src:dx] dx: NMU diff for 64-bit
time_t transition
Marked as fixed in versions dx/1:4.4.4-15.1.
> tags 1070980 + sid trixie
Bug #1070980 {Done: Andreas Tille } [src:libamplsolver]
libamplsolver: FTBFS on architectures calling fedisableexcept (ppc64el, s390x,
riscv64, ...)
Added tag(s) trixie and sid.
> tags 1071017 + sid trixie
Bug #1071017 [obs-source-copy] FTBFS: source-copy.cpp:615:31: error: ‘void
obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is
deprecated [-Werror=d
Bug#1071263: linux-image-6.8.9-amd64: Vulkan applications crash on computers using amdgpu
Control: forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/3343 signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#1071263: linux-image-6.8.9-amd64: Vulkan applications crash on computers using amdgpu
Processing control commands: > forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/3343 Bug #1071263 [linux-image-6.8.9-amd64] linux-image-6.8.9-amd64: Vulkan applications crash on computers using amdgpu Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/drm/amd/-/issues/3343'. -- 1071263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071263: linux-image-6.8.9-amd64: Vulkan applications crash on computers using amdgpu
Package: linux-image-6.8.9-amd64 Version: 6.8.9-1 Severity: important Tags: patch upstream X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, Vulkan applications will crash when using version 6.8.9 of the linux kernel on systems using amd graphics. Upstream have provided a patch [1] that fixes this issue. There's also a bug report upstream as well [2] for more details. I've also provided a link to the kernel specific patch [3]. 6.8.10 also has this issue fixed. [1] https://patchwork.freedesktop.org/patch/593130/ [2] https://gitlab.freedesktop.org/drm/amd/-/issues/3343 [3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c?id=37447cc246293ab6a0bbeb091ece95f57adcc845 -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.8.9-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod32-1 ii linux-base 4.9 Versions of packages linux-image-6.8.9-amd64 recommends: ii apparmor 3.0.13-2 Versions of packages linux-image-6.8.9-amd64 suggests: ii debian-kernel-handbook 1.0.21 ii firmware-linux-free 20200122-4 ii grub-efi-amd64 2.12-2 pn linux-doc-6.8
Re: ocfs2_dlmfs missing from the cloud kernel
On Fri, May 17, 2024 at 12:31:51PM +0200, Thomas Goirand wrote: > how do I change this? You install the non-cloud kernel. Bastian -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, "Day of the Dove", stardate unknown
ocfs2_dlmfs missing from the cloud kernel
Hi, The module ocfs2_dlmfs may be use to have a filesystem shared with 2 VMs (using for example OpenStack Cinder multi-attach). It's there in Ubuntu, in the "normal" kernel, but not in the Debian cloud kernel. Would it be possible to *not* strip-down this module in the cloud kernel please ? In the source package of the kernel, I can read in: debian/config/config.cloud: ## file: fs/ocfs2/Kconfig ## # CONFIG_OCFS2_FS is not set how do I change this? Cheers, Thomas Goirand (zigo)
Bug#1069077: rockpro64: multiple kernel oops and frequent boot failures
On Friday, 17 May 2024 03:36:35 CEST Forest wrote: > A git bisect reveals it to be fixed by this commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id= > f7a59018953910032231c0a019208c4b0a4a8bc3 > > maple_tree: make mas_erase() more robust > > > > mas_erase() may not deal correctly with all maple states. Make the > > function more robust by ensuring the state is in one of the two acceptable > > states. Kernel 6.8.9 has recently been uploaded to Unstable which has that commit. Can you verify that it indeed fixes this bug? signature.asc Description: This is a digitally signed message part.
Bug#1071258: linux-image-6.1.0-21-amd64: Mouse, trackpad, keyboard behave inconsistently
Package: src:linux Version: 6.1.90-1 Severity: important X-Debbugs-Cc: casa...@acm.org The system information associated to the bug MUST be taken from bug report 1071236. The reason: the problem depends on the kernel version; the present bug report is sent from the problematic computer, but running a different kernel than the one experiencing trouble. The problem: After uprading my laptop (Lenovo L570) from Debian 11 to Debian 12, the system appears to handle input devices (keyboard, trackpad, mouse) inconsistently. Initially, everything works fine, but progressively (after a few minutes) symptoms such as those listed below occur with increasing frequency, till the system is nearly unusable (after about 20 to 30 minutes): 1) When typing text, the cursor suddenly relocates to another position, typically several lines upwards. 2) The mouse buttons have no effect (e.g. to close a window, or to activate a menu entry in an application or the taskbar, or to move to a different workspace). It is then necessary to use the buttons on the trackpad -- then the mouse functions again for a short while. 3) When resizing a window with the mouse, the handles have either no effect at all, or cannot be released to stop resizing. Again, clicking on the trackpad "resets" the mouse. 4) Contextual menus suddenly pop up without having been invoked. Clicking somewhere is required to make them disappear. 5) When using a terminal window, the keyboard suddenly stops working. I have found no other solution than killing the window and reopening another one. 6) On a variety of applications (terminal window, browser, editor), the system sets itself in a state as if the user wanted to make a copy of a text region. Moving the mouse of trackpad selects a portion of the text on the screen. 7) Buttons on mouse and trackpad stop operating; shutting down the computer can only be achieved with a forced shutdown (long press on the on/off hardware button). The problem takes place with Gnome, classic or not, on X.org or not, and also on XFCE. Two different mice were used, with the same effect. It always looks as if linux at times ceases recognizing events from input devices, and at other times generates random phantom events. Other machines (3 models from 2 other manufacturers) previously upgraded from Debian 11 to Debian 12 do not exhibit this problem. Attempted workaround: booting the L570 (upgraded to Debian 12) with the kernel of its previous Debian 11 installation. Thus, when relying upon kernel linux-image-5.10.0-29-amd64 instead of linux-image-6.1.0-21-amd64 mouse, trackpad, and keyboard work again without problem. I welcome any hint at what could have caused such a behaviour, and any suggestion as to how to get rid of it. Could it be that a package became somehow corrupted during installation? In which case, how to detect which one and how to correct it? Many thanks in advance -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 20J8001BMZ product_version: ThinkPad L570 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: N1XET84W (1.62 ) board_vendor: LENOVO board_name: 20J8001BMZ board_version: Not Defined ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:2249] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2249] 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: i915 Kernel modules: i915 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [17aa:2249] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:2249] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Stat
linux-signed-arm64_6.8.9+1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 May 2024 01:42:10 +0200 Source: linux-signed-arm64 Architecture: source Version: 6.8.9+1 Distribution: sid Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Changes: linux-signed-arm64 (6.8.9+1) unstable; urgency=medium . * Sign kernel from linux 6.8.9-1 . * New upstream release: https://kernelnewbies.org/Linux_6.8 * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.1 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.2 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.3 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.4 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.5 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.6 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.7 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.8 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.9 . [ Diederik de Haas ] * d/templates/main.control.in: Add python3-dacite as linux-support Depends * [armhf] Improve Tegra Chromebook support (Closes: #1061680) - [armhf] drivers/net/wireless/marvell/mwifiex: Enable MWIFIEX and MWIFIEX_SDIO as modules - [armhf] drivers/power/supply: Enable CHARGER_BQ24735 as module - [armhf] drivers/hwmon: Enable SENSORS_LM90 as module - [armhf] drivers/media/cec/platform: Enable CEC_TEGRA as module * drivers/thermal: Enable THERMAL_NETLINK * [amd64] drivers/tee/amdtee: Enable AMDTEE as module * [amd64] drivers/platform/x86/amd/pmf: Enable AMD_PMF as module (Closes: #1063161) * Update to 6.8.8: - Drop patches applied upstream: - "Partially revert 'MIPS: Add -Werror to arch/mips/Kbuild'" - "platform/x86: p2sb: On Goldmont only cache P2SB and SPI devfn BAR" - "driver core: Emit reason for pending deferred probe" - "x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set" - "Documentation/hw-vuln: Add documentation for RFDS" - "x86/rfds: Mitigate Register File Data Sampling (RFDS)" - "KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests" - Refresh patches: - Adjust context in "Tweak gitignore for Debian pkg-kernel using git" - Adjust context in "Documentation: Drop sphinx version check" - Adjust context in "firmware: Remove redundant log messages from drivers" - Adjust context in "yama: Disable by default" - Adjust context in "btrfs: warn about RAID5/6 being experimental at mount time" - Adjust context in "x86: Make x32 syscall support conditional on a kernel parameter" - Adjust context in "efi: Lock down the kernel if booted in secure boot mode" - Adjust context in "Export symbols needed by Android drivers" * d/copyright: Exclude 'action-ebpf' as that's a binary blob * d/installer/modules: Remove modules removed from upstream kernel * d/config: Update with the help of kconfigeditor2: - crypto: Remove CRYPTO_CFB and CRYPTO_OFB - drivers/gpu/drm: Remove DRM_LEGACY - drivers/md: Remove MD_FAULTY, MD_LINEAR and MD_MULTIPATH - [alpha,hppa,mips.malta,powerpc,x86] drivers/net/wireless/atmel: Remove ATMEL, PCI_ATMEL and PCMCIA_ATMEL - drivers/net/wireless/cisco: Remove WLAN_VENDOR_CISCO and AIRO - [alpha,hppa,powerpc,x86] drivers/net/wireless/cisco: Remove AIRO_CS - drivers/net/wireless/intersil/hostap: Remove HOSTAP, HOSTAP_FIRMWARE, HOSTAP_FIRMWARE_NVRAM, HOSTAP_PLX, HOSTAP_PCI and HOSTAP_CS - drivers/net/wireless/intersil/orinoco: Remove HERMES_PRISM, HERMES_CACHE_FW_ON_INIT, NORTEL_HERMES, PCMCIA_SPECTRUM and ORINOCO_USB - [alpha,hppa,mips.malta,powerpc,x86] drivers/net/wireless/intersil/orinoco: Remove HERMES, APPLE_AIRPORT, PLX_HERMES, TMD_HERMES, PCI_HERMES, PCMCIA_HERMES - drivers/net/wireless/legacy: Remove USB_NET_RNDIS_WLAN - [alpha,hppa,powerpc,x86] drivers/net/wireless/legacy: Remove PCMCIA_RAYCS and PCMCIA_WL3501 - drivers/net/wireless/marvell/libertas: Remove LIBERTAS_CS - [alpha,hppa,mips.malta,powerpc,x86] drivers/net/wireless/zydas: Remove USB_ZD1201 - drivers/video/fbdev: Remove FB_INTEL_DEBUG FB_INTEL_I2C - [armhf,arm64] drivers/video/fbdev: Remove FB_ARMCLCD - [cloud,x86] drivers/video/fbdev: Remove FB_CARILLO_RANCH and FB_LE80578 - [x86] drivers/video/fbdev: Remove FB_INTEL - fs/fscache: Change FSCACHE to `y` - mm: Remove SLAB_DEPRECATED and SLUB - net/bpfilter: Remove BPFILTER * [rt] Update to 6.8.2-rt11 * [rt] Drop patches applied in 6.8.6: - "printk: For @suppress_panic_printk check for other CPU in panic" - "panic: Flush kernel log buffer at the end" - "dump_stack: Do not get cpu_sync for
linux-signed-amd64_6.8.9+1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 May 2024 01:42:10 +0200 Source: linux-signed-amd64 Architecture: source Version: 6.8.9+1 Distribution: sid Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Changes: linux-signed-amd64 (6.8.9+1) unstable; urgency=medium . * Sign kernel from linux 6.8.9-1 . * New upstream release: https://kernelnewbies.org/Linux_6.8 * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.1 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.2 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.3 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.4 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.5 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.6 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.7 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.8 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8.9 . [ Diederik de Haas ] * d/templates/main.control.in: Add python3-dacite as linux-support Depends * [armhf] Improve Tegra Chromebook support (Closes: #1061680) - [armhf] drivers/net/wireless/marvell/mwifiex: Enable MWIFIEX and MWIFIEX_SDIO as modules - [armhf] drivers/power/supply: Enable CHARGER_BQ24735 as module - [armhf] drivers/hwmon: Enable SENSORS_LM90 as module - [armhf] drivers/media/cec/platform: Enable CEC_TEGRA as module * drivers/thermal: Enable THERMAL_NETLINK * [amd64] drivers/tee/amdtee: Enable AMDTEE as module * [amd64] drivers/platform/x86/amd/pmf: Enable AMD_PMF as module (Closes: #1063161) * Update to 6.8.8: - Drop patches applied upstream: - "Partially revert 'MIPS: Add -Werror to arch/mips/Kbuild'" - "platform/x86: p2sb: On Goldmont only cache P2SB and SPI devfn BAR" - "driver core: Emit reason for pending deferred probe" - "x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set" - "Documentation/hw-vuln: Add documentation for RFDS" - "x86/rfds: Mitigate Register File Data Sampling (RFDS)" - "KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests" - Refresh patches: - Adjust context in "Tweak gitignore for Debian pkg-kernel using git" - Adjust context in "Documentation: Drop sphinx version check" - Adjust context in "firmware: Remove redundant log messages from drivers" - Adjust context in "yama: Disable by default" - Adjust context in "btrfs: warn about RAID5/6 being experimental at mount time" - Adjust context in "x86: Make x32 syscall support conditional on a kernel parameter" - Adjust context in "efi: Lock down the kernel if booted in secure boot mode" - Adjust context in "Export symbols needed by Android drivers" * d/copyright: Exclude 'action-ebpf' as that's a binary blob * d/installer/modules: Remove modules removed from upstream kernel * d/config: Update with the help of kconfigeditor2: - crypto: Remove CRYPTO_CFB and CRYPTO_OFB - drivers/gpu/drm: Remove DRM_LEGACY - drivers/md: Remove MD_FAULTY, MD_LINEAR and MD_MULTIPATH - [alpha,hppa,mips.malta,powerpc,x86] drivers/net/wireless/atmel: Remove ATMEL, PCI_ATMEL and PCMCIA_ATMEL - drivers/net/wireless/cisco: Remove WLAN_VENDOR_CISCO and AIRO - [alpha,hppa,powerpc,x86] drivers/net/wireless/cisco: Remove AIRO_CS - drivers/net/wireless/intersil/hostap: Remove HOSTAP, HOSTAP_FIRMWARE, HOSTAP_FIRMWARE_NVRAM, HOSTAP_PLX, HOSTAP_PCI and HOSTAP_CS - drivers/net/wireless/intersil/orinoco: Remove HERMES_PRISM, HERMES_CACHE_FW_ON_INIT, NORTEL_HERMES, PCMCIA_SPECTRUM and ORINOCO_USB - [alpha,hppa,mips.malta,powerpc,x86] drivers/net/wireless/intersil/orinoco: Remove HERMES, APPLE_AIRPORT, PLX_HERMES, TMD_HERMES, PCI_HERMES, PCMCIA_HERMES - drivers/net/wireless/legacy: Remove USB_NET_RNDIS_WLAN - [alpha,hppa,powerpc,x86] drivers/net/wireless/legacy: Remove PCMCIA_RAYCS and PCMCIA_WL3501 - drivers/net/wireless/marvell/libertas: Remove LIBERTAS_CS - [alpha,hppa,mips.malta,powerpc,x86] drivers/net/wireless/zydas: Remove USB_ZD1201 - drivers/video/fbdev: Remove FB_INTEL_DEBUG FB_INTEL_I2C - [armhf,arm64] drivers/video/fbdev: Remove FB_ARMCLCD - [cloud,x86] drivers/video/fbdev: Remove FB_CARILLO_RANCH and FB_LE80578 - [x86] drivers/video/fbdev: Remove FB_INTEL - fs/fscache: Change FSCACHE to `y` - mm: Remove SLAB_DEPRECATED and SLUB - net/bpfilter: Remove BPFILTER * [rt] Update to 6.8.2-rt11 * [rt] Drop patches applied in 6.8.6: - "printk: For @suppress_panic_printk check for other CPU in panic" - "panic: Flush kernel log buffer at the end" - "dump_stack: Do not get cpu_sync for
