Bug#1022544: linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2
Hi Again. This is in kernel bugzilla now: https://bugzilla.kernel.org/show_bug.cgi?id=216613 Regards, Daniel.
Bug#1022544: linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2
Hi! On Sun, 23 Oct 2022 23:24:46 +0200 Diederik de Haas wrote: > > On Sunday, 23 October 2022 19:01:52 CEST pdorm...@free.fr wrote: > > After upgrade from 6.0.0-1 to 6.0.0-2, I don't have sound anymore. > > I believe that the relevant dmesg message is this one, as it is not printed > > with the 6.0.0-1 version: > > > > snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12 > > snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on > > ehdaudio0D2: -12 skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to > > instantiate card -12 skl_hda_dsp_generic: probe of skl_hda_dsp_generic > > failed with error -12 > > > > git bisect indicates that the bad commit is: > > [7494e2e6c55ed192f2b91c821fd6832744ba8741] ALSA: hda: Fix page fault in > > snd_hda_codec_shutdown() > > Thanks for that wonderful analyses! > > Both you and Lisandro had "sof-audio-pci-intel-tgl" in dmesg, but I don't. > Lisandro also has the firmware-intel-sound package installed (but not you). > Sound on my system works with 6.0.0-2, so the 'intel' part looks relevant. > I have the same bug. In the meantime, I can get sound by disabling SOF, adding "snd-intel-dspcfg.dsp_driver=1" to the kernel command line, but with no mic support. My audio device is Intel tigerlake: $ lspci | grep audio 00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20) And I also have the firmware installed: $ dpkg -l | grep 'firmware-intel-sound\|linux-image-6' ii firmware-intel-sound 20210818-1 all Binary firmware for Intel sound DSPs ii linux-image-6.0.0-2-amd64 6.0.3-1amd64Linux 6.0 for 64-bit PCs (signed) Regards, Daniel.
Processed: Re: Bug#1022544: linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2
Processing control commands: > tag -1 upstream Bug #1022544 [src:linux] linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2 Bug #1022558 [src:linux] linux-image-6.0.0-2-amd64: Audio fails to start, but works with 5.19 Added tag(s) upstream. Added tag(s) upstream. -- 1022544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022544 1022558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022544: linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2
Control: tag -1 upstream On Sunday, 23 October 2022 19:01:52 CEST pdorm...@free.fr wrote: > After upgrade from 6.0.0-1 to 6.0.0-2, I don't have sound anymore. > I believe that the relevant dmesg message is this one, as it is not printed > with the 6.0.0-1 version: > > snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12 > snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on > ehdaudio0D2: -12 skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to > instantiate card -12 skl_hda_dsp_generic: probe of skl_hda_dsp_generic > failed with error -12 > > git bisect indicates that the bad commit is: > [7494e2e6c55ed192f2b91c821fd6832744ba8741] ALSA: hda: Fix page fault in > snd_hda_codec_shutdown() Thanks for that wonderful analyses! Both you and Lisandro had "sof-audio-pci-intel-tgl" in dmesg, but I don't. Lisandro also has the firmware-intel-sound package installed (but not you). Sound on my system works with 6.0.0-2, so the 'intel' part looks relevant. Could you report it upstream by replying to the thread linked in that commit: https://lore.kernel.org/all/20220816111727.3218543-7-cezary.rojew...@intel.com/ signature.asc Description: This is a digitally signed message part.
Processed: Merging sound bugs
Processing commands for cont...@bugs.debian.org: > severity 1022544 important Bug #1022544 [src:linux] linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2 Severity set to 'important' from 'normal' > merge 1022544 1022558 Bug #1022544 [src:linux] linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2 Bug #1022558 [src:linux] linux-image-6.0.0-2-amd64: Audio fails to start, but works with 5.19 Merged 1022544 1022558 > thanks Stopping processing here. Please contact me if you need assistance. -- 1022544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022544 1022558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022559: firmware-misc-nonfree: With firmware-misc-nonfree instaled, system crashes (complete freeze/lockup) every few minutes
Package: firmware-misc-nonfree Version: 20210818-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1022558: linux-image-6.0.0-2-amd64: Audio fails to start, but works with 5.19
Package: src:linux Version: 6.0.3-1 Severity: important X-Debbugs-Cc: lisan...@debian.org >From dmesg (see below) audio stack fails to be initialized. If I boot with 5.19 everything works as expected. [ 36.646398] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 36.647271] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 36.648298] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 36.649675] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 36.657376] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 36.748803] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5 [ 36.749759] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 36.750527] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 36.766188] sof-audio-pci-intel-tgl :00:1f.3: firmware: direct-loading firmware intel/sof/sof-tgl.ri [ 36.766847] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:2:0-57864 [ 36.767532] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0 [ 36.768229] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 36.862793] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:2:0-57864 [ 36.863749] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0 [ 36.872189] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 36.873133] Bluetooth: BNEP filters: protocol multicast [ 36.874082] Bluetooth: BNEP socket layer initialized [ 36.884360] sof-audio-pci-intel-tgl :00:1f.3: firmware: direct-loading firmware intel/sof-tplg/sof-hda-generic-2ch.tplg [ 36.885264] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:22:1 Kernel ABI 3:23:0 [ 36.886343] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet available, widget card binding deferred [ 36.891799] snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12 [ 36.891867] snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on ehdaudio0D2: -12 [ 36.891891] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to instantiate card -12 [ 36.895650] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -12 -- Package-specific info: ** Version: Linux version 6.0.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1 (2022-10-21) ** Command line: BOOT_IMAGE=/vmlinuz-6.0.0-2-amd64 root=/dev/mapper/minerva--vg-root ro ** Not tainted ** Kernel log: [ 26.051482] Bluetooth: hci0: Boot Address: 0x24800 [ 26.052488] Bluetooth: hci0: Firmware Version: 191-21.21 [ 26.068068] r8169 :04:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2) [ 26.068075] r8169 :04:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2) [ 26.068076] r8169 :04:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -2 [ 26.068077] r8169 :04:00.0: Unable to load firmware rtl_nic/rtl8168h-2.fw (-2) [ 26.099450] Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC) [ 26.128618] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351 [ 26.129680] thermal thermal_zone6: failed to read out thermal zone (-61) [ 26.137587] NET: Registered PF_QIPCRTR protocol family [ 26.198974] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 26.206278] intel_rapl_msr: PL4 support detected. [ 26.206388] intel_rapl_common: Found RAPL domain package [ 26.206392] intel_rapl_common: Found RAPL domain core [ 26.206393] intel_rapl_common: Found RAPL domain uncore [ 26.231534] r8169 :04:00.0 enp4s0: Link is Down [ 26.276143] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 26.343929] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 26.343935] Bluetooth: BNEP filters: protocol multicast [ 26.343939] Bluetooth: BNEP socket layer initialized [ 26.346280] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 26.346356] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 26.346539] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 26.346601] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 26.353468] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 26.354006] iwlwifi :00:14.3: Detected RF HR B5, rfid=0x10a100 [ 26.419178] iwlwifi :00:14.3: base HW address: 54:14:f3:d2:89:fd [ 26.425788]
Bug#1022042: kernel 5.10.149-2 does not help
On zondag 23 oktober 2022 19:01:06 CEST Andreas Wirooks wrote: > Am 23.10.22 um 14:27 schrieb Diederik de Haas: > > On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote: > >>> You both have kernel parameters like these. Can you explain why? > >>> I have an AMD GPU on a machine and I have never set parameters like > >>> these. > >> > >> These are parameters for Southern Islands (si) and Sea Islands (cik) AMD > >> GPUs: > > I see you're already 'in' > > https://gitlab.freedesktop.org/drm/amd/-/issues/2216 and that seems like > > an important distinction to mention (to me). > > All the other cases for where this issue was fixed, seem to have (much) > > newer generation of GPUs. > > I will write an update in the drm issue too. > > I tested the old radeon driver by removing all si/cki options with > kernel 5.10.149-2 and it boots ok and uses drm 2 instead drm 3. Excellent. I saw you already added that info to the upstream bug :-) > The debian 11/bullseye backport kernel 5.19.11-1~bpo11+1 boots ok with > the amdgpu driver too using drm 3. Alex Deucher (@agd5f) indicated the problem was caused by an incorrect backport to 5.10 and maybe the 2 identified ones aren't the only ones. On zondag 23 oktober 2022 17:44:17 CEST inasprec...@disroot.org wrote: > I tried booting 5.10.0-19 with an empty command line string and it > worked > > I don’t know if this an entirely separate issue, however. I can > file a separate bug if you think it is appropriate. Given that switching to the radeon driver fixed the issue for you both, then I guess it's the same issue. So let's keep it to this bug, at least for now. signature.asc Description: This is a digitally signed message part.
Bug#1022545: wishlist: please enable CONFIG_LEDS_USER
Source: linux Version: 5.10.140-1 Severity: wishlist X-Debbugs-Cc: dfo...@gmail.com Dear maintainers, please considser building the uleds module (CONFIG_LEDS_USER=m). The kernel documentation says: > The uleds driver supports userspace LEDs. This can be useful for testing > triggers and can also be used to implement virtual LEDs. My use case is a PC with two on-board ethernet ports and only one activity LED on its front panel. thanks, Daniele -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1022042: kernel 5.10.149-2 does not help
Am 23.10.22 um 14:27 schrieb Diederik de Haas: On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote: You both have kernel parameters like these. Can you explain why? I have an AMD GPU on a machine and I have never set parameters like these. These are parameters for Southern Islands (si) and Sea Islands (cik) AMD GPUs: I see you're already 'in' https://gitlab.freedesktop.org/drm/amd/-/issues/2216 and that seems like an important distinction to mention (to me). All the other cases for where this issue was fixed, seem to have (much) newer generation of GPUs. I will write an update in the drm issue too. I tested the old radeon driver by removing all si/cki options with kernel 5.10.149-2 and it boots ok and uses drm 2 instead drm 3. But of course i added these options again and rebooted with 5.10.140-1 because of Vulkan support in the amdgpu driver using drm 3. The debian 11/bullseye backport kernel 5.19.11-1~bpo11+1 boots ok with the amdgpu driver too using drm 3.
Bug#1022544: linux-image-6.0.0-2-amd64: No more sound after upgrade to 6.0.0-2
Package: src:linux Version: 6.0.3-1 Severity: normal Dear Maintainer, After upgrade from 6.0.0-1 to 6.0.0-2, I don't have sound anymore. I believe that the relevant dmesg message is this one, as it is not printed with the 6.0.0-1 version: snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12 snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on ehdaudio0D2: -12 skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to instantiate card -12 skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -12 git bisect indicates that the bad commit is: [7494e2e6c55ed192f2b91c821fd6832744ba8741] ALSA: hda: Fix page fault in snd_hda_codec_shutdown() Ask me if you need further information. Best regards Pascal D -- Package-specific info: ** Version: Linux version 6.0.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1 (2022-10-21) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.0.0-2-amd64 root=UUID=6dc0e7ec-e588-4c76-8c94-0ad097ce4975 ro acpi_backlight=video systemd.show-status=true systemd.restore_state=0 quiet ** Not tainted ** Kernel log: [5.540610] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [5.570644] typec port0: bound usb1-port5 (ops connector_ops [usbcore]) [5.570664] typec port0: bound usb4-port1 (ops connector_ops [usbcore]) [5.609292] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5 [5.609296] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [5.609299] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [5.610210] sof-audio-pci-intel-tgl :00:1f.3: firmware: direct-loading firmware intel/sof/sof-adl.ri [5.610215] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:2:0-57864 [5.610216] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0 [5.610219] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [5.622328] usb 1-10: new full-speed USB device number 3 using xhci_hcd [5.633629] iwlwifi :00:14.3: firmware: direct-loading firmware iwlwifi-so-a0-gf-a0.pnvm [5.633648] iwlwifi :00:14.3: loaded PNVM version a982b33e [5.649224] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000 [5.708919] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:2:0-57864 [5.708931] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0 [5.718238] iwlwifi :00:14.3: base HW address: 84:7b:57:57:88:e3 [5.737125] e1000e :00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 6c:24:08:b8:af:ec [5.737131] e1000e :00:1f.6 eth0: Intel(R) PRO/1000 Network Connection [5.737438] e1000e :00:1f.6 eth0: MAC: 15, PHY: 12, PBA No: FF-0FF [5.774725] usb 1-10: New USB device found, idVendor=8087, idProduct=0033, bcdDevice= 0.00 [5.774739] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [6.526324] typec port1: bound usb1-port6 (ops connector_ops [usbcore]) [6.526358] typec port1: bound usb4-port3 (ops connector_ops [usbcore]) [8.263588] pstore: Using crash dump compression: deflate [8.331887] pstore: Registered efi as persistent store backend [8.413634] input: PC Speaker as /devices/platform/pcspkr/input/input9 [8.431300] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer [8.431302] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules [8.431303] RAPL PMU: hw unit of domain package 2^-14 Joules [8.431303] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules [8.431304] RAPL PMU: hw unit of domain psys 2^-14 Joules [8.432285] cryptd: max_cpu_qlen set to 1000 [8.436833] AVX2 version of gcm_enc/dec engaged. [8.436868] AES CTR mode by8 optimization enabled [9.577729] usb 1-10: USB disconnect, device number 3 [9.669273] intel_rapl_msr: PL4 support detected. [9.669309] intel_rapl_common: Found RAPL domain package [9.669313] intel_rapl_common: Found RAPL domain core [9.669314] intel_rapl_common: Found RAPL domain uncore [9.669316] intel_rapl_common: Found RAPL domain psys [9.732174] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [9.738623] input: SYNA801A:00 06CB:CEC6 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-14/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input10 [9.738703] input: SYNA801A:00 06CB:CEC6 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-14/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input11 [9.738765] hid-generic 0018:06CB:CEC6.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA801A:00 06CB:CEC6] on i2c-SYNA801A:00 [9.739190] iTCO_vendor_support: vendor-support=0 [9.741148] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=6, TCOBASE=0x0400) [
Bug#1022543: Lower intel-rapl-mmio power limit on ThinkPad T490 since 5.18.0-3-amd64
Package: src:linux Version: 6.0.3-1 Severity: important Hello, starting with 5.18.0-3-amd64 I experience significant performance loss (clock speed slows down to 400 MHz) on higher CPU usage. After checking for differences I figured out that the long-term intel rapl mmio power limit now defaults to 5W (AC mode) / 10W (battery mode) compared to 25W with 5.18.0-2-amd64: AC mode: $ uname -a Linux sulfur 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1 (2022-10-21) x86_64 GNU/Linux $ cat /sys/class/power_supply/AC/online 1 $ cat /sys/class/powercap/intel-rapl-mmio/intel-rapl-mmio\:0/constraint_0_power_limit_uw 500 Battery mode: $ uname -a Linux sulfur 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1 (2022-10-21) x86_64 GNU/Linux $ cat /sys/class/power_supply/AC/online 0 $ cat /sys/class/powercap/intel-rapl-mmio/intel-rapl-mmio\:0/constraint_0_power_limit_uw 1000 Note that the limit in battery mode is actually higher than in AC mode. Booting into 5.18.0-2-amd64 the default power limit is 25W: AC mode: $ uname -a Linux sulfur 5.18.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.5-1 (2022-06-16) x86_64 GNU/Linux $ cat /sys/class/power_supply/AC/online 1 $ cat /sys/class/powercap/intel-rapl-mmio/intel-rapl-mmio\:0/constraint_0_power_limit_uw 2500 Battery mode: $ uname -a Linux sulfur 5.18.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.5-1 (2022-06-16) x86_64 GNU/Linux $ cat /sys/class/power_supply/AC/online 0 $ cat /sys/class/powercap/intel-rapl-mmio/intel-rapl-mmio\:0/constraint_0_power_limit_uw 2500 I can manually set the power limit to 2500 (fixing the performance issues), but the embedded controller changes it back to 500 after some time. Please let me know if I can provide any further information. Best regards Hannes -- Package-specific info: ** Version: Linux version 6.0.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC Debian 6.0.3-1 (2022-10-21) ** Command line: BOOT_IMAGE=/vmlinuz-6.0.0-2-amd64 root=/dev/mapper/sulfur--vg-root ro apparmor=0 quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: LENOVO product_name: 20N2CTO1WW product_version: ThinkPad T490 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: N2IET99W (1.77 ) board_vendor: LENOVO board_name: 20N2CTO1WW board_version: SDK0R32862 WIN ** Loaded modules: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device ctr ccm xt_CHECKSUM nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_compat bridge stp llc nf_tables libcrc32c rfcomm cmac algif_hash algif_skcipher af_alg bnep nfnetlink nls_ascii nls_cp437 vfat fat btusb btrtl btbcm btintel btmtk bluetooth uvcvideo videobuf2_vmalloc jitterentropy_rng videobuf2_memops videobuf2_v4l2 videobuf2_common sha512_ssse3 sha512_generic videodev drbg ansi_cprng mc ecdh_generic ecc intel_pmc_core_pltdrv intel_pmc_core snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils soundwire_bus snd_soc_skl x86_pkg_temp_thermal snd_soc_hdac_hda intel_powerclamp coretemp snd_hda_ext_core snd_soc_sst_ipc snd_hda_codec_hdmi snd_soc_sst_dsp iTCO_wdt kvm_intel snd_soc_acpi_intel_match rtsx_pci_sdmmc intel_pmc_bxt iTCO_vendor_support snd_soc_acpi iwlmvm ee1004 watchdog mei_hdcp mmc_core snd_ctl_led intel_rapl_msr snd_soc_core wmi_bmof snd_hda_codec_realtek intel_wmi_thunderbolt kvm snd_compress mac80211 snd_hda_codec_generic irqbypass snd_hda_intel crc32_pclmul libarc4 snd_intel_dspcfg snd_intel_sdw_acpi ghash_clmulni_intel snd_hda_codec iwlwifi rapl e1000e snd_hda_core intel_cstate snd_hwdep xhci_pci snd_pcm intel_uncore xhci_hcd pcspkr joydev ptp i2c_i801 thinkpad_acpi efi_pstore pps_core snd_timer i2c_smbus cfg80211 thunderbolt mei_me processor_thermal_device_pci_legacy usbcore nvram processor_thermal_device rtsx_pci platform_profile mei processor_thermal_rfim ucsi_acpi ledtrig_audio processor_thermal_mbox typec_ucsi intel_lpss_pci processor_thermal_rapl intel_lpss snd idma64 intel_rapl_common usb_common roles intel_pch_thermal soundcore intel_soc_dts_iosf typec wmi rfkill battery int3403_thermal int340x_thermal_zone ac int3400_thermal button acpi_thermal_rel acpi_pad msr parport_pc ppdev lp parport fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_crypt dm_mod i915 i2c_algo_bit drm_buddy drm_display_helper drm_kms_helper cec rc_core crc32c_intel ttm nvme nvme_core drm aesni_intel t10_pi psmouse crypto_simd cryptd crc64_rocksoft evdev crc64 crc_t10dif serio_raw crct10dif_generic crct10dif_pclmul crct10dif_common video -- System Information: Debian Release: bookworm/sid APT prefers
linux-signed-arm64_6.0.3+1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2022 21:05:40 +0200 Source: linux-signed-arm64 Architecture: source Version: 6.0.3+1 Distribution: sid Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-arm64 (6.0.3+1) unstable; urgency=medium . * Sign kernel from linux 6.0.3-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.3 - ALSA: oss: Fix potential deadlock at unregistration - ALSA: rawmidi: Drop register_mutex in snd_rawmidi_free() - ALSA: usb-audio: Fix potential memory leaks - ALSA: usb-audio: Fix NULL dererence at error path - ALSA: hda/realtek: remove ALC289_FIXUP_DUAL_SPK for Dell 5530 - ALSA: hda/realtek: Correct pin configs for ASUS G533Z - ALSA: hda/realtek: Add quirk for ASUS GV601R laptop - ALSA: hda/realtek: Add Intel Reference SSID to support headset keys - io_uring: add custom opcode hooks on fail - io_uring/rw: don't lose partial IO result on fail - io_uring/net: don't lose partial send/recv on fail - io_uring/rw: fix unexpected link breakage - io_uring/rw: don't lose short results on io_setup_async_rw() - io_uring/net: fix fast_iov assignment in io_setup_async_msg() - io_uring/net: don't update msg_name if not provided - io_uring: limit registration w/ SINGLE_ISSUER - io_uring/net: handle -EINPROGRESS correct for IORING_OP_CONNECT - io_uring/af_unix: defer registered files gc to io_uring release (CVE-2022-2602) - io_uring: correct pinned_vm accounting - [x86] hv_netvsc: Fix race between VF offering and VF association message from host - cifs: destage dirty pages before re-reading them for cache=none - cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message - iio: dac: ad5593r: Fix i2c read protocol requirements - iio: ltc2497: Fix reading conversion results - iio: adc: ad7923: fix channel readings for some variants - iio: pressure: dps310: Refactor startup procedure - iio: pressure: dps310: Reset chip after timeout - xhci: dbc: Fix memory leak in xhci_alloc_dbc() - usb: gadget: uvc: Fix argument to sizeof() in uvc_register_video() - usb: add quirks for Lenovo OneLink+ Dock - mmc: core: Add SD card quirk for broken discard - can: kvaser_usb: Fix use of uninitialized completion - can: kvaser_usb_leaf: Fix overread with an invalid command - can: kvaser_usb_leaf: Fix TX queue out of sync after restart - can: kvaser_usb_leaf: Fix CAN state after restart - mmc: renesas_sdhi: Fix rounding errors - mmc: sdhci-tegra: Use actual clock rate for SW tuning correction - mmc: sdhci-sprd: Fix minimum clock limit - i2c: designware: Fix handling of real but unexpected device interrupts - fs: dlm: fix race between test_bit() and queue_work() - fs: dlm: handle -EBUSY first in lock arg validation - fs: dlm: fix invalid derefence of sb_lvbptr - btf: Export bpf_dynptr definition - mbcache: Avoid nesting of cache->c_list_lock under bit locks - HID: multitouch: Add memory barriers - quota: Check next/prev free block number after reading from quota file - platform/chrome: cros_ec_proto: Update version on GET_NEXT_EVENT failure - [arm64] dts: qcom: sdm845-mtp: correct ADC settle time - ASoC: wcd9335: fix order of Slimbus unprepare/disable - ASoC: wcd934x: fix order of Slimbus unprepare/disable - hwmon: (gsc-hwmon) Call of_node_get() before of_find_xxx API - net: thunderbolt: Enable DMA paths only after rings are enabled - regulator: qcom_rpm: Fix circular deferral regression - [arm64] topology: move store_cpu_topology() to shared code - [riscv64] topology: fix default topology reporting - [riscv64] Re-enable counter access from userspace - [riscv64] Make port I/O string accessors actually work - [riscv64] vdso: fix NULL deference in vdso_join_timens() when vfork - [riscv64] Allow PROT_WRITE-only mmap() - [riscv64] Make VM_WRITE imply VM_READ - [riscv64] always honor the CONFIG_CMDLINE_FORCE when parsing dtb - [riscv64] Pass -mno-relax only on lld < 15.0.0 - nvmem: core: Fix memleak in nvmem_register() - nvme-multipath: fix possible hang in live ns resize with ANA access - Revert "drm/amdgpu: use dirty framebuffer helper" - dm: verity-loadpin: Only trust verity targets with enforcement - dmaengine: mxs: use platform_driver_register - dmaengine: qcom-adm: fix wrong sizeof config in slave_config - dmaengine: qcom-adm: fix wrong calling convention for prep_slave_sg - drm/virtio: Check whether transferred 2D BO is shmem - drm/virtio: Unlock reservations on virtio_gpu_object_shmem_init() error - drm/virtio: Unlock reservations on dma_resv_reserve_fences() error - drm/virtio: Use
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Diederik de Haas writes: > Then I'm inclined to think this *is* a separate issue, which is > due to the upgrade to -19, but that you happen to have an AMD > GPU is 'not' relevant. > > I realize it's not what you want, but may result in an useful > extra data point if you (for this test) switch those parameters > to enable radeon support and disable amdgpu support. Can you try > that? > > If that test does not make a difference, then I'm quite sure > it's a separate issue and it would be best to open a new bug > report for that. I tried booting 5.10.0-19 with an empty command line string and it worked, although it’s now using the "radeon" gpu driver while I’d like to use the "amdgpu" driver instead, mainly for better Vulkan support. Booting with command line options to disable "radeon" and enable "amdgpu" works for 5.10.0-18 and earlier. I don’t know if this an entirely separate issue, however. I can file a separate bug if you think it is appropriate. Best regards. -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Diederik de Haas writes: > Then I'm inclined to think this *is* a separate issue, which is > due to the upgrade to -19, but that you happen to have an AMD > GPU is 'not' relevant. > I realize it's not what you want, but may result in an useful > extra data point if you (for this test) switch those parameters > to enable radeon support and disable amdgpu support. Can you try > that? > > If that test does not make a difference, then I'm quite sure > it's a separate issue and it would be best to open a new bug > report for that.
Bug#1022061: debian-kernel-handbook: improve kernel build steps for newbies
Hi Dan! Thanks so much for your description, it already gives me some ideas how to improve things wrt the documentation :-) On Wednesday, 19 October 2022 23:56:23 CEST Dan Coleman wrote: > use test-patches in debian/bin/test-patches. >From bug 1022025: On Thursday, 20 October 2022 21:48:20 CEST Diederik de Haas wrote: > On Thursday, 20 October 2022 19:53:22 CEST Dan Coleman wrote: > > > Apparently "test-patches" does not build a 'headers-common' package and > > > therefor installing the headers failed which in turn made DKMS fail. > > > > That seems like less-than-ideal behavior for test-patches. > > Is that a bug that would benefit from being reported? I (now) do think it is useful to file a (wishlist) bug against src:linux in which you request improvements to the 'test-patches' script: 1) also creates a headers-common package. > When I finally managed to get the test kernel compiled, I couldn't install > it, either via apt or dpkg. I was told that apt would take care of removing > the dependencies causing the conflict, but it didn't. DKMS wasn't > triggered, it was a mess. 2) make it easy/easier to install the resulting kernel deb, which does not involve removing an existing kernel (meta) package. By setting the 'abiname' 'property' you can achieve that, but I don't know if that idea has been evaluated before and discarded. But the kernel maintainers should be able to answer that. Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
On Sunday, 23 October 2022 15:15:36 CEST inasprecali wrote: > It does not boot at all, I'm unable to SSH into it. It's not > merely that the display does not work. Then I'm inclined to think this *is* a separate issue, which is due to the upgrade to -19, but that you happen to have an AMD GPU is 'not' relevant. On Sunday, 23 October 2022 15:18:03 CEST inasprecali wrote: > In my case, it's because, without command line parameters, the > kernel will select the "radeon" driver, while I want to use the > "amdgpu" driver instead. > > The options "radeon.si_support=0 amdgpu.si_support=1" disable > radeon support and enable amdgpu support respectively. I realize it's not what you want, but may result in an useful extra data point if you (for this test) switch those parameters to enable radeon support and disable amdgpu support. Can you try that? If that test does not make a difference, then I'm quite sure it's a separate issue and it would be best to open a new bug report for that. signature.asc Description: This is a digitally signed message part.
Re: Proposed changes to linux package
On Sat, Oct 22, 2022 at 11:15:05AM +0200, Bastian Blank wrote: > On Sat, Oct 22, 2022 at 10:59:30AM +0200, Bastian Blank wrote: > > I would like to do some last minute changes to the linux package > # Drop special case use of rcX as abi name > > While having the ability to distiguish between different RC, it changes > the package names every time. Or should we just go for 0? This would also remove the ordering weirdness a lot of people experienced. Bastian -- "Life and death are seldom logical." "But attaining a desired goal always is." -- McCoy and Spock, "The Galileo Seven", stardate 2821.7
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
On Sun, 23 Oct 2022 13:40:26 +0200 Diederik de Haas wrote: > Does it really not boot? Or does the screen not work properly? > > The cases in this bug report all boot AFAIK, it's just that the screen does > not work properly, but people were able to SSH into the machine. > If your system actually does not boot, then I'm inclined to think that that is > a different problem. It does not boot at all, I'm unable to SSH into it. It's not merely that the display does not work. At the moment, I'm unable to provide additional information, but I'll try looking into it as soon as possible. Best regards -- inasprecali
Bug#1022042: kernel 5.10.149-2 does not help
On Sun, 23 Oct 2022 13:43:30 +0200 Diederik de Haas wrote: > Andreas and inasprecali, > > On zondag 23 oktober 2022 09:17:44 CEST Andreas Wirooks wrote: > > Kernel parameters are: > > radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 > > amdgpu.cik_support=1 amdgpu.gpu_recovery=1 > > You both have kernel parameters like these. Can you explain why? > I have an AMD GPU on a machine and I have never set parameters like these. In my case, it's because, without command line parameters, the kernel will select the "radeon" driver, while I want to use the "amdgpu" driver instead. The options "radeon.si_support=0 amdgpu.si_support=1" disable radeon support and enable amdgpu support respectively. 5.10.0-18 and earlier have always worked as expected. 5.10.0-19, even with the very latest stable update, fails to boot. Best regards. -- inasprecali
Bug#1022276: linux-image-6.0.0-1-amd64: Debian kernels since 5.19 drop Solarflare SFC9000 (SFN5xxx SFN6xxx) support.
Package: src:linux Version: 6.0.2-1+b1 Severity: normal Tags: patch X-Debbugs-Cc: t...@seoss.co.uk Firstly, thanks for the work on the Debian kernel packaging! Upstream kernel v5.19 incorporated a patch which split out Solarflare SFC9000 (NIC model SFN5000 and SFN6000 series) driver support from the main Solarflare driver. Debian stable currently supports these NICs, so this patch adds the necessary config entries to continue driver support for these NICs. These NICs are reasonably commonplace, with used models being frequently traded online (being a good value low-power-consumption 10GB Ethernet NIC), so I think reinstating support for these cards is the right thing to do. Upstream patch set which necessitates this patch: https://lore.kernel.org/netdev/165063937837.27138.6911229584057659609.st...@palantir17.mph.net/ Mainline kernel tree commit set circa c5a13c319e10e Thanks! Tim. --- debian/config/config | 9 + 1 file changed, 9 insertions(+) diff --git a/debian/config/config b/debian/config/config index cf17f586eaba..bfb897386cdc 100644 --- a/debian/config/config +++ b/debian/config/config @@ -3633,6 +3633,15 @@ CONFIG_SFC_MCDI_LOGGING=y CONFIG_SFC_FALCON=m CONFIG_SFC_FALCON_MTD=y +## +## file: drivers/net/ethernet/sfc/siena/Kconfig +## +CONFIG_SFC_SIENA=m +CONFIG_SFC_SIENA_MTD=y +CONFIG_SFC_SIENA_MCDI_MON=y +CONFIG_SFC_SIENA_SRIOV=y +CONFIG_SFC_SIENA_MCDI_LOGGING=y + ## ## file: drivers/net/ethernet/silan/Kconfig ## -- 2.30.2
Bug#1022042: kernel 5.10.149-2 does not help
On zondag 23 oktober 2022 14:10:11 CEST Andreas Wirooks wrote: > > You both have kernel parameters like these. Can you explain why? > > I have an AMD GPU on a machine and I have never set parameters like these. > > These are parameters for Southern Islands (si) and Sea Islands (cik) AMD > GPUs: I see you're already 'in' https://gitlab.freedesktop.org/drm/amd/-/issues/2216 and that seems like an important distinction to mention (to me). All the other cases for where this issue was fixed, seem to have (much) newer generation of GPUs. signature.asc Description: This is a digitally signed message part.
Bug#1022268: linux-image-5.10.0-19-amd64: Boot failure under xen as dom0
Sorry this is production machine and I can't reboot it very often. But tomorrow at night I try it and record boot. I have remote management on this machine. Regards Dan Dne 23. 10. 22 v 13:52 Diederik de Haas napsal(a): Control: severity -1 important Control: tag -1 moreinfo On zondag 23 oktober 2022 11:28:33 CEST Dan Smolik wrote: after upgrade kernel from 5.10.0-18 to 5.10.0-19 system is unbootable. Problem is similar this bug https://bugzilla.kernel.org/show_bug.cgi?id=209177. I try recommended solution mpt3sas.max_queue_depth=1 but nothing helps. Without xen system boots. Unfortunately you described very little about your problem, all I/we know is that there is a 'boot failure' under Xen. And only under Xen. The referenced bug does not mention Xen and has a working workaround ... which does not work for you. Do you have any kind of (boot) log (or screenshot/picture of it), that shows what's actually happening (and/or not happening)?
Bug#1022042: kernel 5.10.149-2 does not help
Am 23.10.22 um 13:43 schrieb Diederik de Haas: You both have kernel parameters like these. Can you explain why? I have an AMD GPU on a machine and I have never set parameters like these. These are parameters for Southern Islands (si) and Sea Islands (cik) AMD GPUs: https://en.wikipedia.org/wiki/List_of_AMD_graphics_processing_units#Features_Overview They can be used with the old "radeon" driver (default) and the "amdgpu" driver. Using the old radeon driver renders these AMD GPUs useless nowadays because of the missing Vulkan support so removing them is not an option. I use them since Debian 9/stretch.
Processed: Re: Bug#1022268: linux-image-5.10.0-19-amd64: Boot failure under xen as dom0
Processing control commands: > severity -1 important Bug #1022268 [src:linux] linux-image-5.10.0-19-amd64: Boot failure under xen as dom0 Severity set to 'important' from 'critical' > tag -1 moreinfo Bug #1022268 [src:linux] linux-image-5.10.0-19-amd64: Boot failure under xen as dom0 Added tag(s) moreinfo. -- 1022268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022268: linux-image-5.10.0-19-amd64: Boot failure under xen as dom0
Control: severity -1 important Control: tag -1 moreinfo On zondag 23 oktober 2022 11:28:33 CEST Dan Smolik wrote: > after upgrade kernel from 5.10.0-18 to 5.10.0-19 system is unbootable. > Problem is similar this bug > https://bugzilla.kernel.org/show_bug.cgi?id=209177. > I try recommended solution mpt3sas.max_queue_depth=1 but nothing helps. > Without xen system boots. Unfortunately you described very little about your problem, all I/we know is that there is a 'boot failure' under Xen. And only under Xen. The referenced bug does not mention Xen and has a working workaround ... which does not work for you. Do you have any kind of (boot) log (or screenshot/picture of it), that shows what's actually happening (and/or not happening)? signature.asc Description: This is a digitally signed message part.
Bug#1022042: kernel 5.10.149-2 does not help
Andreas and inasprecali, On zondag 23 oktober 2022 09:17:44 CEST Andreas Wirooks wrote: > Kernel parameters are: > radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 > amdgpu.cik_support=1 amdgpu.gpu_recovery=1 You both have kernel parameters like these. Can you explain why? I have an AMD GPU on a machine and I have never set parameters like these. signature.asc Description: This is a digitally signed message part.
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
On zondag 23 oktober 2022 12:02:52 CEST inasprecali wrote: > After updating to the latest version (5.10.149-2), my system > running an AMD GPU and CPU still does not boot. I am unable to > retrieve any logs from the systemd journal. Does it really not boot? Or does the screen not work properly? The cases in this bug report all boot AFAIK, it's just that the screen does not work properly, but people were able to SSH into the machine. If your system actually does not boot, then I'm inclined to think that that is a different problem. signature.asc Description: This is a digitally signed message part.
linux-signed-arm64_6.0.3+1_source.changes is NEW
Mapping sid to unstable. binary:ata-modules-6.0.0-2-arm64-di is NEW. binary:btrfs-modules-6.0.0-2-arm64-di is NEW. binary:cdrom-core-modules-6.0.0-2-arm64-di is NEW. binary:crc-modules-6.0.0-2-arm64-di is NEW. binary:crypto-dm-modules-6.0.0-2-arm64-di is NEW. binary:crypto-modules-6.0.0-2-arm64-di is NEW. binary:efi-modules-6.0.0-2-arm64-di is NEW. binary:event-modules-6.0.0-2-arm64-di is NEW. binary:ext4-modules-6.0.0-2-arm64-di is NEW. binary:f2fs-modules-6.0.0-2-arm64-di is NEW. binary:fat-modules-6.0.0-2-arm64-di is NEW. binary:fb-modules-6.0.0-2-arm64-di is NEW. binary:fuse-modules-6.0.0-2-arm64-di is NEW. binary:i2c-modules-6.0.0-2-arm64-di is NEW. binary:input-modules-6.0.0-2-arm64-di is NEW. binary:isofs-modules-6.0.0-2-arm64-di is NEW. binary:jfs-modules-6.0.0-2-arm64-di is NEW. binary:kernel-image-6.0.0-2-arm64-di is NEW. binary:leds-modules-6.0.0-2-arm64-di is NEW. binary:linux-image-6.0.0-2-arm64 is NEW. binary:linux-image-6.0.0-2-cloud-arm64 is NEW. binary:linux-image-6.0.0-2-rt-arm64 is NEW. binary:loop-modules-6.0.0-2-arm64-di is NEW. binary:md-modules-6.0.0-2-arm64-di is NEW. binary:mmc-modules-6.0.0-2-arm64-di is NEW. binary:mtd-core-modules-6.0.0-2-arm64-di is NEW. binary:multipath-modules-6.0.0-2-arm64-di is NEW. binary:nbd-modules-6.0.0-2-arm64-di is NEW. binary:nic-modules-6.0.0-2-arm64-di is NEW. binary:nic-shared-modules-6.0.0-2-arm64-di is NEW. binary:nic-usb-modules-6.0.0-2-arm64-di is NEW. binary:nic-wireless-modules-6.0.0-2-arm64-di is NEW. binary:ppp-modules-6.0.0-2-arm64-di is NEW. binary:sata-modules-6.0.0-2-arm64-di is NEW. binary:scsi-core-modules-6.0.0-2-arm64-di is NEW. binary:scsi-modules-6.0.0-2-arm64-di is NEW. binary:scsi-nic-modules-6.0.0-2-arm64-di is NEW. binary:squashfs-modules-6.0.0-2-arm64-di is NEW. binary:udf-modules-6.0.0-2-arm64-di is NEW. binary:uinput-modules-6.0.0-2-arm64-di is NEW. binary:usb-modules-6.0.0-2-arm64-di is NEW. binary:usb-serial-modules-6.0.0-2-arm64-di is NEW. binary:usb-storage-modules-6.0.0-2-arm64-di is NEW. binary:xfs-modules-6.0.0-2-arm64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Bug#1022025: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot possible)
Revised kernel works for me as well! Thanks everyone for the rapid response.
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
After updating to the latest version (5.10.149-2), my system running an AMD GPU and CPU still does not boot. I am unable to retrieve any logs from the systemd journal. CPU: AMD FX-8350 GPU: AMD R9 270X (Southern Islands Family) Kernel command line parameters: GRUB_CMDLINE_LINUX="radeon.si_support=0 amdgpu.si_support=1" 5.10.0-19 fails to boot, while 5.10.0-18 does. Best regards. -- inasprecali
Processing of linux-signed-arm64_6.0.3+1_source.changes
linux-signed-arm64_6.0.3+1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_6.0.3+1.dsc linux-signed-arm64_6.0.3+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1022268: linux-image-5.10.0-19-amd64: Boot failure under xen as dom0
Package: src:linux Version: 5.10.149-1 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: mar...@mydatex.cz Dear Maintainer, after upgrade kernel from 5.10.0-18 to 5.10.0-19 system is unbootable. Problem is similar this bug https://bugzilla.kernel.org/show_bug.cgi?id=209177. I try recommended solution mpt3sas.max_queue_depth=1 but nothing helps. Without xen system boots. With xen I must use 5.10.0-18. Regards Dan -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Supermicro product_name: Super Server product_version: 0123456789 chassis_vendor: Supermicro chassis_version: 0123456789 bios_vendor: American Megatrends Inc. bios_version: 2.2a board_vendor: Supermicro board_name: X11SSL-F board_version: 1.01 ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback iface eno2 inet manual auto xenbr1 iface xenbr1 inet static address 192.168.2.2 netmask 255.255.255.248 gateway 192.168.2.1 bridge_ports eno2 bridge_stp off # disable Spanning Tree Protocol bridge_waitport 0 # no delay before a port becomes available bridge_fd 0 # no forwarding delay iface eno1 inet manual auto xenbr0 iface xenbr0 inet manual bridge_ports eno1 bridge_stp off # disable Spanning Tree Protocol bridge_waitport 0 # no delay before a port becomes available bridge_fd 0 # no forwarding delay iface enp2s0 inet manual auto xenbr2 iface xenbr2 inet manual bridge_ports enp2s0 bridge_stp off # disable Spanning Tree Protocol bridge_waitport 0 # no delay before a port becomes available bridge_fd 0 # no forwarding delay ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5918] (rev 05) Subsystem: Super Micro Computer Inc Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ie31200_edac Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 05) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:13.0 Non-VGA unclassified device []: Intel Corporation 100 Series/C230 Series Chipset Family Integrated Sensor Hub [8086:a135] (rev 31) Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family Integrated Sensor Hub [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: intel_ish_ipc 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI]) Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31) Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family Thermal Subsystem [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family MEI Controller [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation
Bug#1022070: Acknowledgement (Booting semi-hangs with 'drm_atomic_helper_wait_for_flip_done' errors and alike)
Hi again, It seems the linux regression update [DSA 5257-2] has fixed this issue. Thanks team! Cheers, Kees
Bug#1022025: Fwd: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot possible)
5.10.149-2 solved the problem many thanks for the quick fix Weitergeleitete Nachricht Betreff: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot possible) Datum: Wed, 19 Oct 2022 14:33:04 + Von: Debian Bug Tracking System Antwort an: 1022...@bugs.debian.org An: Michael Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Kernel Team If you wish to submit further information on this problem, please send it to 1022...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems OpenPGP_signature Description: OpenPGP digital signature
Bug#1022042: Fails boot on linux-image-5.10.0.19-amd64
Hi, I can confirm that, I have the same problem here. I can't boot into the 5.10.0.19-amd64 kernel, just a blackscreen. Processor: AMD Ryzen 5 5600G with Radeon Graphics. Awaiting a solution, Maurício Forain.
Bug#1022042: kernel 5.10.149-2 does not help
The new Debian 11/bullseye kernel 5.10.149-2 does not help on my setup. Still a black screen and nothing is logged. Also in rescue mode without "quiet". My GPU is: 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) 02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tobago HDMI Audio [Radeon R7 360 / R9 360 OEM] The GPU is running on an Intel X58 board with Intel Xeon W3530 CPU and classic BIOS. Kernel parameters are: radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.gpu_recovery=1 My setup works flawless with linux-image-5.10.0-18-amd64. Kind regards, Andreas
linux-signed-i386_5.10.149+2_source.changes ACCEPTED into proposed-updates->stable-new
Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2022 22:24:21 +0200 Source: linux-signed-i386 Architecture: source Version: 5.10.149+2 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-i386 (5.10.149+2) bullseye-security; urgency=high . * Sign kernel from linux 5.10.149-2 . * Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega" (Closes: #1022025) * Revert "drm/amdgpu: make sure to init common IP before gmc" (Closes: #1022025) Checksums-Sha1: 2f12445864e6827eb474912d147a3d79e40e0ec7 14265 linux-signed-i386_5.10.149+2.dsc 9174d3ca6848820ea6b4bdedbb35366fb7920403 3747184 linux-signed-i386_5.10.149+2.tar.xz Checksums-Sha256: eabc88a923c24832423c23e420b4f409095c94f0c9c1f20190645bc3fb9c35bb 14265 linux-signed-i386_5.10.149+2.dsc a30f87fbf93840155a214ca566b91f6af8b24f137f6351dce8ff7db71527bf57 3747184 linux-signed-i386_5.10.149+2.tar.xz Files: eccac8665338955ceb0c4f66ed4dd4bd 14265 kernel optional linux-signed-i386_5.10.149+2.dsc 4a0d9d253c137a109a1f2a1b89e5b031 3747184 kernel optional linux-signed-i386_5.10.149+2.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNUlHQACgkQi0FRiLdO NzZhcQ/7BoK4TlyI+Im76291w9aTFNibbFxcqqbOt9hllMCuIcsuHVPJtpXUeLE0 ZmnWO36qK+g+4yPy1I/fxkKqiANyNMCIzeGrCweTFRSwBmk+6bqCSMWVJPj2v3aO /Oucr3h35/Zz/A4dL6xsk4g8uHmkalPVyMWKLeX/nEwDx8wa+lFDaXhK5alPFmRd k+NXPHUGf9dsflCNeHgMkJnoUowa7wStNABopVB0BVwmsu3d5SIM91DUYv8hCdYM TFIVxQpXr26vj6/qyo9ROGj1CazgRDcvhmhs+2Leb7N82Uwnog0jWsA3E4mn3D4X ptXnKZoBTjpvSr5UWa4RLxpNgyNyyRGanit/maJkReUWtAXdFrKHAV0sF4Lmmiod NOJe2ZANJjG201AWc7Qtax0PGbMR/gNkrPwb2puegVi17WMYJ1fAIUI4dWrdJ5ha duFS9mz2E2fO+myvyaPLvGgiW9m3uAlpo5cnTP3KWUATiFuNobUSNjgLqQSC5M4j mJwxWWrL+PgAL1FGg8t245EnoF5oB9pxcQh6M4AJlnRslmYpwur8EoClJU5NN5Ku S99118n5VHBc1ZpRyf8Y3/DW47NUcR0S7+Tmb+OUuy+TtkhbibMUAKkLb/sOh4W1 JsIHSvVtzAriztLkgoZKnOiniPGlTK3z28oiFfbKgoeCU4tUpQE= =Fgtq -END PGP SIGNATURE- Thank you for your contribution to Debian.
linux-signed-arm64_5.10.149+2_source.changes ACCEPTED into proposed-updates->stable-new
Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2022 22:24:21 +0200 Source: linux-signed-arm64 Architecture: source Version: 5.10.149+2 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-arm64 (5.10.149+2) bullseye-security; urgency=high . * Sign kernel from linux 5.10.149-2 . * Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega" (Closes: #1022025) * Revert "drm/amdgpu: make sure to init common IP before gmc" (Closes: #1022025) Checksums-Sha1: 1f8029be2afa8259d1bd56524cee9aaca75e6a9f 7340 linux-signed-arm64_5.10.149+2.dsc 6dc0670584a776e52f2a9bebf5b993ad22f10774 2545540 linux-signed-arm64_5.10.149+2.tar.xz Checksums-Sha256: acf85af64c1cce1d8f0a63b0b2a26e05f293a913090d9f13da5a09e9f9addf3d 7340 linux-signed-arm64_5.10.149+2.dsc c204ea744399b89f34f9a96665e1fd4c59fad1fda072d9f16d6741f117b27de4 2545540 linux-signed-arm64_5.10.149+2.tar.xz Files: 2b9f17ccafbccbf12d1b1cdfc082dae6 7340 kernel optional linux-signed-arm64_5.10.149+2.dsc 8c68e85c862b3cfe4f795518f45be2ee 2545540 kernel optional linux-signed-arm64_5.10.149+2.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNT4eIACgkQi0FRiLdO NzZAFxAAoHQBzB4mB0ZhkPIOdSR9xxY0GVnxhL7b5eHElnByfDVtE1R26bBuGEDB JKEm5ErdlyhGLgJT+1MSd+P2/OH44187PPKaFSXIfXCibd5t6N0U4SZ7yknyrz28 grjolb2kdtTx5OB0Wip0Yn9Vyq2XSNEZeL/QW2hE0fzZCM73Uzs/5jEZK5vS3AuG CepdrYUi2nhmHNj3nJH23DgBHo4O74vo7QB80F6hisFkN6op+X2l0eqfQoJtKfyh /lErBATf3PECIs0t0eZVEA1WpBJBVbUj3pK9yQDo4D0tRJdZFKkfjcSsnuwUJ3Uh zAUGKRn5rVgr3Ot4chsfuR9+GukxCugLLWU0BctRwVPQ0mhga9wGXXLM3R1xdKdE 07VQMLQNDwYH3mX7f5Ik/LnJt0V3IauKjVeTJiK5o+AWyxVe1mQXzDCa7QCcnlbW GxJQ6VEZEjYTN4HRJskxwI20qQKESM6PGPkTcnvwwim41IZD/jLUsd7LLaJ95ztL z7SW1lDz8sWCL+y/b3eEOK47reb9k5Wk78kYoReRrVVP1bGyUH/nga8g8h7F9olO KmaqSJ11/fEj0x5msJzMyBHUB+ji1zJCA/wdKZe5mSUNEH8u+iKnZNeADdIcDOef +E3jy5sxE98NkPwfIxgbCtqEvjEGD4pjlSuiloEbtrl+3vWX3to= =2RUh -END PGP SIGNATURE- Thank you for your contribution to Debian.
linux-signed-amd64_5.10.149+2_source.changes ACCEPTED into proposed-updates->stable-new
Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2022 22:24:21 +0200 Source: linux-signed-amd64 Architecture: source Version: 5.10.149+2 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-amd64 (5.10.149+2) bullseye-security; urgency=high . * Sign kernel from linux 5.10.149-2 . * Revert "drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega" (Closes: #1022025) * Revert "drm/amdgpu: make sure to init common IP before gmc" (Closes: #1022025) Checksums-Sha1: 55361c9e5a377b36a437298986461dfa4b66e6ca 8609 linux-signed-amd64_5.10.149+2.dsc 47706117437efee10024594a4af3d13a5e4d3d7c 2802384 linux-signed-amd64_5.10.149+2.tar.xz Checksums-Sha256: 00011ad99e9bf95fa411f595d8244c083611f6bf308453f02482d7db6e00b2cd 8609 linux-signed-amd64_5.10.149+2.dsc e626983c355796f2fbd76a2ecae39cabdbdddfd5935960a07a138a7d4dfad3be 2802384 linux-signed-amd64_5.10.149+2.tar.xz Files: 55f630c4b84817ccaa095d894dfce9b3 8609 kernel optional linux-signed-amd64_5.10.149+2.dsc 67f76ee1b0b0f11898ad45498b94619d 2802384 kernel optional linux-signed-amd64_5.10.149+2.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNTwZYACgkQi0FRiLdO NzZhiw/8CP2JT64MqhggaISk8uUxVGc69UFIbnehwHPU/FAj2cUdjR3PGpk23/UB Dc2oqwOxKlO85f2GayqUPMKIt3ubHO4dsyyp5nHIrlmigq/Q3v2sN9rH4VrWVRbp O+rg3T6rZnZ5vTSbWX6mQABGQrdHeZJgrEUKSDQmBjkQU4VtxOQnKJGscQJAfASM 0GUIqlV9MLTU0OXGQBiLMNvucs+EmCy1i7OfhD3pmklBau4pKWMrnMybjcyvKiJk 9o4mt4jBrhTz1XRm7B5jp8Tg3jEqFa3ep5PfkS4K8nY6USNsaPenbNoyx7PZlBN5 XtSFSPXpb31EnavyqZZavcgrXhCkhGmr0N9/w/4oQMZN40QS4WlvURypBw8/8eZ3 fkWWBV+N0WqEZaoWggu2VHcDJICRD1r+knMCQ8lcbAv+rzD5pBIX+yhX06GgqH8q DTdSmVY58c/oQFxo4l3ywKJiiVyJIsD3oPca/KYHgZsWxz7qQL9PzS3CHNHb4iKi 3i2J/Es5OgBBhlYvZdAB+xhOYu6FVwVp6Gxts9axYJnGmp2DxNKwt/kwZoXa/uMt fpDcWomcYbWPK8ujqdB1d9zi7AtoBIGuOeqy9QsVa8EZnGkXqylm8LBBFfeayH4H CWaWRyH7CPhITE8P63VYYeZx/kZhb/OspirKeYMkWyEcQXvwIxI= =uR7v -END PGP SIGNATURE- Thank you for your contribution to Debian.
