Bug 2116036
Summary: | [abrt] dcn30_init_hw: WARNING: CPU: 0 PID: 4913 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hubbub.c:566 hubbub2_get_dchub_ref_freq+0x7e/0xa0 [amdgpu] [amdgpu] | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Robin Tetour <Rob.Tetour> | ||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 36 | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved | ||||
Target Milestone: | --- | Keywords: | Reopened | ||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/07c49765b36fe00ca0996168ec81f2e3c4b993c7 | ||||||
Whiteboard: | abrt_hash:ee5e4932845803395b1b6b58293248b4ba841282;VARIANT_ID=workstation; | ||||||
Fixed In Version: | Doc Type: | --- | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2022-11-26 09:43:06 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Robin Tetour
2022-08-06 11:41:36 UTC
Created attachment 1904060 [details]
File: dmesg
Ok it happened again now I think it has to do something with suspend options. Because the display dimmed as if the computer went to sleep and I moved my mouse and it froze. I tried to run my kernel with another parameter i915.psr_enable=0 which I naively thought it would magically fix it, but then I discovered that it does not freeze when I run the GNOME power options on the second display. Only on the internal display. This time it generated a new bug log which for some reason is not reportable so I pushed the files it generated this time on a temporary gitlab repo. https://gitlab.com/RobTheRealLifeAnimoo/log-dump I am going to open an issue on GNOME gitlab just to be sure since it happened when using GNOME but I don't recall this happening when using KDE. I added new logs to the gitlab repo. I think there is a serious problem with my system. This time it froze on splash screen when booting. Had to hard shutdown again. This time it generated whopping 5 crash logs in the kernel-core package. So it is definitely an issue with power-profiles-daemon. I cannot replicate any of these system crashes/freezes since I uninstalled that package. Closing this issue. I am going to open an issue on ppd github. So it looks like it is not a power profiles daemon fault. I have filed a bug report but according to it's maintainer it just uses kernel APIs https://gitlab.freedesktop.org/hadess/power-profiles-daemon/-/issues/104 I seriously don't know what to do now. It is getting very frustrating. I do have somehow stable system but it now feels like I am just dodging the issue - which is not good in my book. I will gladly help resolving the issue and helping with log files. If anyone knows what to do please help!! (In reply to Robin Tetour from comment #6) > So it looks like it is not a power profiles daemon fault. > > I have filed a bug report but according to it's maintainer it just uses > kernel APIs > https://gitlab.freedesktop.org/hadess/power-profiles-daemon/-/issues/104 > > I seriously don't know what to do now. It is getting very frustrating. I do > have somehow stable system but it now feels like I am just dodging the issue > - which is not good in my book. > > I will gladly help resolving the issue and helping with log files. > > If anyone knows what to do please help!! So the system crashed just by opening gnome power settings. Even though the Power-Profiles-Daemon is uninstalled. I have no clue what is happening. Today I tried doing single (e)gpu passthrough and at it's core it works but it is very unstable and generated freezes mainly for the guest os but causes abrt to get some reports https://retrace.fedoraproject.org/faf/reports/496174/ although this is probably not connected. Looks like the problem goes away when setting kernel parameter intel_idle.max_cstate=1 but it is not a permanent solution since the laptop runs very hot after that. |