amdgpu panics
Hans Petter Selasky
hps at selasky.org
Tue Apr 7 09:16:38 UTC 2020
On 2020-04-07 11:06, Grzegorz Junka wrote:
>
> On 07/04/2020 08:54, Hans Petter Selasky wrote:
>> On 2020-04-07 10:27, Grzegorz Junka wrote:
>>> Apr 7 07:54:38 venus kernel: [drm] Display Core initialized with
>>> v3.1.27!
>>> Apr 7 07:54:38 venus kernel: [drm] Connector DP-1: get mode from
>>> tunables:
>>> Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-1
>>> Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode
>>> Apr 7 07:54:38 venus kernel: [drm] Connector DP-2: get mode from
>>> tunables:
>>> Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-2
>>> Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode
>>> Apr 7 07:54:38 venus kernel: [drm] Connector DP-3: get mode from
>>> tunables:
>>> Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-3
>>> Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode
>>
>> Maybe there is a problem configuring the display ports!
>>
>> Can you dump the output from:
>>
>> sysctl -a compat.linuxkpi
>>
>> Maybe there is some knob you need to flip to turn on the monitor!
>>
> root at venus:~ # sysctl -a compat.linuxkpi
> sysctl: unknown oid 'compat.linuxkpi'
>
Is this after loading the amdgpu driver?
Can you show:
kldstat
--HPS
More information about the freebsd-ports
mailing list