bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#28149: 26.0.50; Emacs regularly hangs for multiple seconds in e.g. f


From: Alexander Asteroth
Subject: bug#28149: 26.0.50; Emacs regularly hangs for multiple seconds in e.g. find-file
Date: Tue, 22 Aug 2017 22:47:02 +0200
User-agent: mu4e 0.9.17; emacs 25.2.1

Dear Eli,

maybe it is to early to close the ticket.
Right now I did the following eperiment:

open /var/log/syslog
C-x C-f
Backspace
C-f

first C-x C-f opens ido-find-file
second C-f opens find-file

This produced reproducable GPU Hangs. See following syslog (no lines cut
out)

--------------------------------------
Aug 22 22:38:33 epsilon kernel: [90414.610167] [drm] stuck on render ring
Aug 22 22:38:33 epsilon kernel: [90414.610499] [drm] GPU HANG: ecode 
9:0:0x84dffff8, in Xorg [21887], reason: Engine(s) hung, action: reset
Aug 22 22:38:33 epsilon kernel: [90414.612283] drm/i915: Resetting chip after 
gpu hang
Aug 22 22:38:35 epsilon kernel: [90416.611033] [drm] RC6 on
Aug 22 22:40:00 epsilon kernel: [90501.610885] [drm] stuck on render ring
Aug 22 22:40:00 epsilon kernel: [90501.611184] [drm] GPU HANG: ecode 
9:0:0x84dffff8, in Xorg [21887], reason: Engine(s) hung, action: reset
Aug 22 22:40:00 epsilon kernel: [90501.613000] drm/i915: Resetting chip after 
gpu hang
Aug 22 22:40:02 epsilon kernel: [90503.611308] [drm] RC6 on
Aug 22 22:40:24 epsilon kernel: [90525.599079] [drm] stuck on render ring
Aug 22 22:40:24 epsilon kernel: [90525.599394] [drm] GPU HANG: ecode 
9:0:0x84dffff8, in Xorg [21887], reason: Engine(s) hung, action: reset
Aug 22 22:40:24 epsilon kernel: [90525.601195] drm/i915: Resetting chip after 
gpu hang
Aug 22 22:40:26 epsilon kernel: [90527.599902] [drm] RC6 on
Aug 22 22:40:42 epsilon kernel: [90543.623173] [drm] stuck on render ring
Aug 22 22:40:42 epsilon kernel: [90543.623490] [drm] GPU HANG: ecode 
9:0:0x84dffff8, in Xorg [21887], reason: Engine(s) hung, action: reset
Aug 22 22:40:42 epsilon kernel: [90543.625282] drm/i915: Resetting chip after 
gpu hang
Aug 22 22:40:44 epsilon kernel: [90545.624000] [drm] RC6 on
Aug 22 22:41:06 epsilon kernel: [90567.611346] [drm] stuck on render ring
Aug 22 22:41:06 epsilon kernel: [90567.611448] [drm] GPU HANG: ecode 
9:0:0x84dffff8, in Xorg [21887], reason: Engine(s) hung, action: reset
Aug 22 22:41:06 epsilon kernel: [90567.612672] drm/i915: Resetting chip after 
gpu hang
Aug 22 22:41:08 epsilon kernel: [90569.612251] [drm] RC6 on
Aug 22 22:41:34 epsilon kernel: [90595.611658] [drm] stuck on render ring
Aug 22 22:41:34 epsilon kernel: [90595.611955] [drm] GPU HANG: ecode 
9:0:0x84dffff8, in Xorg [21887], reason: Engine(s) hung, action: reset
Aug 22 22:41:34 epsilon kernel: [90595.613772] drm/i915: Resetting chip after 
gpu hang
Aug 22 22:41:36 epsilon kernel: [90597.612433] [drm] RC6 on
Aug 22 22:41:56 epsilon kernel: [90617.623826] [drm] stuck on render ring
Aug 22 22:41:56 epsilon kernel: [90617.624120] [drm] GPU HANG: ecode 
9:0:0x84dffff8, in Xorg [21887], reason: Engine(s) hung, action: reset
Aug 22 22:41:56 epsilon kernel: [90617.625971] drm/i915: Resetting chip after 
gpu hang
Aug 22 22:41:58 epsilon kernel: [90619.612125] [drm] RC6 on
-----------------------------

How can that be? The Hang happens when switching from ido to regular
find-file. What has GPU to do with that?

-- Alex


Eli Zaretskii writes:

>> From: Alexander Asteroth <alexander.asteroth@h-brs.de>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 28149@debbugs.gnu.org
>> Date: Tue, 22 Aug 2017 18:33:27 +0200
>> 
>> the source of error seems to be related to the graphics driver. Hangs
>> are related to these lines in syslog/dmesg:
>> 
>> --------------------
>> [63129.201509] [drm] stuck on render ring
>> [63129.201808] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [8965], reason: 
>> Engine(s) hung, action: reset
>> [63129.203624] drm/i915: Resetting chip after gpu hang
>> [63131.202095] [drm] RC6 on
>> -------------------
>> 
>> which seem to be temporarly related to the error. Some Tickets about this
>> error are already open in freedesktop.org by other users. Let's hope
>> there will be a workaround.
>
> Thanks for letting us know.  I guess we can now close this bug, then?






reply via email to

[Prev in Thread] Current Thread [Next in Thread]