X11 crash after keeping laptop running a few days

SatoruTajiri · 2021-11-28 06:03:52

Been using Arch Linux for over 2 years now, had my fair share of issues relating to jittery trackpad input (weirdly fixed by hibernating then unhibernating laptop), but this is the first time I've had loss of login for reasons other than OOM.
The session was running for longer than I usually leave it, which may have contributed to the crash.

I am using i3-gaps, and LightDM.

Relevant Journalctl log:
https://pastebin.com/g5vX48zT
Xorg log:
https://pastebin.com/Y2jXbYqU

$ pacman -Qi xorg-server | grep ^Version
Version         : 21.1.1-3
$ pacman -Qi i3-gaps | grep ^Version
Version         : 4.20.1-1
$ pacman -Qi lightdm | grep ^Version
Version         : 1:1.30.0-4

If more information is needed, please ask. I'm happy to provide, so I can get to the bottom of this.

Last edited by SatoruTajiri (2021-11-28 06:14:24)

Slithery · 2021-11-28 06:14:23

Please post a full log, not just the bit that you think is relevant.

SatoruTajiri · 2021-11-28 06:31:15

Slithery wrote:

Please post a full log, not just the bit that you think is relevant.

It's beyond Pastebin's maximum size, and it contains a lot of personal info. I have contained the full X11 logs though, and I can assure you that what I have posted contains all logs around the time of the crash. If you need more information, such as logs around the time of boot, I can post those as needed.

seth · 2021-11-28 08:08:17

The trace fits https://bbs.archlinux.org/viewtopic.php?id=271450
One thing I'll throw at the wall is to drop xf86-video-intel, the other environments were different but using nvidia and amdgpu, afaics nobody w/ the modesetting driver.

first time I've had loss of login for reasons other than OOM.

You don't have swap?

can assure you that what I have posted contains all logs around the time of the crash

The journal contains the abort, that's all. There's hardly any information beyond that in the xorg log.
The journal should™ not be too long if you omit thre brainded and useless "-x" parameter and if it really contains private information, there's a severe flaw in your system setup that you should address immediately.

SatoruTajiri · 2021-11-29 02:49:25

seth wrote:

You don't have swap?

It was exceptional circumstance, even something swap couldn't handle. Either way, it was my fault and not the system's.

seth wrote:

The journal should™ not be too long if you omit thre brainded and useless "-x" parameter and if it really contains private information, there's a severe flaw in your system setup that you should address immediately.

I used the following command to get system logs:

$ journalctl -b -2 | xclip -selection c

I omitted the -x parameter.

$ journalctl -b -2 | wc -l

counted 12605 lines.

As for private information, I'm just a bit paranoid. I expect there would be information on network config and the apps I'm using, but I can totally accept sharing that if it's needed.

I do agree that there are problems with my system, but I have given multiple attempts at solving them myself and with others on IRC, to no avail. Either way I have learned to live with them. The biggest ones I can think of:

Mousepad stutters around and is practically unusable, only on some boots, and is fixed after hibernating/unhibernating
Microphone doesn't work, distorted beyond recognition, I just keep it disabled
Occasionally Internet will stop until I click on the NetworkManager applet, which fixes it - sometimes I have to restart the NetworkManager service

This is the first time I've had something as fatal as X11 crash, and fortunately I've never had a kernel panic or similar.
My laptop is a Lenovo ideapad 330-15IGM, in case that explains anything.

Upon second thought, I'm happy to share full logs, but I'll need some way to shorten it in order to fit it on a paste site (or alternatively a paste site with larger sizes)

Last edited by SatoruTajiri (2021-11-29 02:50:08)

seth · 2021-11-29 08:19:41

I meant whether you have swapspace *now* because w/o you can run OOM very fast (and we're still looking for ways to explain the backtrace pattern)

12605 lines

Long uptime or spam.
Either way, that should make about or less than 300kB. 900kB if it'd be all kanji ? That's not too much. You can feed it into ix.io - see 1st link below.

You may also redact it first but make sure that the redaction is visible, ie. do not just delete things and use clear and unique placeholders (if you feel like hidings MACs don't replace every MAC w/ the same token but a different one for each)

SatoruTajiri · 2021-11-29 08:29:11

seth wrote:

I meant whether you have swapspace *now* because w/o you can run OOM very fast (and we're still looking for ways to explain the backtrace pattern)

Yes I do still have swap. 8GB RAM + 4GB swap. The system was not under extreme stress when the crash happened.

seth wrote:

12605 lines
Long uptime or spam.
Either way, that should make about or less than 300kB. 900kB if it'd be all kanji ? That's not too much. You can feed it into ix.io - see 1st link below.

Probably a mix of uptime and spam (but mostly spam), it's 1.5MB from running Nov 25 to Nov 28. No Unicode characters (at least from what I can see)
ix.io does not upload it (presumably because of the size)

seth · 2021-11-29 09:37:36

If you've a google drive you could upload it there. Otherwise you can use stuff like wetransfer.com
Since you're uploading for download anyway, you can just as much encrypt it and share the password here

[code}/usr/bin/openssl enc -e -aes-256-cbc -salt -in "$file" -out "$file.aes" -pass pass:"$pass" # substitute $file and $pass[/code}

SatoruTajiri · 2021-12-02 01:27:29

I managed to get it onto GitHub's Gist site:
https://gist.githubusercontent.com/Alex … ournal.txt

Haven't redacted or encrypted anything, so I will delete it in a week's time.

loqs · 2021-12-02 03:37:34

Did you try without xf86-video-intel? It still appears to be in use from the X crash in the journal.

SatoruTajiri · 2021-12-02 03:40:39

I have uninstalled it but I will have no way of knowing if it caused the crash or not.
I will try to keep my laptop running for a while to see if it can be reproduced.

Arch Linux

#1 2021-11-28 06:03:52

X11 crash after keeping laptop running a few days

#2 2021-11-28 06:14:23

Re: X11 crash after keeping laptop running a few days

#3 2021-11-28 06:31:15

Re: X11 crash after keeping laptop running a few days

#4 2021-11-28 08:08:17

Re: X11 crash after keeping laptop running a few days

#5 2021-11-29 02:49:25

Re: X11 crash after keeping laptop running a few days

#6 2021-11-29 08:19:41

Re: X11 crash after keeping laptop running a few days

#7 2021-11-29 08:29:11

Re: X11 crash after keeping laptop running a few days

#8 2021-11-29 09:37:36

Re: X11 crash after keeping laptop running a few days

#9 2021-12-02 01:27:29

Re: X11 crash after keeping laptop running a few days

#10 2021-12-02 03:37:34

Re: X11 crash after keeping laptop running a few days

#11 2021-12-02 03:40:39

Re: X11 crash after keeping laptop running a few days

Board footer