[amdgpu] ASSERT()'s in write_i2c*retimer_setting() functions

2019-10-10 Thread Gabriel C
Hello,

I've built recently a new box with a Ryzen3 2200G APU.

Each time I plug in an HDMI cable ( to a TV or Monitor ),
or boot with HDMI connected a lot ASSERT()'s from
write_i2c*retimer_setting() functions are triggered.

I see the same on a Laptop with a Ryzen7 3750H with
hybrid GPU configuration.

Besides the noise in dmesg and the delay on boot,
everything is working fine. I cannot find anything wrong
or broken.

Since the write errors seem to not be fatal, I think a friendly message
would help more instead of flooding the dmesg with dumps while
everything is working properly.

Why is ASSERT() used there?

I have a dmesg from the Ryzen3 box with drm.debug and a snipped
from the Laptop ( not near me right now ) uploaded there:

https://crazy.dev.frugalware.org/amdgpu/

Please let me know if you need more information,
If needed I can upload a dmesg from the Laptop with drm.debug too.


Best Regards,

Gabriel C


[amdgpu] backlight mismatch

2019-09-23 Thread Gabriel C
Hello,

on my new Acer Nitro 5 (AN515-43-R8BF) backlight and actual_backlight value
in sysfs mismatch. When backlight is 0 actual_backlight is still 5140.

root@nitro5:/sys/class/backlight/amdgpu_bl1# cat brightness
255
root@nitro5:/sys/class/backlight/amdgpu_bl1# cat actual_brightness
65535
root@nitro5:/sys/class/backlight/amdgpu_bl1# echo 0 >brightness
root@nitro5:/sys/class/backlight/amdgpu_bl1# cat actual_brightness
5140

The laptop has a hybrid setup Picasso+Polaris11.

01:00.0 Display controller [0380]: Advanced Micro Devices, Inc.
[AMD/ATI] Baffin [Radeon RX 460/560D / Pro
450/455/460/555/555X/560/560X] [1002:67ef] (rev c0)
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Picasso [1002:15d8] (rev c1)

[4.594694] [drm] initializing kernel modesetting (POLARIS11
0x1002:0x67EF 0x1025:0x1367 0xC0).
[4.866696] [drm] initializing kernel modesetting (RAVEN
0x1002:0x15D8 0x1025:0x1366 0xC1).

Please let me know what other informations you may need.

Best Regards,

Gabriel C.


[Regression] 5.3-rc8 suspending from X broken with amdgpu

2019-09-11 Thread Gabriel C
Hello,

I am testing latest rc8/Linus git tree on my new
Acer Nitro 5 (AN515-43-R8BF) Laptop.

The box has an Ryzen7 3750H APU+RX 560x hybrid GPU(s).

Suspending ( closing the Lid ) from tty without X up
is working fine, however with X running doing the same
does not work. The display remains black.

It seems to be triggered from

 .. dcn10_hw_sequencer.c:932
dcn10_verify_allow_pstate_change_high.cold+0xc/0x229 [amdgpu]

The dmesg is way to big to post there so I uploaded it:

dmesg:
 http://crazy.dev.frugalware.org/Nitro5/dmesg.one.txt
lspci:
 http://crazy.dev.frugalware.org/Nitro5/lspci.nnvv.txt
 http://crazy.dev.frugalware.org/Nitro5/lspci.txt
config:
 http://crazy.dev.frugalware.org/Nitro5/config.nitro5-5.3-r8git

I didn't tested any other rcX kernels so I cannot tell if all are affected,
but 5.2.x kernels are working fine on this box.


The dirty state of the build is because this patch, which fixes the
NVME device on that box:
 https://lkml.org/lkml/2019/9/11/569

If you need more infos please let me know.
Also I can test any kind patches.

Best Regards,

Gabriel C