Control: tags -1 + moreinfo

Hi Kevin,

On Mon, Dec 11, 2023 at 02:55:50AM +0100, Kevin Price wrote:
> Package: linux-image-6.1.0-15-amd64
> Version: 6.1.66-1
> Severity: critical
> Control: -1 notfound 6.1.64-1
> 
> When booting 6.1.0-15, my physical amd64/bookworm/gnome computer
> misbehaves in many ways, rendering it largely unusable. With kernels up
> to 6.1.0-13, and even briefly with the otherwise broken 6.1.0-14, all of
> this seemed fine.
> 
> Misbehavior includes, not limited to:
> 
> 1. Most actions take considerably longer than usual.
> 
> 2. The GDM greeter has an English keyboard layout, which otherwise is
> German. (Login works.)
> 
> 3. There seems to be no network connectivity. No WiFi icon. "ping
> 8.8.8.8" returns IIRC network unreachable.
> 
> 4. Launching Firefox does apparently nothing.
> 
> 5. Launching gnome-terminal does work, but some basic commands just
> freeze, such as "ip a" or "sudo dmesg". sudo hangs before prompting for
> the passphrase. At that stage, even "sudo -i", I cannot interrupt with "^C".
> 
> 6. Shutting down takes ages, with systemd waiting for a bunch of
> processes (sudo) and services to terminate, most of the latter seem to
> be somehow network-related, but you tell me which aren't.
> 
> After more that 10 min I used hard power-off, leaving my ext4 dirty, but
> being perfectly able to boot any of 6.1.0-12 through -15, with -12 and
> -13 working properly, and -15 showing the exact same misbehavior
> reproducibly.
> 
> I'll attach all I could get out of reportbug running under 6.1.0-15, and
> please let me know what further testing I may perform IOT help you.
> Please also specify whether you'd like me to do that testing under
> 6.1.0-15, in which I cannot even invoke sudo, or under 6.1.0-13, which
> will do anything fine.

It still would be helpfull if you can get to the logs of the previous
boot. After booting back in the working kernel, do you have anything
sensible logged in the previous boot log? If so can you share that
please? I'm right now curious to find out if we see the same as
#1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
issue.

Regards,
Salvatore

Reply via email to