Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu
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] ? do_syscall_64+0x70/0x120 [4.182372] entry_SYSCALL_64_after_hwframe+0x6e/0x76 [4.182375] RIP: 0033:0x7fcd5e130f19 [4.182376] Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cf 1e 0d 00 f7 d8 64 89 01 48 [4.182378] RSP: 002b:7ffd314afa38 EFLAGS: 0246 ORIG_RAX: 0139 [4.182379] RAX: ffda RBX: 5611ee7f84d0 RCX: 7fcd5e130f19 [4.182380] RDX: RSI: 7fcd5e2644f5 RDI: 0024 [4.182381] RBP: R08: 0040 R09: 5611ee7d3140 [4.182382] R10: 0038 R11: 0246 R12: 7fcd5e2644f5 [4.182383] R13: 0002 R14: 5611ee7f0670 R15: 0
Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu
Yes, the message is from the version 6.7.1-1~exp1, sorry for the doubt. It is just because, package name is «simply»: linux-image-6.7-amd64 and so I wrote 6.7, expecting the exact version from reportbug. I will give it a try then and be back. Le mer. 24 janv. 2024 à 20:02, Diederik de Haas a écrit : > > Control: tag -1 moreinfo > > On Wednesday, 24 January 2024 19:38:16 CET Patrice Duroux wrote: > > Package: src:linux > > Version: 6.7.1-1~exp1 > > Severity: normal > > > > Giving a try to 6.7, here is a message extracted from dmesg: > > Is that dmesg output from 6.7(.0) or 6.7.1? > If from 6.7.1, does the error NOT occur with 6.7.0? > If that's the case, can you test the attached patch with the `test-patches` > script? See the following link for instructions: > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu
[7.194222] i915 :00:02.0: [drm] *ERROR* Failed to probe lspcon [7.194233] i915 :00:02.0: [drm] *ERROR* LSPCON init failed on port D [7.729740] [drm] UVD and UVD ENC initialized successfully. [7.829659] [drm] VCE initialized successfully. [7.831637] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [7.831650] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1 [7.831766] amdgpu: Virtual CRAT table created for GPU [7.831799] amdgpu: Topology: Add dGPU node [0x6981:0x1002] [7.831801] kfd kfd: amdgpu: added device 1002:6981 [7.831811] amdgpu :01:00.0: amdgpu: SE 2, SH per SE 1, CU per SH 5, active_cu_number 10 [7.834477] amdgpu :01:00.0: amdgpu: Using BOCO for runtime pm [7.834989] [drm] Initialized amdgpu 3.56.0 20150101 for :01:00.0 on minor 1 [7.840264] amdgpu :01:00.0: [drm] Cannot find any crtc or sizes [9.050977] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [9.062123] systemd[1]: modprobe@drm.service: Deactivated successfully. [9.062252] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. [9.662446] snd_hda_intel :01:00.1: bound :01:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [ 12.417633] i915 :00:02.0: [drm] *ERROR* Failed to probe lspcon [ 12.417637] i915 :00:02.0: [drm] *ERROR* LSPCON init failed on port D [ 22.566786] i915 :00:02.0: [drm] *ERROR* Failed to probe lspcon [ 22.566790] i915 :00:02.0: [drm] *ERROR* LSPCON init failed on port D Does this need further testing from my side? Thanks!! Le mer. 24 janv. 2024 à 20:09, Patrice Duroux a écrit : > > Yes, the message is from the version 6.7.1-1~exp1, sorry for the doubt. > It is just because, package name is «simply»: linux-image-6.7-amd64 > and so I wrote 6.7, expecting the exact version from reportbug. > I will give it a try then and be back. > > > Le mer. 24 janv. 2024 à 20:02, Diederik de Haas > a écrit : > > > > Control: tag -1 moreinfo > > > > On Wednesday, 24 January 2024 19:38:16 CET Patrice Duroux wrote: > > > Package: src:linux > > > Version: 6.7.1-1~exp1 > > > Severity: normal > > > > > > Giving a try to 6.7, here is a message extracted from dmesg: > > > > Is that dmesg output from 6.7(.0) or 6.7.1? > > If from 6.7.1, does the error NOT occur with 6.7.0? > > If that's the case, can you test the attached patch with the `test-patches` > > script? See the following link for instructions: > > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu
After a test, the patch at https://gitlab.freedesktop.org/drm/amd/-/issues/3122#note_2252835 is working fine on my side. Many thanks to Diederik! Le dim. 28 janv. 2024 à 15:00, Diederik de Haas a écrit : > > Patrice, > > On Sunday, 28 January 2024 11:44:59 CET Linux regression tracking (Thorsten > Leemhuis) wrote: > > On 27.01.24 14:14, Salvatore Bonaccorso wrote: > > > In Debian (https://bugs.debian.org/1061449) we got the following > > > quotred report: > > > > > > On Wed, Jan 24, 2024 at 07:38:16PM +0100, Patrice Duroux wrote: > > >> 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] > > > > > > [...] > > > > Not my area of expertise, but looks a lot like a duplicate of > > https://gitlab.freedesktop.org/drm/amd/-/issues/3122#note_2252835 > > > > Mario (now CCed) already prepared a patch for that issue that seems to work. > > If you can build and test a kernel with the `test-patches` script like before > with the attached patch, but *without* the previous patch (which just reverted > commit b17ef04bf3a4346d66404454d6a646343ddc9749), that would be really useful. > > When you've done that, do a Reply-All to Thorsten Leemhuis' message so that > everyone sees the results. Optionally also reply to the gitlab issue Thorsten > mentioned. > > (It didn't seem useful to send these instructions to all the people/lists)
Bug#1061449: linux-image-6.7-amd64: a boot message from amdgpu
Package: src:linux Version: 6.7.4-1~exp1 Followup-For: Bug #1061449 Dear Maintainer, Just for info, the same error occurs also with 6.7.4-1~exp1. Regards, Patrice [4.067807] [ cut here ] [4.067808] WARNING: CPU: 7 PID: 246 at drivers/gpu/drm/amd/amdgpu/../display/dc/link/link_factory.c:387 construct_phy+0xb26/0xd60 [amdgpu] [4.068223] Modules linked in: amdgpu(+) i915(+) drm_exec amdxcp sd_mod gpu_sched drm_buddy nvme drm_suballoc_helper i2c_algo_bit drm_display_helper nvme_core ahci hid_generic liba hci crc32_pclmul crc32c_intel t10_pi cec libata rc_core crc64_rocksoft_generic drm_ttm_helper ghash_clmulni_intel i2c_hid_acpi crc64_rocksoft sha512_ssse3 ttm crc_t10dif i2c_hid rtsx_ pci_sdmmc sha512_generic xhci_pci crct10dif_generic drm_kms_helper xhci_hcd mmc_core scsi_mod hid intel_lpss_pci crct10dif_pclmul i2c_i801 sha256_ssse3 intel_lpss crc64 thunderbolt dr m e1000e usbcore sha1_ssse3 rtsx_pci video i2c_smbus crct10dif_common usb_common scsi_common idma64 battery wmi button aesni_intel crypto_simd cryptd [4.068253] CPU: 7 PID: 246 Comm: (udev-worker) Not tainted 6.7-amd64 #1 Debian 6.7.4-1~exp1 [4.068256] Hardware name: Dell Inc. Precision 7540/0T2FXT, BIOS 1.29.0 11/03/2023 [4.068257] RIP: 0010:construct_phy+0xb26/0xd60 [amdgpu] [4.068593] Code: b9 01 00 00 00 83 fe 01 74 40 48 8b 82 f8 03 00 00 89 f2 48 c7 c6 70 57 a4 c1 48 8b 40 10 48 8b 00 48 8b 78 08 e8 fa b5 3e e9 <0f> 0b 49 8b 87 d0 01 00 00 b9 0f 0 0 00 00 48 8b 80 e8 04 00 00 48 [4.068595] RSP: 0018:b5d88083f318 EFLAGS: 00010246 [4.068596] RAX: RBX: a0f433036000 RCX: c000efff [4.068598] RDX: RSI: efff RDI: 0001 [4.068598] RBP: a0f4133c3600 R08: R09: b5d88083f0e0 [4.068599] R10: 0003 R11: abcd2428 R12: b5d88083f384 [4.068600] R13: c1905120 R14: b5d88083f6e0 R15: a0f433e11000 [4.068601] FS: 7f9eab8428c0() GS:a0f78c3c() knlGS: [4.068603] CS: 0010 DS: ES: CR0: 80050033 [4.068604] CR2: 7ffe7d8ebf88 CR3: 0001048aa002 CR4: 003706f0 [4.068605] DR0: DR1: DR2: [4.068606] DR3: DR6: fffe0ff0 DR7: 0400 [4.068607] Call Trace: [4.068609] [4.068610] ? construct_phy+0xb26/0xd60 [amdgpu] [4.068947] ? __warn+0x81/0x130 [4.068950] ? construct_phy+0xb26/0xd60 [amdgpu] [4.069285] ? report_bug+0x171/0x1a0 [4.069288] ? handle_bug+0x3c/0x80 [4.069290] ? exc_invalid_op+0x17/0x70 [4.069291] ? asm_exc_invalid_op+0x1a/0x20 [4.069294] ? construct_phy+0xb26/0xd60 [amdgpu] [4.069627] ? construct_phy+0xb26/0xd60 [amdgpu] [4.069965] link_create+0x1b2/0x200 [amdgpu] [4.070298] create_links+0x135/0x420 [amdgpu] [4.070614] dc_create+0x321/0x640 [amdgpu] [4.070931] amdgpu_dm_init.isra.0+0x2a0/0x1df0 [amdgpu] [4.071254] ? sysvec_apic_timer_interrupt+0xe/0x90 [4.071257] ? asm_sysvec_apic_timer_interrupt+0x1a/0x20 [4.071259] ? delay_tsc+0x1e/0xa0 [4.071262] dm_hw_init+0x12/0x30 [amdgpu] [4.071587] amdgpu_device_init+0x1e42/0x24a0 [amdgpu] [4.071838] amdgpu_driver_load_kms+0x19/0x190 [amdgpu] [4.072087] amdgpu_pci_probe+0x165/0x4c0 [amdgpu] [4.072335] local_pci_probe+0x42/0xa0 [4.072338] pci_device_probe+0xc7/0x240 [4.072340] really_probe+0x19b/0x3e0 [4.072343] ? __pfx___driver_attach+0x10/0x10 [4.072344] __driver_probe_device+0x78/0x160 [4.072346] driver_probe_device+0x1f/0x90 [4.072348] __driver_attach+0xd2/0x1c0 [4.072349] bus_for_each_dev+0x85/0xd0 [4.072352] bus_add_driver+0x116/0x220 [4.072354] driver_register+0x59/0x100 [4.072356] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] [4.072601] do_one_initcall+0x58/0x320 [4.072604] do_init_module+0x60/0x240 [4.072606] init_module_from_file+0x89/0xe0 [4.072608] ? generic_update_time+0x4e/0x60 [4.072612] idempotent_init_module+0x120/0x2b0 [4.072614] __x64_sys_finit_module+0x5e/0xb0 [4.072616] do_syscall_64+0x61/0x120 [4.072619] ? exit_to_user_mode_prepare+0x40/0x1e0 [4.072621] ? syscall_exit_to_user_mode+0x2b/0x40 [4.072622] ? do_syscall_64+0x70/0x120 [4.072624] ? syscall_exit_to_user_mode+0x2b/0x40 [4.072625] ? do_syscall_64+0x70/0x120 [4.072627] ? syscall_exit_to_user_mode+0x2b/0x40 [4.072628] ? do_syscall_64+0x70/0x120 [4.072630] ? exit_to_user_mode_prepare+0x40/0x1e0 [4.072631] ? syscall_exit_to_user_mode+0x2b/0x40 [4.072633] ? do_syscall_64+0x70/0x120 [4.072634] entry_SYSCALL_64_after_hwframe+0x6e/0x76 [4.072636] RIP: 0033:0x7f9eac011059 [4.072638] Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0
Bug#949436: firmware-iwlwifi: Got an HT rate (flags:0x88/mcs:15) for a non data frame
Hi Diederik, No more the case, everything is fine after many upgrades since this issue. My system is still the same hardware but with a Debian sid. So, on my side, you can close it. Regards, Patrice Le ven. 23 févr. 2024 à 15:39, Diederik de Haas a écrit : > > Control: tag -1 moreinfo > > On 20 Jan 2020 22:32:26 +0100 Patrice Duroux wrote: > > Package: firmware-iwlwifi > > Version: 20190717-2 > > > > I am reporting this «exception» here without being sure this is the right > > package or if it has been already reported (not easy to check). > > > > [ 48.335755] [ cut here ] > > [ 48.335766] Got an HT rate (flags:0x88/mcs:15) for a non data frame > > [ 48.335839] WARNING: CPU: 7 PID: 543 at > > drivers/net/wireless/intel/iwlwifi/mvm/tx.c:333 > > ... > > [ 48.336015] CPU: 7 PID: 543 Comm: irq/37-iwlwifi Tainted: G OE > > 5.4.0-3-amd64 #1 Debian 5.4.13-1 > > [ 48.336018] Hardware name: Hewlett-Packard HP ZBook 15 G2/2253, BIOS M70 > > Ver. 01.25 08/29/2019 > > [ 48.336039] RIP: 0010:iwl_mvm_get_tx_rate.isra.0+0xc0/0xd0 [iwlmvm] > > ... > > [ 48.336079] Call Trace: > > [ 48.336105] iwl_mvm_set_tx_cmd_rate+0x66/0xc0 [iwlmvm] > > [ 48.336125] iwl_mvm_set_tx_params+0x337/0x4f0 [iwlmvm] > > ... > > [ 48.336862] ---[ end trace c6ab05d82de48c15 ]--- > > While firmware may be relevant, a kernel stack trace indicates it's more > likely > to be a kernel problem. > Can you reproduce this issue with more recent firmware and kernel?
Bug#1000541: firmware-iwlwifi: are some firmwares missing or is the boot looking upstream unavailable ones?
Package: firmware-iwlwifi Version: 20210818-1 Severity: minor Dear Maintainer, This is more an observation than an issue on my system. dmesg messages say: [ 12.316908] iwlwifi :6f:00.0: enabling device ( -> 0002) [ 12.337431] iwlwifi :6f:00.0: firmware: failed to load iwlwifi- cc-a0-66.ucode (-2) [ 12.337443] iwlwifi :6f:00.0: Direct firmware load for iwlwifi- cc-a0-66.ucode failed with error -2 [ 12.337471] iwlwifi :6f:00.0: firmware: failed to load iwlwifi- cc-a0-65.ucode (-2) [ 12.337476] iwlwifi :6f:00.0: Direct firmware load for iwlwifi- cc-a0-65.ucode failed with error -2 [ 12.337494] iwlwifi :6f:00.0: firmware: failed to load iwlwifi- cc-a0-64.ucode (-2) [ 12.337497] iwlwifi :6f:00.0: Direct firmware load for iwlwifi- cc-a0-64.ucode failed with error -2 [ 12.339305] iwlwifi :6f:00.0: firmware: direct-loading firmware iwlwifi- cc-a0-63.ucode [ 12.339338] iwlwifi :6f:00.0: api flags index 2 larger than supported by driver [ 12.339377] iwlwifi :6f:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 12.340243] iwlwifi :6f:00.0: loaded firmware version 63.c04f3485.0 cc-a0-63.ucode op_mode iwlmvm [ 12.340301] iwlwifi :6f:00.0: firmware: failed to load iwl-debug- yoyo.bin (-2) [ 12.649115] iwlwifi :6f:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 12.797211] iwlwifi :6f:00.0: Detected RF HR B3, rfid=0x10a100 [ 12.866241] iwlwifi :6f:00.0: base HW address: 5c:80:b6:e9:d7:d9 [ 13.392299] iwlwifi :6f:00.0 wlp111s0: renamed from wlan0 The iwlwifi-cc-a0-[66,65,64].ucode firmwares do not exist neither in the package neither here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/ But it exists there iwlwifi-cc-a0-67.ucode that is not in the package. Could this be the reason of those messages? Thanks, Patrice ps: my system kernel package is linux-image-5.15.0-1-amd64 (5.15.3-1) -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-1-amd64 (SMP w/12 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.140 -- no debconf information
Bug#1076555: linux-image-6.9.9-amd64: boot crash RIP: 0010:kmem_cache_alloc
Package: src:linux Version: 6.9.9-1 Severity: minor Dear Maintainer, I just faced this boot problem on my sid system for the first time since I updated the Linux kernel a few days ago. I do not know if it could be something related to some hardware failure or a possible software bug in the linux kernel or a service. Regards, Patrice -- Package-specific info: ** Version: Linux version 6.9.9-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-13 (Debian 13.3.0-3) 13.3.0, GNU ld (GNU Binutils for Debian) 2.42.50.20240710) #1 SMP PREEMPT_DYNAMIC Debian 6.9.9-1 (2024-07-13) ** Command line: initrd=\be351e757dc049ffa300ddbaf0f4856a\6.9.9-amd64\initrd.img-6.9.9-amd64 root=UUID=2b8c6592-0954-4ecd-977d-738c855f3dff ro quiet splash systemd.machine_id=be351e757d c049ffa300ddbaf0f4856a ** Not tainted ** Kernel log: [ 12.039117] usb 1-11: Found UVC 1.50 device Integrated_Webcam_HD (1bcf:28c4) [ 12.059706] Intel(R) Wireless WiFi driver for Linux [ 12.059850] iwlwifi :6f:00.0: enabling device ( -> 0002) [ 12.068383] iwlwifi :6f:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x8000 [ 12.068487] iwlwifi :6f:00.0: PCI dev 2723/4080, rev=0x340, rfid=0x10a100 [ 12.073697] iwlwifi :6f:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 12.074053] iwlwifi :6f:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 12.074160] iwlwifi :6f:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 12.074162] iwlwifi :6f:00.0: loaded firmware version 77.a20fb07d.0 cc-a0-77.ucode op_mode iwlmvm [ 12.080445] Bluetooth: Core ver 2.22 [ 12.080462] NET: Registered PF_BLUETOOTH protocol family [ 12.080463] Bluetooth: HCI device and connection manager initialized [ 12.080466] Bluetooth: HCI socket layer initialized [ 12.080468] Bluetooth: L2CAP socket layer initialized [ 12.080470] Bluetooth: SCO socket layer initialized [ 12.113923] usb 1-11: Found UVC 1.50 device Integrated_Webcam_HD (1bcf:28c4) [ 12.131467] usbcore: registered new interface driver uvcvideo [ 12.277127] iwlwifi :6f:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 12.277169] thermal thermal_zone10: failed to read out thermal zone (-61) [ 12.351469] EXT4-fs (sda): mounted filesystem cd65fcb3-29d2-4aa9-9283-c5779d95a14f r/w with ordered data mode. Quota mode: none. [ 12.388912] audit: type=1400 audit(1721324237.855:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/lxc-start" pid=776 comm="apparmo r_parser" [ 12.388933] audit: type=1400 audit(1721324237.855:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/lxc-copy" pid=775 comm="apparmor _parser" [ 12.389739] audit: type=1400 audit(1721324237.859:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="torbrowser_tor" pid=772 comm="apparmor_pa rser" [ 12.389938] audit: type=1400 audit(1721324237.859:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=769 comm="apparmor_p arser" [ 12.389942] audit: type=1400 audit(1721324237.859:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=769 comm="appa rmor_parser" [ 12.389943] audit: type=1400 audit(1721324237.859:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=767 comm="apparmor_parse r" [ 12.390294] audit: type=1400 audit(1721324237.859:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=777 comm="apparmor_pars er" [ 12.390297] audit: type=1400 audit(1721324237.859:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=777 comm="apparmor_parser " [ 12.390299] audit: type=1400 audit(1721324237.859:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=777 comm="apparmor_parser " [ 12.390943] audit: type=1400 audit(1721324237.859:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="passt" pid=778 comm="apparmor_parser" [ 12.426669] iwlwifi :6f:00.0: Detected RF HR B3, rfid=0x10a100 [ 12.497639] iwlwifi :6f:00.0: base HW address: 5c:80:b6:e9:d7:d9 [ 12.568334] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input22 [ 12.683306] input: HDA Intel PCH Headphone Mic as /devices/pci:00/:00:1f.3/sound/card0/input23 [ 12.683354] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input24 [ 12.684214] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input25 [ 12.684261] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input26 [ 12.705467] usb 1-14: USB disconnect, device number 4 [ 12.718264] block nvme0n1: No UUID available providing old NGUID [ 12.718973] iwlwifi :6f:00.0 wlp111s0: renamed from wlan0 [ 12.727856] usbcore: registered new interface driver btusb [
Bug#973551: wireless-regdb: regulatory.bin(.5.gz) are superfluous with crda an abandonware
Package: wireless-regdb Version: 2020.04.29-2 Severity: wishlist Dear Maintainer, Considering both: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972994 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973241 I suspect that crda is obsolete and so the files regulatory.bin(.5.gz) in wireless-regdb, or moved to the crda package itself, isn't it? Thanks, Patrice -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/12 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 wireless-regdb depends on no packages. wireless-regdb recommends no packages. Versions of packages wireless-regdb suggests: pn crda -- no debconf information
kernel 5.2.x and firmware-iwlwifi: incompatibilities?
Hi, I am using Sid on my laptop (HP ZBook 15) and since first linux-image-5.2.0-1 and then linux-image-5.2.0-2 the wifi is not stable and goes down after few seconds. But what is more strange is that with linux-image-5.2.0-1 there is a log trace of the trouble but not with linux-image-5.2.0-2. Here is an extract of the log using first package 5.2.0-1: Aug 7 14:51:56 hp-dark kernel: [9.179880] iwlwifi :3d:00.0: enabling device ( -> 0002) Aug 7 14:51:56 hp-dark kernel: [9.202169] iwlwifi :3d:00.0: firmware: direct-loading firmware iwlwifi-7260-17.ucode Aug 7 14:51:56 hp-dark kernel: [9.202295] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0 op_mode iwlmvm Aug 7 14:51:56 hp-dark kernel: [9.226381] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 Aug 7 14:51:56 hp-dark kernel: [9.248304] iwlwifi :3d:00.0: base HW address: a4:c4:94:7e:87:b3 Aug 7 14:51:56 hp-dark kernel: [9.490499] iwlwifi :3d:00.0 wlp61s0: renamed from wlan0 [...] Aug 7 14:56:28 hp-dark kernel: [ 276.194561] iwlwifi :3d:00.0: Microcode SW error detected. Restarting 0x8200. Aug 7 14:56:28 hp-dark kernel: [ 276.195187] iwlwifi :3d:00.0: Start IWL Error Log Dump: Aug 7 14:56:28 hp-dark kernel: [ 276.195189] iwlwifi :3d:00.0: Status: 0x0080, count: 6 Aug 7 14:56:28 hp-dark kernel: [ 276.195191] iwlwifi :3d:00.0: Loaded firmware version: 17.3216344376.0 Aug 7 14:56:28 hp-dark kernel: [ 276.195193] iwlwifi :3d:00.0: 0x0EDC | ADVANCED_SYSASSERT Aug 7 14:56:28 hp-dark kernel: [ 276.195194] iwlwifi :3d:00.0: 0x0220 | trm_hw_status0 Aug 7 14:56:28 hp-dark kernel: [ 276.195196] iwlwifi :3d:00.0: 0x | trm_hw_status1 Aug 7 14:56:28 hp-dark kernel: [ 276.195197] iwlwifi :3d:00.0: 0x0B30 | branchlink2 Aug 7 14:56:28 hp-dark kernel: [ 276.195199] iwlwifi :3d:00.0: 0x000164C0 | interruptlink1 Aug 7 14:56:28 hp-dark kernel: [ 276.195200] iwlwifi :3d:00.0: 0x | interruptlink2 Aug 7 14:56:28 hp-dark kernel: [ 276.195202] iwlwifi :3d:00.0: 0xDEADBEEF | data1 Aug 7 14:56:28 hp-dark kernel: [ 276.195203] iwlwifi :3d:00.0: 0xDEADBEEF | data2 Aug 7 14:56:28 hp-dark kernel: [ 276.195205] iwlwifi :3d:00.0: 0xDEADBEEF | data3 Aug 7 14:56:28 hp-dark kernel: [ 276.195206] iwlwifi :3d:00.0: 0x1DC083AA | beacon time Aug 7 14:56:28 hp-dark kernel: [ 276.195208] iwlwifi :3d:00.0: 0xCEF54069 | tsf low Aug 7 14:56:28 hp-dark kernel: [ 276.195209] iwlwifi :3d:00.0: 0x0045 | tsf hi Aug 7 14:56:28 hp-dark kernel: [ 276.195211] iwlwifi :3d:00.0: 0x | time gp1 Aug 7 14:56:28 hp-dark kernel: [ 276.195212] iwlwifi :3d:00.0: 0x0FB4FC50 | time gp2 Aug 7 14:56:28 hp-dark kernel: [ 276.195214] iwlwifi :3d:00.0: 0x | uCode revision type Aug 7 14:56:28 hp-dark kernel: [ 276.195215] iwlwifi :3d:00.0: 0x0011 | uCode version major Aug 7 14:56:28 hp-dark kernel: [ 276.195217] iwlwifi :3d:00.0: 0xBFB58538 | uCode version minor Aug 7 14:56:28 hp-dark kernel: [ 276.195219] iwlwifi :3d:00.0: 0x0144 | hw version Aug 7 14:56:28 hp-dark kernel: [ 276.195220] iwlwifi :3d:00.0: 0x40489204 | board version Aug 7 14:56:28 hp-dark kernel: [ 276.195221] iwlwifi :3d:00.0: 0x20D1 | hcmd Aug 7 14:56:28 hp-dark kernel: [ 276.195222] iwlwifi :3d:00.0: 0x24022002 | isr0 Aug 7 14:56:28 hp-dark kernel: [ 276.195224] iwlwifi :3d:00.0: 0x0080 | isr1 Aug 7 14:56:28 hp-dark kernel: [ 276.195225] iwlwifi :3d:00.0: 0x0002 | isr2 Aug 7 14:56:28 hp-dark kernel: [ 276.195226] iwlwifi :3d:00.0: 0x004028C0 | isr3 Aug 7 14:56:28 hp-dark kernel: [ 276.195227] iwlwifi :3d:00.0: 0x | isr4 Aug 7 14:56:28 hp-dark kernel: [ 276.195228] iwlwifi :3d:00.0: 0x4110 | last cmd Id Aug 7 14:56:28 hp-dark kernel: [ 276.195230] iwlwifi :3d:00.0: 0x | wait_event Aug 7 14:56:28 hp-dark kernel: [ 276.195231] iwlwifi :3d:00.0: 0x0094 | l2p_control Aug 7 14:56:28 hp-dark kernel: [ 276.195232] iwlwifi :3d:00.0: 0x00018030 | l2p_duration Aug 7 14:56:28 hp-dark kernel: [ 276.195234] iwlwifi :3d:00.0: 0x000F | l2p_mhvalid Aug 7 14:56:28 hp-dark kernel: [ 276.195235] iwlwifi :3d:00.0: 0x0085 | l2p_addr_match Aug 7 14:56:28 hp-dark kernel: [ 276.195236] iwlwifi :3d:00.0: 0x0005 | lmpm_pmg_sel Aug 7 14:56:28 hp-dark kernel: [ 276.195237] iwlwifi :3d:00.0: 0x15041745 | timestamp Aug 7 14:56:28 hp-dark kernel: [ 276.195238] iwlwifi :3d:00.0: 0x7888 | flow_handler Aug 7 14:56:28 hp-dark kernel: [ 276.195275] iwlwifi :3d:00.0: Fseq Registers: Aug 7 14:56:28 hp-dark kernel: [ 276.195355] iwlwifi :3d:00.0: 0x | FSEQ_ERROR_CODE Aug 7 14:56:28 hp-dark kernel: [ 276.195433] iwlwifi :3d:00.0: 0x | FSEQ_TOP_INIT_VERSION Aug 7 14:56:28 hp-dark kernel: [ 276.195439] iwlwifi :3d:00.0: 0x |
Re: Intel Wifi Solutions for Newer Kernel
Hi, It seems to be better stable on my side with the last 5.2.9-1. Thanks!
Bug#638068: [bisected] initramfs-tools generates unbootable initrd.img on IA-64
Hi, After having a look to the contents of initrd.img-3.0.0-2-mckinley and of initrd.img-2.6.32-5-mckinley, I have notice some points about the first one that don't boot. It confirms that busybox is missing even if the included conf/initramfs.conf says BUSYBOX=y. Also it appears to have a multiarch content and also libm.so is missing. May it be a problem? Regards, Patrice. ps: the diff result is attached. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/73d68774970b09434568c644acfe5...@mail.igh.cnrs.fr
Bug#1076555: linux-image-6.9.9-amd64: boot crash RIP: 0010:kmem_cache_alloc
Hi Ben, All my attempts both after installing 6.9.9 on my current Sid system, or using a snapshot of Sid at that time when linux-image-6.9.9 was pushed (fastidious by the way) have failed. I am not able to get the issue again. But since then it occurs to me that there was also a firmware update (fwupd) for my Dell laptop system (1.32.0 to 1.34.0) $ LC_ALL="C.UTF-8" fwupdmgr get-history Dell Inc. Precision 7540 │ └─System Firmware: │ Device ID: 591f43f1e1ff1092daa9c95dd2b19488a82ae9e4 │ Previous version: 1.32.0 │ Update State: Success │ Last modified: 2024-08-24 11:04 │ GUID: 74992bad-d49d-4f82-bb77-bbe865bea34e │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ └─Precision 7X40 System Update: New version: 1.34.0 Remote ID:lvfs Release ID: 95810 Summary: Firmware for the Dell Precision 7X40 License: Proprietary Size: 22.5 MB Created: 2024-07-11 Urgency: Critical Vendor: Dell Release Flags:• Trusted metadata Description: This stable release fixes the following issues: • This release contains security updates as disclosed in the Dell Security Advisory. Issue:DSA-2024-243 Checksum: 6a5fa4d418e93826767d42405c2a7ad8236647fa4fe85d570d3ae1ccc5dafafb Could this actually be a fix? Regards, Patrice Le jeu. 5 sept. 2024 à 02:14, Ben Hutchings a écrit : > > On Mon, 2024-09-02 at 13:33 +0200, Patrice Duroux wrote: > > Hi Ben, > > > > Le lun. 2 sept. 2024 à 00:59, Ben Hutchings a écrit : > [...] > > > - There is a newer kernel version available in unstable now (6.10.6 or > > > maybe 6.10.7 by the time you read this). Does that fix the issue? > > > > Since then, I have upgraded and am now using the 6.11.x series from > > experimental > > without experiencing this issue anymore. > > That's good news! But 6.11 will not reach unstable for a few weeks. > > > > - Do these same error messages appear on every boot? > > > > Often, but not always. I was also not sure if it could be related to > > #1076561 > > that I had seen pass by at the same time. > > I don't see any connection with that bug. > > > > - If you prevent the dell_wmi_sysman module loading, by adding > > > "blacklist=dell_wmi_sysman" to the kernel command line, do all of the > > > error messages stop appearing? > > > > Would you like me to reinstall one of those kernel versions so as to > > reproduce this issue > > and try adding the option? > > Yes please. > > Ben. > > -- > Ben Hutchings > Theory and practice are closer in theory than in practice - John Levine >
