[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed: What|Removed |Added CC||mari

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed: What|Removed |Added Status|NEW |NEED

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #4 from neoe (h...@n101n.xyz) --- Created attachment 301657 --> https://bugzilla.kernel.org/attachment.cgi?id=301657&action=edit OK version -- You may reply to this email to add a comment. You are receiving this mail because: You

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #5 from neoe (h...@n101n.xyz) --- sorry I don't have bad version dmesg for 6.0 but I have some other information: acpitool -e Kernel version : 5.19.3-gs -ACPI version : 20220331 Freq. scaling driver : amd-pstate Kern

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #6 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) --- That may be a completely separate bug. Maybe you can try to explicitly set which frequency scaling driver is used in both cases to isolate if that's the cause of your iss

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #7 from neoe (h...@n101n.xyz) --- I add 'Command line: BOOT_IMAGE=/boot/vmlinuz-xxx root=/dev/nvme0n1p4 amd_pstate.shared_mem=1' to enable `amd-pstate` for all , I think. when next 6.0.0-rc3 come out, I think I will have another try a

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed: What|Removed |Added Hardware|All |AMD

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #8 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) --- Once you test 6.0-rc3 if it's still failing, please perform a bisect to find the root cause. -- You may reply to this email to add a comment. You are receiving this mai

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #9 from neoe (h...@n101n.xyz) --- I made a git bitsect ``` [cb6b81b21bd9cf09d72b7fe711be1b55001eb166] Merge tag 'drm-misc-next-fixes-2022-07-21' of git://anongit.freedesktop.org/drm/drm-misc into drm-next # git bisect bad Bisecting:

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #10 from neoe (h...@n101n.xyz) --- Created attachment 301670 --> https://bugzilla.kernel.org/attachment.cgi?id=301670&action=edit another dmesg when bad -- You may reply to this email to add a comment. You are receiving this mail

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #11 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) --- > then I don't know whether it's good or bad, because > if say bad, it wake up good > if say good, it use cpufreq instead of expected amd-pstate Because you know there

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #12 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) --- Shot in the dark until we know the causing commit - a6250bdb6c4677ee77d699b338e077b900f94c0c in 6.0-rc2 and latest 5.19.y helps some other people with VT freezes. -- Yo

[Bug 216371] acpi wake up with black screen(failed to get iomux index)

https://bugzilla.kernel.org/show_bug.cgi?id=216371 --- Comment #13 from neoe (h...@n101n.xyz) --- wow, maybe my result is not valid, because I really get lost in the bisect game. [/home/neoe/oss/linux/linux] git bisect good cb6b81b21bd9cf09d72b7fe711be1b55001eb166 is the first bad commit commi