dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 93866] Tonga: Weston-drm direct scan out corruption
by bugzilla-daemon＠freedesktop.org 02 Nov '17

02 Nov '17

https://bugs.freedesktop.org/show_bug.cgi?id=93866 Bug ID: 93866 Summary: Tonga: Weston-drm direct scan out corruption Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: adf.lists(a)gmail.com Created attachment 121287 --> https://bugs.freedesktop.org/attachment.cgi?id=121287&action=edit external picture showing corruption Testing both release and git wayland/weston on R9285. Using weston-launch from fbcon so it uses weston-drm. Apart from https://bugs.freedesktop.org/show_bug.cgi?id=93740 which can be worked around, rendering is good when compositing. If I run something that allows weston to enable direct scanout there is slight corruption. kodi and mpv are the only ways I know to do this. If I do something that changes back yo compositing the corruption goes, taking a screen shot/recording or zooming in will all "fix" the corruption. I am inferring direct scan out is happening as I can't change transparency + the man page for weston-drm says it will be used where possible. Tried going back in time with mesa to see if it ever worked, but I started hitting places where either weston wouldn't start or I always got compositing so no corruption but I could change transparency. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 91666] build fail with cunit - OK on amd64 - KO for i386
by bugzilla-daemon＠freedesktop.org 01 Nov '17

01 Nov '17

https://bugs.freedesktop.org/show_bug.cgi?id=91666 Bug ID: 91666 Summary: build fail with cunit - OK on amd64 - KO for i386 Product: DRI Version: DRI git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: libdrm Assignee: dri-devel(a)lists.freedesktop.org Reporter: fabio.ped(a)libero.it amd64 builds OK: Full build log: https://launchpadlibrarian.net/214693325/buildlog_ubuntu-vivid-amd64.libdrm… Same source package breaks with i386: In file included from ../../../amdgpu/amdgpu_internal.h:35:0, from ../../../tests/amdgpu/cs_tests.c:32: ../../../libdrm_macros.h: In function 'drm_munmap': ../../../libdrm_macros.h:79:4: error: size of unnamed array is negative STATIC_ASSERT(LARGE_OFF_T % 2147483629 == 721 && ^ Full i386 build log: https://launchpadlibrarian.net/214693090/buildlog_ubuntu-vivid-i386.libdrm_… -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 92836] amdgpu does not resume properly from suspend
by bugzilla-daemon＠freedesktop.org 20 Oct '17

20 Oct '17

https://bugs.freedesktop.org/show_bug.cgi?id=92836 Bug ID: 92836 Summary: amdgpu does not resume properly from suspend Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: David(a)WalkerStreet.info My laptop does not resume properly after a suspend. The problem seems to be with the amdgpu kernel module; it's often accompanied by a long stream of dmesg errors reported. Here's a sampling: [ 1494.980561] amdgpu 0000:00:01.0: GPU fault detected: 146 0x0b020504 [ 1494.980561] amdgpu 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ 1494.980561] amdgpu 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [ 1494.980561] VM fault (0x00, vmid 0) at page 0, read from '' (0x00000000) (0) [ 1494.995478] systemd-journald[498]: /dev/kmsg buffer overrun, some messages lost. [ 1494.980561] amdgpu 0000:00:01.0: GPU fault detected: 146 0x0b0a4004 [ 1494.980561] amdgpu 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ 1494.980561] amdgpu 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [ 1494.980561] VM fault (0x00, vmid 0) at page 0, read from '' (0x00000000) (0) [ 1494.995486] systemd-journald[498]: /dev/kmsg buffer overrun, some messages lost. Any ideas? I'm running the 4.2.4-1-default under openSUSE Tumbleweed. Here's some hwinfo data: 09: PCI 01.0: 0300 VGA compatible controller (VGA) [Created at pci.366] Unique ID: vSkL.bMI5Iw7ysWD SysFS ID: /devices/pci0000:00/0000:00:01.0 SysFS BusID: 0000:00:01.0 Hardware Class: graphics card Model: "ATI Carrizo" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x9874 "Carrizo" SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x80af Revision: 0xc5 Driver: "amdgpu" Driver Modules: "drm" Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable) Memory Range: 0xf0000000-0xf07fffff (ro,non-prefetchable) I/O Ports: 0xf000-0xf0ff (rw) Memory Range: 0xff700000-0xff73ffff (rw,non-prefetchable) Memory Range: 0xff740000-0xff75ffff (ro,non-prefetchable,disabled) IRQ: 47 (129945 events) Module Alias: "pci:v00001002d00009874sv0000103Csd000080AFbc03sc00i00" Driver Info #0: Driver Status: amdgpu is active Driver Activation Cmd: "modprobe amdgpu" Config Status: cfg=new, avail=yes, need=no, active=unknown -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 60857] New: Unstable display with Radeon 760G (ASUS M4A78L-M LE)
by bugzilla-daemon＠bugzilla.kernel.org 17 Oct '17

17 Oct '17

https://bugzilla.kernel.org/show_bug.cgi?id=60857 Bug ID: 60857 Summary: Unstable display with Radeon 760G (ASUS M4A78L-M LE) Product: Drivers Version: 2.5 Kernel Version: 3.11 Hardware: i386 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: smf.linux(a)ntlworld.com Regression: No Created attachment 107428 --> https://bugzilla.kernel.org/attachment.cgi?id=107428&action=edit Screen image, dmesg ,lspci and kernel config I have just upgraded this machine from kernel 3.8.13 to 3.11 and I have discovered that the VGA output has become unstable (see attached). The dmesg output shows a number of issues/warnings which may be associated with the problem but that may just be speculation on my part. Please advise. -- You are receiving this mail because: You are watching the assignee of the bug.

1 18

[Bug 37696] New: [RADEON:KMS:PLL] frequent colored lines appear on screen
by bugzilla-daemon＠freedesktop.org 17 Oct '17

17 Oct '17

https://bugs.freedesktop.org/show_bug.cgi?id=37696 Summary: [RADEON:KMS:PLL] frequent colored lines appear on screen Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: roysjosh(a)gmail.com Hello, I'm back again! This bug is about the same hardware as in https://bugs.freedesktop.org/show_bug.cgi?id=19960 . ASUS monitor VH226H, ASUS motherboard M3A78-E, HD3200 (rs780). 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 3200 Graphics [1002:9610] (prog-if 00 [VGA controller]) I just upgraded from f14 to f15 (2.6.38.6-27.fc15.x86_64) and some frequently occurring but not frequent in number colored lines have appeared on my screen... they don't necessarily go all the way across the screen either. I grabbed the "good" registers from bug 19960 and diff'd them to the current regs: [...] 258c258 < 00000404 00000002 (2) --- > 00000404 00000003 (3) 269c269 < 00000430 00910032 (9502770) --- > 00000430 00da0030 (14286896) 275c275 < 00000448 159ec704 (362727172) --- > 00000448 1593a704 (361998084) 278c278 < 00000454 6c012003 (1812013059) --- > 00000454 6c010003 (1812004867) [...] Settings these regs gets rid of the red/white/blue/etc lines: # ./avivotool regset 0x404 0x2 ; ./avivotool regset 0x430 0x910032 OLD: 0x404 (0404) 0x00000003 (3) NEW: 0x404 (0404) 0x00000002 (2) OLD: 0x430 (0430) 0x00da0030 (14286896) NEW: 0x430 (0430) 0x00910032 (9502770) And 0x43c was already set to 7: # ./avivotool regmatch 0x43c 0x43c 0x00000007 (7) Thanks! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 79011] New: GPU lockup, screen freeze with Radeon HD7770
by bugzilla-daemon＠bugzilla.kernel.org 16 Oct '17

16 Oct '17

https://bugzilla.kernel.org/show_bug.cgi?id=79011 Bug ID: 79011 Summary: GPU lockup, screen freeze with Radeon HD7770 Product: Drivers Version: 2.5 Kernel Version: 3.15 / 3.14 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: fabianp(a)fusionzone.nl Regression: No Hi, I am running 64 bit Arch Linux on kernel 3.15, the bug also occured with 3.14, with Intel i5 processor and a AMD Radeon HD7770 graphics card. After a while (randomly), both monitors go to sleep. Sometimes, they wake up after 10-20 seconds and I can continue using the computer, but more often they won't and it requires a hard reboot. When this happens the sound continues playing. Also, rarely the computer freezes, the monitors stay active and all I can move is my mouse, also requiring a hard boot. -- You are receiving this mail because: You are watching the assignee of the bug.

1 17

[Bug 93548] Grid Autosport causes a hard system crash
by bugzilla-daemon＠freedesktop.org 10 Oct '17

10 Oct '17

https://bugs.freedesktop.org/show_bug.cgi?id=93548 Bug ID: 93548 Summary: Grid Autosport causes a hard system crash Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sobkas(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120748 --> https://bugs.freedesktop.org/attachment.cgi?id=120748&action=edit Kernel output, System: kernel - 4.4-rc6 mesa - git radeon 6770 Reproduce: run qualifications and finish them, system locks up Tried kgdb, was rather unhelpful, either everything just froze or oopsed in irq handling code(generally in different places). I think that there might be some memory corruption trace[500MB,xz]: https://drive.google.com/open?id=0B3J0Mg89izcbUzBob1NYNUVlTTg -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 93301] ns2_linux32: radeon VM fault / VM_CONTEXT1_PROTECTION_FAULT_ADDR
by bugzilla-daemon＠freedesktop.org 09 Oct '17

09 Oct '17

https://bugs.freedesktop.org/show_bug.cgi?id=93301 Bug ID: 93301 Summary: ns2_linux32: radeon VM fault / VM_CONTEXT1_PROTECTION_FAULT_ADDR 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: dev(a)illwieckz.net QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120427 --> https://bugs.freedesktop.org/attachment.cgi?id=120427&action=edit syslog (Linux 4.3, mesa git, radeon hawaii r9 390X) Hi I (re) tried Natural Selection 2 yesterday, and I it crashed (as expected), and this time the syslog said: ``` Dec 8 07:20:25 gollum kernel: [16588.241364] radeon 0000:01:00.0: GPU fault detected: 146 0x0e65e014 Dec 8 07:20:25 gollum kernel: [16588.241368] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00007673 Dec 8 07:20:25 gollum kernel: [16588.241369] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x050E0014 Dec 8 07:20:25 gollum kernel: [16588.241370] VM fault (0x04, vmid 2) at page 30323, write from 'CB1' (0x43423100) (224) ---8<--- 120 000+ lines --------------------- Dec 8 07:22:58 gollum kernel: [16741.758495] radeon 0000:01:00.0: GPU fault detected: 146 0x06a59014 Dec 8 07:22:58 gollum kernel: [16741.758506] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00007673 Dec 8 07:22:58 gollum kernel: [16741.758512] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x05150014 Dec 8 07:22:58 gollum kernel: [16741.758518] VM fault (0x04, vmid 2) at page 30323, write from 'CB6' (0x43423600) (336) Dec 8 07:23:03 gollum kernel: [16746.694729] ns2_linux32[16192]: segfault at 1 ip 00000000f3bf8d12 sp 00000000f0b9adf8 error 4 in libc-2.21.so[f3acc000+1b4000] ``` Well, I'm not expecting to see this game working one day, I own this game since 2013-12-15 (it's almost two years) and it never worked, so these guys proved their product is a joke and I don't expect nothing from them. But perhaps this bug can help you to track things on your side, that's why I report it. When the error happened, NS2 was loading assets since 20min to load a tutorial map. I don't have more logs currently but if you have some ideas of things I can record, I can try to reproduce it. I agree the current log is a bit quiet. I've already seen radeon errors like that before in a dpm issue (see #93288 ) but the current bug is unrelated to dpm (dpm was inactive in the current case). I use a Radeon R9 390X with Mesa git on Linux 4.3 here. -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 29725] New: EXT_framebuffer_object extension with free radeon driver
by bugzilla-daemon＠freedesktop.org 08 Oct '17

08 Oct '17

https://bugs.freedesktop.org/show_bug.cgi?id=29725 Summary: EXT_framebuffer_object extension with free radeon driver Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: bioinfornatics(a)gmail.com hi, i am fedora packager and i package this game: http://os.wildfiregames.com/ i see for radeon driver a crash because with EXT_framebuffer_object extension with free radeon driver. beta rpm can be found here: http://koji.fedoraproject.org/koji/taskinfo?taskID=2415654 rpm -qa | grep mesa mesa-dri-drivers-7.8.1-8.fc13.x86_64 mesa-libGL-devel-7.8.1-8.fc13.x86_64 mesa-libGL-7.8.1-8.fc13.x86_64 mesa-debuginfo-7.8.1-8.fc13.x86_64 mesa-libGLU-devel-7.8.1-8.fc13.x86_64 mesa-libGLU-7.8.1-8.fc13.x86_64 -- 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

[Bug 44995] New: Missing support for MGA G200eW WPCM450 [102b:0532]
by bugzilla-daemon＠freedesktop.org 22 Sep '17

22 Sep '17

https://bugs.freedesktop.org/show_bug.cgi?id=44995 Bug #: 44995 Summary: Missing support for MGA G200eW WPCM450 [102b:0532] Classification: Unclassified Product: Mesa Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/MGA AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: lenlen1982(a)gmail.com Please add support for MGA G200eW WPCM450 pci id 102b:0532 06:03.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA G200eW WPCM450 [102b:0532] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell PowerEdge R610 MGA G200eW WPCM450 [1028:0236] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32 (4000ns min, 8000ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at d5800000 (32-bit, prefetchable) [size=8M] Region 1: Memory at de7fc000 (32-bit, non-prefetchable) [size=16K] Region 2: Memory at de800000 (32-bit, non-prefetchable) [size=8M] [virtual] Expansion ROM at de000000 [disabled] [size=64K] Capabilities: <access denied> If you need more info please ask me. I'll feel in this ticket. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016