On Tue, 14 Jul 2020 16:11:35 +0200 Sebastian Andrzej Siewior <bige...@linutronix.de> wrote:
> On 2020-07-14 15:54:57 [+0200], Rafael J. Wysocki wrote: >> On Tue, Jul 14, 2020 at 3:44 PM Sebastian Andrzej Siewior >> <bige...@linutronix.de> wrote:> >> > On 2020-06-24 23:49:52 [+0200], Stephen Berman wrote: >> > >> > Let me summarize the thread here: >> > >> > On Stephen's system, ACPI informs the thermal zone driver to poll the >> > temperature every second and the driver does so. >> > The driver queries the temperature by invoking acpi_evaluate_integer() >> > which invokes (at some point) acpi_ev_queue_notify_request(). >> >> Well, I don't quite see how acpi_ev_queue_notify_request() can be >> invoked from the acpi_evaluate_integer() code path. >> >> Do you have a call trace showing that? > > So the trace in > https://lore.kernel.org/linux-acpi/87o8pjh1i0....@gmx.net/ > > shows the pattern and we nailed it down that it comes from > thermal_get_temp(). I assumed acpi_ex_opcode_2A_0T_0R() since the other > candidate was acpi_ev_asynch_execute_gpe_method(). > > Stephen, the patch attached adds a WARN_ON() statement which will > produce a stack trace (4 or so). Could please run 'dmesg' after a while > and send it back. There should be a > "WARNING in drivers/acpi/acpica/evmisc.c" > > statement or something along the lines. I've now rebuilt 5.6.4 with the new patch; sorry for the delay. Output of dmesg attached. Steve Berman
dmesg-5.6.4.gz
Description: Binary data
