help me understand crash logs

If none of the more specific forums is the right place to ask

help me understand crash logs

Postby MagicPoulp » 2019-01-09 14:22

Please help me understand crash logs.

I just reinstalled debian stable 9. A few hours after, I got a crash with the following syslog logs when the crash happen, in /var/log/syslog.
I am indeed using a program called slack for IRC-like chatting. One line mentions slack. So I guess slack triggered an error. The slack version is based on a generic .deb package for all linux distributions from the slack.com website.

The crash totally freezes the computer. There is no way to recover. One cannot open the tti shell using CTRL + ALT + F1. One must reboot using REISUB. This is weird.

Code: Select all
Jan  9 15:09:49 SEWS200523 kernel: [ 2553.067910] perf: interrupt took too long (3948 > 3908), lowering kernel.perf_event_max_sample_rate to 50500
Jan  9 15:17:01 SEWS200523 CRON[13926]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan  9 15:30:45 SEWS200523 evolution-sourc[875]: secret_service_search_sync: must specify at least one attribute to match
Jan  9 15:58:10 SEWS200523 kernel: [ 5454.399989] nouveau 0000:0f:00.0: gr: TRAP ch 5 [003f99e000 slack[13503]]
Jan  9 15:58:10 SEWS200523 kernel: [ 5454.400008] nouveau 0000:0f:00.0: gr: GPC0/TPC0/TEX: 80000041
Jan  9 15:58:10 SEWS200523 kernel: [ 5454.400024] nouveau 0000:0f:00.0: fifo: read fault at 00029e0000 engine 00 [GR] client 01 [GPC0/T1_0] reason 02 [PTE] on channel 5 [003f99e000
slack[13503]]
Jan  9 15:58:10 SEWS200523 kernel: [ 5454.400027] nouveau 0000:0f:00.0: fifo: gr engine fault on channel 5, recovering...
Jan  9 15:59:13 SEWS200523 kernel: [ 5516.566691] sysrq: SysRq : Keyboard mode set to system default
Jan  9 15:59:13 SEWS200523 kernel: [ 5516.824691] sysrq: SysRq : This sysrq operation is disabled.
Jan  9 15:59:13 SEWS200523 kernel: [ 5516.996683] sysrq: SysRq : This sysrq operation is disabled.
Jan  9 15:59:13 SEWS200523 kernel: [ 5517.169676] sysrq: SysRq : Emergency Sync
Jan  9 15:59:13 SEWS200523 kernel: [ 5517.171829] Emergency Sync complete
Jan  9 15:59:13 SEWS200523 kernel: [ 5517.312672] sysrq: SysRq : Emergency Remount R/O
MagicPoulp
 
Posts: 197
Joined: 2018-11-05 21:30

Re: help me understand crash logs

Postby Head_on_a_Stick » 2019-01-09 16:48

MagicPoulp wrote:The slack version is based on a generic .deb package for all linux distributions from the slack.com website.

^ This is where you went wrong.

Stick to software from the official repositories to enjoy a crash-free experience.

If you want help with the problem then ask the developers, they would probably appreciate a bug report.
User avatar
Head_on_a_Stick
 
Posts: 10321
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: help me understand crash logs

Postby stevepusser » 2019-01-09 19:08

The bug also seems related to the nouveau driver...you could violate your innocent, pure system with the filthy nasty proprietary Nvidia driver to see if that stops the crashes. :)
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Foliate 1.5.3, Minitube 3.1, wine-staging 4.12, Virtual Box 5.2.32 & 6.0.10, Pale Moon 28.6.1, Waterfox 56.2.12
User avatar
stevepusser
 
Posts: 11007
Joined: 2009-10-06 05:53

Re: help me understand crash logs

Postby MagicPoulp » 2019-01-10 09:09

Yes good idea. I submitted to the developers the crash logs.

Officially, slack is only supported on Ubuntu. Still it seems to work most of the time on Debian.

Is there a way to sandbox that application so that it does not freeze the computer?
MagicPoulp
 
Posts: 197
Joined: 2018-11-05 21:30

Re: help me understand crash logs

Postby bw123 » 2019-01-10 15:58

...
Is there a way to sandbox that application so that it does not freeze the computer?
...


The buzzword is "sandbox" lately, I see it everywhere. What does it mean? Is it supposed to keep the sand in the box, or keep the cats out of the sand? I think debian has several ways of containing some difficult programs, but I doubt whether poorly written or incompatible software can be made reliable on stretch without recoding it. Why not use the os it is packaged for?

check this https://wiki.debian.org/DontBreakDebian ... l_machines
User avatar
bw123
 
Posts: 3787
Joined: 2011-05-09 06:02

Re: help me understand crash logs

Postby Head_on_a_Stick » 2019-01-10 16:03

MagicPoulp wrote:Is there a way to sandbox that application so that it does not freeze the computer?

You could try this method:

viewtopic.php?f=16&t=129390

Use the `debootstrap` command to lay down an Ubuntu system rather than sid.

I'm not sure if it will prevent the freezes but at least the application will be running in it's native environment.
User avatar
Head_on_a_Stick
 
Posts: 10321
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: help me understand crash logs

Postby MagicPoulp » 2019-01-11 11:48

How does debootstrap work when using a folder and not a partition? Does it run Ubuntu (for example) inside Debian? Does it work like a VM?
MagicPoulp
 
Posts: 197
Joined: 2018-11-05 21:30

Re: help me understand crash logs

Postby MagicPoulp » 2019-01-11 11:59

I searched about the nouveau driver error. People experience different behaviours when changing kernel versions. Besides, nvidia the grapics amnufacturer in my case, has some proprietary firmware that is not part of the nouveau driver.

https://bugs.freedesktop.org/show_bug.cgi?id=72180
https://bugzilla.kernel.org/show_bug.cgi?id=201847
https://bugzilla.redhat.com/show_bug.cgi?id=1509294

and about the firmware:
https://bugs.launchpad.net/ubuntu/+sour ... ug/1309134

People also say their error disappear using the "blob firmware". What is the blob firmware?
https://bugs.freedesktop.org/show_bug.cgi?id=72180#c29
Brandon Bertelsen 2014-01-09 03:03:08 UTC

It's been about 5 hours since I rebooted using the blob firmware. No problems to report, it seems to be a work-around for this bug.
MagicPoulp
 
Posts: 197
Joined: 2018-11-05 21:30

Re: help me understand crash logs

Postby Head_on_a_Stick » 2019-01-11 19:44

MagicPoulp wrote:How does debootstrap work when using a folder and not a partition?

Exactly the same as with a partition except that you can't boot from it unless it is also a btrfs or zfs subvolume.

MagicPoulp wrote: Does it run Ubuntu (for example) inside Debian?

Yes, that's right.

MagicPoulp wrote:Does it work like a VM?

Not quite, systemd-nspawn is a container rather than a VM so there is no need to split the resources and performance should be native.
User avatar
Head_on_a_Stick
 
Posts: 10321
Joined: 2014-06-01 17:46
Location: /dev/chair


Return to General Questions

Who is online

Users browsing this forum: No registered users and 13 guests

fashionable