undiagnosed driver issues [solved]

[linuxshark]

hi! i swapped to linux mint about a month ago with no issue. but as of a few weeks ago my entire screen would freeze, and no response from my mouse or keyboard. though audio would still play and hard drive will still make sound. i've tired looking for other posts on the forum with the same issue but no luck.

the odd thing is, whenever i'd hard reboot i wouldn't have a freezing issue anymore. so in the morning i'd boot my system, and do my usual stuff and suddenly (usually after clicking) the system would freeze. so i'm left to hard reboot (i didn't know about reisub yet). after that i'd have no freezing.

a solution ive tried doing was having the nvidia drivers boot sooner, but haven't waited to see if that fixed the issue. i wanna post this in case that didn't work and i need a different diagnosis or solution.

(if the post did fix my issue i'll link it here and mark this as solved)

edit: forgot sys info
edit 2: one crucial thing i forgot to mention. this ONLY happens if firefox is open.

Code: Select all

System:
  Kernel: 5.15.0-100-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
    tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: Gigabyte model: GA-78LMT-S2 v: x.x serial: <superuser required> UEFI: Award
    v: F5 date: 10/19/2012
CPU:
  Info: quad core model: AMD FX-4300 bits: 64 type: MT MCP smt: enabled arch: Piledriver rev: 0
    cache: L1: 192 KiB L2: 4 MiB L3: 4 MiB
  Speed (MHz): avg: 2828 high: 3917 min/max: 1400/3800 boost: enabled cores: 1: 3917 2: 3917
    3: 1878 4: 1602 bogomips: 30535
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: ZOTAC driver: nvidia v: 535.161.07 pcie:
    speed: 2.5 GT/s lanes: 4 ports: active: none off: DVI-I-1 empty: DP-1,HDMI-A-1 bus-ID: 01:00.0
    chip-ID: 10de:1380 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1360x768 s-dpi: 84 s-size: 411x232mm (16.2x9.1") s-diag: 472mm (18.6")
  Monitor-1: DVI-I-1 res: 1360x768 hz: 60 dpi: 84 size: 410x230mm (16.1x9.1")
    diag: 470mm (18.5")
  OpenGL: renderer: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 535.161.07
    direct render: Yes
Audio:
  Device-1: AMD SBx00 Azalia vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:14.2
    chip-ID: 1002:4383 class-ID: 0403
  Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX] vendor: ZOTAC
    driver: snd_hda_intel v: kernel pcie: speed: 5 GT/s lanes: 4 bus-ID: 01:00.1 chip-ID: 10de:0fbc
    class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-100-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: de00 bus-ID: 02:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 931.51 GiB used: 257.1 GiB (27.6%)
  ID-1: /dev/sda vendor: Hitachi model: HUA721010KLA330 size: 931.51 GiB speed: 1.5 Gb/s
    type: N/A serial: <filter> rev: A90A scheme: GPT
Partition:
  ID-1: / size: 915.32 GiB used: 257.09 GiB (28.1%) fs: ext4 dev: /dev/sda3
  ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 2-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-3: 3-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-4: 4-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-5: 5-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-6: 6-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
  Device-1: 6-2:3 info: Pixart Imaging Optical Mouse type: Mouse driver: hid-generic,usbhid
    interfaces: 1 rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 093a:2510 class-ID: 0301
  Hub-7: 7-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 18.4 C mobo: N/A gpu: nvidia temp: 28 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 33%
Repos:
  Packages: 2386 apt: 2370 flatpak: 16
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com virginia main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 262 Uptime: 55m wakeups: 0 Memory: 7.74 GiB used: 2.9 GiB (37.4%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 6.0.4 inxi: 3.3.13

[linuxshark]

update: i rolled back to a timeshift from before the freezing occured, and its still happening. meaning what i thought caused it wasn't the case. however this time i hadn't even opened firefox.

but it always seems to happen when i click on something to initiate it (going to a different tab in firefox, a different server in discord, etc.)

good news is the

Code: Select all

REISUB

command works just fine, so even if this is still happening im not going to damage my pc further.

the only possible answer i can think of is that one of the updates between around march 3 to now just doesn't agree with my computer. i just don't understand why this only seems to happen once a day but is fine after a simple reboot.

[SMG]

a solution ive tried doing was having the nvidia drivers boot sooner, but haven't waited to see if that fixed the issue.

Welcome to the forum, linuxshark.

What does the statement I quoted mean you did?

If this is the correct link, there is an F6 update. I have no idea if "modified CPU options" means options were added to the BIOS/UEFI or options were added for the operating system to use.
Machine:
Type: Desktop Mobo: Gigabyte model: GA-78LMT-S2 v: x.x serial: <superuser required> UEFI: Award
v: F5 date: 10/19/2012

but it always seems to happen when i click on something to initiate it (going to a different tab in firefox, a different server in discord, etc.)
...
i just don't understand why this only seems to happen once a day but is fine after a simple reboot.

It sounds like a memory-related issue. You are clearing caches when you reboot. Discord is an extremely resource intensive app and nowadays browers are as well.

I recommend you increase your swapfile size to see if that helps. The default is 2GB and I suggest you try 6GB and see if that helps.
How to Increase Swap Size on Ubuntu Linux

[linuxshark]

hi! thank you for the responee

regarding the nvidia driver thing-- this was what i followed viewtopic.php?p=1895521 and unfortunately didnt help.

the bios thing i'm wholly unsure of. and i don't believe it has anything to do with my issue as i had no problem with it before. i don't really wish to flash it either because if i were to have an issue occur during the process i'd be more than screwed. i wouldn't be able to afford a repair like that.

but if it's true that my issue could be simply memory it'll be an easy fix! i'm currently not home to fuss with my computer but i'll increase my swap partition as soon as i can and see if it works! it makes me happy that it could just be that. again thank you for an answer!

[SMG]

regarding the nvidia driver thing-- this was what i followed viewtopic.php?p=1895521 and unfortunately didnt help.

That fix is for when the nouveau driver loads faster than the nvidia driver. Your inxi output shows the nvidia driver is loaded so that has no bearing on the issue you are seeing.

There is nothing in your output or your description which indicates this is a driver issue.

[linuxshark]

regarding the nvidia driver thing-- this was what i followed viewtopic.php?p=1895521 and unfortunately didnt help.

That fix is for when the nouveau driver loads faster than the nvidia driver. Your inxi output shows the nvidia driver is loaded so that has no bearing on the issue you are seeing.

There is nothing in your output or your description which indicates this is a driver issue.

ah okay. good to know. i thought it was a driver issue due to seeing similar problems being caused by nvidia drivers.

[linuxshark]

I recommend you increase your swapfile size to see if that helps. The default is 2GB and I suggest you try 6GB and see if that helps.
How to Increase Swap Size on Ubuntu Linux

finally home and able to try this. but it isn't working. my terminal just says that '1' isnt a valid option

[linuxshark]

i miss read the command- i successfully increased my swap partition size and rebooted. but my computer is a black screen on startup :/

yet when i use REISUB to reboot it loads up fine

[SMG]

i miss read the command- i successfully increased my swap partition size and rebooted. but my computer is a black screen on startup :/

yet when i use REISUB to reboot it loads up fine

Changing the swapfile size should not have anything to do with booting the computer. What is the output of

Code: Select all

free -h

[linuxshark]

i miss read the command- i successfully increased my swap partition size and rebooted. but my computer is a black screen on startup :/

yet when i use REISUB to reboot it loads up fine

Changing the swapfile size should not have anything to do with booting the computer. What is the output of

Code: Select all

free -h

Code: Select all

               total        used        free      shared  buff/cache   available
Mem:           7.7Gi       2.8Gi       2.9Gi        65Mi       2.1Gi       4.7Gi
Swap:          6.0Gi          0B       6.0Gi

[linuxshark]

gonna update this with new info because ive figured out some more consistent issues with this

my os will freeze up after booting from a shut down, however after restarting with reisub i experience no freezing.

i had originally thought that firefox was causing the issue, but last night i had let my computer sit after boot while i did other things, and it still froze. no applications were open. rebooted through the reisub command, and it was all good.

smg's solution of increasing my swap file unfortunately didn't work, in fact my os froze even sooner after booting up. again, still fine after a restart.

however there is one thing i left out of my original post because i thought it wouldnt have been the cause but i should probably bring it up.

this all started after i had bought monster hunter world and played it for a while. i had 0 issues with the game at all for a good 40 hours. no issue playing with other people, and sometimes id stream it to my friend. zero issues. however after failing a quest i hit some sort of corruption. i had a rollover notification (when it wasn't rollover) and the game was telling me it was currently a festival (there were no festivals scheduled for the date this happened, this happened on march 9th). i didnt suspect anything was wrong but when i looked at the available quests they were flickering between available and unavailable. i tried selecting one and got an error. so instead i tried one of the standard quests, got the book opening animation and then the game just kinda froze. not a full on freeze - it was still running. but no inputs were working. i force closed the game and relaunched it only to find my save data became corrupted.

so. i had to start all over. didnt have any issues really. but when i got to about late-early game (rotten vale) i experienced a freeze mid-hunt. i figured it was because i had tried taking a screenshot and didnt let it finish before trying to alt-tab into pinta. from then on id have infrequent freezes, always during the first boot as far as i remember. but now it happens shortly after a fresh boot, even when i have nothing else open.

another thing i forgot to mention was that i had tried to fully reinstall linux to see if maybe there was some issue with linux itself, but when i got into the live boot and i tried to click install linux. it froze. i had to get someone to redo the usb otherwise it wouldn't be readable. i hope i dont have a bad sector in my hard drive, that could be a possibility.

[SMG]

gonna update this with new info because ive figured out some more consistent issues with this

It sounds like you may have a hardware problem.

When you cold boot (computer is completely off and you turn it on to boot the computer), all the hardware has to initialize and then the operating system starts. When you reboot, that is a "warm" boot and none of the hardware re-initializes. Only the operating system restarts.

...rebooted through the reisub command, and it was all good.

For how long was it "all good"?

smg's solution of increasing my swap file unfortunately didn't work, in fact my os froze even sooner after booting up. again, still fine after a restart.

You posted you did that less than an hour ago.

i had to get someone to redo the usb otherwise it wouldn't be readable.

What does that mean was done to the usb?

[linuxshark]

gonna update this with new info because ive figured out some more consistent issues with this

It sounds like you may have a hardware problem.

When you cold boot (computer is completely off and you turn it on to boot the computer), all the hardware has to initialize and then the operating system starts. When you reboot, that is a "warm" boot and none of the hardware re-initializes. Only the operating system restarts.

...rebooted through the reisub command, and it was all good.

For how long was it "all good"?

smg's solution of increasing my swap file unfortunately didn't work, in fact my os froze even sooner after booting up. again, still fine after a restart.

You posted you did that less than an hour ago.

i had to get someone to redo the usb otherwise it wouldn't be readable.

What does that mean was done to the usb?

-damn, if thats the case that really sucks

-its 'all good' until i turn off my computer via shut down and reboot. but if i use 'restart' it stays fine

-yes, i shut down my computer after increasing the swap file and rebooted to see if it would freeze -- and it froze sooner than it usually does

-im unsure what youre asking. after the linux install froze i was unable to boot from the live boot off the usb. had to reformat it and put a fresh iso of mint on it

[SMG]

-im unsure what youre asking. after the linux install froze i was unable to boot from the live boot off the usb. had to reformat it and put a fresh iso of mint on it

That answers my question.

I don't game and have no idea of the requirements of Monster Hunter world.

Going back to your first post, the below does not seem to fit in with what you have recently been saying:

the odd thing is, whenever i'd hard reboot i wouldn't have a freezing issue anymore. so in the morning i'd boot my system, and do my usual stuff and suddenly (usually after clicking) the system would freeze. so i'm left to hard reboot (i didn't know about reisub yet). after that i'd have no freezing.

If two hard boots means you have no freeze problem and one hard boot and a reboot means you have no freeze problem, then it sounds like something may need warmed up a little bit before it works properly.

[linuxshark]

-im unsure what youre asking. after the linux install froze i was unable to boot from the live boot off the usb. had to reformat it and put a fresh iso of mint on it

That answers my question.

I don't game and have no idea of the requirements of Monster Hunter world.

Going back to your first post, the below does not seem to fit in with what you have recently been saying:

the odd thing is, whenever i'd hard reboot i wouldn't have a freezing issue anymore. so in the morning i'd boot my system, and do my usual stuff and suddenly (usually after clicking) the system would freeze. so i'm left to hard reboot (i didn't know about reisub yet). after that i'd have no freezing.

If two hard boots means you have no freeze problem and one hard boot and a reboot means you have no freeze problem, then it sounds like something may need warmed up a little bit before it works properly.

my apologies- i was a bit unclear and inconsistent with my words.

i tried just let my computer sit for a while after booting last night, and it still froze, meaning i had to restart.

the odd thing is it doesnt happen a specific amount of time after first boot, sometimes itll be 10 minutes after boot and sometimes itll be 30 minutes after boot

[SMG]

i tried just let my computer sit for a while after booting last night, and it still froze, meaning i had to restart.

If that was the previous boot cycle, then please run the following:

Code: Select all

journalctl -b -1 | tail -n 100

That will provide the last 100 lines of the boot cycle which froze. Maybe it will give some clues as to what is happening.

[linuxshark]

i tried just let my computer sit for a while after booting last night, and it still froze, meaning i had to restart.

If that was the previous boot cycle, then please run the following:

Code: Select all

journalctl -b -1 | tail -n 100

That will provide the last 100 lines of the boot cycle which froze. Maybe it will give some clues as to what is happening.

Code: Select all

Mar 23 08:33:04 systemd[1]: systemd-coredump@21-2517-0.service: Deactivated successfully.
Mar 23 08:33:04 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Mar 23 08:33:04 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Mar 23 08:33:04 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 11.
Mar 23 08:33:04 systemd[1]: Stopped Light Display Manager.
Mar 23 08:33:04 systemd[1]: gpu-manager.service: Start request repeated too quickly.
Mar 23 08:33:04 systemd[1]: gpu-manager.service: Failed with result 'start-limit-hit'.
Mar 23 08:33:04 systemd[1]: Failed to start Detect the available GPUs and deal with any system changes.
Mar 23 08:33:04 systemd[1]: lightdm.service: Start request repeated too quickly.
Mar 23 08:33:04 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Mar 23 08:33:04 systemd[1]: Failed to start Light Display Manager.
Mar 23 08:33:07 dbus-daemon[710]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

yep. looks like theres something wrong here

[SMG]

yep. looks like theres something wrong here

Hard to tell what the issue is because you only posted a few lines and the few lines you posted don't go back to the start of the problem.

[linuxshark]

yep. looks like theres something wrong here

Hard to tell what the issue is because you only posted a few lines and the few lines you posted don't go back to the start of the problem.

ah sorry- i just posted what seemed relevant

Code: Select all

                                                                 Stack trace of thread 2490:
                                                                 #0  0x00007f922483f9fc __pthread_kill_implementation (libc.so.6 + 0x969fc)
                                                                 #1  0x00007f92247eb476 __GI_raise (libc.so.6 + 0x42476)
                                                                 #2  0x00007f92247d17f3 __GI_abort (libc.so.6 + 0x287f3)
                                                                 #3  0x0000558dc69566a0 OsAbort (Xorg + 0x1da6a0)
                                                                 #4  0x0000558dc695bea9 n/a (Xorg + 0x1dfea9)
                                                                 #5  0x0000558dc695ce9a FatalError (Xorg + 0x1e0e9a)
                                                                 #6  0x0000558dc67e19de n/a (Xorg + 0x659de)
                                                                 #7  0x00007f92247d2d90 __libc_start_call_main (libc.so.6 + 0x29d90)
                                                                 #8  0x00007f92247d2e40 __libc_start_main_impl (libc.so.6 + 0x29e40)
                                                                 #9  0x0000558dc67ca605 _start (Xorg + 0x4e605)
Mar 23 08:33:03 systemd[1]: systemd-coredump@20-2491-0.service: Deactivated successfully.
Mar 23 08:33:04 systemd[1]: Started Process Core Dump (PID 2517/UID 0).
Mar 23 08:33:04 systemd-coredump[2518]: Process 2516 (Xorg) of user 0 dumped core.
                                                                 
                                                                 Found module linux-vdso.so.1 with build-id: 2bee596cf278856fcc3f881f16f86d158e171fba
                                                                 Found module libnvidia-glcore.so.535.161.07 with build-id: e4608153a7fcebe877db517371bb6cdcd36c376c
                                                                 Found module libnvidia-tls.so.535.161.07 with build-id: 14e7737f14b955510e317b7a7d966d41fe3dcc86
                                                                 Found module libglxserver_nvidia.so with build-id: da16bca1bcb3afdf6b62c59e37afa295fc387454
                                                                 Found module libfbdevhw.so with build-id: 4d7f21d3909369275c61890ff3c2e275cb0502c0
                                                                 Found module libwfb.so with build-id: 9f070bd860452c44b9e32ffb1897f716a6f9b26f
                                                                 Found module vesa_drv.so with build-id: 7b8b5bde700db39019fb318d74ca9d63179cd720
                                                                 Found module fbdev_drv.so with build-id: 2cf5d149b48721c0899218a68c1e2257277945d2
                                                                 Found module modesetting_drv.so with build-id: f71cfd88a0fe6464c41290da4440819472cb0566
                                                                 Found module libdrm_nouveau.so.2 with build-id: 717e881b4ee3b0bc2344b0f63c4fc10c84263f13
                                                                 Found module nouveau_drv.so with build-id: 2f5f52f359d4d8d6e54179abd4e552935636606b
                                                                 Found module libdl.so.2 with build-id: feca1a24889ea0b8e9d7c72e28766c14e189a2cf
                                                                 Found module librt.so.1 with build-id: c573934461956649de9bfa57ea368bdfec09081c
                                                                 Found module nvidia_drv.so with build-id: edb2978b5b1d420e0c55fb6a870e32cf0b2934bb
                                                                 Found module libxcb.so.1 with build-id: 1bef862a339557aa16c34c7a4b27f8f3aea90517
                                                                 Found module libX11.so.6 with build-id: 37a5d7bbb78e3a99ea8376a7c80ea0c62fe06494
                                                                 Found module libGLX.so.0 with build-id: ac8b68a74f1ead77477f89bc98998ecb064e3ae5
                                                                 Found module libGLdispatch.so.0 with build-id: 19c339ecd74c020f1db1342213a07114f4baf5e0
                                                                 Found module libGL.so.1 with build-id: fe7c476406e1e41b511089398540d618177a7dcb
                                                                 Found module libglx.so with build-id: 68f7b553b25b4bc5bd3de28b926823cc11f9185e
                                                                 Found module libbrotlicommon.so.1 with build-id: 43a72967cf84155914c8b3e915926733d1e57c11
                                                                 Found module libbrotlidec.so.1 with build-id: 4b1f390dd6e24d49684db8b2443d082379e8e977
                                                                 Found module libpng16.so.16 with build-id: d58bf7c11ac793d528926238d831792b5ef792cf
                                                                 Found module libmd.so.0 with build-id: cd2d2f71b3967ebde30e2aa43b8eb63339020c06
                                                                 Found module libcap-ng.so.0 with build-id: 9c147584fee3ed3c499a2fa2bdad3aa75ae8f120
                                                                 Found module libcap.so.2 with build-id: b4bf900abf14aabe12d90988ceb30888acb2bcb0
                                                                 Found module liblz4.so.1 with build-id: a85971851cd059f1af80d553c8e7170d42ec59a1
                                                                 Found module libzstd.so.1 with build-id: 5d9d0d946a3154a748e87e17af9d14764519237b
                                                                 Found module libfreetype.so.6 with build-id: bc6c65a19e6f75fea5e74a7fd6c0b91182e1a8b0
                                                                 Found module libfontenc.so.1 with build-id: b1959e0ef458c74b5fd9e6015e3728b620ca88c0
                                                                 Found module libbz2.so.1.0 with build-id: e56b62c27bcc7ace8f9be36b255bd7b31bfde405
                                                                 Found module libz.so.1 with build-id: 30840b79ac329ecbf1dec0bb60180eed256d319f
                                                                 Found module liblzma.so.5 with build-id: b85da6c48eb60a646615392559483b93617ef265
                                                                 Found module libgpg-error.so.0 with build-id: 3fbec71c67bee60d8aef00697ee187079b0fb307
                                                                 Found module libpcre2-8.so.0 with build-id: 184a841c55fb7fe5e3873fcda8368c71016cd54c
                                                                 Found module ld-linux-x86-64.so.2 with build-id: 15921ea631d9f36502d20459c43e5c85b7d6ab76
                                                                 Found module libc.so.6 with build-id: c289da5071a3399de893d2af81d6a30c62646e1e
                                                                 Found module libbsd.so.0 with build-id: 9a6c72469251e2feb63e175ef5cb944ce6e00df3
                                                                 Found module libm.so.6 with build-id: a88ef0199bd5e742ebd0c359edf5cb2be0ec08b5
                                                                 Found module libaudit.so.1 with build-id: 47d5dee8f88c177f563c0836c19f8ac1bb80d899
                                                                 Found module libXdmcp.so.6 with build-id: 6b60f99504aa1d3999ea02a14366d1a39d6c5dcf
                                                                 Found module libxshmfence.so.1 with build-id: f08296172ec7b676e1b371afc936e36add17366d
                                                                 Found module libsystemd.so.0 with build-id: e17e357f3a8e8198b1de01bd084ca319c72d231b
                                                                 Found module libXau.so.6 with build-id: 7089b383cacbfc1760634a3be19a923e51fe3315
                                                                 Found module libXfont2.so.2 with build-id: bf8e9676355223cfd1bee20f9579d55d6b80aa52
                                                                 Found module libpixman-1.so.0 with build-id: 5e936cdac032b6048d9d1a8c0bb0e4a10c86d48c
                                                                 Found module libdrm.so.2 with build-id: 9c7cb19295d20e515902cb0710326a0b8d6394c8
                                                                 Found module libpciaccess.so.0 with build-id: 4c93da952f83c1d085d4bdead692db544c79b004
                                                                 Found module libxcvt.so.0 with build-id: bfdace0c594653ee489362f7fc580908efba3601
                                                                 Found module libunwind.so.8 with build-id: 6087b27829180bc245595d15b8d7b38b298d35af
                                                                 Found module libgcrypt.so.20 with build-id: 60a5e524de0ed8323edf33e9eb9127a9eee02359
                                                                 Found module libselinux.so.1 with build-id: 6fa53202ce676297de24873c886443b2759bfd8a
                                                                 Found module libudev.so.1 with build-id: a09630833014650812000b6504d3773e88672b8f
                                                                 Found module libdbus-1.so.3 with build-id: 63e8b99215502138cb63afd6d65851a5e837ed49
                                                                 Found module Xorg with build-id: 1776c0fbaf7f280b47fede0e535f29231420b913
                                                                 Stack trace of thread 2516:
                                                                 #0  0x00007f2cb098f9fc __pthread_kill_implementation (libc.so.6 + 0x969fc)
                                                                 #1  0x00007f2cb093b476 __GI_raise (libc.so.6 + 0x42476)
                                                                 #2  0x00007f2cb09217f3 __GI_abort (libc.so.6 + 0x287f3)
                                                                 #3  0x000055b724e9a6a0 OsAbort (Xorg + 0x1da6a0)
                                                                 #4  0x000055b724e9fea9 n/a (Xorg + 0x1dfea9)
                                                                 #5  0x000055b724ea0e9a FatalError (Xorg + 0x1e0e9a)
                                                                 #6  0x000055b724d259de n/a (Xorg + 0x659de)
                                                                 #7  0x00007f2cb0922d90 __libc_start_call_main (libc.so.6 + 0x29d90)
                                                                 #8  0x00007f2cb0922e40 __libc_start_main_impl (libc.so.6 + 0x29e40)
                                                                 #9  0x000055b724d0e605 _start (Xorg + 0x4e605)
Mar 23 08:33:04 systemd[1]: systemd-coredump@21-2517-0.service: Deactivated successfully.
Mar 23 08:33:04 systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Mar 23 08:33:04 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Mar 23 08:33:04 systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 11.
Mar 23 08:33:04 systemd[1]: Stopped Light Display Manager.
Mar 23 08:33:04 systemd[1]: gpu-manager.service: Start request repeated too quickly.
Mar 23 08:33:04 systemd[1]: gpu-manager.service: Failed with result 'start-limit-hit'.
Mar 23 08:33:04 systemd[1]: Failed to start Detect the available GPUs and deal with any system changes.
Mar 23 08:33:04 systemd[1]: lightdm.service: Start request repeated too quickly.
Mar 23 08:33:04 systemd[1]: lightdm.service: Failed with result 'exit-code'.
Mar 23 08:33:04 systemd[1]: Failed to start Light Display Manager.
Mar 23 08:33:07 dbus-daemon[710]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Mar 23 08:34:24 acpid[705]: client 923[0:0] has disconnected
Mar 23 08:34:27 kernel: sysrq: This sysrq operation is disabled.
Mar 23 08:34:28 kernel: sysrq: This sysrq operation is disabled.
Mar 23 08:34:29 kernel: sysrq: This sysrq operation is disabled.
Mar 23 08:34:30 kernel: sysrq: Emergency Sync
Mar 23 08:34:30 kernel: Emergency Sync complete
Mar 23 08:34:31 kernel: sysrq: Emergency Remount R/O

[SMG]

ah sorry- i just posted what seemed relevant

c tags are for short snippets of code which are less than one line long. When you are posting multi-line output (such as something with 100 lines) please use code tags. Code tags retain the formatting from the terminal. c tags do not.