linux-kernel - Re: [GIT PULL] ACPI fixes for v5.16-rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 4 Dec 2021 09:04:12 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux PM <linux-pm@...r.kernel.org>
Subject: Re: [GIT PULL] ACPI fixes for v5.16-rc3

On Fri, Nov 26, 2021 at 11:38 AM Rafael J. Wysocki <rafael@...nel.org> wrote:
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
>  acpi-5.16-rc3

Hmm. This may be unrelated, but I don't think I've seen this before..
On my laptop, I get

  WARNING: CPU: 4 PID: 95940 at kernel/workqueue.c:1441 __queue_work+0x2f9/0x3b0
  Workqueue: kec_query acpi_ec_event_processor
  ..
  Call Trace:
   <TASK>
   queue_work_on+0x20/0x30
   advance_transaction+0x1a1/0x500
   acpi_ec_transaction+0x15c/0x410
   acpi_ec_space_handler+0xd2/0x270
   acpi_ev_address_space_dispatch+0x216/0x2a3
   ? acpi_ec_resume+0x20/0x20
   acpi_ex_access_region+0x1dc/0x255
   ? acpi_os_wait_semaphore+0x48/0x70
   acpi_ex_field_datum_io+0xfd/0x178
   acpi_ex_read_data_from_field+0x12e/0x171
   acpi_ex_resolve_node_to_value+0x1fe/0x281
   acpi_ds_evaluate_name_path+0x75/0xe9
   acpi_ds_exec_end_op+0x8f/0x411
   acpi_ps_parse_loop+0x495/0x5bc
   acpi_ps_parse_aml+0x94/0x2c2
   acpi_ps_execute_method+0x15e/0x193
   acpi_ns_evaluate+0x1c6/0x25d
   acpi_evaluate_object+0x12e/0x226
   acpi_ec_event_processor+0x63/0x90
   process_one_work+0x217/0x3c0

and it seems to be happening at resume time.

This was when running a51e3ac43ddb, so not the very latest git tree,
but recent.

Maybe I've missed a report of this?

               Linus