dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 36393] New: r200: font corruption in fog test
by bugzilla-daemon＠freedesktop.org 25 Feb '14

25 Feb '14

https://bugs.freedesktop.org/show_bug.cgi?id=36393 Summary: r200: font corruption in fog test Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r200 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: nikai(a)nikai.net Created an attachment (id=45812) --> (https://bugs.freedesktop.org/attachment.cgi?id=45812) fog test in mesa-7.9.2 In src/tests/fog the text appears distorted, looking somewhat similar to bug 34280. But in contrast, this problem is also present in mesa-7.9.2. System environment: -- system architecture: i686 -- Linux distribution: Gentoo -- GPU: R200 514D -- Model: ATI Radeon 9100 QM (AGP) -- Display connector: VGA -- xf86-video-ati: 982c22f16c8eeee9be81779fbfe17d8d3f9b6897 -- xserver: 1.9.4 -- mesa: 9dacbe222641443af000a82161922a5ade206340 and -- mesa: 7.9.2 -- drm: 2.4.25 -- kernel: 2.6.38.2 -- 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

[Bug 58904] New: gloss demo broken when right clicked
by bugzilla-daemon＠freedesktop.org 25 Feb '14

25 Feb '14

https://bugs.freedesktop.org/show_bug.cgi?id=58904 Priority: medium Bug ID: 58904 Assignee: dri-devel(a)lists.freedesktop.org Summary: gloss demo broken when right clicked Severity: normal Classification: Unclassified OS: Linux (All) Reporter: smoki00790(a)gmail.com Hardware: x86 (IA32) Status: NEW Version: git Component: Drivers/DRI/r200 Product: Mesa Created attachment 72339 --> https://bugs.freedesktop.org/attachment.cgi?id=72339&action=edit gloss broken picture gloss demo from mesa demos When being right clicked then lose texture. Picture is in attachement. Started with 99109e9fe08f13c40ffc55e305a69e51740fc6c4 , also there with current git master. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 58121] New: Radeon SUMO: LVDS panel blanks when enabling external monitor
by bugzilla-daemon＠bugzilla.kernel.org 25 Feb '14

25 Feb '14

https://bugzilla.kernel.org/show_bug.cgi?id=58121 Summary: Radeon SUMO: LVDS panel blanks when enabling external monitor Product: Drivers Version: 2.5 Kernel Version: 3.9 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: niels_ole(a)salscheider-online.de Regression: No Created an attachment (id=101411) --> (https://bugzilla.kernel.org/attachment.cgi?id=101411) dmesg with drm.debug=4 When I enable both my LVDS panel and an external monitor (e.g. DP or VGA), my LVDS panel blanks. This is on a radeon SUMO GPU (AMD A6-3410MX APU). I have attached the dmesg output with drm.debug=4 and my Xorg.0.log. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 9

[Bug 64443] New: [r600g] Oil Rush (Steam version) crashes
by bugzilla-daemon＠freedesktop.org 23 Feb '14

23 Feb '14

https://bugs.freedesktop.org/show_bug.cgi?id=64443 Priority: medium Bug ID: 64443 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] Oil Rush (Steam version) crashes Severity: major Classification: Unclassified OS: All Reporter: romulasry(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Steam_SetMinidumpSteamID: Caching Steam ID: 76561197977568184 [API loaded no] X Error of failed request: GLXBadFBConfig Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 34 () Serial number of failed request: 51 Current serial number in output stream: 80 -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 43248] New: Starting teeworlds results in black screen
by bugzilla-daemon＠freedesktop.org 18 Feb '14

18 Feb '14

https://bugs.freedesktop.org/show_bug.cgi?id=43248 Bug #: 43248 Summary: Starting teeworlds results in black screen Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sandy.8925(a)gmail.com Created attachment 53856 --> https://bugs.freedesktop.org/attachment.cgi?id=53856 dmesg output Hardware: Asus K53TA laptop. AMD A6-3400M with integrated Radeon HD6520G and discrete Radeon HD6650M. Display is through 6520G. Software: Ubuntu 11.04 64 bit with kernel 3.2-rc1 and xorg-edgers ppa. When I start teeworlds, the screen goes blank (the display seems to be switched off). However I am able to switch to command line using Ctrl + Alt + F1 and running: sudo service gdm start and sudo service gdm stop restarts Gnome for me. dmesg shows some errors with atombios. -- 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: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."
by Jonathan Nieder 17 Feb '14

17 Feb '14

Hi dri developers, Two corrupt-EDID/dmesg-spam puzzles for you. Seems to be a regression, though I'm not sure from when. Stuart Pook writes[1]: > Every 10 seconds I get the messages at the end of my bug report in > /var/log/kern.log. My /var/log/kern.log is very big! [...] > I have a Benq Product Name FP241W manufactured February 2007 Revision > B4-125 and used to use the DVI input. The EDID data in the DVI input > suddenly failed and the my PC would not longer boot. I plugged my PC > into the HDMI input of the monitor and the machine boots but X does not > start at the correct resolution. It appears that the EDID data from HMDI > input does not propose "1920x1200". [...] > So once X is running > I unplug my PC from the HDMI input and plug it into the DVI input. All > works well, the screen saver makes the screen go into standby mode, > except that the kernel tells me that the EDID data is not correct every > 10 seconds. Is there a way to make it stop? [...] > [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 34 > [drm:drm_edid_block_valid] *ERROR* Raw EDID: > <3>a1 80 ff ff ff ff ff 00 09 d1 db 76 be 0f 00 00 ...........v.... > <3>07 11 01 03 80 34 21 78 ea 5a d5 a7 56 4b 9b 24 .....4!x.Z..VK.$ > <3>13 50 54 bd ef 80 71 4f 81 90 81 80 81 8c a9 40 .PT...qO.......@ > <3>b3 00 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 ......(<..p.#@0 > <3>36 00 07 44 21 00 00 1e d5 09 80 a0 20 5e 63 10 6..D!....... ^c. > <3>10 60 52 08 78 2d 11 00 00 1a 00 00 00 fd 00 38 .`R.x-.........8 > <3>4c 1e 53 11 00 0a 20 20 20 20 20 20 00 00 00 fc L.S... .... > <3>00 42 65 6e 51 20 32 34 31 57 0a 20 20 20 00 dc .BenQ 241W. .. Lisandro Damián Nicanor Pérez Meyer writes[1]: > With a dual screen setup. Not so long ago (less than a week) both monitors > (ViewSonic VG2021wm) were working fine. Somehow the monitor connected to the > DVI port started not being detected correctly on boot (wrong edid?). Dmesg > shows: > > [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 54 > [drm:drm_edid_block_valid] *ERROR* Raw EDID: > <3>00 ff ff ff ff ff ff 00 5a 63 1e d9 01 01 01 01 ........Zc...... > <3>18 11 01 03 0e 2b 1b 78 2e cf c5 a3 5a 49 a0 25 .....+.x....ZI.% > <3>12 50 54 bf ef 80 81 80 81 40 71 4f 01 01 01 01 .PT......@qO.... > <3>01 01 01 01 01 01 21 39 90 30 62 1a 27 40 68 b0 ......!9.0b.'@h. > <3>36 00 b1 0e 11 00 00 1c 36 00 00 ff 00 51 44 57 6.......6....QDW > <3>30 37 32 34 36 30 38 36 37 0a 00 00 00 fd 00 32 072460867......2 > <3>4b 1e 52 11 00 0a 20 20 20 20 20 20 00 00 00 fc K.R... .... > <3>00 56 47 32 30 32 31 77 6d 2d 32 0a 20 20 00 64 .VG2021wm-2. .d > > And so I can't go more than 1024x768 on a 1680x1050 capable LCD. As this was > working some days ago, there must have been a regression somewhere :-/ [...] > On Vie 29 Abr 2011 22:08:09 Jonathan Nieder escribió: >> Thanks. Could you try the patch from >> >> https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7 >> >> and see what happens when booting with the drm.edid_strict=0 option? > > The patch works perfectly, so at least I have a workaround :-) Thank you! > > Now the question is why the DVI port gets a corrupt EDID while the VGA port > gets it right. Or maybe the code processing the EDID of the DVI port is wrong? > > Don't heasitate in contacting me if I can be of any further help. Known problem? Ideas? Jonathan [1] There are many more details in the original reports, at http://bugs.debian.org/622993 https://bugs.freedesktop.org/show_bug.cgi?id=31943 looks vaguely similar.

5 13

[Bug 66331] New: WebGL water demo crashes LLVM
by bugzilla-daemon＠freedesktop.org 05 Feb '14

05 Feb '14

https://bugs.freedesktop.org/show_bug.cgi?id=66331 Priority: medium Bug ID: 66331 Assignee: dri-devel(a)lists.freedesktop.org Summary: WebGL water demo crashes LLVM Severity: normal Classification: Unclassified OS: Linux (All) Reporter: greg(a)chown.ath.cx Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 81647 --> https://bugs.freedesktop.org/attachment.cgi?id=81647&action=edit Dump with R600_DEBUG=ps,vs,fs The WebGL demo http://madebyevan.com/webgl-water/ crashes r600g with LLVM enabled: firefox: /home/greg/build/llvm-3.3.src/include/llvm/CodeGen/MachineInstr.h:272: llvm::MachineOperand& llvm::MachineInstr::getOperand(unsigned int): Assertion `i < getNumOperands() && "getOperand() out of range!"' failed. Stack dump: 0. Running pass 'Function Pass Manager' on module 'tgsi'. 1. Running pass 'R600 Emit Clause Markers Pass' on function '@main' Aborted (core dumped) This happens both with LLVM 3.3 and latest code from SVN. I tried to dump a detailed log, but it actually crashes in a different place when dumping the shaders - might be related though. Log is attached. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 56534] New: All anti-aliasing methods buggy at cayman
by bugzilla-daemon＠freedesktop.org 04 Feb '14

04 Feb '14

https://bugs.freedesktop.org/show_bug.cgi?id=56534 Priority: medium Bug ID: 56534 Assignee: dri-devel(a)lists.freedesktop.org Summary: All anti-aliasing methods buggy at cayman Severity: normal Classification: Unclassified OS: Linux (All) Reporter: v10lator(a)myway.de Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 69244 --> https://bugs.freedesktop.org/attachment.cgi?id=69244&action=edit A in-game screenshot without any anti-aliasing method active. MSAA looks just ugly (not like anti-aliasing should look like) and Oil Rush spams "OpenGL error: invalid operation", MLAA doesn't seem to do anything and FXAA just gives a white screen. All anti-aliasing methods where tested with Oil Rush. Exact settings: MSAA: 8x, setted from the game launcher. FXAA: Setted from the game launcher. MLAA: 32x (for both, 2D and 3D) forced by drirc. -- You are receiving this mail because: You are the assignee for the bug.

1 29

[Bug 58354] New: r600g locks up in Unigine Tropics with drm-next
by bugzilla-daemon＠freedesktop.org 26 Jan '14

26 Jan '14

https://bugs.freedesktop.org/show_bug.cgi?id=58354 Priority: medium Bug ID: 58354 Assignee: dri-devel(a)lists.freedesktop.org Summary: r600g locks up in Unigine Tropics with drm-next Severity: critical Classification: Unclassified OS: All Reporter: alexandre.f.demers(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Testing with drm-next with latest mesa, ddx and drm, Unigine Tropics locks up when launching the demo. The problem appears somewhere between a636a9829175987e74ddd28a2e87ed17ff7adfdc (locks) and 1a1494def7eacbd25db05185aa2e81ef90892460 (OK). I'll pinpoint it tomorrow. -- You are receiving this mail because: You are the assignee for the bug.

1 30

[Bug 58667] New: Random crashes on CAYMAN
by bugzilla-daemon＠freedesktop.org 26 Jan '14

26 Jan '14

https://bugs.freedesktop.org/show_bug.cgi?id=58667 Priority: medium Bug ID: 58667 Assignee: dri-devel(a)lists.freedesktop.org Summary: Random crashes on CAYMAN Severity: normal Classification: Unclassified OS: All Reporter: v10lator(a)myway.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI This is with newest mesa from git with kernel 3.8-rc1 (+ this patch: http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.8&id=668bbc8… ) The screen first freezes (mouse still movable, keyboard not responding, not even to MagSysRQ), then the monitor goes off (standby) and back on with only garbage on the screen. Not sure if this has anything to do with it (but it should get fixed anyway) but dmesg gets spammed with this: [ 533.928472] radeon 0000:03:00.0: GPU fault detected: 146 0x00335514 [ 533.928477] radeon 0000:03:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ 533.928483] radeon 0000:03:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 where the address isn't always the same, example: [ 533.928374] radeon 0000:03:00.0: GPU fault detected: 146 0x0033ed14 [ 533.928379] radeon 0000:03:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ 533.928385] radeon 0000:03:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 -- You are receiving this mail because: You are the assignee for the bug.

1 51

← Newer
1
...
36
37
38
39
40
41
42
...
73
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2013