Bug 32238

Summary:	Crash in glxMakeCurrent
Product:	Mesa	Reporter:	Benoit Jacob <bjacob>
Component:	GLX	Assignee:	mesa-dev
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	medium	CC:	bugs.freedesktop
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Benoit Jacob 2010-12-08 10:39:21 UTC

This is coming from https://bugzilla.mozilla.org/show_bug.cgi?id=616416

A user is reporting segmentation fault in glxMakeCurrent, which AFAICS can only be a bug in the implementation.

Program received signal SIGSEGV, Segmentation fault.
0x00007fffeec3cac0 in xcb_glx_get_string_string_length () from
/usr/lib/libxcb-glx.so.0
(gdb) bt
#0  0x00007fffeec3cac0 in xcb_glx_get_string_string_length () from
/usr/lib/libxcb-glx.so.0
#1  0x00007ffff0342dbb in __glXGetString (dpy=0x7fffee83e000, opcode=153,
contextTag=10027013, name=7939) at glx_query.c:82
#2  0x00007ffff033ef6c in __indirect_glGetString (name=7939) at single2.c:686
#3  0x00007ffff031006e in indirect_bind_context (gc=0x7fffd9ffa1e0,
old=0x7fffd9ff9880, draw=10486546, read=10486546) at indirect_glx.c:156
#4  0x00007ffff030cbb9 in MakeContextCurrent (dpy=0x7fffee83e000,
draw=10486546, read=10486546, gc_user=0x7fffd9ffa1e0) at glxcurrent.c:263
#5  0x00007ffff030cc6a in glXMakeCurrent (dpy=0x7fffee83e000, draw=10486546,
gc=0x7fffd9ffa1e0) at glxcurrent.c:287
#6  0x00007ffff6f38667 in ?? () from /usr/lib64/firefox-4.0b8pre/libxul.so
#7  0x00007ffff6f38988 in ?? () from /usr/lib64/firefox-4.0b8pre/libxul.so
#8  0x00007ffff6f37efd in ?? () from /usr/lib64/firefox-4.0b8pre/libxul.so
#9  0x00007ffff6f37ff2 in
mozilla::gl::GLContextProviderGLX::CreateOffscreen(gfxIntSize const&,
mozilla::gl::ContextFormat const&) ()
   from /usr/lib64/firefox-4.0b8pre/libxul.so


His opengl information:

OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on R600 (HD2XXX,HD3XXX)
OpenGL version string: 1.4 (2.1 Mesa 7.9)
OpenGL extensions:

Comment 1 Octoploid 2010-12-08 20:28:05 UTC

As I wrote on the mozilla bug:

I normally use my monitor in portrait mode:
DVI-0 connected 1050x1680+0+0 left
When I rotate it back to its default position and run
"xrandr --output DVI-0 --rotate normal" there are no
crashes anymore and webgl is working fine.

Comment 2 Octoploid 2010-12-09 01:52:37 UTC

It seems as though that the RS780 microcode didn't
get loaded at boot-time on the kernel I was using
during the tests:

Dec 04 06:41:20 [kernel] Linux agpgart interface v0.103
Dec 04 06:41:20 [kernel] [drm] Initialized drm 1.1.0 20060810
Dec 04 06:41:20 [kernel] [drm] radeon defaulting to kernel modesetting.
Dec 04 06:41:20 [kernel] [drm] radeon kernel modesetting enabled.
Dec 04 06:41:20 [kernel] radeon 0000:01:05.0: PCI INT A -> GSI 18 (level, low)
-> IRQ 18
Dec 04 06:41:20 [kernel] radeon 0000:01:05.0: setting latency timer to 64
Dec 04 06:41:20 [kernel] [drm] initializing kernel modesetting (RS780
0x1002:0x9614).
Dec 04 06:41:20 [kernel] [drm] register mmio base: 0xFBEE0000
Dec 04 06:41:20 [kernel] [drm] register mmio size: 65536
Dec 04 06:41:20 [kernel] ATOM BIOS: 113
Dec 04 06:41:20 [kernel] radeon 0000:01:05.0: VRAM: 128M 0xC0000000 -
0xC7FFFFFF (128M used)
Dec 04 06:41:20 [kernel] radeon 0000:01:05.0: GTT: 512M 0xA0000000 - 0xBFFFFFFF
Dec 04 06:41:20 [kernel] [drm] Detected VRAM RAM=128M, BAR=128M
Dec 04 06:41:20 [kernel] [drm] RAM width 32bits DDR
Dec 04 06:41:20 [kernel] [TTM] Zone  kernel: Available graphics memory: 2026154
kiB.
Dec 04 06:41:20 [kernel] [TTM] Initializing pool allocator.
Dec 04 06:41:20 [kernel] [drm] radeon: 128M of VRAM memory ready
Dec 04 06:41:20 [kernel] [drm] radeon: 512M of GTT memory ready.
Dec 04 06:41:20 [kernel] [drm] radeon: irq initialized.
Dec 04 06:41:20 [kernel] [drm] GART: num cpu pages 131072, num gpu pages 131072
Dec 04 06:41:20 [kernel] radeon 0000:01:05.0: WB enabled
Dec 04 06:41:20 [kernel] [drm] ring test succeeded in 1 usecs
Dec 04 06:41:20 [kernel] [drm] radeon: ib pool ready.
Dec 04 06:41:20 [kernel] [drm] ib test succeeded in 0 usecs
Dec 04 06:41:20 [kernel] [drm] Enabling audio support
Dec 04 06:41:20 [kernel] [drm] Radeon Display Connectors
Dec 04 06:41:20 [kernel] [drm] Connector 0:
Dec 04 06:41:20 [kernel] [drm]   VGA
Dec 04 06:41:20 [kernel] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48
0x7e4c 0x7e4c
Dec 04 06:41:20 [kernel] [drm]   Encoders:
Dec 04 06:41:20 [kernel] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
Dec 04 06:41:20 [kernel] [drm] Connector 1:
Dec 04 06:41:20 [kernel] [drm]   DVI-D
Dec 04 06:41:20 [kernel] [drm]   HPD3
Dec 04 06:41:20 [kernel] [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58
0x7e5c 0x7e5c
Dec 04 06:41:20 [kernel] [drm]   Encoders:
Dec 04 06:41:20 [kernel] [drm]     DFP3: INTERNAL_KLDSCP_LVTMA
Dec 04 06:41:20 [kernel] [drm] radeon: power management initialized
Dec 04 06:41:20 [kernel] [drm] fb mappable at 0xF0141000
Dec 04 06:41:20 [kernel] [drm] vram apper at 0xF0000000
Dec 04 06:41:20 [kernel] [drm] size 7258112
Dec 04 06:41:20 [kernel] [drm] fb depth is 24
Dec 04 06:41:20 [kernel] [drm]    pitch is 6912
Dec 04 06:41:20 [kernel] Console: switching to colour frame buffer device 131x105
Dec 04 06:41:20 [kernel] fb0: radeondrmfb frame buffer device
Dec 04 06:41:20 [kernel] drm: registered panic notifier
Dec 04 06:41:20 [kernel] [drm] Initialized radeon 2.7.0 20080528 for
0000:01:05.0 on minor 0

Notice that the line: [drm] Loading RS780 Microcode
is missing. I've checked my kernel logs and this was
the only time it didn't get loaded during boot.
(I don't use modules, everything is build in)

I don't know, could this be the reason for the bug I
was observing?

Comment 3 Alex Deucher 2010-12-09 05:00:05 UTC

(In reply to comment #2)
> Notice that the line: [drm] Loading RS780 Microcode
> is missing. I've checked my kernel logs and this was
> the only time it didn't get loaded during boot.
> (I don't use modules, everything is build in)
> 
> I don't know, could this be the reason for the bug I
> was observing?

It loaded fine otherwise you'd have no accel at all.

Comment 4 Octoploid 2010-12-12 04:10:59 UTC

I cannot reproduce the problem anymore, so I'm closing this bug.
See the mozilla bug for more info.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.