Bug#1061449: marked as done (linux-image-6.7-amd64: a boot message from amdgpu)
Your message dated Sat, 02 Mar 2024 19:00:11 + with message-id and subject line Bug#1061449: fixed in linux 6.7.7-1 has caused the Debian Bug report #1061449, regarding linux-image-6.7-amd64: a boot message from amdgpu 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.) -- 1061449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.7.1-1~exp1 Severity: normal Dear Maintainer, Giving a try to 6.7, here is a message extracted from dmesg: [4.177226] [ cut here ] [4.177227] WARNING: CPU: 6 PID: 248 at drivers/gpu/drm/amd/amdgpu/../display/dc/link/link_factory.c:387 construct_phy+0xb26/0xd60 [amdgpu] [4.177658] Modules linked in: amdgpu(+) i915(+) sd_mod drm_exec amdxcp gpu_sched drm_buddy nvme i2c_algo_bit drm_suballoc_helper drm_display_helper ahci nvme_core hid_generic crc32_pclmul libahci crc32c_intel t10_pi cec libata crc64_rocksoft_generic ghash_clmulni_intel rc_core drm_ttm_helper crc64_rocksoft sha512_ssse3 i2c_hid_acpi ttm rtsx_pci_sdmmc i2c_hid xhci_pci crc_t10dif sha512_generic mmc_core scsi_mod xhci_hcd drm_kms_helper video hid crct10dif_generic intel_lpss_pci crct10dif_pclmul i2c_i801 sha256_ssse3 intel_lpss crc64 thunderbolt drm e1000e usbcore sha1_ssse3 rtsx_pci i2c_smbus scsi_common crct10dif_common idma64 usb_common battery wmi button aesni_intel crypto_simd cryptd [4.177689] CPU: 6 PID: 248 Comm: (udev-worker) Not tainted 6.7-amd64 #1 Debian 6.7.1-1~exp1 [4.177691] Hardware name: Dell Inc. Precision 7540/0T2FXT, BIOS 1.29.0 11/03/2023 [4.177692] RIP: 0010:construct_phy+0xb26/0xd60 [amdgpu] [4.178050] Code: b9 01 00 00 00 83 fe 01 74 40 48 8b 82 f8 03 00 00 89 f2 48 c7 c6 00 35 a7 c1 48 8b 40 10 48 8b 00 48 8b 78 08 e8 ba b7 5b fb <0f> 0b 49 8b 87 d0 01 00 00 b9 0f 00 00 00 48 8b 80 e8 04 00 00 48 [4.178052] RSP: 0018:aad300857408 EFLAGS: 00010246 [4.178053] RAX: RBX: 96df636a1700 RCX: c000efff [4.178054] RDX: RSI: efff RDI: 0001 [4.178055] RBP: 96df4d379c00 R08: R09: aad3008571d0 [4.178056] R10: 0003 R11: bded2428 R12: aad300857474 [4.178057] R13: c1933140 R14: aad3008577d0 R15: 96df43e82000 [4.178058] FS: 7fcd5d9648c0() GS:96e2cc38() knlGS: [4.178060] CS: 0010 DS: ES: CR0: 80050033 [4.178061] CR2: 7fcd5d932a6d CR3: 000103e9a004 CR4: 003706f0 [4.178062] DR0: DR1: DR2: [4.178063] DR3: DR6: fffe0ff0 DR7: 0400 [4.178063] Call Trace: [4.178066] [4.178067] ? construct_phy+0xb26/0xd60 [amdgpu] [4.178422] ? __warn+0x81/0x130 [4.178426] ? construct_phy+0xb26/0xd60 [amdgpu] [4.178784] ? report_bug+0x171/0x1a0 [4.178787] ? handle_bug+0x3c/0x80 [4.178789] ? exc_invalid_op+0x17/0x70 [4.178790] ? asm_exc_invalid_op+0x1a/0x20 [4.178793] ? construct_phy+0xb26/0xd60 [amdgpu] [4.179149] ? construct_phy+0xb26/0xd60 [amdgpu] [4.179507] link_create+0x1b2/0x200 [amdgpu] [4.179865] create_links+0x135/0x420 [amdgpu] [4.180196] dc_create+0x321/0x640 [amdgpu] [4.180529] amdgpu_dm_init.isra.0+0x2a0/0x1ed0 [amdgpu] [4.180881] ? sysvec_apic_timer_interrupt+0xe/0x90 [4.180883] ? asm_sysvec_apic_timer_interrupt+0x1a/0x20 [4.180885] ? delay_tsc+0x37/0xa0 [4.180889] dm_hw_init+0x12/0x30 [amdgpu] [4.181240] amdgpu_device_init+0x1e42/0x24a0 [amdgpu] [4.181517] amdgpu_driver_load_kms+0x19/0x190 [amdgpu] [4.181793] amdgpu_pci_probe+0x165/0x4c0 [amdgpu] [4.182067] local_pci_probe+0x42/0xa0 [4.182070] pci_device_probe+0xc7/0x240 [4.182072] really_probe+0x19b/0x3e0 [4.182075] ? __pfx___driver_attach+0x10/0x10 [4.182076] __driver_probe_device+0x78/0x160 [4.182078] driver_probe_device+0x1f/0x90 [4.182079] __driver_attach+0xd2/0x1c0 [4.182081] bus_for_each_dev+0x85/0xd0 [4.182083] bus_add_driver+0x116/0x220 [4.182085] driver_register+0x59/0x100 [4.182087] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] [4.182356] do_one_initcall+0x58/0x320 [4.182359] do_init_module+0x60/0x240 [4.182361] init_module_from_file+0x89/0xe0 [4.182364] idempotent_init_module+0x120/0x2b0 [4.182366] __x64_sys_finit_module+0x5e/0xb0 [4.182367] do_syscall_64+0x61/0x120 [4.182370] ?
Bug#1056056: marked as done (linux-image-6.1.0-13-amd64: After a 'warm' reboot the disk is missing (not detected by the bios) on a HP t640)
Your message dated Sat, 02 Mar 2024 19:00:11 + with message-id and subject line Bug#1056056: fixed in linux 6.7.7-1 has caused the Debian Bug report #1056056, regarding linux-image-6.1.0-13-amd64: After a 'warm' reboot the disk is missing (not detected by the bios) on a HP t640 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.) -- 1056056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.55-1 Severity: important X-Debbugs-Cc: b...@sparknarrowcasting.nl If the HP t640 (I tried 2 different systems) runs this kernel, a 'reboot' will result in the BIOS reporting that the disk is missing. After a cold reboot (turning the device off and on again) the disk wil be detected and the system will boot as expected. The next reboot will again trigger this bug. Other HP thin-clients from similar series (t620, t630, t655) do not have the same problem. Debian bullseye (kernel 5.10) does not have this problem, but upgrading to 6.1.0 (through bulleye-backports) will trigger this bug. Upgrading bookworm to a 6.5 kernel (through bookworm-backports) does not solve the bug. Because the installer uses the same kernel, after the installation is complete and does the reboot, the bug will be triggered. -- Package-specific info: ** Version: Linux version 6.1.0-13-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=3b7b05fe-9cdc-49e7-9416-319125d9858e ro quiet ** Not tainted ** Kernel log: [ 0.00] Linux version 6.1.0-13-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) [ 0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=3b7b05fe-9cdc-49e7-9416-319125d9858e ro quiet [ 0.00] BIOS-provided physical RAM map: [ 0.00] BIOS-e820: [mem 0x-0x0009] usable [ 0.00] BIOS-e820: [mem 0x000a-0x000f] reserved [ 0.00] BIOS-e820: [mem 0x0010-0x09df] usable [ 0.00] BIOS-e820: [mem 0x09e0-0x09ffdfff] reserved [ 0.00] BIOS-e820: [mem 0x09ffe000-0x0a1f] usable [ 0.00] BIOS-e820: [mem 0x0a20-0x0a20afff] ACPI NVS [ 0.00] BIOS-e820: [mem 0x0a20b000-0x7a88dfff] usable [ 0.00] BIOS-e820: [mem 0x7a88e000-0x7a980fff] reserved [ 0.00] BIOS-e820: [mem 0x7a981000-0x7a9b5fff] ACPI data [ 0.00] BIOS-e820: [mem 0x7a9b6000-0x7af20fff] ACPI NVS [ 0.00] BIOS-e820: [mem 0x7af21000-0x7c96bfff] reserved [ 0.00] BIOS-e820: [mem 0x7c96c000-0x7ca04fff] type 20 [ 0.00] BIOS-e820: [mem 0x7ca05000-0x7dff] usable [ 0.00] BIOS-e820: [mem 0x7e00-0x7fff] reserved [ 0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [ 0.00] BIOS-e820: [mem 0xfd00-0xfdff] reserved [ 0.00] BIOS-e820: [mem 0xfeb8-0xfec01fff] reserved [ 0.00] BIOS-e820: [mem 0xfec1-0xfec10fff] reserved [ 0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved [ 0.00] BIOS-e820: [mem 0xfed4-0xfed44fff] reserved [ 0.00] BIOS-e820: [mem 0xfed8-0xfed8] reserved [ 0.00] BIOS-e820: [mem 0xfedc2000-0xfedc] reserved [ 0.00] BIOS-e820: [mem 0xfedd4000-0xfedd5fff] reserved [ 0.00] BIOS-e820: [mem 0xfee0-0xfeef] reserved [ 0.00] BIOS-e820: [mem 0xff00-0x] reserved [ 0.00] BIOS-e820: [mem 0x0001-0x00015eff] usable [ 0.00] BIOS-e820: [mem 0x00015f00-0x00017eff] reserved [ 0.00] BIOS-e820: [mem 0x00017f00-0x00017f33] usable [ 0.00] BIOS-e820: [mem 0x00017f34-0x00017fff] reserved [ 0.00] NX (Execute Disable) protection: active [ 0.00] efi: EFI v2.70 by American Megatrends [ 0.00] efi: TPMFinalLog=0x7aed8000 ACPI 2.0=0x7a998000 ACPI=0x7a998000
Bug#1064507: marked as done (linux-image-amd64: Enable CONFIG_SENSORS_HP_WMI)
Your message dated Sat, 02 Mar 2024 19:00:11 + with message-id and subject line Bug#1064507: fixed in linux 6.7.7-1 has caused the Debian Bug report #1064507, regarding linux-image-amd64: Enable CONFIG_SENSORS_HP_WMI 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.) -- 1064507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-amd64 Version: 6.5.10-1~bpo12+1 Severity: wishlist X-Debbugs-Cc: none, Lukasz Stelmach Dear Maintainer, Please enable CONFIG_SENSORS_HP_WMI to build hp-wmi-sensors module. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: arm64, armel Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-amd64 depends on: ii linux-image-6.5.0-0.deb12.4-amd64 6.5.10-1~bpo12+1 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: linux Source-Version: 6.7.7-1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 Mar 2024 08:22:54 +0100 Source: linux Architecture: source Version: 6.7.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1053650 1056056 1061449 1064507 Changes: linux (6.7.7-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.5 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.6 - mmc: sdhci-pci-o2micro: Fix a warm reboot issue that disk can't be detected by BIOS (Closes: #1056056) https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.7 - drm/amd/display: Only allow dig mapping to pwrseq in new asic (Closes: #1061449) . [ Weizhao Ouyang ] * Enable CONFIG_MFD_RK8XX_SPI for RK3588 SoC - MFD_RK8XX_SPI as built-in, same behavior as MFD_RK8XX_I2C . [ Uwe Kleine-König ] * [armhf] Enable DRM_PANEL_MIPI_DBI as a module for stm32mp157c-lxa-tac-gen2. * Backport a patch from v6.8-rc1 to be more verbose about pending deferred probes helping debugging of failed boot attempts. * [arm64] Make PINCTRL_ROCKCHIP builtin. . [ Vincent Blut ] * [x86] drivers/hwmon: Enable SENSORS_HP_WMI as module (Closes: #1064507) . [ Weihao Li] * [loong64] Build kernel image and udebs for loong64 (Closes: #1053650) Checksums-Sha1: 809f094e8d0f99ae6e9309118cff2beab3e53967 229550 linux_6.7.7-1.dsc 117f49946b9aef88988413febc00206d172ada74 144157632 linux_6.7.7.orig.tar.xz 3e4cec166430d91e066f8f476ef28e7587186fcb 1512756 linux_6.7.7-1.debian.tar.xz 1ea24e987c0c12f658f9354dc6127aac3f517ed8 7439 linux_6.7.7-1_source.buildinfo Checksums-Sha256: 496ed72685f9c58d313364d68b3c369853dc50d8d70697be767b702108cb1407 229550 linux_6.7.7-1.dsc 7748aecb4cf74300413ca1985fdab6d2ed082b6ddfcbd4823f3cbf6b3f8bc307 144157632 linux_6.7.7.orig.tar.xz 5ced01e4649bb873327572b69fa0fd3349705995c1267b662af161e2945a8c07 1512756 linux_6.7.7-1.debian.tar.xz ed871cebb89ac75fda21932243f8780a93da7b78ffd7f4d17cccee9b19e60637 7439 linux_6.7.7-1_source.buildinfo Files: f48e17a347cb1e4d21a28b57ea771634 229550 kernel optional linux_6.7.7-1.dsc b47e35f377b1ce371a4e6ceef2f6bed4 144157632 kernel optional linux_6.7.7.orig.tar.xz
Bug#1053650: marked as done ([loong64] Build a kernel image and udebs for loong64.)
Your message dated Sat, 02 Mar 2024 19:00:11 + with message-id and subject line Bug#1053650: fixed in linux 6.7.7-1 has caused the Debian Bug report #1053650, regarding [loong64] Build a kernel image and udebs for loong64. 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.) -- 1053650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux Version: 6.5.3-1 Severity: wishlist User: debian-de...@lists.debian.org Usertags: loongarch64 Dear maintainer, The Linux kernel source package does not yet support the Loong64 architecture. This patch has added support for deb and udeb, and we hope to adopt it. Thanks Weihao Li >From 87a0a9a9ab379e65a7d2abef989b318ca8a15272 Mon Sep 17 00:00:00 2001 From: Weihao Li Date: Fri, 15 Sep 2023 09:14:00 +0800 Subject: [PATCH 1/1] [loong64] Build a kernel image and udebs for loong64. --- debian/config/defines |1 + debian/config/loong64/config | 1832 + debian/config/loong64/defines | 15 + debian/config/loong64/none/defines|4 + debian/installer/kernel-versions |1 + debian/installer/modules/loong64/crc-modules |1 + .../modules/loong64/crypto-dm-modules |1 + .../installer/modules/loong64/crypto-modules |1 + debian/installer/modules/loong64/f2fs-modules |1 + debian/installer/modules/loong64/fat-modules |1 + debian/installer/modules/loong64/fb-modules |1 + debian/installer/modules/loong64/fuse-modules |1 + .../installer/modules/loong64/input-modules |1 + debian/installer/modules/loong64/jfs-modules |1 + debian/installer/modules/loong64/kernel-image |1 + debian/installer/modules/loong64/md-modules |1 + .../modules/loong64/mtd-core-modules |1 + debian/installer/modules/loong64/mtd-modules |1 + .../modules/loong64/multipath-modules |1 + debian/installer/modules/loong64/nbd-modules |1 + debian/installer/modules/loong64/nic-modules |1 + .../modules/loong64/nic-shared-modules|1 + .../installer/modules/loong64/nic-usb-modules |1 + .../modules/loong64/nic-wireless-modules |1 + debian/installer/modules/loong64/pata-modules |1 + debian/installer/modules/loong64/ppp-modules |1 + debian/installer/modules/loong64/sata-modules |1 + .../modules/loong64/scsi-core-modules |1 + debian/installer/modules/loong64/usb-modules |1 + .../modules/loong64/usb-serial-modules|1 + .../modules/loong64/usb-storage-modules |1 + 31 files changed, 1879 insertions(+) create mode 100644 debian/config/loong64/config create mode 100644 debian/config/loong64/defines create mode 100644 debian/config/loong64/none/defines create mode 100644 debian/installer/modules/loong64/crc-modules create mode 100644 debian/installer/modules/loong64/crypto-dm-modules create mode 100644 debian/installer/modules/loong64/crypto-modules create mode 100644 debian/installer/modules/loong64/f2fs-modules create mode 100644 debian/installer/modules/loong64/fat-modules create mode 100644 debian/installer/modules/loong64/fb-modules create mode 100644 debian/installer/modules/loong64/fuse-modules create mode 100644 debian/installer/modules/loong64/input-modules create mode 100644 debian/installer/modules/loong64/jfs-modules create mode 100644 debian/installer/modules/loong64/kernel-image create mode 100644 debian/installer/modules/loong64/md-modules create mode 100644 debian/installer/modules/loong64/mtd-core-modules create mode 100644 debian/installer/modules/loong64/mtd-modules create mode 100644 debian/installer/modules/loong64/multipath-modules create mode 100644 debian/installer/modules/loong64/nbd-modules create mode 100644 debian/installer/modules/loong64/nic-modules create mode 100644 debian/installer/modules/loong64/nic-shared-modules create mode 100644 debian/installer/modules/loong64/nic-usb-modules create mode 100644 debian/installer/modules/loong64/nic-wireless-modules create mode 100644 debian/installer/modules/loong64/pata-modules create mode 100644 debian/installer/modules/loong64/ppp-modules create mode 100644 debian/installer/modules/loong64/sata-modules create mode 100644 debian/installer/modules/loong64/scsi-core-modules create mode 100644 debian/installer/modules/loong64/usb-modules create mode 100644 debian/installer/modules/loong64/usb-serial-modules create mode 100644
linux_6.7.7-1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 Mar 2024 08:22:54 +0100 Source: linux Architecture: source Version: 6.7.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1053650 1056056 1061449 1064507 Changes: linux (6.7.7-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.5 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.6 - mmc: sdhci-pci-o2micro: Fix a warm reboot issue that disk can't be detected by BIOS (Closes: #1056056) https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.7 - drm/amd/display: Only allow dig mapping to pwrseq in new asic (Closes: #1061449) . [ Weizhao Ouyang ] * Enable CONFIG_MFD_RK8XX_SPI for RK3588 SoC - MFD_RK8XX_SPI as built-in, same behavior as MFD_RK8XX_I2C . [ Uwe Kleine-König ] * [armhf] Enable DRM_PANEL_MIPI_DBI as a module for stm32mp157c-lxa-tac-gen2. * Backport a patch from v6.8-rc1 to be more verbose about pending deferred probes helping debugging of failed boot attempts. * [arm64] Make PINCTRL_ROCKCHIP builtin. . [ Vincent Blut ] * [x86] drivers/hwmon: Enable SENSORS_HP_WMI as module (Closes: #1064507) . [ Weihao Li] * [loong64] Build kernel image and udebs for loong64 (Closes: #1053650) Checksums-Sha1: 809f094e8d0f99ae6e9309118cff2beab3e53967 229550 linux_6.7.7-1.dsc 117f49946b9aef88988413febc00206d172ada74 144157632 linux_6.7.7.orig.tar.xz 3e4cec166430d91e066f8f476ef28e7587186fcb 1512756 linux_6.7.7-1.debian.tar.xz 1ea24e987c0c12f658f9354dc6127aac3f517ed8 7439 linux_6.7.7-1_source.buildinfo Checksums-Sha256: 496ed72685f9c58d313364d68b3c369853dc50d8d70697be767b702108cb1407 229550 linux_6.7.7-1.dsc 7748aecb4cf74300413ca1985fdab6d2ed082b6ddfcbd4823f3cbf6b3f8bc307 144157632 linux_6.7.7.orig.tar.xz 5ced01e4649bb873327572b69fa0fd3349705995c1267b662af161e2945a8c07 1512756 linux_6.7.7-1.debian.tar.xz ed871cebb89ac75fda21932243f8780a93da7b78ffd7f4d17cccee9b19e60637 7439 linux_6.7.7-1_source.buildinfo Files: f48e17a347cb1e4d21a28b57ea771634 229550 kernel optional linux_6.7.7-1.dsc b47e35f377b1ce371a4e6ceef2f6bed4 144157632 kernel optional linux_6.7.7.orig.tar.xz 5b43a0437dbfaca68f24d07e35139613 1512756 kernel optional linux_6.7.7-1.debian.tar.xz 6ec17d7507e91f7cfef904ffc74f7d39 7439 kernel optional linux_6.7.7-1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmXi1ghfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89Es/EQAIyq/00l2wY+KhjZEuD6W03YpYc4vyDf cFzV6qWzMg0fhE7Cpn0xZV0M3jc5ElY8V1wbBMXbKbwaU7lEHtLV4CIBEy0EpFcK n0/gPSC6cLaHQ2hQ3DVzLGa4HrrkG/4Az27R8tdHR/FKfKBhlLegpJqoNEu/zcS/ N6NmiRvpAOTg545Z8ducU0QcP6Q7BuHnH2t6MzQgByuKjUNtEDBH14MgMpPweKYo 6Ar3+61xeZh5yUaxBmemGeYuLS9K4j2OIbvQroWjCqUtFcA7Yr8z7wx7PTK8aQrX gwmetI7r5hyPFjX/rjrEu+NSc2iWYY1Itft0oFi1cThSi+nKW044CoH+S1dxKvNW Uhqp+PIWtVTC6SDLZQjUDPajuApjWjzLhsCdIpEZiiNHzKSfCAuFYoy+LJcXUD6g ID/ZM6gs1+6jXyBAokWJ4ezesz7p1NORq0WNK2aRqGReVa72NSdKx2jpO/xTeNBB Th3ELOSJ27VvWA+NymuQdqN1WBgh3rHAzg3/iZxQkYLwvtH1qB9d/PcaiKk4OEGi Wn6tHONP9S5U62jTuCYcF/VstBIBcpXbfdyO1Gv+FoS09uzPs2so7cVes7tSzxQ/ /9CsoycaTbnbU1YFl3m/HsAenZS4hrzZQAcq7HaUWnNCygTjS4RWtYDaivaG96VU kRoMoiufOzsE =VBdB -END PGP SIGNATURE- pgp7KWYfh8T_5.pgp Description: PGP signature
Bug#1065320: linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle
Package: src:linux Version: 6.1.76-1 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: leeejobsacco...@mail.co.uk Dear Maintainer, * What led up to the situation? Trying to boot the system with the 6.1.0-18 kernel * What exactly did you do (or not do) that was effective (or ineffective)? I tried adding 'boot_delay=1000' boot option to slow the console scroll rate, to enable better recording of the error messages. I tried rebooting the previous 6.1.0-17 kernel. * What was the outcome of this action? After adding the 'boot_delay=1000' option the boot process progressed no further than "Loading initial ramdisk ..." (left for several minutes - required power cycle). The system boots sucessfully on the previous 6.1.0-17 kernel * What outcome did you expect instead? I expected the system to successfully boot. * Additional observations This system also normally includes 'hpet=disable' and 'acpi_enforce_resources=lax' boot options but removing these made no difference. Although I was not able to boot the system with the 'boot_delay=1000' option and obtain clear photographs of the console output - the ones I've attached suffer from 'overprinting' - it does seem clear that ACPI errors are being reported. There appear to be two distinct phases to this problem. Initially, ACPI seems to be reporting errors for "GPE", as shown in the first attached photograph, but after ~10 seconds or so, ACPI then switches to continuously reporting an error for PM_TIMER, as shown in the second attached photograph. At this point a power cycle is required. Purging and reinstalling the package made no difference. Atm, only three kernels are installed on this system but I have had more in the past as I normally compile my own kernels from the corresponding Debian source package. My own 6.1.76-1 kernel also suffers from the same problem, whereas my own 6.1.69-1 kernel boots and runs Ok. Comparing the kernel configs for 6.1.0-17 and 6.1.0-18 showed just one functional change - an additional Compile-time checks and compiler option, which did not seem relevant to this problem. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTeK COMPUTER INC. product_name: E203NA product_version: 1.0 chassis_vendor: ASUSTeK COMPUTER INC. chassis_version: 1.0 bios_vendor: American Megatrends Inc. bios_version: E203NA.312 board_vendor: ASUSTeK COMPUTER INC. board_name: E203NA board_version: 1.0 ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge [8086:5af0] (rev 0b) Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge [1043:1980] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 500 [1043:1980] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 1064976 - wontfix Bug #1064976 [linux-headers-amd64] linux-headers-6.6.13+bpo-amd64 incorrectly depends on the corresponding linux-image-amd64 package Removed tag(s) wontfix. > End of message, stopping processing here. Please contact me if you need assistance. -- 1064976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
