Processed: reassign 1013870 to src:linux

[Debian Bug Tracking System]

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

> reassign 1013870 src:linux
Bug #1013870 [linux-image-amd64] Missing NHPOLY1305 configs
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.18.5+1.
Ignoring request to alter fixed versions of bug #1013870 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1013739 to src:linux

[Debian Bug Tracking System]

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

> reassign 1013739 src:linux 5.10.120-1
Bug #1013739 [linux-image-amd64] linux-image-amd64: Boots with totally blank 
screens on docking stations; applies to all kernel image versions
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.10.120+1.
Ignoring request to alter fixed versions of bug #1013739 to the same values 
previously set
Bug #1013739 [src:linux] linux-image-amd64: Boots with totally blank screens on 
docking stations; applies to all kernel image versions
Marked as found in versions linux/5.10.120-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1014352 to lvm2, forcibly merging 1014314 1014352

[Debian Bug Tracking System]

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

> reassign 1014352 lvm2
Bug #1014352 [initramfs-tools] dpkg: error processing package initramfs-tools 
(--configure)
Bug reassigned from package 'initramfs-tools' to 'lvm2'.
No longer marked as found in versions initramfs-tools/0.141.
Ignoring request to alter fixed versions of bug #1014352 to the same values 
previously set
> forcemerge 1014314 1014352
Bug #1014314 {Done: Bastian Blank } [lvm2] lvm2: Missing 
69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail
Bug #1014353 {Done: Bastian Blank } [lvm2] lvm2: initramfs 
hook fails due to missing 69-lvm-metad.rules
Bug #1014352 [lvm2] dpkg: error processing package initramfs-tools (--configure)
Severity set to 'serious' from 'important'
Marked Bug as done
Marked as fixed in versions lvm2/2.03.15-2.
Marked as found in versions lvm2/2.03.15-1.
Bug #1014353 {Done: Bastian Blank } [lvm2] lvm2: initramfs 
hook fails due to missing 69-lvm-metad.rules
Merged 1014314 1014352 1014353
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1014314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014314
1014352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014352
1014353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1014272: src:linux: sign-file: correct error handling

[Salvatore Bonaccorso]

Hi Ansgar,

On Sun, Jul 03, 2022 at 11:47:51AM +0200, Ansgar wrote:
> Source: linux
> Version: 5.18.5-1
> Severity: normal
> Tags: upstream
> Control: found -1 4.19.208-1 5.10.84-1
> 
> The functions CMS_final, i2d_CMS_bio_stream, i2d_PKCS7_bio and
> BIO_free all return 1 for success or 0 for failure. The old check
> for a value less than 0 would never catch an error.
> 
> I tried signing a kernel module with the patched sign-file and that
> still worked.

Can you forward your patch to upstream?

Regards,
Salvatore

Bug#1012741: Reproduced

[Matthias Maier]

Dear all,

I think this is an issue with the Hardware token and not with the
userland libraries and tools.

More specifically, I am able to reproduce this bug with

Device type: YubiKey 4
Firmware version: 4.3.7

on a Gentoo system, whereas "reproduce.sh" succeeds with
a newer Yubikey:

Device type: YubiKey 5 NFC
Firmware version: 5.4.3

Software and versions:

openssl-1.1.1o
yubico-piv-tool-2.3.0

Best,
Matthias

Bug#1014394: linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Diederik de Haas]

On Tuesday, 5 July 2022 21:55:54 CEST Michael wrote:
> and for your request:

Sorry I wasn't clear in my request.

> > and eventually guest processes start to randomly crash, e.g.:
> > 
> > Jun 30 20:17:01 vmguest kernel: traps: sh[250946] general protection fault
> > ip:7fb0c341708e sp:7ffec3154378 error:0 in
> > libc-2.31.so[7fb0c33a6000+14b000]
> > Jul 01 00:00:02 vmguest kernel: traps: hostname[253617] general protection
> > fault ip:7f905f2b24a6 sp:7fff44a30e30 error:0 in
> > libc-2.31.so[7f905f299000+14b000]
> > Jul 01 00:53:01 vmguest kernel: traps: wget[254290] general protection
> > fault ip:7f934bc23fda sp:7ffd716954d0 error:0 in
> > libtasn1.so.6.6.0[7f934bc1a000+c000]

I assumed these errors occurred in 1 boot session and having the FULL dmesg/
kern.log from *that* session would be useful.
Don't 'grep' the messages which you think are relevant. Often times there are 
other messages which give important clues to experts (which I am not), which 
seem irrelevant/harmless to you and me.
I'm guessing this bug should be sent upstream and they will (highly) likely 
ask for a full dmesg/kernel log.
(I'm merely trying to collect as much useful information as possible)

HTH,
  Diederik

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

Bug#1014429:

[Andreas Hasenack]

Ok, my current theory is this, please poke holes:

autofs and nfs-common are both unpacked. Then the setup begins.

If autofs is setup first, it means systemctl daemon-reload will be
called at the end, and that will run all the generators. Since
nfs-common is already unpacked, it's generator is on disk, and will be
run.

But /etc/nfs.conf doesn't exist yet: it's produced by ucf in
nfs-common's postinst. That means the generator will not be able to
fetch the pipefs-directory config, and will just exit silently. But
autofs is being started, and it requires rpc_pipefs.target, but at
this time, that target unit is the one from the nfs-common package
that will trigger the var-lib-nfs-rpc_pipefs.mount unit.

Then nfs-common is setup. This time, it will produce /etc/nfs.conf,
and when systemctl daemon-reload is called and the generator run, it
will find /etc/nfs.conf, and the pipefs-directory setting, and see
it's different from the default, and produce the generated target and
mount files, which will mount rpc_pipefs in /run/rpc_pipefs now.

Bug#1014429: nfs-utils: rpc_pipefs mounted twice

[Andreas Hasenack]

Package: nfs-utils
Version: 1:2.6.1-2
Severity: normal

Dear Maintainer,

on a fresh debian sid VM, if I "apt install autofs -y", at the end I
will have rpc_pipefs mounted in two places:

root@sid-autofs-nfs-common:~# mount -t rpc_pipefs

root@sid-autofs-nfs-common:~# apt install autofs -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  keyutils libevent-core-2.1-7 libldap-2.5-0 libldap-common
libnfsidmap1 libsasl2-2 libsasl2-modules libsasl2-modules-db
nfs-common rpcbind
Suggested packages:
  libsasl2-modules-gssapi-mit | libsasl2-modules-gssapi-heimdal
libsasl2-modules-ldap libsasl2-modules-otp libsasl2-modules-sql
open-iscsi watchdog
The following NEW packages will be installed:
  autofs keyutils libevent-core-2.1-7 libldap-2.5-0 libldap-common
libnfsidmap1 libsasl2-2 libsasl2-modules libsasl2-modules-db
nfs-common rpcbind
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,408 kB of archives.
After this operation, 4,306 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/main amd64 autofs amd64
5.1.8-1+b1 [292 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 libevent-core-2.1-7
amd64 2.1.12-stable-5+b1 [137 kB]
Get:3 http://deb.debian.org/debian sid/main amd64 libsasl2-modules-db
amd64 2.1.28+dfsg-6 [38.4 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 libsasl2-2 amd64
2.1.28+dfsg-6 [77.3 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 libldap-2.5-0 amd64
2.5.12+dfsg-2 [227 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 libnfsidmap1 amd64
1:2.6.1-2 [85.0 kB]
Get:7 http://deb.debian.org/debian sid/main amd64 rpcbind amd64
1.2.6-3 [52.0 kB]
Get:8 http://deb.debian.org/debian sid/main amd64 keyutils amd64
1.6.3-1 [61.4 kB]
Get:9 http://deb.debian.org/debian sid/main amd64 nfs-common amd64
1:2.6.1-2 [282 kB]
Get:10 http://deb.debian.org/debian sid/main amd64 libldap-common all
2.5.12+dfsg-2 [72.2 kB]
Get:11 http://deb.debian.org/debian sid/main amd64 libsasl2-modules
amd64 2.1.28+dfsg-6 [84.2 kB]
Fetched 1,408 kB in 1s (2,215 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package autofs.
(Reading database ... 23161 files and directories currently installed.)
Preparing to unpack .../00-autofs_5.1.8-1+b1_amd64.deb ...
Unpacking autofs (5.1.8-1+b1) ...
Selecting previously unselected package libevent-core-2.1-7:amd64.
Preparing to unpack .../01-libevent-core-2.1-7_2.1.12-stable-5+b1_amd64.deb ...
Unpacking libevent-core-2.1-7:amd64 (2.1.12-stable-5+b1) ...
Selecting previously unselected package libsasl2-modules-db:amd64.
Preparing to unpack .../02-libsasl2-modules-db_2.1.28+dfsg-6_amd64.deb ...
Unpacking libsasl2-modules-db:amd64 (2.1.28+dfsg-6) ...
Selecting previously unselected package libsasl2-2:amd64.
Preparing to unpack .../03-libsasl2-2_2.1.28+dfsg-6_amd64.deb ...
Unpacking libsasl2-2:amd64 (2.1.28+dfsg-6) ...
Selecting previously unselected package libldap-2.5-0:amd64.
Preparing to unpack .../04-libldap-2.5-0_2.5.12+dfsg-2_amd64.deb ...
Unpacking libldap-2.5-0:amd64 (2.5.12+dfsg-2) ...
Selecting previously unselected package libnfsidmap1:amd64.
Preparing to unpack .../05-libnfsidmap1_1%3a2.6.1-2_amd64.deb ...
Unpacking libnfsidmap1:amd64 (1:2.6.1-2) ...
Selecting previously unselected package rpcbind.
Preparing to unpack .../06-rpcbind_1.2.6-3_amd64.deb ...
Unpacking rpcbind (1.2.6-3) ...
Selecting previously unselected package keyutils.
Preparing to unpack .../07-keyutils_1.6.3-1_amd64.deb ...
Unpacking keyutils (1.6.3-1) ...
Selecting previously unselected package nfs-common.
Preparing to unpack .../08-nfs-common_1%3a2.6.1-2_amd64.deb ...
Unpacking nfs-common (1:2.6.1-2) ...
Selecting previously unselected package libldap-common.
Preparing to unpack .../09-libldap-common_2.5.12+dfsg-2_all.deb ...
Unpacking libldap-common (2.5.12+dfsg-2) ...
Selecting previously unselected package libsasl2-modules:amd64.
Preparing to unpack .../10-libsasl2-modules_2.1.28+dfsg-6_amd64.deb ...
Unpacking libsasl2-modules:amd64 (2.1.28+dfsg-6) ...
Setting up libsasl2-modules:amd64 (2.1.28+dfsg-6) ...
Setting up rpcbind (1.2.6-3) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/rpcbind.service →
/lib/systemd/system/rpcbind.service.
Created symlink
/etc/systemd/system/sockets.target.wants/rpcbind.socket →
/lib/systemd/system/rpcbind.socket.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
Setting up libldap-common (2.5.12+dfsg-2) ...
Setting up libsasl2-modules-db:amd64 (2.1.28+dfsg-6) ...
Setting up libevent-core-2.1-7:amd64 (2.1.12-stable-5+b1) ...
Setting up libsasl2-2:amd64 (2.1.28+dfsg-6) ...
Setting up keyutils (1.6.3-1) ...
Setting up autofs (5.1.8-1+b1) ...

Creating config file /etc/auto.master with new version

Creating config file /etc/auto.net with new version

Creating config file /etc/auto.misc with new version

Creating config 

Bug#1014394: linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Michael]

on the host's /var/log/apt/term.log:

Log started: 2022-06-12  10:57:30
...
Preparing to unpack .../08-linux-image-5.10.0-15-amd64_5.10.120-1_amd64.deb 
...

Unpacking linux-image-5.10.0-15-amd64 (5.10.120-1) ...
Preparing to unpack .../09-linux-image-amd64_5.10.120-1_amd64.deb ...
Unpacking linux-image-amd64 (5.10.120-1) over (5.10.113-1) ...
...
Setting up linux-image-5.10.0-15-amd64 (5.10.120-1) ...
...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-14-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-14-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-15-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-15-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.10.0-15-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.10.0-15-amd64
Found initrd image: /boot/initrd.img-5.10.0-15-amd64
Found linux image: /boot/vmlinuz-5.10.0-14-amd64
Found initrd image: /boot/initrd.img-5.10.0-14-amd64
Adding boot menu entry for EFI firmware configuration
done
...
Setting up linux-image-amd64 (5.10.120-1) ...
...
Log ended: 2022-06-12  10:58:50


so, the kernel was installed on 2022-06-12.


and for your request:

# cat <(gunzip -c /var/log/kern.log.{4,3,2}.gz) /var/log/kern.log{.1,} | 
grep -B5 -E "hrtimer|clocksource|traps:|Code:|general|segfault"


Apr 18 22:24:41 vmguest kernel: [1669500.364257] clocksource: timekeeping 
watchdog on CPU1: kvm-clock wd-wd read-back delay of 64914ns
Apr 18 22:24:41 vmguest kernel: [1669500.364328] clocksource: wd-tsc-wd 
read-back delay of 314448ns, clock-skew test skipped!

--
Apr 19 13:42:46 vmguest kernel: [0.00] DMI: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006

Apr 19 13:42:46 vmguest kernel: [0.00] Hypervisor detected: KVM
Apr 19 13:42:46 vmguest kernel: [0.00] kvm-clock: Using msrs 
4b564d01 and 4b564d00
Apr 19 13:42:46 vmguest kernel: [0.00] kvm-clock: cpu 0, msr 
236b8001, primary cpu clock
Apr 19 13:42:46 vmguest kernel: [0.02] kvm-clock: using sched 
offset of 5303526299 cycles
Apr 19 13:42:46 vmguest kernel: [0.07] clocksource: kvm-clock: 
mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 
881590591483 ns

--
Apr 19 13:42:46 vmguest kernel: [0.180275] PM: hibernation: Registered 
nosave memory: [mem 0x0009f000-0x0009]
Apr 19 13:42:46 vmguest kernel: [0.180276] PM: hibernation: Registered 
nosave memory: [mem 0x000a-0x000e]
Apr 19 13:42:46 vmguest kernel: [0.180277] PM: hibernation: Registered 
nosave memory: [mem 0x000f-0x000f]
Apr 19 13:42:46 vmguest kernel: [0.180280] [mem 0x4000-0xfebf] 
available for PCI devices
Apr 19 13:42:46 vmguest kernel: [0.180282] Booting paravirtualized 
kernel on KVM
Apr 19 13:42:46 vmguest kernel: [0.180288] clocksource: 
refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 
7645519600211568 ns

--
Apr 19 13:42:46 vmguest kernel: [0.216877] ACPI: Core revision 20200925
Apr 19 13:42:46 vmguest kernel: [0.217175] APIC: Switch to symmetric 
I/O mode setup

Apr 19 13:42:46 vmguest kernel: [0.217795] x2apic enabled
Apr 19 13:42:46 vmguest kernel: [0.218367] Switched APIC routing to 
physical x2apic.
Apr 19 13:42:46 vmguest kernel: [0.221130] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
Apr 19 13:42:46 vmguest kernel: [0.221204] clocksource: tsc-early: 
mask: 0x max_cycles: 0x1598c7dcb76, max_idle_ns: 
440795222846 ns

--
Apr 19 13:42:46 vmguest kernel: [0.349407] smpboot: Max logical 
packages: 1
Apr 19 13:42:46 vmguest kernel: [0.349411] smpboot: Total of 4 
processors activated (11986.22 BogoMIPS)
Apr 19 13:42:46 vmguest kernel: [0.355058] node 0 deferred pages 
initialised in 4ms

Apr 19 13:42:46 vmguest kernel: [0.355163] devtmpfs: initialized
Apr 19 13:42:46 vmguest kernel: [0.355163] x86/mm: Memory block size: 
128MB
Apr 19 13:42:46 vmguest kernel: [0.357525] clocksource: jiffies: mask: 
0x max_cycles: 0x, max_idle_ns: 764504178510 ns

--
Apr 19 13:42:46 vmguest kernel: [0.709892] NetLabel:  unlabeled traffic 
allowed by default
Apr 19 13:42:46 vmguest kernel: [0.709892] PCI: Using ACPI for IRQ 
routing
Apr 19 13:42:46 vmguest kernel: [0.709892] PCI: pci_cache_line_size set 
to 64 bytes
Apr 19 13:42:46 vmguest kernel: [0.710019] e820: reserve RAM buffer 
[mem 0x0009fc00-0x0009]
Apr 19 13:42:46 vmguest kernel: [0.710030] e820: reserve RAM buffer 
[mem 0x3fff-0x3fff]
Apr 19 13:42:46 vmguest kernel: [0.715223] clocksource: Switched to 
clocksource kvm-clock

--
Apr 19 13:42:46 vmguest kernel: [0.736766] AppArmor: AppArmor 
Filesystem Enabled

Apr 19 13:42:46 vmguest kernel: [0.736806] pnp: PnP ACPI init
Apr 19 13:42:46 vmguest kernel: [0.736937] pnp 00:00: Plug and Play 
ACPI device, IDs PNP0303 

Bug#1014394: Stable Proposed Updates Kernel

[Richard Laysell]

Hello,

I have installed the Stable-Proposed-Updates kernel on the virtual host
(linux-image-5.10.0-16-amd64 - 5.10.127-1) and I am still seeing
Firefox crashing frequently in a virtual guest running on this host.

I do not see any messages logged in kern.log when the whole of Firefox
crashes, but I do see the following messages when individual tabs in
Firefox crash (these tab crashes also happened with 5.10.0-15-amd64 -
5.10.120.1 but not with 5.10.0-14-amd64 - 5.10.113-1).

These are from the virtual guest however, not the host.  I do not see
any errors logged to kern.log on the host (even though that is the
system running the problematic kernel).

Jul  5 20:10:23 vwbbase kernel: [  342.977899] DOM Worker[4222]:
segfault at 7fd700942000 ip 7fd72ba9a307 sp 7fd71ce03cd0 error
4 in libxul.so[7fd7278dd000+5559000]
Jul  5 20:10:23 vwbbase kernel: [  342.977907] Code: c7 0f 84 48 ff ff
ff 4c 8d 77 38 4c 8d 6f 60 48 8d 6c 24 04 0f 1f 80 00 00 00 00 8b 53 38
49 63 c7 48 03 43 28 44 89 7c 24 04 <44> 8b 38 48 89 ee 4c 89 ef 89 10
4c 89 f2 e8 e6 9a ff ff 45 85 ff
Jul  5 20:13:52 vwbbase kernel: [  552.210131] traps: Web Content[4872]
general protection fault ip:7f0fa8c39426 sp:7ffe80eff5c0 error:0 in
libxul.so[7f0fa490e000+5559000]
Jul  5 20:13:54 vwbbase kernel: [  554.146579] traps: Web Content[5025]
general protection fault ip:7f7cf735b068 sp:7fffaffe93c0 error:0 in
libxul.so[7f7cf350e000+5559000]

Happy to do more testing and send more logs if it helps.

Regards,

Richard

Processed: Re: Bug#1014394: linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 5.10.120-1
Bug #1014394 [linux-image-5.10.0-15-arm64] linux kernel 5.10.0-15 on virtualbox 
host causes random process crashes in guests
Bug reassigned from package 'linux-image-5.10.0-15-arm64' to 'src:linux'.
No longer marked as found in versions linux-signed-arm64/5.10.120+1.
Ignoring request to alter fixed versions of bug #1014394 to the same values 
previously set
Bug #1014394 [src:linux] linux kernel 5.10.0-15 on virtualbox host causes 
random process crashes in guests
Marked as found in versions linux/5.10.120-1.
> tag -1 upstream moreinfo
Bug #1014394 [src:linux] linux kernel 5.10.0-15 on virtualbox host causes 
random process crashes in guests
Added tag(s) upstream and moreinfo.

-- 
1014394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1014394: linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Diederik de Haas]

Control: reassign -1 src:linux 5.10.120-1
Control: tag -1 upstream moreinfo

On Tuesday, 5 July 2022 12:09:00 CEST Michael wrote:
> package: linux-image-5.10.0-15-arm64
> version: 5.10.120-1
> 
> i am running virtualbox 6.1.34 from the virtualbox.org repo on a debian
> 11.3 host. the guest also runs debian 11.3.
> 
> when both host and guest run the latest stable kernel 5.10.0-15
> (5.10.120-1) i get random process crashes in the guest when having
> significant i/o for longer than a few seconds on the host.
> 
> and eventually guest processes start to randomly crash, e.g.:
> 
> Jun 30 20:17:01 vmguest kernel: traps: sh[250946] general protection fault
> ip:7fb0c341708e sp:7ffec3154378 error:0 in
> libc-2.31.so[7fb0c33a6000+14b000]
> Jul 01 00:00:02 vmguest kernel: traps: hostname[253617] general protection
> fault ip:7f905f2b24a6 sp:7fff44a30e30 error:0 in
> libc-2.31.so[7f905f299000+14b000]
> Jul 01 00:53:01 vmguest kernel: traps: wget[254290] general protection
> fault ip:7f934bc23fda sp:7ffd716954d0 error:0 in
> libtasn1.so.6.6.0[7f934bc1a000+c000]
> 
> if i switch to kernel 5.10.0-14 (5.10.113-1) on the host (the guest kernel
> remains 5.10.0-15), then the random process crashes in the guest disappear,
> although the complaints from hrtimer and clocksource still remain, but
> significantly less often.

This indeed looks like an upstream regression between 5.10.113 and 5.10.120.

What surprises me are the time gaps between those GPF messages, ~3.5h and 50m, 
but not within the same second/minute. What happens between those time stamps?

If there are more messages around those GPF messages, it would be useful to 
share those as well.

In Stable-Proposed-Updates there is a 5.10.127-1 version and it would be 
useful to test whether the issue happens with that version too.

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

Bug#1012829: marked as done (kernel 5.17.6-1 causes issues with Audio out via HDMI (workaround: intel_iommu=igfx_off))

[Debian Bug Tracking System]

Your message dated Tue, 05 Jul 2022 19:35:12 +0200
with message-id <2645963.mvXUDI8C0e@bagend>
and subject line Re: Bug#1012829: Updates -
has caused the Debian Bug report #1012829,
regarding kernel 5.17.6-1 causes issues with Audio out via HDMI (workaround: 
intel_iommu=igfx_off)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1012829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.17.11-1
Severity: normal
Tags: upstream

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

After scouring my logs I've found this started after my first 
boot
of kernel 5.17.6-1 (2022-05-14). I started having issues with 
audio
out via HDMI - especially if the device had its input changed or
was turned off.

Kernel 5.17.0-1-amd64 (Debian 5.17.3-1 (2022-04-18) does not 
have
this issue, which should help reduce the Δ somewhat.

The problem remains with linux-image-5.17.0-3-amd64. I am 
currently
unable (unwilling?) to test linux-image-5.18.0, as my root
filesytem uses ZFS, and there are currently no DKMS packages 
that
build on linux-image-5.18. (I don't have an abundance of time to
try to both get an upstream zfs set of packages built as well as
figure out how to get a rootfs booting using that kernel 
module.)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

By plugging my error into Google, I was lead to

https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg478114.html,
which wasn't _quite_ what I was looking for, but it mentioned 
the
intel_iommu driver, and as the device id in my error message 
used
an Intel driver (snd_hda_intel), it seemed a reasonable place to
start looking.

That lead me to
https://www.kernel.org/doc/Documentation/Intel-IOMMU.txt, which
explicitly said:

"If you encounter issues with graphics devices, you can try 
adding
option intel_iommu=igfx_off to turn off the integrated graphics
engine.  If this fixes anything, please ensure you file a bug
reporting the problem."

As the motherboard has an Intel integrated graphics engine, and 
the
rest of the document seemed to describe the error message I was
seeing, it seemed reasonable to try the option 
intel_iommu=igfx_off

   * What was the outcome of this action?

The problems vanished, and the error messages stopped appearing 
in
my kernel log.

I initially thought to add this to the kernel.org bugzilla, but
they had a useful message saying "Please use your distribution's
bug tracking tools" which is reasonable, as I am using a Debian
kernel.

I'm not sure the appropriate way to report the issue upstream 
(if
it is even is an issue upstream). Unfortuantely, I can't test 
the
latest 5.18 kernel yet, as my root filesystem uses ZFS, and 
there
are no working DKMS packages for it yet.

*** End of the template - remove these template lines ***

-- Package-specific info:
** Version:
Linux version 5.17.0-3-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
11.3.0-3) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Debian 
5.17.11-1 (2022-05-26)

** Command line:
BOOT_IMAGE=/ROOT/debian@/boot/vmlinuz-5.17.0-3-amd64 root=ZFS=rpool/ROOT/debian 
ro apparmor=1 security=apparmor nvidia-drm.modeset=1 delayacct 
intel_iommu=igfx_off

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Jun 14 11:32:14 pilot kernel: [162022.120060] dmar_fault: 82685 callbacks 
suppressed
Jun 14 11:32:14 pilot kernel: [162022.120071] DMAR: [DMA Read NO_PASID] Request 
device [01:00.1] fault addr 0x6ca224000 [fault reason 0x06] PTE Read access is 
not set
Jun 14 11:32:14 pilot kernel: [162022.120250] DMAR: [DMA Read NO_PASID] Request 
device [01:00.1] fault addr 0x6ca224000 [fault reason 0x06] PTE Read access is 
not set
Jun 14 

Bug#1012829: Updates -

[Troy Telford]

I have built a vanilla kernel 5.17.6 to replicate the issue, but before I was 
able to test it (to reproduce it and send a report to kernel.org 
’s bugzilla), I became very ill with COVID-19, which put 
everything on hold for a while.

Now that I’ve largely recovered, I have been able run a system apt upgrade - 
and noticed that the zfs modules have been updated to support kernel 5.18, so I 
am now able to test against `linux-image-5.18.0-2` - it seemed to make sense to 
see if I could reproduce against that first, if only to see if a newer kernel 
resolved the issue.

It appears that was the correct move:

- I’ve been able to boot the Debian 5.18.0-2 linux-image package,
- After about nine days of uptime, I’ve been unable to reproduce the issue.
- There are none of the `DMAR: DRHD: handling fault` messages in the kernel log.

I believe this bug can be closed, as it does not appear to be an issue with the 
current kernels.


signature.asc
Description: Message signed with OpenPGP

Bug#1014394: Also Affected - linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Richard Laysell]

Hello,

I am also affected by this same bug.

I run Firefox in a virtual machine and if I am running the
5.10.0-15-amd64 kernel on the virtual host, then Firefox crashes
regularly in the virtual guest.

However, if I run the 5.10.0-14-amd64 kernel on the virtual host, then
I see no crashes.

In both cases the virtual guest is running the 5.10.0-15-amd64 kernel

This is on Debian Bullseye

VirtualBox packages are from Fasttrack
virtualbox   6.1.34-dfsg-3~fto11+1amd64
virtualbox-dkms  6.1.34-dfsg-3~fto11+1amd64
virtualbox-qt6.1.34-dfsg-3~fto11+1amd64

Kernels are the standard Debian kernels from stable (both host and
guest)
linux-image-5.10.0-14-amd64  5.10.113-1   amd64
linux-image-5.10.0-15-amd64  5.10.120-1   amd64

I have seen this issue on two separate systems, so I do not think it is
hardware related.

Happy to do any testing or provide any logs you can suggest.

Regards,

Richard

Bug#1012547: linux: disable user namespaces per default

[Philippe Cerfon]

On Thu, Jun 16, 2022 at 6:19 PM Philippe Cerfon  wrote:
> Well I guess the 6 or so root security holes, and counting

And here we go already, faster than even I'd have expected:

Say welcome to CVE-2022-32250, the next root security hole which would
apparently have been mitigated if Debian were to ship sane defaults.

Shall we guess how many systems are going to be compromised because of
that?! I guess, none, because attackers surely understand that they
should abuse something that's needed for some containers and flatpaks
:-)

Bug#992555: probably same on Dell Inspiron 3580

[Piotr A. Dybczyński]

On Mon, 1 Nov 2021 13:54:14 +0100 Hendrik Buchner 
wrote:
> > Hi,
> > 
> > both: after upgrade from Buster and after clean install laptop does
> > not wake up when opening lid. Simply freezes, only power off helps.
> > 
> > When I boot Bullseye with 4.19 kernel it works.
> > 
> > Regards,
> > Piotr A. Dybczyński
> > -- 
> > /**
> >   dr Piotr A. Dybczyński 
> >  homepage: https://www.dybczynski.pl/Piotr e-mail:
> > pi...@dybczynski.pl
> > PAD***/
> > 
> > 
> Hi,
> 
> I found out, that disabling Intels VT-d in the BIOS let the suspend and
> resume work again with kernel 5.10.
> Can you please check and confirm this on your laptop?
> 
> 

Hi, I found today the above question.

Yes, after disabling Intels VT direct access my laptop  (Dell Inspiron 3580)
goes to sleep and wakes up successfully!

Thanks for this tip!

All the best,
Piotr

-- 
/**
  dr Piotr A. Dybczyński 
 homepage: https://www.dybczynski.pl/Piotr e-mail: pi...@dybczynski.pl
PAD***/

Bug#1014394: linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Michael]

package: linux-image-5.10.0-15-arm64
version: 5.10.120-1

i am running virtualbox 6.1.34 from the virtualbox.org repo on a debian 
11.3 host. the guest also runs debian 11.3.


when both host and guest run the latest stable kernel 5.10.0-15 
(5.10.120-1) i get random process crashes in the guest when having 
significant i/o for longer than a few seconds on the host.


i.e., when i do a

 # mv  

or even a

 # md5sum 

or anything that causes significant i/o traffic on the host, the guest 
first starts with complaining:


Jul 01 20:44:49 vmguest kernel: hrtimer: interrupt took 21312191 ns
Jul 01 20:45:20 vmguest kernel: clocksource: timekeeping watchdog on CPU0: 
kvm-clock wd-wd read-back delay of 816732ns
Jul 01 20:45:20 vmguest kernel: clocksource: wd-tsc-wd read-back delay of 
2540783ns, clock-skew test skipped!


and eventually guest processes start to randomly crash, e.g.:

Jun 30 20:17:01 vmguest kernel: traps: sh[250946] general protection fault 
ip:7fb0c341708e sp:7ffec3154378 error:0 in 
libc-2.31.so[7fb0c33a6000+14b000]
Jul 01 00:00:02 vmguest kernel: traps: hostname[253617] general protection 
fault ip:7f905f2b24a6 sp:7fff44a30e30 error:0 in 
libc-2.31.so[7f905f299000+14b000]
Jul 01 00:53:01 vmguest kernel: traps: wget[254290] general protection 
fault ip:7f934bc23fda sp:7ffd716954d0 error:0 in 
libtasn1.so.6.6.0[7f934bc1a000+c000]


if i switch to kernel 5.10.0-14 (5.10.113-1) on the host (the guest kernel 
remains 5.10.0-15), then the random process crashes in the guest disappear, 
although the complaints from hrtimer and clocksource still remain, but 
significantly less often.


i started a thread in the 'debian-user' mailing list:
https://lists.debian.org/debian-user/2022/07/msg00043.html

thank you for looking into this!

greetings...

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Ansgar]

Hi,

On Tue, 2022-07-05 at 09:00 +0200, Bastian Blank wrote:
> On Mon, Jul 04, 2022 at 10:34:39PM +0200, Ansgar wrote:
> > As a further test I tried a different PKCS#11 module:
> 
> Could you try the same with "openssl cms"?  Just to make sure it's
> not sign-file itself.

I replaced the `./sign-file` call with:

+---
| openssl cms -sign -binary -outform DER -engine pkcs11 \
| -keyform engine -inkey "${pkcs11_uri}" -signer ${cert_path} \
| -md sha256 -nocerts -noattr -nosmimecap \
| -in data.ko -out data.ko.p7s
+---

and got the same results as with sign-file, both with
libykcs11.so.2.2.0 and opensc-pkcs11.so.

All of this happened on my laptop running a current Debian testing.

There is at least one ykcs11-specific bug (missing the initial zero
bytes), but the broken signature itself happens with both modules.

Ansgar

need help disabling some devices / device scanning - lspci shuts down my lenovo E480

[Eugen Stan]

Hello,

I'm writing here because I am a bit desperate and figured it's worth a 
shot.


I have a Lenovo E480 with Radeon RX550 
https://www.lenovo.com/in/en/laptops/thinkpad/thinkpad-e-series/ThinkPad-E480/p/22TP2TEE480 
.


The computer shuts down when I do lspci, hwinfo, or start lutris (for 
games) and sometimes when I log-in after resume.


Otherwise the computer works great and there are no issues.

If I disable acpi during kernel boot --acpi=off lspci works ok.
Any idea what is happening?
Any idea how I can disable ACPI scanning for the GPU / new video devices ?!

Any ideas on what to try to fix this?


More information:

* Running Debian 11.3 Linux 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 
(2022-06-09) x86_64 GNU/Linux

* I took the laptop to two repair shops. thermal paste was replaced.
* I upgraded Bios to latest version.

One thing that I did notice is that I can't see the dedicated Radeon GPU 
in lspci.


Ouptut from lspci, lsmod and dmesg:

lspci -nnk -> https://paste.debian.net/plain/1246205

lspci -> https://paste.debian.net/plain/1246206

lspci -vvv https://paste.debian.net/plain/1246207

lsmod -> https://paste.debian.net/plain/1246207

dmesg -T https://paste.debian.net/1246209/


Thanks,
Eugen

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Bastian Blank]

On Mon, Jul 04, 2022 at 10:34:39PM +0200, Ansgar wrote:
> As a further test I tried a different PKCS#11 module:

Could you try the same with "openssl cms"?  Just to make sure it's not
sign-file itself.

The complete command line I use to create signatures for kernel modules
is:

| openssl cms -sign -binary -outform DER -signer "$SIGNING_KEY_FILE" -md sha256 
-nocerts -noattr -nosmimecap -in "$filein" -out "$fileout"

Bastian

-- 
Immortality consists largely of boredom.
-- Zefrem Cochrane, "Metamorphosis", stardate 3219.8