Re: System crash (gpu hang?)
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 *
Reply to: