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

2022-11-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |PATCH_ALREADY_AVAILABLE

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-10-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

Frank Kruger (fkrue...@mailbox.org) changed:

   What|Removed |Added

 CC||fkrue...@mailbox.org

--- Comment #22 from Frank Kruger (fkrue...@mailbox.org) ---
This might be worth to look at:
https://gitlab.freedesktop.org/drm/amd/-/issues/2164

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-09-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

--- Comment #21 from The Linux kernel's regression tracker (Thorsten Leemhuis) 
(regressi...@leemhuis.info) ---
(In reply to neoe from comment #18)
> a bitsec need about 14 iterators

FWIW, it's likely just about 8 if it's really between v6.0-rc1..v6.0-rc2

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-09-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

--- Comment #20 from neoe (h...@n101n.xyz) ---
6.0.0-rc4 also black-screen after sleep by 'acpitool -s'

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-09-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

--- Comment #19 from neoe (h...@n101n.xyz) ---
I see 6.0.0-rc4 come out today, so I had a test on it.

"acpitool -e" shows the "Freq. scaling driver   : amd-pstate"  , better than
rc2

but also noticed that the HDMI-audio output is gone, I just can say there seems
alot amdgpu changes. I just cannot follow the test process according to the
state. 

As a linux user and lover, I decided to stick to 5.19.y until 6.0.0 become
stable. 

Thank you all guys.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-09-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

--- Comment #18 from neoe (h...@n101n.xyz) ---
sorry, not yet.
a compile takes 12 minutes, and a bitsec need about 14 iterators, and not
automatic yet. quite expensive for me. 
I don't know if any amd zen2 will have the same problem. 
So I think if 6.0.0 release and still problem, I will make an automatic script
to do the git bitsect test, if there are no better ways.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-09-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

The Linux kernel's regression tracker (Thorsten Leemhuis) 
(regressi...@leemhuis.info) changed:

   What|Removed |Added

 CC||regressi...@leemhuis.info

--- Comment #17 from The Linux kernel's regression tracker (Thorsten Leemhuis) 
(regressi...@leemhuis.info) ---
neoe, any news? Did you try what Mario suggested?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

--- Comment #16 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
In that case I think you should redo the bisect with amdgpu blacklisted for the
entire duration so that any instability in the middle of the release doesn't
lead to a bad result.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

--- Comment #15 from neoe (h...@n101n.xyz) ---
added nomodeset to 6.0.0-rc2 still wake up to black screen.
means this is more likely acpi bug than amdgpu bug.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

--- Comment #14 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
It's unfortunate it ends on a merge commit but not unheard of.
https://stackoverflow.com/questions/17267816/git-bisect-with-merged-commits

If that's a true result, you should be able to add nomodeset which will turn
off amdgpu and check whether you can suspend/resume.  If so it does confirm
this is still an amdgpu bug.

The real commit from that one should be
6f2c8d5f16594a13295d153245e0bb8166db7ac9, but you have that marked as good
above. The only other stuff in that merge request is nouveau which shouldn't
affect your system.

If nomodeset helps I think you should redo your bisect.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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
commit cb6b81b21bd9cf09d72b7fe711be1b55001eb166
Merge: 3cfb5bc94fab 6f2c8d5f1659
Author: Dave Airlie 
Date:   Fri Jul 22 13:43:46 2022 +1000

Merge tag 'drm-misc-next-fixes-2022-07-21' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next

Short summary of fixes pull:

 * amdgpu: Fix for drm buddy memory corruption
 * nouveau: PM fixes; DP fixes

Signed-off-by: Dave Airlie 

From: Thomas Zimmermann 
Link:
https://patchwork.freedesktop.org/patch/msgid/Ytj65+PdAJs4jIEO@linux-uq9g

 drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | 16 
 drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.h |  2 +-
 drivers/gpu/drm/nouveau/nouveau_connector.c  |  8 +++-
 drivers/gpu/drm/nouveau/nouveau_display.c|  4 ++--
 drivers/gpu/drm/nouveau/nouveau_fbcon.c  |  2 +-
 5 files changed, 15 insertions(+), 17 deletions(-)



[/home/neoe/oss/linux/linux] git bisect log

git bisect start
# status: waiting for both good and bad commits
# good: [1b54a0121dba12af268fb75c413feabdb9f573d4] drm/amd/display: Reduce
stack size in the mode support function
git bisect good 1b54a0121dba12af268fb75c413feabdb9f573d4
# status: waiting for bad commit, 1 good commit known
# bad: [2bc7ea71a73747a77e7f83bc085b0d2393235410] Merge tag
'topic/nouveau-misc-2022-07-27' of git://anongit.freedesktop.org/drm/drm into
drm-next
git bisect bad 2bc7ea71a73747a77e7f83bc085b0d2393235410
# good: [c877bed82e1017c102c137d432933ccbba92c119] drm/i915/gt: Only kick the
signal worker if there's been an update
git bisect good c877bed82e1017c102c137d432933ccbba92c119
# bad: [ee8b1ef9a6b089abf7a9c7d094b6e93fa05f15b9] Merge tag
'amd-drm-next-5.20-2022-07-26' of https://gitlab.freedesktop.org/agd5f/linux
into drm-next
git bisect bad ee8b1ef9a6b089abf7a9c7d094b6e93fa05f15b9
# bad: [cb6b81b21bd9cf09d72b7fe711be1b55001eb166] Merge tag
'drm-misc-next-fixes-2022-07-21' of git://anongit.freedesktop.org/drm/drm-misc
into drm-next
git bisect bad cb6b81b21bd9cf09d72b7fe711be1b55001eb166
# good: [676ad8e997036e2f815c293b76c356fb7cc97a08] drm: rcar-du: Lift z-pos
restriction on primary plane for Gen3
git bisect good 676ad8e997036e2f815c293b76c356fb7cc97a08
# good: [c96cfaf8fc02d4bb70727dfa7ce7841a3cff9be2] drm/nouveau: Don't
pm_runtime_put_sync(), only pm_runtime_put_autosuspend()
git bisect good c96cfaf8fc02d4bb70727dfa7ce7841a3cff9be2
# good: [6f2c8d5f16594a13295d153245e0bb8166db7ac9] drm/amdgpu: Fix for drm
buddy memory corruption
git bisect good 6f2c8d5f16594a13295d153245e0bb8166db7ac9
# good: [3cfb5bc94fab39c456dccee75553f7f6c52ee7f7] Merge tag 'du-next-20220707'
of git://linuxtv.org/pinchartl/media into drm-next
git bisect good 3cfb5bc94fab39c456dccee75553f7f6c52ee7f7
# first bad commit: [cb6b81b21bd9cf09d72b7fe711be1b55001eb166] Merge tag
'drm-misc-next-fixes-2022-07-21' of git://anongit.freedesktop.org/drm/drm-misc
into drm-next

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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 is a problem with this part way through it's better to
force all the tests to use acpi-cpufreq.  It removes more variability in the
test result.

> but there is already 2 rev left, so can I leave it for you the developer?

I don't know what are actually left, I think I'd need to see the whole log to
see what happens.  With the above guidance can you narrow down to a specific
commit?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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=edit
another dmesg when bad

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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: 5 revisions left to test after this (roughly 3 steps)
[676ad8e997036e2f815c293b76c356fb7cc97a08] drm: rcar-du: Lift z-pos restriction
on primary plane for Gen3

bad amdgpu
# git bisect good
Bisecting: 2 revisions left to test after this (roughly 2 steps)
[c96cfaf8fc02d4bb70727dfa7ce7841a3cff9be2] drm/nouveau: Don't
pm_runtime_put_sync(), only pm_runtime_put_autosuspend()

bad amdgpu
cpufreq but wake up good

```
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

but there is already 2 rev left, so can I leave it for you the developer?

btw, I start from tags/v6.0-rc1(bad) and  tags/v5.19(good) with 7097 revisions,
I hope there are no regression  more than once, and hope the result range is
meaningful.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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 mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:

   What|Removed |Added

   Hardware|All |AMD

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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 and upload the
dmesghere.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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 issue.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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

  Kernel version : 6.0.0-rc2-gs   -ACPI version : 20220331
  Freq. scaling driver   : acpi-cpufreq

6.0.0 seems `amd-pstate` not loaded, but use `acpi-cpufreq`

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
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=edit
OK version

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #3 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
Also, please share a full dmesg from the previous working kernel and full dmesg
from broken kernel.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:

   What|Removed |Added

 CC||mario.limoncie...@amd.com

--- Comment #2 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
Can you please bisect
(https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html)?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla


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

2022-08-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216371

neoe (h...@n101n.xyz) changed:

   What|Removed |Added

Summary|acpi wake up with black |acpi wake up with black
   |screen  |screen(failed to get iomux
   ||index)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

___
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla