Bug 2231095

Summary: segfault at 21c ip 00007f00248bbd34 sp 00007f0023bfec10 error 6 in libvulkan_lvp.so[7f0024657000+348000] likely on CPU 1 (core 1, socket 0)
Product: [Fedora] Fedora Reporter: Andre Robatino <robatino>
Component: mesaAssignee: Adam Jackson <ajax>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 38CC: ajax, bskeggs, igor.raits, j, lyude, mail, rhughes, rstrode, tstellar, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andre Robatino 2023-08-10 14:41:11 UTC 
When using a Fedora 39 guest in VirtualBox 7.0.10, if 3D acceleration is enabled in the guest, the guest eventually freezes, forcing a hard power off, and a message similar to the following appears in dmesg:

segfault at 21c ip 00007f00248bbd34 sp 00007f0023bfec10 error 6 in libvulkan_lvp.so[7f0024657000+348000] likely on CPU 1 (core 1, socket 0)

Not sure if this is a bug in VirtualBox or mesa. The host is F38. The guest works fine if 3D acceleration is not enabled.

mesa-vulkan-drivers-23.1.5-1.fc38.x86_64

Reproducible: Always
Comment 1 Andre Robatino 2023-08-10 14:47:02 UTC 
I had the same trouble when installing the F39 guest from Fedora-Workstation-Live-x86_64-39-20230809.n.2.iso, the installer would freeze up until I disabled 3D acceleration in the guest. Am using Oracle's VirtualBox (not RPM Fusion).
Comment 2 Andre Robatino 2023-08-11 15:44:34 UTC 
I just tried running both Fedora-Workstation-Live-x86_64-39-20230809.n.2.iso and Fedora-Workstation-Live-x86_64-38-1.6.iso live with 3D acceleration enabled, and confirmed that they both freeze eventually, so whether the guest is F38 or F39 appears to have nothing to do with it. However, I did not see any dmesg errors when the freeze happened when running live, so maybe mesa-vulkan-drivers-23.1.5-1.fc38.x86_64 isn't involved, or maybe only when doing an install, not running live.