From: Dmitry Antipov <dmantipov@yandex.ru>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: ACPI BIOS bug and memory leak?
Date: Wed, 27 Mar 2024 13:48:32 +0300 [thread overview]
Message-ID: <9d0a3bd8-62d6-43cc-8109-311448ad0867@yandex.ru> (raw)
Is it possible that this:
[ 7.727080] ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20230628/psargs-335)
[ 7.728470] ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
is somehow related to:
unreferenced object 0xffff944e85013d58 (size 56):
comm "thermald", pid 966, jiffies 4294674933
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 0d 01 2d 00 00 00 00 00 ..........-.....
94 8c 05 80 51 b8 ff ff 00 00 00 00 00 00 00 00 ....Q...........
backtrace (crc 41e9984d):
[<000000004b53f9d1>] kmem_cache_alloc+0x256/0x340
[<000000008d9ead3a>] acpi_ps_alloc_op+0xbf/0xd0
[<000000002f1e617e>] acpi_ps_get_next_arg+0xbb/0x6a0
[<00000000b697bac7>] acpi_ps_parse_loop+0x466/0x6b0
[<000000008dbc2acb>] acpi_ps_parse_aml+0x80/0x3c0
[<00000000b26066ae>] acpi_ps_execute_method+0x13f/0x270
[<00000000f80592ab>] acpi_ns_evaluate+0x12b/0x2c0
[<00000000bbc91886>] acpi_evaluate_object+0x14e/0x310
[<000000005729c43d>] acpi_run_osc+0x158/0x270
[<00000000e6666993>] int3400_thermal_run_osc+0x73/0xc0 [int3400_thermal]
[<000000000a474314>] current_uuid_store+0xd5/0x110 [int3400_thermal]
[<00000000e27be786>] kernfs_fop_write_iter+0x13e/0x1f0
[<00000000992f9e08>] vfs_write+0x293/0x460
[<000000008b9e130c>] ksys_write+0x6d/0xf0
[<000000007d501d09>] do_syscall_64+0x85/0x170
[<0000000073c5a34b>] entry_SYSCALL_64_after_hwframe+0x6c/0x74
(recently observed on 6.9.0-rc1)
Dmitry
next reply other threads:[~2024-03-27 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 10:48 Dmitry Antipov [this message]
2024-03-31 2:46 ` ACPI BIOS bug and memory leak? Armin Wolf
2024-04-02 18:26 ` Dmitry Antipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d0a3bd8-62d6-43cc-8109-311448ad0867@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.