dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 80628] New: The way KMS works doesn't support HDMI/DP well
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=80628 Priority: medium Bug ID: 80628 Assignee: dri-devel(a)lists.freedesktop.org Summary: The way KMS works doesn't support HDMI/DP well Severity: enhancement Classification: Unclassified OS: Linux (All) Reporter: tom.ty89(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/other Product: DRI If the machine has no monitor attached at all before boot, KMS couldn't probe the monitor and make it goes into native resolution afterwards. This issue is not very obvious when DVI/VGA are the only connectors available because of their mechanism. When it comes to HDMI/DP, the monitor is considered disconnected when it's powered off. Then the issue become annoying, while we have to make sure that one monitor is connected and switched on before boot. Moreover, display managers have to be started manually under such situation after you turn on your monitor. Not even all DM can start X in optimal resolution without some "xrandr hack" By the way, it's funny that if you got one attached, you can power on others later without getting into the problem. Just that I am not sure if it's because all my monitors have the same optimal resolution. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 78541] New: QXL DRM Driver Freezes QEMU KVM Guest when Switching to Text Console
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=78541 Priority: medium Bug ID: 78541 Assignee: dri-devel(a)lists.freedesktop.org Summary: QXL DRM Driver Freezes QEMU KVM Guest when Switching to Text Console Severity: major Classification: Unclassified OS: Linux (All) Reporter: reimth(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/other Product: DRI Host: - Debian Linux with kernel 3.11-2-amd64 - QEMU emulator version 1.7.0 (Debian 1.7.0+dfsg-2) - Spice server 0.12.4 - libvirt Virtual Machine Manager 0.9.5 Guest: - Ubuntu Saucy with kernel 3.11.0-20-generic Reproduce: - Start qemu with option -global qxl-vga.revision=4, which allows drm to load the qxl driver Other parameters related to graphics: + -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 + -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on + -chardev spicevmc,id=charchannel0,name=vdagent + -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 - Check with dmesg, that QXL DRM has been correctly initialised - Send Ctrl-Alt-Fn (n = 1, 2, ...) to VM guest Bug: Virtual machine manager will switch to console but freezes with strange display. Guest cannot be contacted any more. Switching back to vc is not possible. ssh connections will hang. No netconsole output. The guest must be restarted using forced shutdown. The problem occurs also for qemu 2.0. It does not occur, if only userspace driver is used (omit option -global qxl-vga.revision=4). In this case lspci reports: 00:02.0 VGA compatible controller: Red Hat, Inc. Device 0100 (rev 03) and dmesg reports: [drm] Initialized drm 1.1.0 20060810 [drm:qxl_pci_probe] *ERROR* qxl too old, doesn't support client_monitors_config, use xf86-video. I can provide further information, but need some guidance, what you prefer in order to locate the root cause of the problem. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 99352] DRM/IMX first primary plane with pixel format DRM_FORMAT_YUV420 the screen is discolored
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=99352 Bug ID: 99352 Summary: DRM/IMX first primary plane with pixel format DRM_FORMAT_YUV420 the screen is discolored Product: DRI Version: DRI git Hardware: ARM OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: zillevdr(a)gmx.de Created attachment 128874 --> https://bugs.freedesktop.org/attachment.cgi?id=128874&action=edit screen picture the fb on the first primary plane with pixel format DRM_FORMAT_YUV420 is the screen fail colored. It could be that YUV will misinterpreted as RGB. If I copy only y data to fb the screen is red with a shadow from the picture. Only u-plane the screen is green and same with v-plane is blue. A picture from the screen are attached. Tested with kernel 4.10-rc3 and 4.9. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 53544] New: Incorrect modeline due to incorrect EDID block for LG SL80 TV
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=53544 Bug #: 53544 Summary: Incorrect modeline due to incorrect EDID block for LG SL80 TV Classification: Unclassified Product: DRI Version: DRI CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: paulepanter(a)users.sourceforge.net The LG SL80 TV exhibits the same garbled screen as reported in #26294 [1] when connecting an ASUS Eee PC 701 4G over VGA. This is just a separate report for this particular TV and a patch is going to be send to the list. Log files are included in comment 26294#c20 and comment 26294#c21 of the referenced report. [1] https://bugs.freedesktop.org/show_bug.cgi?id=26294 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 15

[Bug 101037] nouveau: crash when starting chrome
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=101037 Bug ID: 101037 Summary: nouveau: crash when starting chrome 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: hramrach(a)gmail.com 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98 [Quadro NVS 295] [10de:06fd] (rev a1) Linux 4.10.0-trunk-amd64 #1 SMP Debian 4.10.7-1~exp1 (2017-03-30) x86_64 libdrm-nouveau2 2.4.80-1 libgl1-mesa-dri 17.0.4-1 xserver-xorg-video-nouveau 1:1.0.15-1 May 14 09:34:36 iscsi kernel: [ 482.205629] BUG: unable to handle kernel NULL pointer dereference at 0000000000000021 May 14 09:34:36 iscsi kernel: [ 482.205629] BUG: unable to handle kernel NULL pointer dereference at 0000000000000021 May 14 09:34:36 iscsi kernel: [ 482.205654] IP: dma_fence_wait_timeout+0x30/0xf0 May 14 09:34:36 iscsi kernel: [ 482.205654] IP: dma_fence_wait_timeout+0x30/0xf0 May 14 09:34:36 iscsi kernel: [ 482.205659] PGD 0 May 14 09:34:36 iscsi kernel: [ 482.205659] PGD 0 May 14 09:34:36 iscsi kernel: [ 482.205766] CPU: 1 PID: 1696 Comm: InputThread Tainted: G OE 4.10.0-trunk-amd64 #1 Debian 4.10.7-1~exp1 May 14 09:34:36 iscsi kernel: [ 482.205772] Hardware name: /DQ45CB, BIOS CBQ4510H.86A.0133.2011.0810.1010 08/10/2011 May 14 09:34:36 iscsi kernel: [ 482.205777] task: ffff8a4d2c13afc0 task.stack: ffffb8c2416e0000 May 14 09:34:36 iscsi kernel: [ 482.205781] RIP: 0010:dma_fence_wait_timeout+0x30/0xf0 May 14 09:34:36 iscsi kernel: [ 482.205785] RSP: 0018:ffffb8c2416e3aa0 EFLAGS: 00010206 May 14 09:34:36 iscsi kernel: [ 482.205789] RAX: 0000000000000001 RBX: ffff8a4c9a817480 RCX: ffffffffc07cffa0 May 14 09:34:36 iscsi kernel: [ 482.205794] RDX: 7fffffffffffffff RSI: 0000000000000001 RDI: ffff8a4d2c27c600 May 14 09:34:36 iscsi kernel: [ 482.205798] RBP: ffff8a4d2c27c600 R08: ffff8a4d2c3e9000 R09: 0000000000000000 May 14 09:34:36 iscsi kernel: [ 482.205802] R10: ffff8a4d302763a8 R11: ffff8a4d314bb600 R12: 0000000000000001 May 14 09:34:36 iscsi kernel: [ 482.205807] R13: 7fffffffffffffff R14: 0000000000000001 R15: 0000000000000001 May 14 09:34:36 iscsi kernel: [ 482.205811] FS: 00007f341c83e700(0000) GS:ffff8a4d3bc80000(0000) knlGS:0000000000000000 May 14 09:34:36 iscsi kernel: [ 482.205819] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 14 09:34:36 iscsi kernel: [ 482.205823] CR2: 0000000000000021 CR3: 000000022c2bc000 CR4: 00000000000406e0 May 14 09:34:36 iscsi kernel: [ 482.205828] Call Trace: May 14 09:34:36 iscsi kernel: [ 482.205843] ? drm_atomic_helper_wait_for_fences+0x48/0x130 [drm_kms_helper] May 14 09:34:36 iscsi kernel: [ 482.205895] ? nv50_disp_atomic_commit+0x18e/0x290 [nouveau] May 14 09:34:36 iscsi kernel: [ 482.205902] ? drm_atomic_helper_update_plane+0xeb/0x150 [drm_kms_helper] May 14 09:34:36 iscsi kernel: [ 482.205928] ? __setplane_internal+0x1d9/0x2a0 [drm] May 14 09:34:36 iscsi kernel: [ 482.205939] ? drm_mode_cursor_universal+0x11c/0x200 [drm] May 14 09:34:36 iscsi kernel: [ 482.205950] ? drm_mode_cursor_common+0x80/0x170 [drm] May 14 09:34:36 iscsi kernel: [ 482.205961] ? drm_mode_cursor_ioctl+0x54/0x70 [drm] May 14 09:34:36 iscsi kernel: [ 482.205973] ? drm_ioctl+0x1ea/0x470 [drm] May 14 09:34:36 iscsi kernel: [ 482.205978] ? __schedule+0x23b/0x6f0 May 14 09:34:36 iscsi kernel: [ 482.205989] ? drm_mode_setplane+0x1a0/0x1a0 [drm] May 14 09:34:36 iscsi kernel: [ 482.205994] ? _copy_to_user+0x4d/0x60 May 14 09:34:36 iscsi kernel: [ 482.206022] ? nouveau_drm_ioctl+0x66/0xc0 [nouveau] May 14 09:34:36 iscsi kernel: [ 482.206027] ? do_vfs_ioctl+0x9f/0x600 May 14 09:34:36 iscsi kernel: [ 482.206032] ? __check_object_size+0xfb/0x1d9 May 14 09:34:36 iscsi kernel: [ 482.206035] ? SyS_ioctl+0x74/0x80 May 14 09:34:36 iscsi kernel: [ 482.206039] ? system_call_fast_compare_end+0xc/0x9b May 14 09:34:36 iscsi kernel: [ 482.206043] Code: 48 85 d2 41 55 41 54 55 53 0f 88 ab 00 00 00 48 89 fd 41 89 f4 49 89 d5 66 66 66 66 90 48 8b 45 08 41 0f b6 f4 4c 89 ea 48 89 ef <ff> 50 20 49 89 c4 66 66 66 66 90 5b 4c 89 e0 5d 41 5c 41 5d c3 May 14 09:34:36 iscsi kernel: [ 482.206069] RIP: dma_fence_wait_timeout+0x30/0xf0 RSP: ffffb8c2416e3aa0 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 102319] Crashes and freezes when switching VTs
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=102319 Bug ID: 102319 Summary: Crashes and freezes when switching VTs Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: General Assignee: dri-devel(a)lists.freedesktop.org Reporter: marcin.marcin.m(a)gmail.com I have a weird problem while switching vts I have a dual-GPU setup: intel i5-5200U as the default OpenGL renderer and GeForce 940M as the discrete card. I'm using the intel modesetting driver for the Intel graphics and xf86-video-nouveau for DRI_PRIME. If I run SDDM/LXDM as my display manager (on Arch Linux), then switch the TTY to tty2, then switch back to tty7 (DM), I get only a blinking cursor. If I run LightDM as my display manager, it survives a tty switch, but if I start an X server in tty2 and then switch directly to tty7, LightDM crashes. If I switch tty2 -> tty3 (no x server) -> tty7, on the other hand, the DM does *not* crash. The whole problem doesn't occur when using the `nomodeset` kernel option, (i.e. when my DE runs in software rendering mode) Whenever I switch the ttys or when I launch the DM I get the following output in the dmesg log: https://pastebin.com/FgzZLEGg I asked about it on #nouveau and I was told that since the intel driver takes care of the rendering, it is the one to blame here. On the intel side, the problem occurs with both xf86-video-intel and the modesetting driver The problem only occurs with the X server that is launched by a DM. If I run startx directly from the tty on both vts, everything works correctly. It is not observed on a machine without nvidia graphics and with intel i5-7500K as the CPU/integrated GPU, with fairly same software stack. OS: Arch Linux, DE: Cinnamon -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 74532] New: Sanitize all freed GPU memory
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=74532 Priority: medium Bug ID: 74532 Keywords: security Assignee: dri-devel(a)lists.freedesktop.org Summary: Sanitize all freed GPU memory Severity: normal Classification: Unclassified OS: Linux (All) Reporter: nikoli(a)gmx.us Hardware: All Status: NEW Version: unspecified Component: General Product: DRI X11 applications are able to get and display in human readable form parts of closed applications, see: https://github.com/mpv-player/mpv/issues/521 It means applications like skype can silently send much more data, then you expect, even when you run them as separate user. Asked about this security problem in #gentoo-hardened, #radeon and #dri-devel, summarizing: 0) Currently GPU memory is not sanitized by kernel, nothing enforces and ensures its sanitizing. 1) https://grsecurity.net Linux kernel patches add ability to sanitize all freed memory, but they do not affect GPU memory: https://en.wikibooks.org/wiki/Grsecurity/Appendix/Grsecurity_and_PaX_Config… 2) The only secure place to clean memory is kernel, because if application or X server crashes, memory will not be erased. 3) Some applications possibly will work slower, so better make sanitizing configurable by adding build and run time kernel options. 4) Most likely this problem affects opencl too. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 103751] Very slow display on Legacy mode, but it's normal on UEFI mode
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=103751 Bug ID: 103751 Summary: Very slow display on Legacy mode, but it's normal on UEFI mode Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: Leo-Chen(a)quantatw.com When I start boot into OS in text mode with BIOS Legacy mode,it is very slow display for example do type cmd: cat /proc/cpuinfo ,but I had tried add a GRUB_CMDLINE_LINUX=”vga=normal” in /etc/default/grub. It can be normal display My config on the server : OS ver:Ubuntu 16.04.x server w/o GUI VGA: onboard AST2x00 w/o install expansion vga card -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 32821] New: [mach64] DRI doesn't work on SGRAM with 4096Kb
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=32821 Summary: [mach64] DRI doesn't work on SGRAM with 4096Kb Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/other AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: nss.zpeedzter(a)gmail.com Created an attachment (id=41615) --> (https://bugs.freedesktop.org/attachment.cgi?id=41615) with default packages and default conf I have an integrated ATI Rage Pro 2x on a Dell OptiPlex GX1. I'm running ARCHLINUX here's a part of the xorg log with default packages and default configuration [ 23.698] (--) Depth 24 pixmap format is 32 bpp [ 23.757] (WW) MACH64(0): DRI static buffer allocation failed -- need at least 10000 kB video memory .... .... [ 23.791] (II) MACH64(0): Direct rendering disabled and the second situation: I install mach64drm from AUR and added an xorg.conf and switched to 16bpp here's a part of xorg log: [ 25.394] (II) MACH64(0): I2C bus "Mach64" initialized. [ 25.455] (WW) MACH64(0): DRI static buffer allocation failed -- need at least 7593 kB video memory .... .... [ 25.489] (II) MACH64(0): Direct rendering disabled -- 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

[Bug 28000] New: [Mobile GM965/GL96][Wine][3D] Display and textures corrupted in Warhammer 40k Soulstorm
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=28000 Summary: [Mobile GM965/GL96][Wine][3D] Display and textures corrupted in Warhammer 40k Soulstorm Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: fdelente(a)mail.cpod.fr Created an attachment (id=35465) --> (https://bugs.freedesktop.org/attachment.cgi?id=35465) Xorg.0.log $ lspci 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) $ uname -m i686 $ uname -a Linux slick 2.6.32.3-smp #7 SMP PREEMPT Tue Apr 6 19:10:03 CEST 2010 i686 Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz GenuineIntel GNU/Linux -- xf86-video-intel/xserver/mesa/libdrm version: xf86-video-intel-2.11.0-i386-1 xorg-server-1.8.0-i386-1 Mesa-7.8.1-i386-1 libdrm-2.4.20-i386-1 -- kernel version: ("uname -r") 2.6.32.3-smp -- Linux distribution: Slackware 13.0 initially, but I recompiled many packages from source -- Machine or mobo model: Packard Bell BG46 fr -- Display connector: (e.g. VGA, DVI, HDMI, S-video, ...) VGA? LCD panel 3) Reproduce steps. Probability if not 100% reproducible. 100% reproducible: when starting Soulstorm, some bitmaps and 3D textures are corrupted. The same game works flawlessly on another computer with an Nvidia card. 4) Attachment: -- Xorg.0.log -- dmesg output (better with boot option "drm.debug=0x06") -- xorg.conf (if you changed any default options) No change there -- screenshot or photo (optional, a picture is worth a thousand words) -- output of "xrandr --verbose" for display mode issue -- intel_reg_dumper output (see the guide) for display issue. -- for GPU hang, get the last batch buffer (see the guide). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 12

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019