[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2020-11-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #13 from Vadim Yanitskiy (vyanits...@sysmocom.de) --- Here we go: [ 582.721066] amdgpu: iceland_populate_all_memory_levels(): mclk_table has 3 entries [ 582.721081] amdgpu: iceland_populate_all_memory_levels(): dpm_levels[0] is

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2020-11-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 Vadim Yanitskiy (vyanits...@sysmocom.de) changed: What|Removed |Added CC|

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2020-11-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #11 from Rogério Brito (rbr...@ime.usp.br) --- Dear Michel and other people, Since the last time that I reported this bug, the lock ups have not happened anymore. OTOH, the messages on the dmesg log persist. I can include newer logs

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2019-03-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #10 from Rogério Brito (rbr...@ime.usp.br) --- Created attachment 282071 --> https://bugzilla.kernel.org/attachment.cgi?id=282071=edit corresponding Xorg log to dmesg with error messages from amdgpu -- You are receiving this mail

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2019-03-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #9 from Rogério Brito (rbr...@ime.usp.br) --- Created attachment 282069 --> https://bugzilla.kernel.org/attachment.cgi?id=282069=edit dmesg log of kernel 4.19 with error messages amdgpu -- You are receiving this mail because: You

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2019-03-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #8 from Rogério Brito (rbr...@ime.usp.br) --- Dear Michel, (In reply to Michel Dänzer from comment #7) > (In reply to Rogério Brito from comment #5) > > First of all, sorry for the late reply. I had really a really bad start of > >

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2019-03-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #7 from Michel Dänzer (mic...@daenzer.net) --- (In reply to Rogério Brito from comment #5) > First of all, sorry for the late reply. I had really a really bad start of > the year (death in family, complications caused by that, health

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2019-02-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #6 from Rogério Brito (rbr...@ime.usp.br) --- Oh, I forgot to say that the kernel that I am using is currently identified as: Linux zatz 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux I can report the

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2019-02-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #5 from Rogério Brito (rbr...@ime.usp.br) --- Dear Michel, First of all, sorry for the late reply. I had really a really bad start of the year (death in family, complications caused by that, health problems, fire at home and also

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2018-11-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 fin4...@hotmail.com changed: What|Removed |Added CC||fin4...@hotmail.com --- Comment #3

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2018-11-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #4 from fin4...@hotmail.com --- Created attachment 279641 --> https://bugzilla.kernel.org/attachment.cgi?id=279641=edit AMD wip kernel config with 1000Hz timer for Ryzen 5 1600 desktop PC -- You are receiving this mail because:

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2018-11-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #2 from Michel Dänzer (mic...@daenzer.net) --- From the dmesg output, it looks like the AMD GPU is powered off most of the time. Do the freezes happen when you explicitly use it for something, e.g. for a game via DRI_PRIME=1? -- You

[Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!

2018-11-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201763 --- Comment #1 from Rogério Brito (rbr...@ime.usp.br) --- Created attachment 279599 --> https://bugzilla.kernel.org/attachment.cgi?id=279599=edit dmesg log with kernel 4.18.10 -- You are receiving this mail because: You are watching the