Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20

2024-04-23 Thread Bastian Blank
Control: reassign -1 src:linux Control: severity -1 normal Control: tags -1 moreinfo On Mon, Apr 22, 2024 at 09:12:59AM +0200, bouv...@buxtehude.debian.org wrote: > Something seems wrong in 6.1.0-20, but it is not immediately wrong: it waits > until some sort of trigger. After that, rebooting

Processed: Re: Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux Bug #1069642 [linux-image-6.1.0-20-amd64] linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20 Bug reassigned from package 'linux-image-6.1.0-20-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #1069642 to the same

Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20

2024-04-23 Thread Bouvier
FWIW, and following Jacob Rhoads' remark, we are also running CrowdStrike Falcon Sensor on all our machines, virtuals servers and laptops alike. That would explain why I don't have the same problem at home. -- Cédric Bouvier System Engineer, IRU Geneva +41-22-918 2927 (direct)

Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20

2024-04-22 Thread Jacob Rhoads
Seeing this same issue. In my case, it ended up being caused by Crowdstrike Falcon Sensor combined with this specific kernel. Reverting the kernel or upgrading Falcon (via Falcon upgrade policy) works around this issue, for now. I think I see that 6.1.87 has attempted to fix some BHI

Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20

2024-04-22 Thread Damian
Same problem here, but with a different call trace. The RIP logline had one of `security_file_permission` and `security_netlink_send`, I don't remember which one.