https://bugzilla.kernel.org/show_bug.cgi?id=216371
Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:
What|Removed |Added
Status|NEEDINFO
https://bugzilla.kernel.org/show_bug.cgi?id=216371
Frank Kruger (fkrue...@mailbox.org) changed:
What|Removed |Added
CC|
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
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.
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
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
https://bugzilla.kernel.org/show_bug.cgi?id=216371
The Linux kernel's regression tracker (Thorsten Leemhuis)
(regressi...@leemhuis.info) changed:
What|Removed |Added
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
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
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
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
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.
--
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
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
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:
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
https://bugzilla.kernel.org/show_bug.cgi?id=216371
Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:
What|Removed |Added
Hardware|All |AMD
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
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
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
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
https://bugzilla.kernel.org/show_bug.cgi?id=216371
Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:
What|Removed |Added
Status|NEW
https://bugzilla.kernel.org/show_bug.cgi?id=216371
Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:
What|Removed |Added
CC|
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
24 matches
Mail list logo
