Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #192819 > unrolled thread

System crash (gpu hang?)

Started byPétùr <peturvilj@gmail.com>
First post2018-02-21 16:20 +0100
Last post2018-03-02 23:50 +0100
Articles 5 — 3 participants

Back to article view | Back to linux.debian.user


Contents

  System crash (gpu hang?) Pétùr <peturvilj@gmail.com> - 2018-02-21 16:20 +0100
    Re: System crash (gpu hang?) Ben Caradoc-Davies <ben@transient.nz> - 2018-02-21 22:00 +0100
      Re: System crash (gpu hang?) Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-02-22 00:00 +0100
      Re: System crash (gpu hang?) Ben Caradoc-Davies <ben@transient.nz> - 2018-02-22 02:30 +0100
        Re: System crash (gpu hang?) Ben Caradoc-Davies <ben@transient.nz> - 2018-03-02 23:50 +0100

#192819 — System crash (gpu hang?)

FromPétùr <peturvilj@gmail.com>
Date2018-02-21 16:20 +0100
SubjectSystem crash (gpu hang?)
Message-ID<vlElz-8qf-3@gated-at.bofh.it>
I recently experimented some crashes on debian sid.

The system becomes unresponsive and falls back to the login (lightdm)
window after few minutes.

Here is the dmesg log if someone has the time to help me figure out what
is going on:

https://paste.aperture-sc.net/?95de7f038710fd42#q18U+ujcdN+oYVKPkF8uHPCTWUehItZGtzvXYTsgHVU=

Petur

[toc] | [next] | [standalone]


#192848

FromBen Caradoc-Davies <ben@transient.nz>
Date2018-02-21 22:00 +0100
Message-ID<vlJEC-3j3-13@gated-at.bofh.it>
In reply to#192819
On 22/02/18 04:19, Pétùr wrote:
> I recently experimented some crashes on debian sid.
> The system becomes unresponsive and falls back to the login (lightdm)
> window after few minutes.
> Here is the dmesg log if someone has the time to help me figure out what
> is going on:
> https://paste.aperture-sc.net/?95de7f038710fd42#q18U+ujcdN+oYVKPkF8uHPCTWUehItZGtzvXYTsgHVU=
> Petur

I have also seen this GPU hang on sid. It started occurring every time I 
opened Eclipse Oxygen.2 with export SWT_GTK3=0 so I had to unset this 
environment variable. I am using Intel HD Graphics 630.

Kind regards,

-- 
Ben Caradoc-Davies <ben@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

[toc] | [prev] | [next] | [standalone]


#192861

FromCindy-Sue Causey <butterflybytes@gmail.com>
Date2018-02-22 00:00 +0100
Message-ID<vlLwJ-4sC-13@gated-at.bofh.it>
In reply to#192848
On 2/21/18, Ben Caradoc-Davies <ben@transient.nz> wrote:
> On 22/02/18 04:19, Pétùr wrote:
>> I recently experimented some crashes on debian sid.
>> The system becomes unresponsive and falls back to the login (lightdm)
>> window after few minutes.
>> Here is the dmesg log if someone has the time to help me figure out what
>> is going on:
>> https://paste.aperture-sc.net/?95de7f038710fd42#q18U+ujcdN+oYVKPkF8uHPCTWUehItZGtzvXYTsgHVU=
>> Petur
>
> I have also seen this GPU hang on sid. It started occurring every time I
> opened Eclipse Oxygen.2 with export SWT_GTK3=0 so I had to unset this
> environment variable. I am using Intel HD Graphics 630.


Mine locked up last night worse than it has in a very long time. It
took a long time, but I was able to break out of it by PATIENTLY
shutting down programs tab by tab, window by window.

Trying to shut entire programs down just seems to clog things up worse
and faster. I've had to do the hardware power off button number a
couple times in response. I HATE that route because it's when you see
that orphan something or other deal during the next bootup.

Something was running that I tried to track down. I figured out what
it might be once a while back, but I forget what it is now. Didn't
have the cognitive togetherness to be able to figure out again last
night....

It may fall under "cron" or something. I'm pretty sure it's something
that runs regularly. I have no idea why it locked up that bad last
night, but it sure did.

I heard it kick in just a split second before my computer locked up.
Sometime just after midnight as has been its pattern.

By heard it, I mean I could hear hardware take on an extra load when I
hadn't clicked anything. There was basically about 200MB of breathing
room out of ~9GB total in "mem" and "swap" k/t "free -m".

Just sharing because someone with a fancier quiet system or in a noisy
work environment might not have that advantage of hearing whatever I'm
hearing kick in....

PS I just encountered "kworker" two days ago during an accidentally
issued (wide open) "ps aux". If I understand the chatter across the
Net, that looks like something that might have potential as a useful
check point when tracking down memory issues.

Or not......... if I didn't understand correctly. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]


#192865

FromBen Caradoc-Davies <ben@transient.nz>
Date2018-02-22 02:30 +0100
Message-ID<vlNRU-63S-7@gated-at.bofh.it>
In reply to#192848
On 22/02/18 09:50, Ben Caradoc-Davies wrote:
> On 22/02/18 04:19, Pétùr wrote:
>> I recently experimented some crashes on debian sid.
>> The system becomes unresponsive and falls back to the login (lightdm)
>> window after few minutes.
>> Here is the dmesg log if someone has the time to help me figure out what
>> is going on:
>> https://paste.aperture-sc.net/?95de7f038710fd42#q18U+ujcdN+oYVKPkF8uHPCTWUehItZGtzvXYTsgHVU= 
>> Petur
> I have also seen this GPU hang on sid. It started occurring every time I 
> opened Eclipse Oxygen.2 with export SWT_GTK3=0 so I had to unset this 
> environment variable. I am using Intel HD Graphics 630.

I reported the bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891056

I found another workaround, which was to disable xfwm4 compositing (I am 
using XFCE).

Kind regards,

-- 
Ben Caradoc-Davies <ben@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

[toc] | [prev] | [next] | [standalone]


#193286

FromBen Caradoc-Davies <ben@transient.nz>
Date2018-03-02 23:50 +0100
Message-ID<vp1F3-hg-79@gated-at.bofh.it>
In reply to#192865
On 22/02/18 14:27, Ben Caradoc-Davies wrote:
> On 22/02/18 09:50, Ben Caradoc-Davies wrote:
>> On 22/02/18 04:19, Pétùr wrote:
>>> I recently experimented some crashes on debian sid.
>>> The system becomes unresponsive and falls back to the login (lightdm)
>>> window after few minutes.
>>> Here is the dmesg log if someone has the time to help me figure out what
>>> is going on:
>>> https://paste.aperture-sc.net/?95de7f038710fd42#q18U+ujcdN+oYVKPkF8uHPCTWUehItZGtzvXYTsgHVU= 
>>> Petur
>> I have also seen this GPU hang on sid. It started occurring every time 
>> I opened Eclipse Oxygen.2 with export SWT_GTK3=0 so I had to unset 
>> this environment variable. I am using Intel HD Graphics 630.
> I reported the bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891056
> I found another workaround, which was to disable xfwm4 compositing (I am 
> using XFCE).

Fixed in version mesa/17.3.6-1 on sid.

Kind regards,

-- 
Ben Caradoc-Davies <ben@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web