dri-devel March 2011

dri-devel@lists.freedesktop.org

88 participants
477 discussions

[regression] 2.6.37-post-rc7 with radeon kms: reproducably locks up hard when using desktop cube of kwin
by Martin Steigerwald 08 Mar '11

08 Mar '11

I will add a regression entry in bugzilla after I got the URL of that mail. Hi! No, I do not actively search for lockup bugs, but they seem to search me ;). martin@shambhala:~> cat /proc/version Linux version 2.6.38-rc7-tp42-00142-g212e349 (martin@shambhala) (gcc version 4.4.5 (Debian 4.4.5-11) ) #4 PREEMPT Sat Mar 5 12:03:41 CET 2011 locks up hard when using desktop cube of kwin from KDE 4.5.1. It happens within a few seconds to about 30 seconds after activating the effect with Ctrl-F11. Otherwise the machine seems to work fine so far - if that continues I do not have much of a problem with the bug since I do not use desktop cube other than for getting a feel of compositing performance. Effects seem to be more fluent, more smooth anyway, I guess due to Radeon KMS page flipping. I am using X.org 1.9.4 with Radeon driver 1:6.14.0-1 on Debian Wheezy/Sid/Experimental on a ThinkPad T42 with: martin@shambhala:~> lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] [1002:4e50] This didn't happen with 2.6.37-tp42-rtime-00004-g9eb63ce, same gcc. Possibly related to bug #28622 "radeon video lookup". As I am in my holidays in Sevilla I will only care about bisecting when it rains three days in a row ;) - cause I insist on my holidays being holidays and so will only do light kernel testing ;). I wanted to report this nonetheless since at least on my machine this is really easy to reproduce. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7

4 11

i915: 2.6.36: Monitor incorrectly detects 1920x1199
by Mario 'BitKoenig' Holbe 08 Mar '11

08 Mar '11

Hello, starting with 2.6.36 my monitor detects a resolution of 1920x1199 instead of 1920x1200. The monitor displays 1920x1199 on its OSD, and as a result, I guess, the display is blurred in the middle section (top to down) - most likely due to stretching applied by the monitor. This issue shows up when loading i915 (KMS enabled) with 2.6.37 and 2.6.36 (also 2.6.36.2). With 2.6.35 (up to 2.6.35.10) the monitor correctly detects (and displays on OSD) 1920x1200 and doesn't blur anything. The Chipset is an Intel G35 on an Asus P5E-V HDMI, the monitor is a Yuraku YV24WBH1 connected via DVI (DVI to HDMI adapter, the board doesn't have a separate DVI port). The `fbset' output with 2.6.37 and 2.6.35.10 doesn't differ: mode "1920x1200" geometry 1920 1200 1920 1200 32 timings 0 0 0 0 0 0 0 rgba 8/16,8/8,8/0,0/0 endmode dmesg excerpt for 2.6.37: [ 2.733019] efifb: probing for efifb [ 2.744452] efifb: framebuffer at 0xd0000000, mapped to 0xf8280000, using 7552k, total 7552k [ 2.769712] efifb: mode is 1600x1200x32, linelength=6400, pages=1 [ 2.787964] efifb: scrolling: redraw [ 2.798678] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 2.927422] fb0: EFI VGA frame buffer device [ 71.202957] [drm] Initialized drm 1.1.0 20060810 [ 71.374419] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 71.374423] i915 0000:00:02.0: setting latency timer to 64 [ 71.474329] i915 0000:00:02.0: irq 44 for MSI/MSI-X [ 71.669097] [drm] initialized overlay support [ 71.942025] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver [ 72.223827] fb0: inteldrmfb frame buffer device [ 72.223829] drm: registered panic notifier [ 72.223961] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 [ 87.492007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [ 87.572007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [ 87.652006] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [ 87.732007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [ 87.812007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [ 87.892007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [ 87.972008] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [ 88.052006] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [ 89.692006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved] [ 89.772006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved] [ 89.852006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved] [ 89.932007] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved] [ 90.012007] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved] [ 90.092006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved] [ 90.172006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved] [ 90.252006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved] dmesg excerpt for 2.6.35.10: [ 3.401792] efifb: probing for efifb [ 3.412804] efifb: framebuffer at 0xd0000000, mapped to 0xf8280000, using 3072k, total 3072k [ 3.438065] efifb: mode is 1024x768x32, linelength=4096, pages=1 [ 3.456058] efifb: scrolling: redraw [ 3.466773] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 3.540728] fb0: EFI VGA frame buffer device [ 52.667436] [drm] Initialized drm 1.1.0 20060810 [ 52.824746] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 52.824750] i915 0000:00:02.0: setting latency timer to 64 [ 52.901066] i915 0000:00:02.0: irq 47 for MSI/MSI-X [ 52.901076] [drm] set up 7M of stolen space [ 53.255059] [drm] initialized overlay support [ 53.806061] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver [ 54.171524] fb0: inteldrmfb frame buffer device [ 54.171525] drm: registered panic notifier [ 54.171681] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 The monitor's EDID information via `get-edid | parse-edid': # EDID version 1 revision 3 Section "Monitor" # Block type: 2:0 3:fc Identifier "MB24W" VendorName "NTS" ModelName "MB24W" # Block type: 2:0 3:fc # Block type: 2:0 3:fd HorizSync 30-74 VertRefresh 50-61 # Max dot clock (video bandwidth) 160 MHz # Block type: 2:0 3:ff # DPMS capabilities: Active off:yes Suspend:no Standby:no Mode "1920x1200" # vfreq 59.950Hz, hfreq 74.038kHz DotClock 154.000000 HTimings 1920 1968 2000 2080 VTimings 1200 1203 1209 1235 Flags "-HSync" "+VSync" EndMode # Block type: 2:0 3:fc # Block type: 2:0 3:fd # Block type: 2:0 3:ff EndSection PS: I mailed this to lkml about a week ago, maybe dri-devel@ will suit better? regards Mario -- File names are infinite in length where infinity is set to 255 characters. -- Peter Collinson, "The Unix File System"

1 1

[Bug 29022] [REGRESSION? 2.6.38-rc4] nouveau NV50/NVA8 screen freeze
by bugzilla-daemon＠bugzilla.kernel.org 08 Mar '11

08 Mar '11

https://bugzilla.kernel.org/show_bug.cgi?id=29022 --- Comment #16 from Lucas Stach <dev(a)lynxeye.de> 2011-03-08 15:40:44 --- No please leave it open for now, just remove the regression flag. Also you could add _full_ dmesg output and the versions of your userspace (xf86-video-nouveau, x-server, libdrm and if installed mesa). Dmesg after crash may also be interesting (hopefully we find something this time, but I doubt it). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 29022] [REGRESSION? 2.6.38-rc4] nouveau NV50/NVA8 screen freeze
by bugzilla-daemon＠bugzilla.kernel.org 08 Mar '11

08 Mar '11

https://bugzilla.kernel.org/show_bug.cgi?id=29022 --- Comment #15 from Florian Mickler <florian(a)mickler.org> 2011-03-08 15:36:50 --- If you find the commit that made this worse it may hint at a solution or maybe just reverting fixes things... so if you can use git bisect (man git-bisect), please do so. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 29022] [REGRESSION? 2.6.38-rc4] nouveau NV50/NVA8 screen freeze
by bugzilla-daemon＠bugzilla.kernel.org 08 Mar '11

08 Mar '11

https://bugzilla.kernel.org/show_bug.cgi?id=29022 --- Comment #14 from Marc Koschewski <marc(a)osknowledge.org> 2011-03-08 12:46:01 --- To be honest, I doubt _this_ is rolled out. The behavior might be there in 2.6.37 but in 2.6.38 it seems to be worse. With 2.6.37 I have some random lock-ups leading to the GPU once in a month (I consider this normal, even as NVidia itself has problems like this with their drivers). The recent 2.6.38-rc kernels freeze actually after some minutes. And this can be reproduced. But OK, since you seem to say that there's nothing we could do about it at this point - as nobody seems to know a solution - what do we do with the bug report? Close it? Sad to hear I won't be able to use the 2.6.38 release. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 29022] [REGRESSION? 2.6.38-rc4] nouveau NV50/NVA8 screen freeze
by bugzilla-daemon＠bugzilla.kernel.org 08 Mar '11

08 Mar '11

https://bugzilla.kernel.org/show_bug.cgi?id=29022 --- Comment #13 from Lucas Stach <dev(a)lynxeye.de> 2011-03-08 11:26:25 --- This _is_ already rolled out, as no nouveau version so far didn't lock up randomly on NVA8. It seems you were enormously lucky to not see them on .37. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 29022] [REGRESSION? 2.6.38-rc4] nouveau NV50/NVA8 screen freeze
by bugzilla-daemon＠bugzilla.kernel.org 08 Mar '11

08 Mar '11

https://bugzilla.kernel.org/show_bug.cgi?id=29022 --- Comment #12 from Marc Koschewski <marc(a)osknowledge.org> 2011-03-08 08:42:13 --- I have no other card to test over here. :/ rc8 still fails to behave like 2.6.37. Is this really going to be rolled out? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

Radeon driver failed to work on PAE kernel with memory over 4G?
by april 08 Mar '11

08 Mar '11

Hi all: I'm using Ubunut10.10 with kernel 2.6.35-23-generic-pae (4G ddr3 memory) and try to use radeon driver, but failed. Can radeon driver support PAE kernel with memory over 4G? Thanks [ 20.344777] ------------[ cut here ]------------ [ 20.344812] WARNING: at /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_gart.c:176 radeon_gart_bind+0x196/0x1a0 [radeon]() [ 20.344817] Hardware name: *** [ 20.344820] trying to bind memory to unitialized GART ! [ 20.344822] Modules linked in: binfmt_misc parport_pc ppdev snd_hda_codec_via snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device radeon ttm video output i2c_viapro drm_kms_helper drm agpgart i2c_algo_bit lp snd soundcore snd_page_alloc parport usbhid hid pata_via via_velocity crc_ccitt via_sdmmc [ 20.344862] Pid: 313, comm: plymouthd Tainted: G W 2.6.35-23-generic-pae #41-Ubuntu [ 20.344866] Call Trace: [ 20.344873] [<c0152852>] warn_slowpath_common+0x72/0xa0 [ 20.344901] [<f873e396>] ? radeon_gart_bind+0x196/0x1a0 [radeon] [ 20.344926] [<f873e396>] ? radeon_gart_bind+0x196/0x1a0 [radeon] [ 20.344932] [<c0152923>] warn_slowpath_fmt+0x33/0x40 [ 20.344958] [<f873e396>] radeon_gart_bind+0x196/0x1a0 [radeon] [ 20.344969] [<f85fe4f6>] ? __ttm_tt_get_page+0x76/0x110 [ttm] [ 20.344995] [<f873bf11>] radeon_ttm_backend_bind+0x31/0xa0 [radeon] [ 20.345004] [<f85fe7df>] ? ttm_tt_populate+0x6f/0x90 [ttm] [ 20.345013] [<f85fe854>] ttm_tt_bind+0x54/0x80 [ttm] [ 20.345022] [<f85fef68>] ? ttm_bo_add_ttm+0x58/0xe0 [ttm] [ 20.345032] [<f85ff282>] ttm_bo_handle_move_mem+0x172/0x390 [ttm] [ 20.345042] [<f86013ad>] ttm_bo_move_buffer+0x10d/0x130 [ttm] [ 20.345063] [<f85c6ae4>] ? drm_mm_split_at_start+0x24/0x80 [drm] [ 20.345073] [<f8601476>] ttm_bo_validate+0xa6/0x140 [ttm] [ 20.345083] [<f860169c>] ttm_bo_init+0x18c/0x1f0 [ttm] [ 20.345112] [<f873dce1>] radeon_bo_create+0x111/0x240 [radeon] [ 20.345138] [<f873da80>] ? radeon_ttm_bo_destroy+0x0/0xa0 [radeon] [ 20.345168] [<f87525d6>] radeon_gem_object_create+0x76/0xe0 [radeon] [ 20.345197] [<f87526a7>] radeon_gem_create_ioctl+0x67/0xe0 [radeon] [ 20.345203] [<c01c645d>] ? trace_fn_bin+0x4d/0x70 [ 20.345220] [<f85bdb2d>] drm_ioctl+0x1ad/0x430 [drm] [ 20.345226] [<c01c645d>] ? trace_fn_bin+0x4d/0x70 [ 20.345256] [<f8752640>] ? radeon_gem_create_ioctl+0x0/0xe0 [radeon] [ 20.345263] [<c01410a5>] ? __wake_up+0x45/0x60 [ 20.345269] [<c03f376d>] ? tty_ldisc_deref+0xd/0x10 [ 20.345275] [<c03ee66f>] ? tty_write+0x1af/0x210 [ 20.345281] [<c01c645d>] ? trace_fn_bin+0x4d/0x70 [ 20.345286] [<c02309c2>] vfs_ioctl+0x32/0xb0 [ 20.345303] [<f85bd980>] ? drm_ioctl+0x0/0x430 [drm] [ 20.345309] [<c0231259>] do_vfs_ioctl+0x79/0x2d0 [ 20.345315] [<c03ee4c0>] ? tty_write+0x0/0x210 [ 20.345320] [<c0231517>] sys_ioctl+0x67/0x80 [ 20.345326] [<c01c645d>] ? trace_fn_bin+0x4d/0x70 [ 20.345332] [<c010939f>] sysenter_do_call+0x12/0x28 [ 20.345337] [<c01c645d>] ? trace_fn_bin+0x4d/0x70 [ 20.345342] [<c01c645d>] ? trace_fn_bin+0x4d/0x70 [ 20.345346] ---[ end trace 2cbcf253eb8f50f9 ]--- [ 20.345350] [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 768 pages at 0x00000000 [ 20.351698] [TTM] Couldn't bind backend. [ 20.355853] radeon 0000:01:00.0: object_init failed for (3145728, 0x00000002) [ 20.358834] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (3145728, 2, 4096, -22) [ 20.376787] ------------[ cut here ]------------

2 1

[Bug 32889] New: [i915g] SIGSEGV src/gallium/drivers/i915/i915_state_emit.c:414
by bugzilla-daemon＠freedesktop.org 08 Mar '11

08 Mar '11

https://bugs.freedesktop.org/show_bug.cgi?id=32889 Summary: [i915g] SIGSEGV src/gallium/drivers/i915/i915_state_emit.c:414 Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/Gallium/i915g AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: vlee(a)vmware.com mesa: 6d9ca78ef7bf831b9b63f4bda68623cbae627508 (master) chipset: 945GM (Intel GMA 950) system architecture: i686 xserver-xorg-video-intel: 2:2.12.0-1ubuntu5.1 libdrm-intel1: 2.4.21-1ubuntu2.1 kernel version: 2.6.35-24-generic Linux distribution: Ubuntu 10.10 i386 Run piglit fbo-blit-d24s8 test. $ ./bin/fbo-blit-d24s8 -auto Segmentation fault (core dumped) Program terminated with signal 11, Segmentation fault. #0 0x01102b3b in i915_emit_hardware_state (i915=0x8a6e370) at src/gallium/drivers/i915/i915_state_emit.c:414 414 struct i915_texture *tex = i915_texture(cbuf_surface->texture); (gdb) bt #0 0x01102b3b in i915_emit_hardware_state (i915=0x8a6e370) at src/gallium/drivers/i915/i915_state_emit.c:414 #1 0x010fe0e6 in i915_vbuf_render_draw_arrays (render=0x8a84788, start=0, nr=4) at src/gallium/drivers/i915/i915_prim_vbuf.c:516 #2 0x01194f9d in draw_pt_emit_linear (emit=0x8a6ad30, vert_info=0xbff42328, prim_info=0xbff4239c) at src/gallium/auxiliary/draw/draw_pt_emit.c:265 #3 0x0112fc82 in emit (emit=0x8a6ad30, vert_info=0xbff42328, prim_info=0xbff4239c) at src/gallium/auxiliary/draw/draw_pt_fetch_shade_pipeline.c:168 #4 0x01130023 in fetch_pipeline_generic (middle=0x8a6acc8, fetch_info=0x0, prim_info=0xbff4239c) at src/gallium/auxiliary/draw/draw_pt_fetch_shade_pipeline.c:286 #5 0x01130144 in fetch_pipeline_linear_run (middle=0x8a6acc8, start=0, count=4, prim_flags=0) at src/gallium/auxiliary/draw/draw_pt_fetch_shade_pipeline.c:345 #6 0x01135155 in vsplit_segment_simple_linear (vsplit=0x8a7ee30, flags=0, istart=0, icount=4) at src/gallium/auxiliary/draw/draw_pt_vsplit_tmp.h:229 #7 0x011354ee in vsplit_run_linear (frontend=0x8a7ee30, start=0, count=4) at src/gallium/auxiliary/draw/draw_split_tmp.h:61 #8 0x0112d494 in draw_pt_arrays (draw=0x8a69348, prim=6, start=0, count=4) at src/gallium/auxiliary/draw/draw_pt.c:113 #9 0x0112e049 in draw_vbo (draw=0x8a69348, info=0xbff425a4) at src/gallium/auxiliary/draw/draw_pt.c:481 #10 0x010fc5d3 in i915_draw_vbo (pipe=0x8a6e370, info=0xbff425a4) at src/gallium/drivers/i915/i915_context.c:81 #11 0x019d3690 in util_draw_arrays (pipe=0x8a6e370, mode=6, start=0, count=4) at src/gallium/auxiliary/util/u_draw.h:58 #12 0x019d3757 in util_draw_vertex_buffer (pipe=0x8a6e370, vbuf=0x8b17920, offset=0, prim_type=6, num_verts=4, num_attribs=2) at src/gallium/auxiliary/util/u_draw_quad.c:63 #13 0x01952f15 in draw_quad (st=0x8ad80a0, x0=-1, y0=-1, x1=1, y1=1, z=0.54321003, color=0x8a97324) at src/mesa/state_tracker/st_cb_clear.c:175 #14 0x019535be in clear_with_quad (ctx=0x8a96618, color=0 '\000', depth=2 '\002', stencil=4 '\004') at src/mesa/state_tracker/st_cb_clear.c:299 #15 0x01953cfd in st_Clear (ctx=0x8a96618, mask=48) at src/mesa/state_tracker/st_cb_clear.c:530 #16 0x018ddbb0 in _mesa_Clear (mask=1280) at src/mesa/main/clear.c:242 #17 0x0804b907 in run_test () at piglit/tests/fbo/fbo-blit-d24s8.c:179 #18 0x0804bce9 in piglit_display () at piglit/tests/fbo/fbo-blit-d24s8.c:242 #19 0x0804dce3 in display () at piglit/tests/util/piglit-framework.c:52 #20 0x002d2820 in fghRedrawWindow (window=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece. ) at freeglut_main.c:210 #21 fghcbDisplayWindow (window=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece. ) at freeglut_main.c:227 #22 0x002d6660 in fgEnumWindows (enumCallback=0x2d2790 <fghcbDisplayWindow>, enumerator=0xbff42948) at freeglut_structure.c:394 #23 0x002d2cdb in fghDisplayAll () at freeglut_main.c:249 #24 glutMainLoopEvent () at freeglut_main.c:1450 #25 0x002d3605 in glutMainLoop () at freeglut_main.c:1498 #26 0x0804de8c in main (argc=1, argv=0xbff42bd4) at piglit/tests/util/piglit-framework.c:118 (gdb) frame 0 #0 0x01102b3b in i915_emit_hardware_state (i915=0x8a6e370) at src/gallium/drivers/i915/i915_state_emit.c:414 414 struct i915_texture *tex = i915_texture(cbuf_surface->texture); (gdb) print cbuf_surface $1 = (struct pipe_surface *) 0x0 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 32887] New: [r600g] SIGSEGV src/gallium/drivers/r600/r600_state.c:237
by bugzilla-daemon＠freedesktop.org 08 Mar '11

08 Mar '11

https://bugs.freedesktop.org/show_bug.cgi?id=32887 Summary: [r600g] SIGSEGV src/gallium/drivers/r600/r600_state.c:237 Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: vlee(a)vmware.com mesa: 6d9ca78ef7bf831b9b63f4bda68623cbae627508 (master) chipset: RV620 system architecture: i686 libdrm-dev: 2.14.21-1ubuntu2.1 kernel version: 2.6.35-24-generic Linux distribution: Ubuntu 10.10 i386 Run piglit fbo-generatemipmap-formats test. $ ./bin/fbo-generatemipmap-formats -auto Using test set: Core formats Testing 3 Testing 4 Testing GL_RGB Testing GL_RGBA Testing GL_ALPHA Probe at (129,1) Expected: 1.000000 1.000000 1.000000 0.250000 Observed: 1.000000 1.000000 1.000000 0.000000 Testing GL_LUMINANCE Probe at (1,1) Expected: 1.000000 1.000000 1.000000 1.000000 Observed: 0.000000 0.000000 0.000000 1.000000 Testing GL_LUMINANCE_ALPHA Testing GL_INTENSITY Probe at (1,1) Expected: 1.000000 1.000000 1.000000 1.000000 Observed: 0.000000 0.000000 0.000000 0.000000 Testing GL_ALPHA4 Probe at (129,1) Expected: 1.000000 1.000000 1.000000 0.250000 Observed: 1.000000 1.000000 1.000000 0.000000 Testing GL_ALPHA8 Probe at (129,1) Expected: 1.000000 1.000000 1.000000 0.250000 Observed: 1.000000 1.000000 1.000000 0.000000 Testing GL_ALPHA12 Segmentation fault (core dumped) Program terminated with signal 11, Segmentation fault. #0 0x01108338 in r600_draw_common (draw=0xbf9537b4) at src/gallium/drivers/r600/r600_state.c:237 237 if (rctx->vertex_elements->count < rctx->vs_shader->shader.bc.nresource) { (gdb) bt #0 0x01108338 in r600_draw_common (draw=0xbf9537b4) at src/gallium/drivers/r600/r600_state.c:237 #1 0x011087c9 in r600_draw_vbo (ctx=0x8fdad50, info=0xbf953c34) at src/gallium/drivers/r600/r600_state.c:307 #2 0x0125fbcd in st_draw_vbo (ctx=0x92ec4b0, arrays=0x932e590, prims=0xbf953cdc, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001', min_index=0, max_index=3) at src/mesa/state_tracker/st_draw.c:732 #3 0x012e5961 in vbo_draw_arrays (ctx=0x92ec4b0, mode=7, start=0, count=4, numInstances=1) at src/mesa/vbo/vbo_exec_array.c:588 #4 0x012e5ac8 in vbo_exec_DrawArrays (mode=7, start=0, count=4) at src/mesa/vbo/vbo_exec_array.c:619 #5 0x0804d636 in piglit_draw_rect_tex () #6 0x0804b4e3 in draw_mipmap () #7 0x0804bbd9 in test_format () #8 0x0804bd02 in piglit_display () #9 0x0804de93 in display () #10 0x00a8b820 in fghRedrawWindow (window=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece. ) at freeglut_main.c:210 #11 fghcbDisplayWindow (window=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece. ) at freeglut_main.c:227 #12 0x00a8f660 in fgEnumWindows (enumCallback=0xa8b790 <fghcbDisplayWindow>, enumerator=0xbf953f88) at freeglut_structure.c:394 #13 0x00a8bcdb in fghDisplayAll () at freeglut_main.c:249 #14 glutMainLoopEvent () at freeglut_main.c:1450 #15 0x00a8c605 in glutMainLoop () at freeglut_main.c:1498 #16 0x0804e03c in main () (gdb) frame 0 #0 0x01108338 in r600_draw_common (draw=0xbf9537b4) at src/gallium/drivers/r600/r600_state.c:237 237 if (rctx->vertex_elements->count < rctx->vs_shader->shader.bc.nresource) { (gdb) print rctx->vertex_elements $1 = (struct r600_vertex_element *) 0x0 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

← Newer
1
...
35
36
37
38
39
40
41
...
48
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2011