Conversation

Notices

1. Embed this notice
   Alauddin Maulana Hirzan 💻 (maulanahirzan@mastodon.bsd.cafe)'s status on Friday, 31-Jan-2025 16:44:00 JST Alauddin Maulana Hirzan 💻

   Testing OpenCL in FreeBSD with my dGPU AMD RX550 (Polaris 12). Several problems that i have found:
   1. Using clinfo crashed FreeBSD (reproducible)
   2. Using Python lib to access OpenCL is success, but FreeBSD crashed when I close Python's Interpreter (reproducible)
   3. Running Chromium crashed FreeBSD after several minutes (reproducible)

   What should I do to fix this? #FreeBSD #dGPU #AMDGPU

   • Embed this notice
     feld (feld@friedcheese.us)'s status on Friday, 31-Jan-2025 16:43:58 JST feld

     in reply to
     @maulanahirzan as in actual kernel panics ??
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Friday, 31-Jan-2025 16:45:53 JST feld

     in reply to
     @maulanahirzan Enable this first
     
     https://www.daemonology.net/blog/2013-11-06-automated-freebsd-panic-reporting.html
   • Embed this notice
     Alauddin Maulana Hirzan 💻 (maulanahirzan@mastodon.bsd.cafe)'s status on Friday, 31-Jan-2025 16:45:54 JST Alauddin Maulana Hirzan 💻

     in reply to

     • feld

     @feld there is a possibility of kernel panic. But I did not know how to log the error.

   • Embed this notice
     feld (feld@friedcheese.us)'s status on Friday, 31-Jan-2025 16:50:49 JST feld

     in reply to

     • feld
     @maulanahirzan Even if you can't get mails off it hopefully having a functional dumpdev will help collect them. If it does panic properly it should at least write something that will be extracted on next boot to /var/crash
     
     I think you want to set this sysctl if you want to see the panic and debugger
     
     debug.debugger_on_panic=1
     
     I'm away from my BSD box until the morning but yeah let's get this in front of the right people