* [Bug 218354] New: Writing to dgpu_disable always produce Input/Output error
@ 2024-01-08 18:16 bugzilla-daemon
0 siblings, 0 replies; only message in thread
From: bugzilla-daemon @ 2024-01-08 18:16 UTC (permalink / raw
To: platform-driver-x86
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-01-08 18:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-01-08 18:16 [Bug 218354] New: Writing to dgpu_disable always produce Input/Output error bugzilla-daemon
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 read-only IMAP folder(s) and NNTP newsgroup(s).