dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 204683] New: amdgpu: ring sdma0 timeout
by bugzilla-daemon＠bugzilla.kernel.org 14 Oct '19

14 Oct '19

https://bugzilla.kernel.org/show_bug.cgi?id=204683 Bug ID: 204683 Summary: amdgpu: ring sdma0 timeout Product: Drivers Version: 2.5 Kernel Version: 5.3.0-rc5 Hardware: x86-64 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: mh(a)familie-heinz.name Regression: No Hi, when playing some games I randomly (sometimes after 5 minutes, sometimes after 2 hours) get a blank screen, sometimes audio still works, sometimes the whole system locks up. I've seen this with Rise of the Tomb Raider and 7 Days to Die so far. I finally managed to sync the log files to disk to get an error, before whole thing locked up: Aug 24 11:13:33 egalite kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=368056, emitted seq=368057 Aug 24 11:13:33 egalite kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out Aug 24 11:13:33 egalite kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 7DaysToDie.x86_ pid 8108 thread 7DaysToDie:cs0 Aug 24 11:13:33 egalite kernel: amdgpu 0000:0c:00.0: GPU reset begin! Aug 24 11:13:33 egalite kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered Only a hard reset made me recover from that. This is with a self-built kernel 5.3.0-rc5. Also happens with 5.2.1. Mesa: 19.1.4-1 GPU: Vega 56 Best Matthias -- You are receiving this mail because: You are watching the assignee of the bug.

1 13

[Bug 106795] Laptop with Intel+Nvidia hybrid graphics won't suspend after hibernation
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=106795 Bug ID: 106795 Summary: Laptop with Intel+Nvidia hybrid graphics won't suspend after hibernation Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: network723(a)rkmail.ru Created attachment 139988 --> https://bugs.freedesktop.org/attachment.cgi?id=139988&action=edit kernel log with drm.debug=0x0e A laptop with hybrid graphics won't suspend on the second time after it was hibernated and restored. Kernel log shows some nouveau-related error messages. For details see https://bugzilla.suse.com/show_bug.cgi?id=1094780 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 100389] Can't cap framerate
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=100389 Bug ID: 100389 Summary: Can't cap framerate Product: DRI Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: medium Component: General Assignee: dri-devel(a)lists.freedesktop.org Reporter: nw9165-3201(a)yahoo.com Hi, it's seems like it's not possible to cap (limit) the framerate. Or is it? If it's not currently possible, could you please implement it? Regards -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 51042] New: Turning off connector polling in drm_kms_helper inhibits HDMI hot plug
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=51042 Bug #: 51042 Summary: Turning off connector polling in drm_kms_helper inhibits HDMI hot plug Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: dargllun(a)gmail.com When turning off connector polling in drm_kms_helper using the poll=N module parameter HDMI hot plugging does not work anymore. Quoting Alex Deucher: See this discussion for details and some logs: http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.ati/22107 -- 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 88921] X fails to start on QEMU/KVM with cirrus KMS since 3.19-rc
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=88921 Bug ID: 88921 Summary: X fails to start on QEMU/KVM with cirrus KMS since 3.19-rc Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: tiwai(a)suse.de X modesetting driver fails to start with cirrus KMS on QEMU/KVM since 3.19-rc. The culprit is the commit 8975626ea35adcca561f8a81dedccfbc5dd8ec72 drm/cirrus: allow 32bpp framebuffers for cirrus drm Reverting this commit makes X working again. X modesetting driver seems to try to open 1024x768x32 graphics, where the pitch is 4096 and greater than max_pitch (4088) defined in cirrus_check_framebuffer(). And it doesn't fall back to 24bpp as the patch expected. Tested with 3.19-rc7 with qemu 2.1 -vga cirrus option. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 93718] nouveau + moveablecore => endless havoc (possibly a general drm problem)
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=93718 Bug ID: 93718 Summary: nouveau + moveablecore => endless havoc (possibly a general drm problem) 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: rwhite(a)pobox.com NOTE: I'm actually using the gentoo x11 overlay which seems to be an xorg git... So reserving movable core on the linux command line seems to cause random failure in my nouveau dual monitor desktop system. (I suspect it's happening to a lessor extent on my radeon laptop as well). So anyway, I've been using "moveablecore=2G" on my kernel command line for some time in order to accommodate hugepages (etc) for transient virtual machines. When I started playing with SDDM and kde Plasma I started getting display hangs. The exact moment and error of the hang/error is hard to catch, but just starting sddm is enough to cause my dmesg to fill with faults. They all looked memory/state related so I started playing around. With no kernelcore= or moveablecore= options on the kernel command line the system seems rock steady. Using either (they both reserve a movable memory NUMA region that anonymous mappings via mmap() "like" and the kernel is free to relocate by juggling page tables and copying physical images) seems to steal data will-he/nil-he out from under nouveau. ASIDE: I say it may be happening on my radeon laptop because Chromium gets render-hung there for odd reasons but the diagnostics are more vague. So the work-around is to not use these options, but I suspect there's some missing page locking or whatever creating phantom failures... particularly in nouveau... particularly under high render pressure. With "moveablecore=2G kernelcore=3G" I can't even get all the way through the sddm password entry without a messy crash. This seems to line up with a lot of can-not-duplicate type of error reports I found with google, so I figure'd I drop my datapoint here. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 102339] QXL driver hangs on virt guest login, kernel 4.12
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=102339 Bug ID: 102339 Summary: QXL driver hangs on virt guest login, kernel 4.12 Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: high Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: chuckebbert.lk(a)gmail.com >From https://bugzilla.redhat.com/show_bug.cgi?id=1481365 Description of problem: Using KVM, QXL driver emits error message over and over, I never get to my home screen. It seems to be happening while attempting to switch resolution. Another user reports that everything works if he uses 1024x768. Version-Release number of selected component (if applicable): 4.12.5 Steps to Reproduce: 1. Remove "rhgb" from kernel command line because of a possibly different QXL bug (don't have the link right now.) 2. Boot into graphical mode under KVM. Login screen appears, try to log in. 3. Desktop never appears. System log keeps getting these messages: Aug 13 14:03:40 localhost-live kernel: f 4026531862#140: failed to wait on release 22 after spincount 301 Aug 13 14:03:41 localhost-live kernel: f 4026531862#140: failed to wait on release 22 after spincount 301 Aug 13 14:03:41 localhost-live kernel: f 4026531862#140: failed to wait on release 22 after spincount 301 Aug 13 14:03:41 localhost-live kernel: f 4026531864#142: failed to wait on release 24 after spincount 301 Aug 13 14:03:42 localhost-live kernel: f 4026531864#142: failed to wait on release 24 after spincount 301 Aug 13 14:03:42 localhost-live kernel: f 4026531864#142: failed to wait on release 24 after spincount 301 Message is from drivers/gpu/drm/qxl/qxl_release.c::qxl_fence_wait() DMA fence operations are timing out. System can be shut down normally from the VM monitor, it's not frozen. The VM is only usable in text console mode. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 71083] New: (struct drm_encoder_helper_funcs)->mode_set not re-called after display (and EDID) change
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=71083 Priority: medium Bug ID: 71083 Assignee: dri-devel(a)lists.freedesktop.org Summary: (struct drm_encoder_helper_funcs)->mode_set not re-called after display (and EDID) change Severity: normal Classification: Unclassified OS: All Reporter: zajec5(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: DRM/other Product: DRI I use my DCE5 Barts (HD69xx) with AV-receiver Onkyo TX-SR605 and one of the following displays: 1) TV Sony Bravia KDL-52X3500 2) Projector Epson EH-TW6100 My problem is that when I change display connected to the Onkyo's output EDID changes, but drm doesn't call mode_set as long as I use the same resolution. To force drm to call mode_set I've to change resolution (xrandr --output HDMI-0 --mode X) and then swtich back to the mode I want. While the display seems to be working fine without that mode_set call, the audio engine doesn't. As part of the modesetting handler we read ELD-related info from EDID and write it to the audio engine of the GPU. Without this happening I can't play correctly audio (because also sees info about previous device, not the current one). I think mode_set should be called every time EDID changes. Is that right? In case someone's curious: 1) EDID with Onkyo + Sony TV: 00ffffffffffff003dcb610700000000 0011010380a05a780a0dc9a057479827 12484c21080081800101010101010101 010101010101023a801871382d40582c 450040846300001e011d007251d01e20 6e28550040846300001e000000fc0054 582d53523630350a20202020000000fd 00303e0e460f000a2020202020200185 02034c705c1f03041213051420071610 15110206010f1e0b1a191d0e0a242625 2335097f070f7f071707503f06c05706 005f7e01671e00834f00006c030c0012 00b82dc000000000e3050301023a80d0 72382d40102c458040846300001e011d 00bc52d01e20b828554040846300001e 00000000000000000000000000000078 2) EDID with Onkyo + Epson projector: 00ffffffffffff004ca333d000000000 0c150104952616780aa0558d515a962a 1c505400000001010101010101010101 0101010101016a4d80a07038fc413020 36007ed710000018d49a80a07038fc41 302036007ed710000038000000fc0053 414d53554e470a2020202020000000fc 00313733485430322d4330310a200035 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 92481] [Patch] Mostly cosmetic changes for drm_dp_mst_i2c_xfer in Linux 4.3-rc5
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=92481 Bug ID: 92481 Summary: [Patch] Mostly cosmetic changes for drm_dp_mst_i2c_xfer in Linux 4.3-rc5 Product: DRI Version: unspecified Hardware: Other 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 118905 --> https://bugs.freedesktop.org/attachment.cgi?id=118905&action=edit Numerous mostly cosmetic fixed to drm_dp_mst_i2c_xfer in linux 4.3-rc5/drivers/gpu/drm/drm_dp_mst_topology.c AFTER Dave Airlie's other changes have been applied Thanks to Dave Airlie and Daniel Vitter for the the fixes to drm_dp_mst_i2c_xfer to avoid possibly sending unitialized data in DisplayPort multistream tranport i2c queries and to enforce the limit on the number of i2c transactions in a single i2c request to avoid a possible buffer overflow. The attached patch is based on the file with Dave's aforementioned changes applied. It is an a bunch of mostly cosmetic ("maintainability") changes, which I will list below: a. Move the parameter validations to before the call to drm_dp_get_validated_mstb_ref(), so that, if they fail, they do not need to use "goto out", thereby reducing the number of goto's and the longest distance between a goto and its target label. I imagine it also makes these rare failure cases a few nanoseconds faster without delaying the common case. b. Because of the above, txmsg no longer needs to be initialized to NULL. c. Have different error messages and error codes (E2BIG, and EINVAL) for num > 4 and the i2c transaction not ending with a read statement, for clearer debugging if either of these errors should occur, which should help in cases where the errors only occur sporadically or the person observing the error cannot easily recompile and install a new kernel to get more information. Error reproduction is precious, so it's best not to waste them with unnecessary ambiguity. These errors previous returned EIO, but EIO connotes a complaint from the hardware, hence the change to E2BIG and EINVAL. By the way, I am assuming that these conditions really can be caused by user level code accessing /dev/i2c... If not, then I would be happy to replace them with BUG_ON() statements. d. Delete the comment "see if last msg is a read", since (c) makes it redundant due to the clearer diagnostic message "Final DP-MST I2C transaction was not a read". e. Since we're concerned about invalid i2c message parameters resulting in invalid memory references, also guard against num <= 0. Return -EDOM in this case, since that really would cause a problem with the mathematical domain of a function, because the line "...num_transactions = num - 1" would result in -1 being cast into 255 for the 8 bit field num_transactions. f. Eliminate the variable "reading", which was computed and used only once, immediately after it was computed. g. Be more friendly to the optimizer by using unlikely() (and likely() instead of unlikely() in one place to reduce the number of parentheses). h. Be more friendly to the optimizer and maybe make the code more readable by consolidating the seven computions of "num - 1" into a new variable, "count". I know that having two varaibles named "num" and "count" where count == num - 1 is not the greatest naming convention. Please feel free to rename. There actually is one place toward the end of the function where "num" is used (rather than num - 1). h. Do the check for num - 1 > DP_REMOTE_I2C_READ_MAX_TRANSACTIONS in a manner not susceptible to integer overflow. I realize that this patch conflates all these different minor changes. I would be willing to submit these changes individually or in a few smaller groups if necessary. By the way, the attached patch assumes is against Linux 4.3-rc5 after Dave Airlie's patch from http://lists.freedesktop.org/archives/dri-devel/2015-October/092465.html is applied. Anyhow, I hope this patch is helpful. Adam -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 69675] New: audio broken in 24Hz/24p since 3.11 (regression)
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=69675 Priority: medium Bug ID: 69675 Assignee: dri-devel(a)lists.freedesktop.org Summary: audio broken in 24Hz/24p since 3.11 (regression) Severity: normal Classification: Unclassified OS: All Reporter: pierre-bugzilla(a)ossman.eu Hardware: Other Status: NEW Version: unspecified Component: DRM/other Product: DRI Bug 64503 is back again, but this time it isn't a case of PEBKAC. Instead it is commit e6e792092e816bea0797995c886fb057c91d4546 that breaks things. With 3.10 I have just this 24p mode in Xorg: [ 47.361] (II) RADEON(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) With 3.11 I have two: Xorg.0.log:[ 56.189] (II) RADEON(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) Xorg.0.log:[ 56.189] (II) RADEON(0): Modeline "1920x1080"x24.0 74.18 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) And although the second one gives me an image, audio is royally screwed up. Please revert, or at least give us a knob to disable these extra modes. -- You are receiving this mail because: You are the assignee for the bug.

1 56

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019