re: kern/58710: amdgpu kernel bug -- modesetting driver GL Rendering failure

["matthew green via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR kern/58710; it has been noted by GNATS.

From: matthew green <mrg%eterna23.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
    netbsd-bugs%netbsd.org@localhost
Subject: re: kern/58710: amdgpu kernel bug -- modesetting driver GL Rendering failure
Date: Tue, 01 Oct 2024 06:08:54 +1000

 is there a chance you can try -current on this system?  for me it
 was working mostly good with an RX 550, but i don't recall trying
 netbsd-10 branch recently.  i'll try to find time to do that, but
 i can't promise anything for a week or more.
 
 > Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device=
  has no render node (t=3D0.462674) [GFX1-]: glxtest: DRM device has no ren=
 der node
 
 i wonder if you, like me on some systems, are missing the render
 nodes in /dev/dri that are created i modern systems, but not there
 for older ones that have been upgraded.  eg, i just created this
 on one system it was missing on:
 
 the-blessing /dev# l dri
 total 0
 crw-rw----  1 root  wheel  180, 0 Jul 24 20:47 card0
 the-blessing /dev# sh MAKEDEV drm0
 the-blessing /dev# l dri
 total 0
 crw-rw----  1 root  wheel  180,   0 Jul 24 20:47 card0
 crw-rw----  1 root  wheel  180, 128 Sep 30 13:05 renderD128
 
 i don't *think* this is relevant, so if it doesn't help are you
 capable of patching Mesa to expand the errors and determine where
 exactly the shader creation is failing?  if so, please add some
 diagnostic to si_create_shader_variant() to track down which of
 the various paths that return false was taken?
 
 thanks.
 
 
 .mrg.