dri-devel March 2015

dri-devel@lists.freedesktop.org

196 participants
1117 discussions

[Bug 80683] New: EDID valid check ignores errors in CEA blocks
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=80683 Priority: medium Bug ID: 80683 Assignee: dri-devel(a)lists.freedesktop.org Summary: EDID valid check ignores errors in CEA blocks Severity: normal Classification: Unclassified OS: All Reporter: stefan.bruens(a)rwth-aachen.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/other Product: DRI in linux/drivers/gpu/drm/drm_edid.c: bool drm_edid_block_valid(u8 *raw_edid, int block, bool print_bad_edid) { ... if (csum) { if (print_bad_edid) { DRM_ERROR("EDID checksum is invalid, remainder is %d\n", csum); } /* allow CEA to slide through, switches mangle this */ if (raw_edid[0] != 0x02) goto bad; } ... return true; --- i.e. CEA blocks are always reported as valid. This occurs frequently for me with a Radeon 7750 and a Dell U2713HM connected via DisplayPort, the I2C-over-AUX seems to be buggy and swallows single bytes. If I change the "return true;" to "return !csum;" bad transfers are retried. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 73624] New: AST2300 KMS EDID issue on C2750D4I
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=73624 Priority: medium Bug ID: 73624 Assignee: dri-devel(a)lists.freedesktop.org Summary: AST2300 KMS EDID issue on C2750D4I Severity: normal Classification: Unclassified OS: All Reporter: johannesobermayr(a)gmx.de Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/other Product: DRI Created attachment 92079 --> https://bugs.freedesktop.org/attachment.cgi?id=92079&action=edit EDID issue with KMS AST2300 doesn't fetch right EDID data ... [ 10.599714] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 73 [ 10.599718] Raw EDID: [ 10.599721] 00 ff ff ff ff ff ff 00 09 d1 0b 79 45 54 00 00 [ 10.599723] 29 12 01 03 0e 2f 1a 78 2e 35 85 a6 56 48 9a 24 [ 10.599725] 12 50 54 a5 6b ba 71 00 81 0d 00 00 00 00 00 00 [ 10.599727] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 10.599729] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 10.599731] 00 00 00 00 00 00 00 00 00 00 00 00 02 01 ff ff [ 10.599733] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.599734] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 89549] DisplayLink (udl) Linux kernel memory fault on USB hot unplug, proposed patch
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=89549 Bug ID: 89549 Summary: DisplayLink (udl) Linux kernel memory fault on USB hot unplug, proposed patch Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: adam_richter2004(a)yahoo.com Created attachment 114235 --> https://bugs.freedesktop.org/attachment.cgi?id=114235&action=edit Add ".get_vblank_counter = drm_vblank_count," to DisplayLink drm_driver functions [This is an edit of an email that I sent yesterday to linux-fbdev at vger.kernel.org and the Linux kernel udlfb maintainer.] In Linux-4.0-rc3, the DisplayLink driver gets a kernel memory fault when its USB device is unplugged, specifically when vblank_disable_and_save in linux-4.0-rc3/drivers/gpu/drm/drm_irq.c attempts to call the NULL function pointer dev->driver_get_vblank_counter. linux-4.0-rc3/Documentation/DocBook/drm.tmpl says of that field, "Otherwise drivers can use the drm_vblank_count helper function to handle this operation." Trying that seems to have eliminated the oops when I unplug the device, although I do see these lines in the console log at device driver initialization time that I think are probably fine, but which I should mention in case the indicate that I did the wrong the thing: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] No driver support for vblank timestamp query. If that doesn't look like a problem, then please apply the attached patch and push it upstream. The patch just adds one line that appears in six other framebuffer drivers to initialize the driver_get_vblank_counter drm_driver function. Thanks in advance for your attention to this problem. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 28841] New: Heavy text corruption in virtual consoles using DRI
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=28841 Summary: Heavy text corruption in virtual consoles using DRI Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: eblanca76(a)users.sourceforge.net I have a clean install of latest ubuntu lucid lynx, I added framebuffer support for g550 (matroxfb) and text in virtual consoles appears corrupted, it is made of random pixels appearing far away from the expected prompt. I can get back to clean text if I switch to xorg (ctrl+f7) then back to the virtual console, but if I type in new text, it appears ugly as usual. The only workaround for this is to disable DRI, then the text appears perfect and no switch is needed. Of course, this way the system cannot support any game. I attach my actual xorg.conf. My config: ubuntu 10.04 (Lucid) 2.6.32-22-generic i686 GNU/Linux with gnome 2.30.2 and xorg X server 1.7.6. -- 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 48215] New: [NV11] Display constantly switches on and off roughly every 10 seconds.
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=48215 Bug #: 48215 Summary: [NV11] Display constantly switches on and off roughly every 10 seconds. Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/other AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: alex.buell(a)munted.org.uk Display constantly switches on and off roughly every 10 seconds on my NV11 machine. This started happening with 3.2.0. Checking backwards, 3.1.0 works just fine. I am currently trying a bisect to find the problem. -- 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 52560] New: Xorg -configure creats useless xorg.conf for tdfx
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=52560 Bug #: 52560 Summary: Xorg -configure creats useless xorg.conf for tdfx Classification: Unclassified Product: DRI Version: XOrg CVS Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: tuxracer(a)hispeed.ch Had want to install my old Voodoo3/2000 PCI that 2 or 3 years ago perfectly work. Now on actual xorg-server at least 1.10 1.11 1.12 I really unable to configure a working 3D. If i use the driver without any xorg.conf I can use at least Software-Rendering. But if i create a xorg.conf using Xorg -configure it gives no 3D. On old xorg-servers the only thing i had to do for 3D on this card was to set the resolution to 1024x768 at 16bit colordepth and it worked. -- 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 38364] New: Ignoring invalid EDID block 1 do entire edid is invalid and not just block 1
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=38364 Summary: Ignoring invalid EDID block 1 do entire edid is invalid and not just block 1 Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: zaverel(a)free.fr Hello , All is fine except i can't change resolution on my second monitor vga ,tv in fact, (reported as DVI-I-2 ) anymore with my 9400gt. Now , i'm on : linux-2.6.39-gentoo-r1 xorg-server-1.10.2 xf86-video-nouveau-0.0.16_pre20110323 libdrm-2.4.25 Errors in dmesg are: nouveau 0000:02:00.0: DVI-I-2: Ignoring invalid EDID block 1. [drm:drm_edid_block_valid] *ERROR* Raw EDID: <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ whatever i valid with xrandr is not really do on my tv although xrandr say it's good , my tv always report 1202x670 50hz I tried with and without xorg.conf My last kernel working is linux-2.6.36-gentoo-r6. If, i tweak drm_edid.c from kernel-2.6.39-gentoo-r1 like this: --- drm_edid.c 2011-06-10 22:37:36.605848000 +0200 +++ linux/drivers/gpu/drm/drm_edid.c 2011-06-13 13:04:43.136786102 +0200 @@ -292,7 +292,7 @@ block + (valid_extensions + 1) * EDID_LENGTH, j, EDID_LENGTH)) goto out; - if (drm_edid_block_valid(block + (valid_extensions + 1) * EDID_LENGTH)) { + if (drm_edid_block_valid(block + (valid_extensions + 0) * EDID_LENGTH)) { valid_extensions++; break; } that work good like before but i'm not sure that is safe. More info in http://lists.freedesktop.org/archives/nouveau/2011-June/008548.html I can post logs here too , just tell me. See you -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 88886] GPU fault detected on luxmark luxball HDR test with AMD Tahiti
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=88886 Bug ID: 88886 Summary: GPU fault detected on luxmark luxball HDR test with AMD Tahiti Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: commiethebeastie(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Luxmark 3.1b1 Luxball HDR test. agd5f drm-next-3.20-wip kernel System doesn`t respond to sysrq "B" key. Latest mesa-git with llvm-3.7svn build. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 88461] The computer sometimes freezes after waking up when playing vdpau accelerated video
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=88461 Bug ID: 88461 Summary: The computer sometimes freezes after waking up when playing vdpau accelerated video Product: Mesa Version: 10.4 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: maaniv(a)gmail.com Created attachment 112293 --> https://bugs.freedesktop.org/attachment.cgi?id=112293&action=edit dmesg log I use smplayer (mplayer gui frontend) to watching video. Linux 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64 GNU/Linux Radeon 7850 2GB -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=87278 Bug ID: 87278 Summary: Packet0 not allowed and GPU fault detected errors with Serious Engine games Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: daniel(a)constexpr.org Created attachment 110808 --> https://bugs.freedesktop.org/attachment.cgi?id=110808&action=edit dmesg output with the GPU fault errors filtered out Running Serious Sam 3 or The Talos Principle spams dmesg with thousands of these errors: [ 6001.212237] radeon 0000:01:00.0: GPU fault detected: 147 0x02528801 [ 6001.212243] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0FF02192 [ 6001.212246] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x12088001 [ 6001.212249] VM fault (0x01, vmid 9) at page 267395474, read from TC (136) There are also a few "Packet0 not allowed" errors (followed by a hex dump): [15446.473341] radeon 0000:01:00.0: Packet0 not allowed! So far it's only these errors in dmesg - I haven't observed any actual rendering issues, crashes, GPU lockups because of this. I have only attached a filtered kernel log with the GPU fault errors removed - the full log is available at http://constexpr.org/tmp/serious-dmesg.log (140 MiB). Both of these games use the Serious Engine 3.5 (Serious Sam 3) or 4 (The Talos Principle). This is also reproducible with The Talos Principle Public Test which as of now is still available as a free download on Steam. Kernel: 3.18.0-gentoo GPU: Radeon HD 7950 Driver: radeonsi, Mesa 10.5.0-devel (git-ff96537) This might be related to bug 84500 - however those spurious Packet0 have been gone for a while now with updated Mesa - now I got them again but only while running Serious Engine games. -- You are receiving this mail because: You are the assignee for the bug.

1 33

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2015