From: Hans de Goede <hdegoede@redhat.com>
To: "Limonciello, Mario" <Mario.Limonciello@dell.com>,
"Barnabás Pőcze" <pobrn@protonmail.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Cc: "platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: Keyboard regression by intel-vbtn
Date: Wed, 30 Sep 2020 15:28:23 +0200 [thread overview]
Message-ID: <fce9f346-5c02-0997-216a-14ab6c8b336d@redhat.com> (raw)
In-Reply-To: <DM6PR19MB2636BD25C7C828D28CF27CC8FA320@DM6PR19MB2636.namprd19.prod.outlook.com>
Hi,
On 9/29/20 10:47 PM, Limonciello, Mario wrote:
>>
>> I requested on the Ubuntu bug for someone to provide these.
>>
>
> Joe Barnett was kind enough to share two ACPI dumps to compare.
> Not affected:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415318/+files/1.2.0.acpidump
>
> Affected:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415405/+files/1.13.0.acpidump
Thank you, I took a look at these (before completing my allow-list fix),
but there is not really much which stands out. The only related thing which
stands out is that the 1.13.0 dsdt.dsl has this new bit:
Case (0x08)
{
Return (^^PCI0.LPCB.H_EC.VGBI.VGBS ())
}
Inside the _DSM of the HIDD / INT33D5 device.
Method (_DSM, 4, Serialized) // _DSM: Device-Specific Method
{
If ((Arg0 == ToUUID ("eeec56b3-4442-408f-a792-4edd4d758054")))
What is interesting here is that the PCI0.LPCB.H_EC.VGBI.VGBS object/method
does not actually exist the correct path is:
^^PCI0.LPCB.ECDV.VGBI.VGBS
So this does suggest that something around the VGBS handling changed
(and since it points to a non existing ACPI object, possibly broke)
in the newer BIOS version. But what exactly is going on on this XPS 2-in-1
cannot really be derived from the acpidumps.
Regards,
Hans
next prev parent reply other threads:[~2020-09-30 13:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:48 Keyboard regression by intel-vbtn Takashi Iwai
2020-09-29 9:21 ` Hans de Goede
2020-09-29 9:29 ` Takashi Iwai
2020-09-29 9:59 ` Barnabás Pőcze
2020-09-29 10:17 ` Hans de Goede
2020-09-29 12:27 ` Limonciello, Mario
2020-09-29 12:54 ` Hans de Goede
2020-09-29 14:25 ` Limonciello, Mario
2020-09-29 16:53 ` Andy Shevchenko
2020-09-29 20:37 ` Limonciello, Mario
2020-09-29 20:47 ` Limonciello, Mario
2020-09-30 13:28 ` Hans de Goede [this message]
2020-09-30 15:12 ` Limonciello, Mario
2020-09-30 15:36 ` Hans de Goede
2020-09-30 16:02 ` Limonciello, Mario
2020-09-29 14:19 ` Hans de Goede
2020-09-30 13:21 ` Hans de Goede
2020-09-30 13:21 ` Hans de Goede
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=fce9f346-5c02-0997-216a-14ab6c8b336d@redhat.com \
--to=hdegoede@redhat.com \
--cc=Mario.Limonciello@dell.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.com \
--cc=tiwai@suse.de \
/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