Bug#1053122: linux-image-6.5.0-1-amd64: using smp_processor_id() in preemptible

2023-10-15 Thread Diederik de Haas
Control: forwarded -1 https://mastodon.tn/@ghazi/111240903155846113 On Sunday, 15 October 2023 17:20:25 CEST Gabriel Francisco wrote: > I found this link: https://gitlab.freedesktop.org/drm/amd/-/issues/2877 > where other people are facing the same issue as me signature.asc Description: This is

Processed: Re: Bug#1053122: linux-image-6.5.0-1-amd64: using smp_processor_id() in preemptible

2023-10-15 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://mastodon.tn/@ghazi/111240903155846113 Bug #1053122 [src:linux] linux-image-6.5.0-1-amd64: Kernel page fault in Set Bug forwarded-to-address to 'https://mastodon.tn/@ghazi/111240903155846113'. -- 1053122: https://bugs.debian.org/cgi-bin/bugrepor

Bug#1053646: Fixed in linux-image-6.1.0.12: i915 crashed kernel while changed display scale

2023-10-15 Thread Rpnpif
Hi, This issue is fixed in linux-image-6.1.0.12-amd64 from stable. Please, backport this fix in bullseye-backports. Regards. -- Rpnpif

Bug#1054008: linux-image-6.5.0-2-amd64: Can't boot due to ACPI Error (GPE0D)

2023-10-15 Thread Pelle
Package: src:linux Version: 6.5.6-1 Severity: important Dear Maintainer, After upgrading to Linux 6.5, after the GRUB splash screen, instead of booting as usual, I get a rapidly looping message: ACPI Error: No handler or method for GPE0D, disabling event (20230331/evgpe-839) The device bo

Bug#1054005: linux-image-6.5.0-1-amd64: System freeze when suspend or hybrid-suspend or hibernate

2023-10-15 Thread Nicola
Package: src:linux Version: 6.5.3-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: bram...@gmail.com Dear Maintainer, The system is a laptop, Lenovo Ideapad S 15-IKB. When the laptop enter in suspend mode, or hibernate or simply the lid switch calls to switch off the moni

Bug#1053122: linux-image-6.5.0-1-amd64: using smp_processor_id() in preemptible

2023-10-15 Thread Gabriel Francisco
Just an update on this bug. I found this link: https://gitlab.freedesktop.org/drm/amd/-/issues/2877 where other people are facing the same issue as me and I can confirm that disabling FreeSync on my monitor settings makes the freezes/hangs to disappear. Best, *Gabriel Francisco* Linux User #5078

Bug#1053994: Acknowledgement (the es8316 module does not work on the huawei mate d15 laptop)

2023-10-15 Thread Николай
it is also possible that there is not enough topology for this type of laptop 15.10.2023 16:51, Debian Bug Tracking System пишет: Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1053994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053994. T

Bug#1053994: the es8316 module does not work on the huawei mate d15 laptop

2023-10-15 Thread Николай
Package: linux-image-amd64 Version: 6.1.55-1 saber716rus@BOM-WXX9 ~> lsmod | grep es8316 snd_soc_es8316 53248  0 snd_soc_core  348160  4 snd_acp3x_rn,snd_soc_es8316,snd_soc_dmic,snd_acp3x_pdm_dma snd_pcm   159744  9 snd_hda_codec_hdmi,snd_pci_acp6x,snd_hda_intel,snd_

Bug#1034159: Kernel support for more ChromeOS devices

2023-10-15 Thread Alper Nebi Yasak
Control: severity -1 important On 2023-04-10 15:52 +03:00, Alper Nebi Yasak wrote: > Source: linux > Version: 6.1.20-2 > Severity: wishlist I had this as wishlist because I didn't have that much time to work on it until the release. But hardware support is "severity: important". > I've been goin

Processed: Re: Bug#1034159: Kernel support for more ChromeOS devices

2023-10-15 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1034159 [src:linux] Kernel support for more ChromeOS devices Severity set to 'important' from 'wishlist' -- 1034159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034159 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#1053991: linux-image-6.1.0-13-amd64: Only one monitor of multi-monitor displaying after upgrade

2023-10-15 Thread Rachel Waldram
Package: src:linux Version: 6.1.55-1 Severity: important Dear Maintainer, * What led up to the situation? Regular apt update. * What exactly did you do (or not do) that was effective (or ineffective)? Rebooted system after apt upgrade. * What was the outcome of this action?