Bug 1007658

Summary: openSUSE 13.2 Kernel 3.16.7-45.1 broke 3D acceleration / drm
Product: [openSUSE] openSUSE Distribution Reporter: kolA flash <kolAflash>
Component: KernelAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium CC: astieger, thomas-formella
Version: 13.2   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 13.2   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: glxinfo while running the different kernels, plus lspci

Description kolA flash 2016-10-28 23:17:59 UTC
Created attachment 699945 [details]
glxinfo while running the different kernels, plus lspci

I can't get 3D acceleration with the following kernels:
- kernel-default-3.16.7-45.1
- kernel-desktop-3.16.7-45.1

The old kernel-default-3.16.7-42.1 was working fine and I can successfully workaround the bug by booting kernel-default-3.16.7-42.1 agai (sadly that's no good choice because of the critical security fixes in 3.16.7-42.1).

Interestingly kernel-vanilla-3.16.7-45.1 is working too.


So it appears, that some openSUSE patches in 3.16.7-45.1 break 3D acceleration.

My PC is having an onboard "Radeon HD 4200" card, but I'm using an dedicated "Radeon HD 6450".

Sadly I couldn't diff-out the critical part in the changes between 3.16.7-42.1 and 3.16.7-45.1. But maybe someone else has a clue!?

I attached lspci output.

And I also attached glxinfo output while running the different kernels. In that files you can clearly see an "libGL error" and kernel-default-3.16.7-45.1 only offering "Gallium 0.4 on llvmpipe" (which means software-rendering - as far as I know) instead of "Gallium 0.4 on AMD CAICOS".
Comment 1 Thomas Formella 2016-10-29 08:38:19 UTC
Same problem here. Possibly related to https://bugzilla.opensuse.org/show_bug.cgi?id=1007035 ?
Comment 2 Thomas Formella 2016-10-29 16:27:37 UTC
Problem solved on my machine after updating to kernel 3.16.7-48-default
Comment 3 Andreas Stieger 2016-10-29 20:08:50 UTC
resolving as duplicate of bug 1007035

*** This bug has been marked as a duplicate of bug 1007035 ***