You are not logged in.
That is good, because that can make us confident that these results are actually correct!
The next step now is to report this regression in accordance to https://docs.kernel.org/admin-guide/rep … sions.html, can you do this or do you need help with that?
Offline
I'm sure you will have done it (if you don't mind) before I finish reading the documentation.
I warmly thank you all for your patience and support.
Offline
Can you please post the kernel messages from a boot with the latest mainline kernel (gromit will need them for the report) https://pkgbuild.com/~gromit/linux-bise … kg.tar.zst you can reboot and access them with:
journalctl -kb -1
Offline
Yes also it would be cool if you could post your email address and a name so I can credit you for the report and put you in CC. This is normally done via "Reported-by: Your name <email@provider.xyz>".
Offline
here is bad linux-mainline-6.12rc5-1-x86_64's log: http://0x0.st/XGtZ.txt
my email is available in my profile.
Offline
my email is available in my profile.
I can not see your email there, it just offers the Forum-Mailer functionality ..
Offline
yes, sorry.
sukolyn@rocketmail.com
Offline
I don't see a regression report about the issue, here*
I really don't feel comfortable or legitimate(?) about reporting.
Could you do it, please ?
*or did I miss the report ?
Offline
Have you looked for the report on https://gitlab.freedesktop.org/drm/amd/-/issues instead? Which is where amdgpu kernel module bugs are handled.
Offline
I don't see it there too.
the doc says to ask for regression at lore.kernel.org
Offline
the doc says to ask for regression at lore.kernel.org
Correct reporting it as a regression is in addition to reporting it as a bug. The kernel development system can be confusing, subsystems are free to choose their own practices for reporting bugs and submitting of patches.
Offline
I already filled a bug report 3 weeks ago
Offline
Why didn't you report there that the offending commit has been biseccted to 949658cb9b69ab9d22a42a662b2fdc7085689ed8 ?
Online
because I didn't know I had to.
I just did.
Offline
commit done.
waiting for current kernel works before marking as solved.
Offline
You could open a issue on Arch's gitlab instance against the linux package asking for the commit to be back-ported to avoid waiting for it to pass through the various tress to stable.
Edit:
Currently your commit is part of an open pull request to the drm tree from there to mainline then to stable.
Last edited by loqs (2024-11-23 15:22:30)
Offline