From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218354] New: Writing to dgpu_disable always produce Input/Output error
Date: Mon, 08 Jan 2024 18:16:59 +0000 [thread overview]
Message-ID: <bug-218354-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218354
Bug ID: 218354
Summary: Writing to dgpu_disable always produce Input/Output
error
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: athul.krishna.kr@protonmail.com
Regression: No
Created attachment 305687
--> https://bugzilla.kernel.org/attachment.cgi?id=305687&action=edit
output of journalctl and lspci
Device Info:
Asus Zephyrus G14 GA402RJ
Latest BIOS
Arch_x86_64
Kernel 6.6.10-arch1
Minimal arch install
ISSUE: Writing 0 to /sys/devices/platform/asus-nb-wmi/dgpu_disable, will always
produce an Input/Output error(echo 1 | tee ../dgpu_disable). While writing 1 to
it seems fine. There's also an issue of system crash and reboot after echo 1 |
tee ../pci/rescan.
Steps to Reproduce:
echo 1 | tee ../remove(dgpu path)
echo 1 | tee /sys/devices/platform/asus-nb-wmi/dgpu_disable
echo 0 | tee /sys/devices/platform/asus-nb-wmi/dgpu_disable
echo 1 | tee /sys/bus/pci/rescan
Observations:
Did the above steps 10 times, everytime it produced an Input/Output error and
everytime system crashed and rebooted, during pci rescan.
journalctl -p 3 showed an ACPI error after writing 0 to dgpu_disable.
journalctl -p 3, lspci are attached.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2024-01-08 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-218354-215701@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.