Bug#1006477: Still broken in latest bullseye backports kernel but not in vanilla kernel

I downloaded the vanilla 5.16.11 kernel from kernel.org, compiled it and installed it. This time the resulting kernel worked flawlessly (well, almost). The machine boots normally and the USB card is working great. Both the ethernet ports and USB ports in it are functioning well. The only issue I

linux-signed-i386_5.16.18+1_source.changes is NEW

Mapping sid to unstable. binary:acpi-modules-5.16.0-6-686-di is NEW. binary:acpi-modules-5.16.0-6-686-pae-di is NEW. binary:ata-modules-5.16.0-6-686-di is NEW. binary:ata-modules-5.16.0-6-686-pae-di is NEW. binary:btrfs-modules-5.16.0-6-686-di is NEW. binary:btrfs-modules-5.16.0-6-686-pae-di is

Processing of linux-signed-i386_5.16.18+1_source.changes

linux-signed-i386_5.16.18+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_5.16.18+1.dsc linux-signed-i386_5.16.18+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1008692: refcount_t: underflow; use-after-free. in dmesg output

Package: src:linux Version: 5.17.1-1~exp1 Severity: normal X-Debbugs-Cc: hba...@gmail.com Dear Maintainer, * What led up to the situation? Log in to Gnome desktop and open browser Trigger overview mode (mouse to top left corner) Grab Firefox titlebar and try to move to next right desktop

Bug#1008681: linux-image-5.16.0-5-amd64: WARNING: CPU: 1 PID: 1061 at fs/nfsd/nfs4state.c:5891 nfs4_preprocess_stateid_op+0x600/0x690 [nfsd]

On Wednesday, 30 March 2022 19:49:03 CEST Laurent Bonnaud wrote: > Thanks for looking at the problem and pointing to this commit! > > The affected system is a production system and a lot of people depend on it. > Therefore I am not comfortable to run a self-patched kernel on it, and I > would

linux-signed-i386_5.17.1+1~exp1_source.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Mar 2022 09:16:17 +0200 Source: linux-signed-i386 Architecture: source Version: 5.17.1+1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Kernel Team Changed-By: Bastian Blank Changes:

linux-signed-amd64_5.16.18+1_source.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Mar 2022 22:46:53 +0200 Source: linux-signed-amd64 Architecture: source Version: 5.16.18+1 Distribution: sid Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes:

Bug#1008681: linux-image-5.16.0-5-amd64: WARNING: CPU: 1 PID: 1061 at fs/nfsd/nfs4state.c:5891 nfs4_preprocess_stateid_op+0x600/0x690 [nfsd]

On Wednesday, 30 March 2022 17:24:35 CEST Laurent Bonnaud wrote: > Package: src:linux > Version: 5.16.14-1 > > this system is used as a NFS server for about 100 clients. After several > days of uptime I saw the following WARNING in the kernel log Part of the commit msg of

linux-signed-amd64_5.16.18+1_source.changes is NEW

Mapping sid to unstable. binary:acpi-modules-5.16.0-6-amd64-di is NEW. binary:ata-modules-5.16.0-6-amd64-di is NEW. binary:btrfs-modules-5.16.0-6-amd64-di is NEW. binary:cdrom-core-modules-5.16.0-6-amd64-di is NEW. binary:crc-modules-5.16.0-6-amd64-di is NEW.

Processing of linux-signed-amd64_5.16.18+1_source.changes

linux-signed-amd64_5.16.18+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_5.16.18+1.dsc linux-signed-amd64_5.16.18+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux-signed-i386_5.17.1+1~exp1_source.changes is NEW

binary:acpi-modules-5.17.0-trunk-686-di is NEW. binary:acpi-modules-5.17.0-trunk-686-pae-di is NEW. binary:ata-modules-5.17.0-trunk-686-di is NEW. binary:ata-modules-5.17.0-trunk-686-pae-di is NEW. binary:btrfs-modules-5.17.0-trunk-686-di is NEW. binary:btrfs-modules-5.17.0-trunk-686-pae-di is

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

Hi, Diederik de Haas wrote: > I (still) think the most likely culprit is in the ATA/disk subsystem, but the > progress stalled when the request came in to apply custom patches to the > kernel (which IIRC was primarily to gather further information). Yep, and that's still on my TODO list.

Processing of linux-signed-i386_5.17.1+1~exp1_source.changes

linux-signed-i386_5.17.1+1~exp1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_5.17.1+1~exp1.dsc linux-signed-i386_5.17.1+1~exp1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux-signed-amd64_5.17.1+1~exp1_source.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Mar 2022 09:16:17 +0200 Source: linux-signed-amd64 Architecture: source Version: 5.17.1+1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Kernel Team Changed-By: Bastian Blank Changes:

linux-signed-arm64_5.17.1+1~exp1_source.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Mar 2022 09:16:17 +0200 Source: linux-signed-arm64 Architecture: source Version: 5.17.1+1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Kernel Team Changed-By: Bastian Blank Changes:

Bug#999551: Support Landlock by default in Debian kernels

I support enabling this in default Debian kernels. It would allow application developers to use landlock sandboxing while developing programs. By not enabling it, developers have to build custom kernels and ask that their customers do this as well to run landlock protected programs. It should not

linux-signed-arm64_5.17.1+1~exp1_source.changes is NEW

binary:ata-modules-5.17.0-trunk-arm64-di is NEW. binary:btrfs-modules-5.17.0-trunk-arm64-di is NEW. binary:cdrom-core-modules-5.17.0-trunk-arm64-di is NEW. binary:crc-modules-5.17.0-trunk-arm64-di is NEW. binary:crypto-dm-modules-5.17.0-trunk-arm64-di is NEW.

Processing of linux-signed-arm64_5.17.1+1~exp1_source.changes

linux-signed-arm64_5.17.1+1~exp1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_5.17.1+1~exp1.dsc linux-signed-arm64_5.17.1+1~exp1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

On woensdag 30 maart 2022 08:38:30 CEST Salvatore Bonaccorso wrote: > Do we have a report upstream already about this issue? What I tried to achieve with my involvement is determining where (exactly) the problem is to determine which upstream to contact. I (still) think the most likely culprit

linux-signed-amd64_5.17.1+1~exp1_source.changes is NEW

binary:acpi-modules-5.17.0-trunk-amd64-di is NEW. binary:ata-modules-5.17.0-trunk-amd64-di is NEW. binary:btrfs-modules-5.17.0-trunk-amd64-di is NEW. binary:cdrom-core-modules-5.17.0-trunk-amd64-di is NEW. binary:crc-modules-5.17.0-trunk-amd64-di is NEW.

Processing of linux-signed-amd64_5.17.1+1~exp1_source.changes

linux-signed-amd64_5.17.1+1~exp1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_5.17.1+1~exp1.dsc linux-signed-amd64_5.17.1+1~exp1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: limit source to linux, tagging 1008501

Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1008501 + pending Bug #1008501 [linux-headers-5.17.0-rc8-common] pahole-flags.sh: inaccessible or not

linux_5.16.18-1_source.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Mar 2022 22:46:53 +0200 Source: linux Architecture: source Version: 5.16.18-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1008122 Changes:

Bug#1008656: linux-image-5.10.0-13-cloud-amd64: Consider AHCI SATA support in cloud kernels

Package: src:linux Version: 5.10.106-1 Severity: wishlist Dear Maintainer, While experimenting with oVirt and cloud-init I noticed that providing user-data scripts was possible with the "generic" cloud image but not the "genericcloud" variant. So I tried to reproduce it with `virt-install` to

Bug#1008122: marked as done (linux-image-5.16.0-5-amd64: no sound on vostro 14 3000)

Your message dated Wed, 30 Mar 2022 08:10:08 + with message-id and subject line Bug#1008122: fixed in linux 5.16.18-1 has caused the Debian Bug report #1008122, regarding linux-image-5.16.0-5-amd64: no sound on vostro 14 3000 to be marked as done. This means that you claim that the problem

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

Am Mi., 30. Mär. 2022, um 08:38 +0200 schrieb Salvatore Bonaccorso : [...] > Thanks for constantly testing the new versions (there is 5.16.18-1 > upcoming btw, or 5.17.1 in experiemntal). I'm just testing whatever is pulled in automatically by linux-image-686 (in bookworm). > > Do we have a

Processed: severity of 1008497 is important

Processing commands for cont...@bugs.debian.org: > severity 1008497 important Bug #1008497 [src:linux] linux-image-5.10.0-13-arm64: 5.10.0-13-arm64 gets stuck after loading ramdisk on VMWareFusion under M1. 5.10.0-12-arm64 works. Severity set to 'important' from 'critical' > thanks Stopping

Processed: Re: Bug#1008299: linux-image-5.10.0-12-amd64: Last update of linux-image-5.10.0-12-amd64 break encrypted network on docker

Processing control commands: > tags -1 + confirmed pending Bug #1008299 [src:linux] linux-image-5.10.0-12-amd64: Last update of linux-image-5.10.0-12-amd64 break encrypted network on docker Added tag(s) confirmed and pending. -- 1008299:

Bug#1008299: linux-image-5.10.0-12-amd64: Last update of linux-image-5.10.0-12-amd64 break encrypted network on docker

Control: tags -1 + confirmed pending On Sat, Mar 26, 2022 at 10:54:39AM +, Ulrich Vandenhekke wrote: > Package: src:linux > Version: 5.10.103-1 > Severity: important > X-Debbugs-Cc: ulrich@gmail.com > > Dear Maintainer, > > After upgrading the last version of

Processed: reassign 1008142 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 1008142 src:linux 5.16.12-1 Bug #1008142 {Done: Jiri Kastner } [linux-image-arm64] enable CONFIG_OF_OVERLAY Bug reassigned from package 'linux-image-arm64' to 'src:linux'. No longer marked as found in versions

Processed: reassign 1007864 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 1007864 src:linux 4.19.232-1 Bug #1007864 [linux-source-4.19] linux-source-4.19: Kernel compilation error when CONFIG_BPF_SYSCALL not set Bug reassigned from package 'linux-source-4.19' to 'src:linux'. No longer marked as found in

Bug#913310: marked as done (nfs-common: Systemd does not correctly read /etc/default/nfs-common)

Your message dated Wed, 30 Mar 2022 08:34:24 +0200 with message-id and subject line Re: Bug#913310: nfs-common: Systemd does not correctly read /etc/default/nfs-common has caused the Debian Bug report #913310, regarding nfs-common: Systemd does not correctly read /etc/default/nfs-common to be

Processed: closing 1006998

Processing commands for cont...@bugs.debian.org: > close 1006998 Bug #1006998 [linux-source-4.19] Kernel 4.19 compilation from source fails with error Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1006998:

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

Hi, On Sat, Mar 26, 2022 at 05:19:03PM +0100, Petra Rübe-Pugliese wrote: > On Sat 12 Mar 2022 at 21:31:38 +0100 Petra R.-P. > wrote: > > On Sat 05 Mar 2022 at 17:59:51 +0100 Petra R.-P. > > wrote: > > [...] > > > > The error persists also in linux-image-5.16.0-4-686 (5.16.12-1) . > >

Processed: tagging 913310

Processing commands for cont...@bugs.debian.org: > tags 913310 - moreinfo Bug #913310 [nfs-common] nfs-common: Systemd does not correctly read /etc/default/nfs-common Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 913310: