Mailinglist Archive: opensuse-bugs (2746 mails)

< Previous Next >
[Bug 826322] New: X server switches to llvmpipe after kernel-desktop security update (2013-513)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sun, 23 Jun 2013 12:01:20 +0000
  • Message-id: <bug-826322-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=826322

https://bugzilla.novell.com/show_bug.cgi?id=826322#c0


Summary: X server switches to llvmpipe after kernel-desktop
security update (2013-513)
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: x86-64
OS/Version: openSUSE 12.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: lufterd@xxxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101
Firefox/21.0

After security kernel update (openSUSE-2013-513) from 3.7.10-1.11 to
3.7.10-1.16 KWin compositing became slow and switched from OpenGL/Raster to
XRender/Native. KWin writes to stdout that OpenGL driver is Gallium3D via
llvmpipe (my graphics adapter is Intel HD4000).

There is an error message on boot:
[ 15.222270] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart
module.
[ 15.222279] DRM: Fill_in_dev failed.

After that I loaded kernel 3.7.10-1.11 and everything works fine for now. But
Apper states that there is a security hole and suggests me to update.

I've also tries some other kernels and they have no such problem too (3.9.7 and
3.10rc6).

Reproducible: Always

Steps to Reproduce:
1. Update kernel to 3.7.10-1.16 (openSUSE-2013-513 security update)
Actual Results:
OpenGL driver falls back to llvmpipe and all graphical operations performed on
CPU

Expected Results:
Hardware accelerated OpenGL

Hardware:
Lenovo ThinkPad X230
CPU: Intel Core i5 3230m (Ivy Bridge)
GPU: Intel HD4000 (integrated)

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
This Thread
  • No further messages