Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Armin Wolf <W_Armin@gmx.de>
Cc: Athul Krishna <athul.krishna.kr@protonmail.com>,
	"corentin.chary@gmail.com" <corentin.chary@gmail.com>,
	"acpi4asus-user@lists.sourceforge.net"
	<acpi4asus-user@lists.sourceforge.net>,
	"platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: ERROR: Writing to dgpu_disable cause Input/Output error
Date: Mon, 8 Jan 2024 18:00:33 -0600	[thread overview]
Message-ID: <20240109000033.GA1986948@bhelgaas> (raw)
In-Reply-To: <af094d61-eec0-456e-aeba-6e80c95424c5@gmx.de>

On Sat, Jan 06, 2024 at 11:33:35PM +0100, Armin Wolf wrote:
> Am 04.01.24 um 03:50 schrieb Athul Krishna:
> 
> > 
> > 
> > 
> > 
> > Sent with Proton Mail secure email.
> > 
> > On Thursday, January 4th, 2024 at 1:05 AM, Armin Wolf <W_Armin@gmx.de> wrote:
> > 
> > 
> > > Am 03.01.24 um 19:51 schrieb Athul Krishna:
> > > 
> > > > Hello,
> > > > This is my first time reporting an issue in the kernel.
> > > > 
> > > > Device Details:
> > > > 
> > > > * Asus Zephyrus G14 (||||||GA402RJ)
> > > > * Latest BIOS
> > > > * Arch_x86_64
> > > > * Kernel: 6.6.9
> > > > * Minimal install using archinstall
> > > > 
> > > > ISSUE: Using /dgpu_disable /provided by _asus-nb-wmi _to disable and
> > > > enable dedicated gpu,
> > > > causes system crash and reboots, randomly.
> > > > 9/10 times writing 0 to dgpu_disable will produce an Input/Output
> > > > error, but the value will be changed to 0, half the time system will
> > > > crash and reboot. While writing 1 to it doesn't produce an error, I
> > > > have observed system crash twice just after that.
> > > > 
> > > > Steps to Reproduce:
> > > > 
> > > > * Remove dpgu: echo 1 | sudo tee ../remove (dgpu path)
> > > > * echo 1 | sudo tee /sys/devices/platform/asus-nb-wmi/dgpu_disable
> > > > * echo 0 | sudo tee /sys/devices/platform/asus-nb-wmi/dgpu_disable
> > > > 
> > > > * echo 1 | sudo tee /sys/bus/pci/rescan
> > > > 
> > > > After writing 0 to dgpu_disable, there's an entry in journal about an
> > > > ACPI bug.
> > > > Output of 'journalctl -p 3' and lspci is attached.
> > > 
> > > Hi,
> > > 
> > > Can you share the output of "acpidump" and the content of "/sys/bus/wmi/devices/05901221-D566-11D1-B2F0-00A0C9062910[-X]/bmof"?
> > > The bmof files contain a description of the WMI interfaces of your machine, which might be important for diagnosing the error.
> > > 
> > > Thanks,
> > > Armin Wolf
> > Here's the output of 'acpidump > acpidump.out' and 'cat /sys/bus/wmi/devices/05901221-D566-11D1-B2F0-00A0C9062910[-X]/bmof'
> 
> Ok, it seems the ACPI code tries to access an object ("GC00") which does not exist.
> This is the reason why disabling the dGPU fails with -EIO.
> 
> I am unfortunately not that knowledgeable when it comes to PCI problems, i CCed the linux-pci mailing list in hope that
> they can better help you in this regard.

FWIW, I don't know enough about what's going on here to see a PCI
connection.  I do see a bunch of PCI-related stuff around rfkill, but
I don't think that's involved here.

I think the path here is this, which doesn't seem to touch anything in
PCI:

  dgpu_disable_store
    asus_wmi_set_devstate(ASUS_WMI_DEVID_DGPU, ..., &result)
      asus_wmi_evaluate_method(ASUS_WMI_METHODID_DEVS, ...)
        asus_wmi_evaluate_method3
          wmi_evaluate_method(ASUS_WMI_MGMT_GUID, ...)
    if (result > 1)
      return -EIO

But if I missed it, let me know and I'll be happy to take another
look.

Bjorn

  reply	other threads:[~2024-01-09  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <GuvjyxvIK4bJrayfrvuGPORpcPhPT9WFxxtQ1nqeEyamn_po0WuVInoXQVRmpwBQkW9K0CCwDqSg6kXPEI9YTlU0LQ_FtIMmpxluOirycpw=@protonmail.com>
     [not found] ` <13fad62a-c82c-45b6-bd78-ad51232dbe14@gmx.de>
     [not found]   ` <fXvoFRg43mZOs78mEX_CwN_2pi7KyVZkAIymCHa5i6DTyX-spNAHz6RDl31vrx_d1y-wrJhXEcUgPMHvmUwbDgYAXOgIOG_qdF3KCWTpJx8=@protonmail.com>
2024-01-06 22:33     ` ERROR: Writing to dgpu_disable cause Input/Output error Armin Wolf
2024-01-09  0:00       ` Bjorn Helgaas [this message]
2024-01-09 10:29         ` Armin Wolf
2024-01-23 15:34           ` Bjorn Helgaas
2024-02-06 14:24             ` Athul Krishna
2024-02-06 15:25               ` Bjorn Helgaas

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=20240109000033.GA1986948@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=W_Armin@gmx.de \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=athul.krishna.kr@protonmail.com \
    --cc=corentin.chary@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=platform-driver-x86@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox