linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Gabriel C <nix.or.die@gmail.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Schmauss, Erik" <erik.schmauss@intel.com>
Subject: Re: [Kernel 5.1] ACPI_DEBUG messages without CONFIG_ACPI_DEBUG being set
Date: Tue, 7 May 2019 09:01:34 +0200	[thread overview]
Message-ID: <CAJZ5v0gRWEL1shQE3im0VxiPRBYat86o=R_NVQbc3JgOX8uT6w@mail.gmail.com> (raw)
In-Reply-To: <CAEJqkgh-eh0F0rNBChhurH0LWTLFP0DyfFzKj66p4Z2d1kM2gw@mail.gmail.com>

+Erik

On Tue, May 7, 2019 at 1:33 AM Gabriel C <nix.or.die@gmail.com> wrote:
>
> Hello,
>
> while testing kernel-5.1 I get on one of my Lenovo Laptops very
> strange 'ACPI Debug:' messages.
>
> After some grepping I realized these are Debug messages from DSDT ,
> however my kernel does
> not have ACPI_DEBUG enabled.
>
> I found out the module triggering this, on this Laptop is
> ideapad_laptop , but looking at the code
> I cannot see what would causes that.
>
> Also on the same Laptop with any 5.0.X kernels I cannot see these.
>
>
> ~$ grep -i ACPI_DEBUG /boot/config-5.1-fw1
> # CONFIG_ACPI_DEBUGGER is not set
> # CONFIG_ACPI_DEBUG is not set
> # CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set
> # CONFIG_THINKPAD_ACPI_DEBUG is not set
>
> .. dmesg ..
> ...
> [   68.020812] calling  ideapad_acpi_driver_init+0x0/0x1000
> [ideapad_laptop] @ 1322
> [   68.026708] input: Ideapad extra buttons as
> /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/input/input16
> [   68.038236] ACPI Debug:  "=====QUERY_64====="
> [   68.050232] ACPI Debug:  "=====QUERY_65====="
> [   68.060218] ACPI Debug:  "=====QUERY_64====="
> [   68.092216] probe of VPC2004:00 returned 1 after 71386 usecs
> [   68.092245] initcall ideapad_acpi_driver_init+0x0/0x1000
> [ideapad_laptop] returned 0 after 69751 usecssg
>
> ...
>
> These =====QUERY_XX===== messages are from DSDT:
>
> ~/acpi$ grep QUERY dsdt.dsl
>                Debug = "=====QUERY_11====="
>                Debug = "=====QUERY_12====="
>                Debug = "=====QUERY_24====="
>                Debug = "=====QUERY_25====="
>                Debug = "=====QUERY_37====="
>                Debug = "=====QUERY_38====="
>                Debug = "=====QUERY_64====="
>                Debug = "=====QUERY_65====="
>
> Also this is the code from DSDT for QUERY 64 and 65:
>
> ...
>             Method (_Q64, 0, NotSerialized)  // _Qxx: EC Query
>            {
>                Debug = "=====QUERY_64====="
>                If ((OSYS == 0x07D9))
>                {
>                    If (((WLEX == One) & (WLAT == One)))
>                    {
>                        SGOV (0x02040005, One)
>                    }
>                    Else
>                    {
>                        SGOV (0x02040005, Zero)
>                    }
>                }
>            }
>
>            Method (_Q65, 0, NotSerialized)  // _Qxx: EC Query
>            {
>                Debug = "=====QUERY_65====="
>                If ((OSYS == 0x07D9))
>                {
>                    If (((BTEX == One) & (BTAT == One)))
>                    {
>                        SGOV (0x0202000B, One)
>                    }
>                    Else
>                    {
>                        SGOV (0x0202000B, Zero)
>                    }
>                }
>            }
>
> ...
>
>
> Any idea what would cause this ?
>
> BR,
>
> Gabriel C

  reply	other threads:[~2019-05-07  7:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 23:34 [Kernel 5.1] ACPI_DEBUG messages without CONFIG_ACPI_DEBUG being set Gabriel C
2019-05-07  7:01 ` Rafael J. Wysocki [this message]
2019-05-07  7:32   ` Gabriel C
2019-05-07  8:34     ` Rafael J. Wysocki
2019-05-07  9:33       ` Gabriel C
2019-05-07 18:46         ` Schmauss, Erik
2019-05-07 19:06           ` Gabriel C
2019-05-07 20:17             ` Schmauss, Erik
2019-05-07 21:39               ` Gabriel C

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='CAJZ5v0gRWEL1shQE3im0VxiPRBYat86o=R_NVQbc3JgOX8uT6w@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=erik.schmauss@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix.or.die@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).