https://bugs.freedesktop.org/show_bug.cgi?id=104854
Martin Peres changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #11 from José Pekkarinen ---
aw, and yes, if I don't blacklist the module, the trace happens, which
certainly blows my mind, as it's built in, modprobe shouldn't affect it.
José.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #10 from José Pekkarinen ---
Created attachment 140293
--> https://bugs.freedesktop.org/attachment.cgi?id=140293&action=edit
dri config to work it around.
I spent some more time toying this around and I found that, building
the dr
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #9 from José Pekkarinen ---
Created attachment 140225
--> https://bugs.freedesktop.org/attachment.cgi?id=140225&action=edit
boot process on 4.17.2.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #8 from José Pekkarinen ---
I'm afraid I reproduced this again using the kernel 4.17.2 where I see the
following commit:
commit 9ca5a2ae4259e7aec8efb0db0f6ec721a6854c54
Merge: bee797529d7c c62ec4610c40
Author: Linus Torvalds
Date:
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #7 from Alex Deucher ---
possibly related to:
https://bugzilla.kernel.org/show_bug.cgi?id=199693
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mai
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #6 from José Pekkarinen ---
So far no luck, seems like with the acpi_backlight and removing laptop mode
from my services initialisation gives more chances to successfully boot without
issues, but eventually the bug will turn up.
--
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #5 from José Pekkarinen ---
Created attachment 138467
--> https://bugs.freedesktop.org/attachment.cgi?id=138467&action=edit
backtrace trying drm-4.17
As stated in bug 105760, drm-4.17 didn't make any difference for me, though,
set
https://bugs.freedesktop.org/show_bug.cgi?id=104854
taij...@posteo.de changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=104854
José Pekkarinen changed:
What|Removed |Added
Attachment #137911|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #3 from Alex Deucher ---
What kernel are you using? I don't see any way the fw loading type could not
be set correctly for any chip unless a module parameter was provided. Please
attach your full dmesg output. What module paramete
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #2 from José Pekkarinen ---
Created attachment 137911
--> https://bugs.freedesktop.org/attachment.cgi?id=137911&action=edit
Initialization output on SMU firmware load.
Seems that autodetection of firmware method to load fails to g
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #1 from José Pekkarinen ---
I believe the issue is actually shown before, these are the lines prior
to the error:
Mar 4 22:00:16 bee kernel: [ 35.741939] amdgpu: [powerplay] Failed to notify
smc display settings!
Mar 4 22:00:16
https://bugs.freedesktop.org/show_bug.cgi?id=104854
Bug ID: 104854
Summary: smu7_populate_single_firmware_entry fails to load
powerplay firmware.
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS
14 matches
Mail list logo