dri-devel September 2010

dri-devel@lists.freedesktop.org

71 participants
367 discussions

[Bug 30406] New: moving windows really slow when using gallium + xorg state tracker in KDE
by bugzilla-daemon＠freedesktop.org 12 Oct '10

12 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=30406 Summary: moving windows really slow when using gallium + xorg state tracker in KDE Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: martinstolpe(a)gmail.com Created an attachment (id=38989) --> (https://bugs.freedesktop.org/attachment.cgi?id=38989) oprofile when moving windows When using gallium with the xorg state tracker moving windows becomes really slow. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 18

[Bug 29012] New: [r300g] Driver needs some kind of force_s3tc_enable option
by bugzilla-daemon＠freedesktop.org 11 Oct '10

11 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29012 Summary: [r300g] Driver needs some kind of force_s3tc_enable option Product: Mesa Version: git Platform: All OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: rankincj(a)googlemail.com Some games (such as World of Warcraft) need S3TC texture support, and so will crash if the OpenGL S3TC extensions are not advertised. Currently, the only way to make Gallium advertise the S3TC extensions is to load the IP-encumbered libtxc_dxtn library. WoW can run successfully using the r300c driver without the libtxc_dxtn, provided the force_s3tc_enable option is used. (There are some issues with corrupt textures, although some of these issues might be caused e.g. by r300c not supporting texture cache regions. However, my point is that WoW doesn't crash instantly with a null pointer exception if the S3TC extensions are available.) -- 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

r300 PenumbraOverture complete hang 2.6.35/36-rc3 (regression)
by PJBrs 10 Oct '10

10 Oct '10

Hello, I'm experiencing a hard lock (i.e., no magic SysRq) after playing PenumbraOverture for about a minute on my ThinkPad t43p with kernel 2.6.35 / 2.6.36-rc3. I'm using KMS. 2.6.34 works fine. I didn't test thoroughly with 2.6.35. With 2.6.36-rc3, I did not mess with any of the new power savings settings. Some more info: lspci says: ATI Technologies Inc M24GL [Mobility FireGL V3200] (rev 80) System info: Slackware 13.1, Mesa 7.8.1, Xserver 1.7.7. Has this bug (or one like it) already been reported? And if not, what can I do to be of help? Should I open a bug report, and if so, where? What further info do you need (kernel config, xorg.conf)? I can build and test new kernels, but I don't know how to bisect them. Also, I don't know how to gather a call trace. PJ

2 2

nouveau/ttm: BUG in ttm_bo_release_list
by Marcin Slusarz 09 Oct '10

09 Oct '10

Hi Since upgrade from 2.6.35 to 2.6.36-rc3 (nouveau tree) I'm hitting this bug a couple of times a day: [ 2869.618504] ------------[ cut here ]------------ [ 2869.618532] kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:153! [ 2869.618560] invalid opcode: 0000 [#1] PREEMPT SMP [ 2869.618600] last sysfs file: /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.0/pm_status [ 2869.618637] CPU 0 [ 2869.618649] Modules linked in: nouveau ttm drm_kms_helper snd_hda_codec_realtek snd_hda_intel snd_hda_codec [ 2869.618730] [ 2869.618742] Pid: 11, comm: kworker/0:1 Not tainted 2.6.36-rc3-nv+ #485 P6T SE/System Product Name [ 2869.618781] RIP: 0010:[<ffffffffa0082c9e>] [<ffffffffa0082c9e>] ttm_bo_release_list+0x37/0xcf [ttm] [ 2869.618830] RSP: 0018:ffff8801bfd85d40 EFLAGS: 00010202 [ 2869.618855] RAX: 0000000000000001 RBX: ffff8801b1e50c00 RCX: ffff8801b7500330 [ 2869.618887] RDX: 0000000000000001 RSI: 0000000000000037 RDI: ffff8801b1e50c44 [ 2869.618918] RBP: ffff8801bfd85d60 R08: 0000000000000002 R09: ffff8801bf683000 [ 2869.618950] R10: ffff8801b1e50c70 R11: 0000000000000000 R12: ffff8801b1e50c44 [ 2869.618981] R13: ffff8801b7500188 R14: 0000000000000000 R15: ffff8801b7500738 [ 2869.619013] FS: 0000000000000000(0000) GS:ffff880001e00000(0000) knlGS:0000000000000000 [ 2869.619048] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 2869.619074] CR2: 00007f2cc0f6b000 CR3: 00000001bfe8a000 CR4: 00000000000006f0 [ 2869.619106] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 2869.619137] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 2869.619168] Process kworker/0:1 (pid: 11, threadinfo ffff8801bfd84000, task ffff8801bfd88000) [ 2869.619205] Stack: [ 2869.619217] 0000000000000000 ffff8801b1e50c44 ffffffffa0082c67 ffff8801bdcb8ab0 [ 2869.619262] <0> ffff8801bfd85d80 ffffffff8121c83a ffff8801b1e50000 ffff8801b1e50c00 [ 2869.619318] <0> ffff8801bfd85dd0 ffffffffa00839f4 ffff880001e0ebc0 0000000000000001 [ 2869.619374] Call Trace: [ 2869.619392] [<ffffffffa0082c67>] ? ttm_bo_release_list+0x0/0xcf [ttm] [ 2869.619425] [<ffffffff8121c83a>] kref_put+0x43/0x4d [ 2869.619451] [<ffffffffa00839f4>] ttm_bo_delayed_delete+0xa2/0xf9 [ttm] [ 2869.619484] [<ffffffffa0083a4b>] ? ttm_bo_delayed_workqueue+0x0/0x30 [ttm] [ 2869.619517] [<ffffffffa0083a65>] ttm_bo_delayed_workqueue+0x1a/0x30 [ttm] [ 2869.619551] [<ffffffff8107eb83>] process_one_work+0x29f/0x448 [ 2869.619580] [<ffffffff8107f0e5>] worker_thread+0x1d6/0x349 [ 2869.619607] [<ffffffff8107ef0f>] ? worker_thread+0x0/0x349 [ 2869.619635] [<ffffffff81082198>] kthread+0x7d/0x85 [ 2869.619661] [<ffffffff8102edd4>] kernel_thread_helper+0x4/0x10 [ 2869.619692] [<ffffffff8105c10b>] ? finish_task_switch+0x49/0xb2 [ 2869.619722] [<ffffffff814333d1>] ? _raw_spin_unlock_irq+0x19/0x34 [ 2869.619752] [<ffffffff814339ad>] ? restore_args+0x0/0x30 [ 2869.619779] [<ffffffff8108211b>] ? kthread+0x0/0x85 [ 2869.619805] [<ffffffff8102edd0>] ? kernel_thread_helper+0x0/0x10 [ 2869.619832] Code: 48 8d 5f bc 48 83 ec 08 8b 07 4c 8b 6f c4 85 c0 74 04 0f 0b eb fe 8b 47 fc 85 c0 74 04 0f 0b eb fe 8b 87 a8 00 00 00 85 c0 74 04 <0f> 0b eb fe 48 83 bb 38 01 00 00 00 74 04 0f 0b eb fe 48 83 bb [ 2869.620255] RIP [<ffffffffa0082c9e>] ttm_bo_release_list+0x37/0xcf [ttm] [ 2869.620295] RSP <ffff8801bfd85d40> [ 2869.629610] ---[ end trace 302a6257f0da8cdc ]--- this is BUG_ON(atomic_read(&bo->cpu_writers)); I'm on b642f07208988270ac402d2548d42dab1d5fec92 "drm/nv50: fix 100c90 write on nva3". If you have any patches / ideas how to debug this, let me know. Marcin

3 4

Error message on RV710: reserve failed for wait
by Jean Delvare 07 Oct '10

07 Oct '10

Hi all, I am running kernel 2.6.36-rc6 on a Radeon HD4350 (RV710), and I see the following error messages in the logs: Sep 30 14:09:27 endymion kernel: [21556.560593] radeon 0000:07:00.0: ffff88007c334000 reserve failed for wait Sep 30 14:09:29 endymion kernel: [21558.253859] radeon 0000:07:00.0: ffff88007c334000 reserve failed for wait Sometimes that's just one or two of these, sometimes a bunch of them. I didn't notice any major problem so far. What kind of issue may result from this error? I see the message comes from function radeon_bo_wait() but I have no idea what this function does. Here are the messages related to my Radeon card as found in the kernel boot log: [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. alloc irq_desc for 30 on node -1 alloc kstat_irqs on node -1 radeon 0000:07:00.0: PCI INT A -> GSI 30 (level, low) -> IRQ 30 radeon 0000:07:00.0: setting latency timer to 64 [drm] initializing kernel modesetting (RV710 0x1002:0x954F). [drm] register mmio base: 0xFBEE0000 [drm] register mmio size: 65536 ATOM BIOS: 113 radeon 0000:07:00.0: VRAM: 512M 0x00000000 - 0x1FFFFFFF (512M used) radeon 0000:07:00.0: GTT: 512M 0x20000000 - 0x3FFFFFFF [drm] Detected VRAM RAM=512M, BAR=256M [drm] RAM width 64bits DDR [TTM] Zone kernel: Available graphics memory: 1024276 kiB. [TTM] Initializing pool allocator. [drm] radeon: 512M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. alloc irq_desc for 64 on node -1 alloc kstat_irqs on node -1 radeon 0000:07:00.0: irq 64 for MSI/MSI-X radeon 0000:07:00.0: radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV710 Microcode [drm] ring test succeeded in 1 usecs [drm] radeon: ib pool ready. [drm] ib test succeeded in 0 usecs [drm] Enabling audio support failed to evaluate ATIF got AE_BAD_PARAMETER [drm] Default TV standard: NTSC [drm] Default TV standard: NTSC [drm] Radeon Display Connectors [drm] Connector 0: [drm] VGA [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [drm] Encoders: [drm] CRT2: INTERNAL_KLDSCP_DAC2 [drm] Connector 1: [drm] HDMI-A [drm] HPD1 [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] Connector 2: [drm] DVI-I [drm] HPD4 [drm] DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c [drm] Encoders: [drm] CRT1: INTERNAL_KLDSCP_DAC1 [drm] DFP2: INTERNAL_UNIPHY2 [drm] Internal thermal controller with fan control [drm] radeon: power management initialized [drm] fb mappable at 0xD0142000 [drm] vram apper at 0xD0000000 [drm] size 8294400 [drm] fb depth is 24 [drm] pitch is 7680 checking generic (d0000000 1000000) vs hw (d0000000 20000000) fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver Console: switching to colour dummy device 80x25 Console: switching to colour frame buffer device 240x67 fb0: radeondrmfb frame buffer device drm: registered panic notifier [drm] Initialized radeon 2.6.0 20080528 for 0000:07:00.0 on minor 0 The only thing out of the ordinary I could spot is the "failed to evaluate ATIF" message, but apparently it is only a debug message, so I doubt it is related (but it would certainly be nice to solve that problem too.) Let me know if I can provide more information, or help in any way with debugging this issue. Thanks, -- Jean Delvare

2 3

Re: Any SYSRQ key to force mode switch to console mode when using KMS?
by Randy Dunlap 06 Oct '10

06 Oct '10

On Thu, 23 Sep 2010 18:31:32 +0200 Uwe Bonnes wrote: [just adding cc's] > >>>>> "Randy" == Randy Dunlap <rdunlap(a)xenotime.net> writes: > > > Randy> Is CONFIG_DRM_KMS_HELPER enabled in your kernel .config file? If > Randy> not, we need to find out how to enable it (there is no kconfig > Randy> prompt for it). > > Yes, it is enabled > > Randy> Can you check if Alt-Sysrq-H (help) lists V for "force-fb(V)"? > Yes, it is listed. > > And yes, my last experiments where with ALT-CTL-sysreq, so doomed for non > function due to operator error. > > However: > When running X, X.Org X Server 1.9.0 on Thinkpad R50 RV250, Alt-Sysrq-v > switches to an all-black display. By console switching with ALT-CLT-F1 I > get back to the booting console and ALT-CLT-F7 brings me back to X. Running > on the console and calling Alt-Sysrq-v prints > SysRq : Restore framebuffer console > > Is there some omission by the distribution or my setup that Alt-Sysrq-v when > running X results in an all-black screen? > > And when I hit the hibernate problem, the screen stays black even with a > console switch after Alt-Sysrq-v > > Bye > -- > Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de > > Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt > --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***

2 1

[Bug 29834] New: System freeze upon X startup with KMS enabled (RV730)
by bugzilla-daemon＠freedesktop.org 04 Oct '10

04 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29834 Summary: System freeze upon X startup with KMS enabled (RV730) Product: DRI Version: XOrg 6.7.0 Platform: Other OS/Version: All Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: info(a)noctus.net Created an attachment (id=38216) --> (https://bugs.freedesktop.org/attachment.cgi?id=38216) kern.log messages upon freeze Trying to start X with KMS enabled on my HD4670 (RV730) card freezes the system and I have to SysRq out of that situation. Since this only happens with the final release of the 2.6.35 kernel I am currently stuck with the RC6 which does not display this behavior. See the attached kern.log output in case of such freeze. I am running the latest Git masters of both xf86-video-ati (5a7c9d94733a0db1d3565447acc9f0e751db5950 here ATM) as well as mesa (f3ec111b0af9d268e6b3c6d3226a448d19e45d8c here ATM). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 14

[Bug 29513] New: Kwin crash when i change the decoration.
by bugzilla-daemon＠freedesktop.org 04 Oct '10

04 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29513 Summary: Kwin crash when i change the decoration. Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: marokanski.kazak(a)gmail.com I reported this bug to bugs.kde.org and they said that the crash is because of the video driver so i should send it upstream. I have Mesa 7.8.2 and Xorg 1.8.0- the default coming with openSUSE 11.3. My video card is ATI Radeon HD3450. Here is a copy of the bug i sent to Bugs.kde Application: kwin (4.5.00 (KDE 4.5.0)) KDE Platform Version: 4.5.00 (KDE 4.5.0) Qt Version: 4.6.3 Operating System: Linux 2.6.34-12-default i686 Distribution: "openSUSE 11.3 (i586)" -- Information about the crash: - What I was doing when the application crashed: Kwin crashes every time i change the window decoration. It recovers almost instantly with the new decoration that i selected. Sometimes after recovery the desktop effects are stopped and i have to turn them on. The crash also occurrs when i setup transperant windows with exactly the same crash. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin), signal: Segmentation fault [KCrash Handler] #7 0xb6b2727b in dri2DrawableGetMSC (psc=0x83f6ff8, pdraw=0x0, ust=0xbfb51a28, msc=0xbfb51a20, sbc=0xbfb51a18) at dri2_glx.c:226 #8 0xb6b00107 in __glXGetVideoSyncSGI (count=0xbfb51a6c) at glxcmds.c:2317 #9 0xb761d5c4 in KWin::SceneOpenGL::waitSync (this=0x89a96c0) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/scene_opengl.cpp:781 #10 0xb7633874 in KWin::SceneOpenGL::flushBuffer (this=0x89a96c0, mask=32, damage=...) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/scene_opengl.cpp:830 #11 0xb768588a in KWin::SceneOpenGL::paint (this=0x89a96c0, damage=..., toplevels=...) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/scene_opengl.cpp:761 #12 0xb7662794 in KWin::Workspace::performCompositing (this=0x81a2a48) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/composite.cpp:454 #13 0xb7695a5b in KWin::Workspace::qt_metacall (this=0x81a2a48, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfb51d5c) at /usr/src/debug/kdebase-workspace-4.5.0/build/kwin/workspace.moc:583 #14 0xb669befd in QMetaObject::metacall (object=0x81a2a48, cl=QMetaObject::InvokeMetaMethod, idx=190, argv=0xbfb51d5c) at kernel/qmetaobject.cpp:237 #15 0xb66aafe8 in QMetaObject::activate (sender=0x81a2cf8, m=0xb67b25a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295 #16 0xb66f7a35 in QTimer::timeout (this=0x81a2cf8) at .moc/release-shared/moc_qtimer.cpp:134 #17 0xb66b08e6 in QTimer::timerEvent (this=0x81a2cf8, e=0xbfb522b0) at kernel/qtimer.cpp:271 #18 0xb66a8774 in QObject::event (this=0x81a2cf8, e=0xbfb522b0) at kernel/qobject.cpp:1212 #19 0xb5bcfc64 in QApplicationPrivate::notify_helper (this=0x8070350, receiver=0x81a2cf8, e=0xbfb522b0) at kernel/qapplication.cpp:4302 #20 0xb5bd7bf7 in QApplication::notify (this=0xbfb525e4, receiver=0x81a2cf8, e=0xbfb522b0) at kernel/qapplication.cpp:3706 #21 0xb719b2c1 in KApplication::notify (this=0xbfb525e4, receiver=0x81a2cf8, event=0xbfb522b0) at /usr/src/debug/kdelibs-4.5.0/kdeui/kernel/kapplication.cpp:310 #22 0xb75f7c4f in KWin::Application::notify (this=0xbfb525e4, o=0x81a2cf8, e=0xbfb522b0) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/main.cpp:372 #23 0xb6695e0e in QCoreApplication::notifyInternal (this=0xbfb525e4, receiver=0x81a2cf8, event=0xbfb522b0) at kernel/qcoreapplication.cpp:726 #24 0xb66c470e in sendEvent (this=0x8070b28) at kernel/qcoreapplication.h:215 #25 QTimerInfoList::activateTimers (this=0x8070b28) at kernel/qeventdispatcher_unix.cpp:618 #26 0xb66c4ffd in QEventDispatcherUNIX::processEvents (this=0x806f280, flags=...) at kernel/qeventdispatcher_unix.cpp:939 #27 0xb5c80f5a in QEventDispatcherX11::processEvents (this=0x806f280, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #28 0xb669511d in QEventLoop::processEvents (this=0xbfb52534, flags=...) at kernel/qeventloop.cpp:149 #29 0xb6695319 in QEventLoop::exec (this=0xbfb52534, flags=...) at kernel/qeventloop.cpp:201 #30 0xb6699c70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #31 0xb5bcd164 in QApplication::exec () at kernel/qapplication.cpp:3581 #32 0xb7693fab in kdemain (argc=3, argv=0xbfb52834) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/main.cpp:531 #33 0x0804860b in main (argc=3, argv=0xbfb52834) at /usr/src/debug/kdebase-workspace-4.5.0/build/kwin/kwin_dummy.cpp:3 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

Re: DRM-related kmalloc-32 memory leak in 2.6.35
by Andrew Morton 04 Oct '10

04 Oct '10

On Wed, 25 Aug 2010 15:59:09 -0500 Matt Mackall <mpm(a)selenic.com> wrote: > On Tue, 2010-08-24 at 10:37 -0500, Christoph Lameter wrote: > > On Tue, 24 Aug 2010, Matt Mackall wrote: > > > > > kmalloc-32 1113344 1113344 32 128 1 : tunables 0 0 > > > 0 : slabdata 8698 8698 0 > > > > > > That's /proc/slabinfo on my laptop with SLUB. It looks like my last > > > reboot popped me back to 2.6.33 so it may also be old news, but I > > > couldn't spot any reports with Google. > > > > Boot with "slub_debug" as a kernel parameter > > > > and then do a > > > > cat /sys/kernel/slab/kmalloc-32/alloc_calls > > > > to find the caller allocating the objets. > > Still present in 2.6.35. Appears to be DRM: > > 845 drm_vm_open_locked+0x72/0x109 age=43/37572/59269 pid=2089 > cpus=0-1 > > That's after about a minute of uptime. Grows to 100k in about a day. > > dmesg bits: > [ 0.834653] [drm] Initialized drm 1.1.0 20060810 > [ 0.834986] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > [ 0.834995] pci 0000:00:02.0: setting latency timer to 64 > [ 1.002572] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining > [ 1.002580] [drm] MTRR allocation failed. Graphics performance may suffer. > [ 1.019880] acpi device:03: registered as cooling_device2 > [ 1.021520] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3 > [ 1.021543] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) > [ 1.021855] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 > > This is with: > > 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 > Integrated Graphics Controller (rev 03) > 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 > Integrated Graphics Controller (rev 03) > Matt tells me that this (drop-dead box-killing!) bug is still present in current kernels. Could someone take a look please? The code seems very simple, and I couldn't spot a problem. Probably this means that I'm even simpler.

5 7

[Bug 29580] New: Pixmap corruption in gnome-shell when many icons are loaded
by bugzilla-daemon＠freedesktop.org 04 Oct '10

04 Oct '10

https://bugs.freedesktop.org/show_bug.cgi?id=29580 Summary: Pixmap corruption in gnome-shell when many icons are loaded Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: fred(a)crozat.net Created an attachment (id=37871) --> (https://bugs.freedesktop.org/attachment.cgi?id=37871) corrupted pixmaps hardware : 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device f362 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16 Memory at e8000000 (32-bit, prefetchable) [size=64M] I/O ports at c000 [size=256] Memory at ec020000 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at ec000000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon kernel : 2.6.34-12-desktop (openSUSE 11.3), using KMS radeon driver xorg driver : 6.13.1 Mesa 7.8.2 (openSUSE 11.3 package) when starting GNOME-Shell (2.29.1) with clutter 1.2.8 (or gnome-shell git, compiled against clutter 1.3 branch), if I open gnome-shell application menu, all pixmaps displayed in gnome-shell become corrupted, as well as application window shadows. Kernel sometimes states : radeon 0000:01:05.0: e3e1b280 reserve failed for wait -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 9

← Newer
1
...
11
12
13
14
15
16
17
...
37
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2010