Control: tag -1 moreinfo

On Mon, 29 Jul 2024 18:07:37 +0200 Patrice Duroux
<patrice.dur...@gmail.com> wrote:
> Hi Bastian,
> Sorry I probably did something wrong with gnome-logs. Let's go then
> with journalctl
> and here are attached the complete log files, or at least I hope so!
[...]

OK, so we have:

> WARNING: CPU: 11 PID: 541 at mm/page_alloc.c:4556 __alloc_pages+0x2a3/0x340

This means something tried to allocate a chunk of kernel memory that is
larger than the kernel page allocator supports.

[...]
>  acpi_ds_build_internal_buffer_obj+0xa5/0x170
>  acpi_ds_eval_data_object_operands+0x13a/0x140
>  acpi_ds_exec_end_op+0x440/0x500
>  acpi_ps_parse_loop+0xfb/0x6b0
>  acpi_ps_parse_aml+0x80/0x3d0
>  acpi_ps_execute_method+0x13f/0x270
>  acpi_ns_evaluate+0x128/0x2d0
>  acpi_evaluate_object+0x14d/0x2f0
>  __query_block+0x10a/0x1e0 [wmi]
>  wmi_query_block+0x88/0xd0 [wmi]
>  init_bios_attributes.part.0+0x55/0x2f0 [dell_wmi_sysman]
>  sysman_init+0x158/0xff0 [dell_wmi_sysman]
>  ? __pfx_sysman_init+0x10/0x10 [dell_wmi_sysman]
>  do_one_initcall+0x58/0x320
>  do_init_module+0x60/0x240
>  init_module_from_file+0x89/0xe0
>  idempotent_init_module+0x120/0x2b0
>  __x64_sys_finit_module+0x5e/0xb0

That happened during initialisation of the dell_wmi_sysman module.

[...]
> general protection fault, probably for non-canonical address 
> 0x800771b66d9d7272: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 11 PID: 521 Comm: (udev-worker) Tainted: G        W          
> 6.9.10-amd64 #1  Debian 6.9.10-1
> Hardware name: Dell Inc. Precision 7540/0T2FXT, BIOS 1.32.0 04/01/2024
> RIP: 0010:kmem_cache_alloc_node+0xed/0x360
[...]
> general protection fault, probably for non-canonical address 
> 0x800771b66d9d7272: 0000 [#2] PREEMPT SMP NOPTI
> CPU: 11 PID: 696 Comm: fsck.ext4 Tainted: G      D W          6.9.10-amd64 #1 
>  Debian 6.9.10-1
> Hardware name: Dell Inc. Precision 7540/0T2FXT, BIOS 1.32.0 04/01/2024
> RIP: 0010:kmem_cache_alloc+0xd7/0x340
[...]

Then later on the kernel heap allocation crashes, suggesting memory
corruption.  Maybe related to the first failure, maybe not.

- 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?

- Do these same error messages appear on every boot?

- 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?

Ben.

-- 
Ben Hutchings
Computers are not intelligent.  They only think they are.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to