How to figure out what is causing my laptop to crash

jbodhorn · 2016-09-20 19:42:17

I have a few laptops that I run Arch linux on, but only one am I really having a problem where it seems to randomly crash. The crashes are not completely random, but they do only seem to happen when I'm typing on the command line. The crashes don't necessarily happen when executing commands but when I'm typing them. The majority of the time these crashes happen when I'm using ssh, I have a couple raspberry pi's and an odroid-xu4 I work on via ssh, but I also have two laptops running arch linux that I use for personal minecraft servers that I usually work on via ssh.

I finally decided to ask for help with this issue because today I wasn't using ssh, I was dd'ing an img file in one terminal window and using the command line to copy some files to an external drive in another terminal window when I had this same type of crash happen.

I'm pretty sure dd had finished and I was making a folder to copy my files into and... crash... My screen goes black and I have white horizontal lines of varying thickness flickering across my screen. This seems to be specific to this laptop and I'm not sure why it happens, I've never seen this happen on any other machine I've ran arch linux on.

This always happens very suddenly, no warning what so ever, the laptop doesn't lag or seem to present any issues prior to this happening. I'll be typing my next command and black screen with flickering white horizontal lines. I'm running arch with gnome and use the gnome terminal included with gnome, I dual boot this laptop with arch and win 10 and don't seem to have any issues with random crashes while using windows, only in arch. I've not seen this happen in the past when running ubuntu gnome or fedora with gnome, only with arch and only on this laptop...

The laptop in question is an HP Elitebook 2740p convertible laptop it's got a core i5 m560 dual core @ 2.67GHz, intel integrated graphics, 8gb ram, 160gb intel ssd, wacom touchscreen(2 finger touch and also pen with eraser). I don't recall the crash happening before gnome was installed when I was setting up arch but I've never ran this laptop for any longer than needed without a DE, I'm not sure that it's a gnome problem because I've ran gnome on this laptop in the past with other 'nix OS.

If anyone can point me in the right direction as to diagnosing this problem I could really use the help, this isn't something that's come up for me on any other machine running linux...

infinarchy · 2016-09-20 20:00:39

empty

Last edited by infinarchy (2017-11-04 21:44:52)

jbodhorn · 2016-09-20 21:22:08

infinarchy wrote:

Do u have any log files for us?

What log files would I need to post, this is part of the problem. I'm not even sure where to look or how to find certain sections of my journal

journalctl -xe

outputs

-- Logs begin at Wed 2016-04-20 14:09:10 EDT, end at Tue 2016-09-20 16:53:05 EDT. --
Sep 20 16:53:05 elitebook org.gnome.Shell.desktop[560]: (gnome-shell:560): Clutter-CRITICAL **: clutter_layout_manager_get_child_meta: asserrtion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed
Sep 20 16:53:05 elitebook org.gnome.Shell.desktop[560]: (gnome-shell:560): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Sep 20 16:53:05 elitebook org.gnome.Shell.desktop[560]: (gnome-shell:560): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Sep 20 16:53:05 elitebook org.gnome.Shell.desktop[560]: (gnome-shell:560): Clutter-CRITICAL **: clutter_layout_manager_get_child_meta: asserrtion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed
Sep 20 16:53:05 elitebook org.gnome.Shell.desktop[560]: (gnome-shell:560): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Sep 20 16:53:05 elitebook org.gnome.Shell.desktop[560]: (gnome-shell:560): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed

those three lines are repeated literally over and over and over,

journalctl -xe

shows 1001 lines and all that it shows is those three lines repeated as posted.

in the help for journalctl I believe the -S option was to output from a certain timestamp but I kept getting a failed to parse error

[joe@elitebook ff7c56d0e6b141d69973d8681fcb4285]$ journalctl -S "Sep 20 14:45:00"
Failed to parse timestamp: Sep 20 14:45:00

when I looked at the bugzilla for the error posted above other people systems become unresponsive but music keeps playing, my system goes black screen with flickering white lines, music and video if playing freezes too. Earlier today when this happened the only thing I had open aside from gnome terminal was chrome, the only thing common to all my crashes that I know of is the gnome terminal, and as I said I've never had this issue on other machines running Arch with gnome.

jbodhorn · 2016-09-20 22:01:03

infinarchy wrote:

Do u have any log files for us?

Here's a pastebin of my journal during the hour in which the crash happened, the crash happened toward the end of the hour shortly before I posted my question

http://pastebin.com/bp1zq5tJ

infinarchy · 2016-09-20 22:15:19

empty

Last edited by infinarchy (2017-11-04 21:44:48)

jbodhorn · 2016-09-20 23:05:04

infinarchy wrote:

Do you work with another Terminal (like xterm) and tell us if your laptop crashs again.

Can do, I'll be playing with the terminal a lot tonight so another crash is bound to happen. I was looking through my pastebin and I'm guessing the crash was here at 14:40:03:

Sep 20 14:40:03 elitebook kernel: iwlwifi 0000:43:00.0: Too many chunks: 20
Sep 20 14:52:12 elitebook dbus[309]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'

The time is about right and the missing chunk of time after that would be when I booted into windows to post my question and use chkdsk to scan the ntfs formatted drive that was plugged in during the crash.

to get that output I used journalctl -n90000 > /home/joe/log.txt then I opened the txt in gedit and copied the hour during during the crash to pastebin.

R00KIE · 2016-09-20 23:22:14

I would start by ruling out hardware problems, run memtest and see if the ram is ok, also check journalctl's output for any errors, I'm thinking MCE (machine check exception) errors but it could also be something else.

Is this a recent problem? You mention gnome, did it receive any update lately? Any update to graphics driver?

jbodhorn · 2016-09-21 01:18:20

R00KIE wrote:

I would start by ruling out hardware problems, run memtest and see if the ram is ok, also check journalctl's output for any errors, I'm thinking MCE (machine check exception) errors but it could also be something else.
Is this a recent problem? You mention gnome, did it receive any update lately? Any update to graphics driver?

Long story short I don't think I have any hardware problems and the crashing I'm describing has been happening since I first installed arch, I reinstalled arch twice since the first install and each time I have this crashing problem. I mentioned gnome because every time I've had this crash happen it was when I was typing in the gnome terminal. I tried using xterm, seriously can you not copy and paste in xterm!?

I've done hardware tests(hp has a bunch built into the bios) and I've tested the ram, no errors. I never had this problem running any other linux on this laptop and even windows being windows hasn't crashed on me in quite a while on this laptop. Even when I have problems in windows it's usually only programs freezing, I end task them restart them and keep working.

My time on this laptop usually ends up being on windows, if this laptop was having hardware issues that were causing crashes I'm pretty sure that would be much more apparent in windows than linux. Honestly I'd use Arch on this laptop a lot more if it weren't so buggy, I can't even get lid close action do nothing to work, no matter what I do the damn thing goes to sleep...

The crashing has been an issue on this laptop since installing arch, I only have a 160gb ssd in this laptop and it's my primary laptop so I had to make a choice, it came down to windows with ubuntu or arch. I don't like ubuntu's standard DE and ubuntu gnome is slow to get updates... I've honestly just been hoping I'd get an update that would fix it but the crashing, but it's been an on going problem. It happens from go on a fresh install of arch and gnome. I'd run a different linux OS but I've grown to not really like anything but arch, as far as switching from gnome to another DE once again, I really don't like any other DE.

My biggest issue with switching to another OS or even switching DE is my touchscreen, arch with gnome has been the only linux OS/DE that I've actually gotten my touchscreen to work properly. Even with arch I had finally gotten my touchscreen working and setup and it worked for a while then an update killed finger touch, pen kept working. I could not get it working again, I even went and compiled and installed all the wacom drivers needed, yet still my touchscreen would not respond to finger touch, I have a post on these forums about it... Then one day after an update I noticed my touchscreen started working again, I only found out it was working again when I accidentally touched the screen, at that point I had completely given up on the touchscreen working in arch again... atm I'm afraid to update wacom anything since the touchscreen and pen are actually working, I've blocked it from being updated actually...

Tomorrow I'm supposed to be getting a new laptop, I might just start searching for a new OS to run on this laptop along side arch. Once the new laptop comes I'll be able to wipe windows from this one since I'll have it on the new laptop,

jbodhorn · 2016-09-21 03:29:32

ok, happened again, I don't believe I had a terminal open at all, I was about to mount a samba share in nautilus and crash. This time in my journal it notes a reboot, that would be me holding down the power button after taking a pic of the screen with my phone.

here's the pic
http://s22.postimg.org/kmwf3rjbl/IMG_20 … 756695.jpg

and the section of my journal before the crash

Sep 20 22:34:29 elitebook google-chrome.desktop[1432]: [415:415:0920/223429:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState()
Sep 20 22:34:34 elitebook google-chrome.desktop[1432]: [415:415:0920/223434:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState()
Sep 20 22:36:22 elitebook wpa_supplicant[357]: wlo1: WPA: Group rekeying completed with 00:1f:90:f2:9c:17 [GTK=TKIP]
Sep 20 22:39:25 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:39:25 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:39:25 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:39:25 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:39:25 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:39:25 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:39:25 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:39:26 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:39:26 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:39:26 elitebook gnome-settings-daemon.desktop[462]: (gnome-settings-daemon:462): media-keys-plugin-WARNING **: Could not find accelerator for accel id 101
Sep 20 22:44:27 elitebook sudo[3418]:      joe : TTY=pts/0 ; PWD=/home/joe/Downloads ; USER=root ; COMMAND=/usr/bin/sync
Sep 20 22:44:27 elitebook sudo[3418]: pam_unix(sudo:session): session opened for user root by joe(uid=0)
Sep 20 22:44:27 elitebook sudo[3418]: pam_unix(sudo:session): session closed for user root
Sep 20 22:44:33 elitebook kernel: mmc0: card aaaa removed
Sep 20 22:44:33 elitebook kernel: sdhci-pci 0000:44:06.1: Will use DMA mode even though HW doesn't fully claim to support it.
Sep 20 22:44:33 elitebook dbus[291]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Sep 20 22:44:33 elitebook systemd[1]: Starting Hostname Service...
Sep 20 22:44:33 elitebook dbus[291]: [system] Successfully activated service 'org.freedesktop.hostname1'
Sep 20 22:44:33 elitebook systemd[1]: Started Hostname Service.
Sep 20 22:44:36 elitebook kernel: mmc0: new SDHC card at address aaaa
Sep 20 22:44:36 elitebook kernel: mmcblk0: mmc0:aaaa SU08G 7.40 GiB 
Sep 20 22:44:36 elitebook kernel:  mmcblk0: p1 p2
Sep 20 22:44:36 elitebook kernel: EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Sep 20 22:44:36 elitebook udisksd[301]: Mounted /dev/mmcblk0p2 at /run/media/joe/202638e1-4ce4-45df-9a00-ad725c2537bb on behalf of uid 1000
Sep 20 22:44:36 elitebook gvfs-udisks2-volume-monitor[586]: disc.c:350: error opening file BDMV/index.bdmv
Sep 20 22:44:36 elitebook gvfs-udisks2-volume-monitor[586]: disc.c:350: error opening file BDMV/BACKUP/index.bdmv
Sep 20 22:44:36 elitebook tracker-miner-fs.desktop[525]: Tracker-Message: Mount point added for URN 'urn:nepomuk:datasource:202638e1-4ce4-45df-9a00-ad725c2537bb'
Sep 20 22:44:36 elitebook tracker-miner-fs.desktop[525]: Tracker-Message:   Not crawling, removable devices disabled in config
Sep 20 22:44:36 elitebook tracker-miner-fs.desktop[525]: Tracker-Message: Mount point 'file:///run/media/joe/202638e1-4ce4-45df-9a00-ad725c2537bb' already exists in store: 'urn:uuid:3b35c7f8-1950-b5ac-8d2d-cc7d7f687188'
Sep 20 22:44:36 elitebook udisksd[301]: Mounted /dev/mmcblk0p1 at /run/media/joe/boot on behalf of uid 1000
Sep 20 22:44:36 elitebook gvfs-udisks2-volume-monitor[586]: disc.c:350: error opening file BDMV/index.bdmv
Sep 20 22:44:36 elitebook gvfs-udisks2-volume-monitor[586]: disc.c:350: error opening file BDMV/BACKUP/index.bdmv
Sep 20 22:44:36 elitebook tracker-miner-fs.desktop[525]: Tracker-Message: Mount point added for URN 'urn:nepomuk:datasource:22E0-C711'
Sep 20 22:44:36 elitebook tracker-miner-fs.desktop[525]: Tracker-Message:   Not crawling, removable devices disabled in config
Sep 20 22:44:36 elitebook tracker-miner-fs.desktop[525]: Tracker-Message: Mount point 'file:///run/media/joe/boot' already exists in store: 'urn:uuid:1d3faa9b-e304-7c84-20e8-aaa4eacd2f25'
Sep 20 22:44:36 elitebook dbus-daemon[402]: Activating service name='org.gnome.Shell.HotplugSniffer'
Sep 20 22:44:36 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Shell.HotplugSniffer'
Sep 20 22:44:38 elitebook org.gnome.Shell.desktop[559]: (gnome-shell:559): Gjs-WARNING **: JS ERROR: TypeError:  is null
Sep 20 22:44:38 elitebook org.gnome.Shell.desktop[559]: ContentTypeDiscoverer<._onContentTypeGuessed/<@resource:///org/gnome/shell/ui/components/autorunManager.js:133
Sep 20 22:44:38 elitebook org.gnome.Shell.desktop[559]: _proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:86
Sep 20 22:45:07 elitebook sudo[3472]:      joe : TTY=pts/0 ; PWD=/home/joe/Downloads ; USER=root ; COMMAND=/usr/bin/umount /dev/mmcblk0p1
Sep 20 22:45:07 elitebook sudo[3472]: pam_unix(sudo:session): session opened for user root by joe(uid=0)
Sep 20 22:45:07 elitebook udisksd[301]: Cleaning up mount point /run/media/joe/boot (device 179:1 is not mounted)
Sep 20 22:45:07 elitebook tracker-miner-fs.desktop[525]: Tracker-Message: Mount:'boot' with UUID:'22E0-C711' now unmounted from:'/run/media/joe/boot'
Sep 20 22:45:07 elitebook dbus[291]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Sep 20 22:45:07 elitebook systemd[1]: Starting Hostname Service...
Sep 20 22:45:07 elitebook sudo[3472]: pam_unix(sudo:session): session closed for user root
Sep 20 22:45:08 elitebook dbus[291]: [system] Successfully activated service 'org.freedesktop.hostname1'
Sep 20 22:45:08 elitebook systemd[1]: Started Hostname Service.
Sep 20 22:45:11 elitebook sudo[3477]:      joe : TTY=pts/0 ; PWD=/home/joe/Downloads ; USER=root ; COMMAND=/usr/bin/umount /dev/mmcblk0p2
Sep 20 22:45:11 elitebook sudo[3477]: pam_unix(sudo:session): session opened for user root by joe(uid=0)
Sep 20 22:45:11 elitebook udisksd[301]: Cleaning up mount point /run/media/joe/202638e1-4ce4-45df-9a00-ad725c2537bb (device 179:2 is not mounted)
Sep 20 22:45:11 elitebook tracker-miner-fs.desktop[525]: Tracker-Message: Mount:'1.3 GB Volume' with UUID:'202638e1-4ce4-45df-9a00-ad725c2537bb' now unmounted from:'/run/media/joe/202638e1-4ce4-45df-9a00-ad725c2537bb'
Sep 20 22:45:11 elitebook sudo[3477]: pam_unix(sudo:session): session closed for user root
Sep 20 22:45:19 elitebook kernel: mmc0: card aaaa removed
Sep 20 22:45:19 elitebook kernel: sdhci-pci 0000:44:06.1: Will use DMA mode even though HW doesn't fully claim to support it.
Sep 20 22:46:22 elitebook wpa_supplicant[357]: wlo1: WPA: Group rekeying completed with 00:1f:90:f2:9c:17 [GTK=TKIP]
Sep 20 22:48:23 elitebook google-chrome.desktop[1432]: [644:644:0920/224823:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState()
Sep 20 22:48:23 elitebook google-chrome.desktop[1432]: [644:644:0920/224823:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState()
Sep 20 22:49:16 elitebook sudo[3575]:      joe : TTY=pts/0 ; PWD=/home/joe/Downloads ; USER=root ; COMMAND=/usr/bin/nano /home/joe/.ssh/known_hosts
Sep 20 22:49:16 elitebook sudo[3575]: pam_unix(sudo:session): session opened for user root by joe(uid=0)
Sep 20 22:49:28 elitebook sudo[3575]: pam_unix(sudo:session): session closed for user root
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.ControlCenter.SearchProvider'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.Contacts.SearchProvider'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.Documents'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.Nautilus'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.Boxes.SearchProvider'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.Calculator.SearchProvider'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.Calendar'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.clocks'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.seahorse.Application'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.Photos'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Activating service name='org.gnome.EpiphanySearchProvider'
Sep 20 22:53:53 elitebook systemd[367]: Starting GNOME Terminal Server...
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Calculator.SearchProvider'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Boxes.SearchProvider'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.ControlCenter.SearchProvider'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Nautilus'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.clocks'
Sep 20 22:53:53 elitebook PackageKit[1121]: resolve transaction /5_acedadce from uid 1000 finished with success after 0ms
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Terminal'
Sep 20 22:53:53 elitebook systemd[367]: Started GNOME Terminal Server.
Sep 20 22:53:53 elitebook PackageKit[1121]: resolve transaction /6_ecceddad from uid 1000 finished with success after 0ms
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Photos'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Calendar'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Contacts.SearchProvider'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.EpiphanySearchProvider'
Sep 20 22:53:53 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Documents'
Sep 20 22:53:54 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.seahorse.Application'
Sep 20 22:53:54 elitebook org.gnome.Photos[402]: GEGL-geglmodule.c-Message: Module '/usr/lib/gegl-0.3/matting-levin.so' load error: libumfpack.so.5: cannot open shared object file: No such file or directory
Sep 20 22:53:54 elitebook org.gnome.Nautilus[402]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Sep 20 22:53:54 elitebook org.gnome.Photos[402]: GEGL-geglmodule.c-Message: Module '/usr/lib/gegl-0.3/lens-correct.so' load error: liblensfun.so.1: cannot open shared object file: No such file or directory
Sep 20 22:53:54 elitebook org.gnome.Nautilus[402]: /usr/share/nautilus-python/extensions/nautilus-admin.py:18: PyGIWarning: GConf was imported without specifying a version first. Use gi.require_version('GConf', '2.0') before import to ensure that the right version gets loaded.
Sep 20 22:53:54 elitebook org.gnome.Nautilus[402]:   from gi.repository import Nautilus, GObject, GConf, Gtk, GLib
Sep 20 22:53:54 elitebook org.gnome.Nautilus[402]: Initializing nautilus-open-terminal extension
Sep 20 22:53:54 elitebook org.gnome.Documents[402]: Gjs-Message: JS LOG: Can't find a valid getting started PDF document
Sep 20 22:53:54 elitebook dbus-daemon[402]: Activating service name='com.intel.dleyna-renderer'
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: dLeyna core version 0.5.0
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: dleyna-renderer-service version 0.5.0
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Type[0] Level[0x13] Mask[0x4C] Flags[0x4F]
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Load file [/home/joe/.config/dleyna-renderer-service.conf]
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: [General settings]
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Never Quit: F
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Connector Name: dbus
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Port: 0
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Push host port: 0
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: [Logging settings]
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Log Type : 0
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Log Level: 0x13
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: [Network filtering settings]
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Enabled : F
Sep 20 22:53:54 elitebook dleyna-renderer-service[3766]: Entries: (null)
Sep 20 22:53:54 elitebook dbus-daemon[402]: Successfully activated service 'com.intel.dleyna-renderer'
Sep 20 22:56:22 elitebook wpa_supplicant[357]: wlo1: WPA: Group rekeying completed with 00:1f:90:f2:9c:17 [GTK=TKIP]
Sep 20 22:57:13 elitebook dbus-daemon[402]: Activating service name='org.gnome.Nautilus'
Sep 20 22:57:13 elitebook dbus-daemon[402]: Successfully activated service 'org.gnome.Nautilus'
Sep 20 22:57:13 elitebook org.gnome.Nautilus[402]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Sep 20 22:57:13 elitebook org.gnome.Nautilus[402]: /usr/share/nautilus-python/extensions/nautilus-admin.py:18: PyGIWarning: GConf was imported without specifying a version first. Use gi.require_version('GConf', '2.0') before import to ensure that the right version gets loaded.
Sep 20 22:57:13 elitebook org.gnome.Nautilus[402]:   from gi.repository import Nautilus, GObject, GConf, Gtk, GLib
Sep 20 22:57:13 elitebook org.gnome.Nautilus[402]: Initializing nautilus-open-terminal extension
Sep 20 22:57:13 elitebook org.gnome.Nautilus[402]: (nautilus:3934): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' does not exist
Sep 20 22:57:13 elitebook dbus[291]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Sep 20 22:57:13 elitebook systemd[1]: Starting Hostname Service...
Sep 20 22:57:13 elitebook dbus[291]: [system] Successfully activated service 'org.freedesktop.hostname1'
Sep 20 22:57:13 elitebook systemd[1]: Started Hostname Service.
Sep 20 22:57:16 elitebook gvfsd[427]: ** (process:3949): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Operation not supported by backend
-- Reboot --

I see when my volume buttons stopped working, I went to watch a youtube video and was stuck at full volume till I could change it from the top bar drop down menu... I swear it's only this laptop I have constant issues with arch on, yet windows 7, 8.1, and 10 all run fine on it.... as much as I like arch, this laptop just doesn't, I think this is the first time I wasn't trying to type a command in a terminal that I had this happen...

R00KIE · 2016-09-21 11:00:54

I would be inclined to say it might be a graphics driver problem, but it might still be a hardware problem that is only exposed when certain conditions are met. As a test you could install another DE, for example xfce, and use it without compositing active and see if you can make the machine crash.

You also mention ntfs, which driver are you using, the one from the kernel or fuse?

Post the output of 'lspci -nn' so everyone can have a better idea of the hardware we are talking about.

jbodhorn · 2016-09-21 13:34:30

lspci -nn

00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 02)
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
00:16.3 Serial controller [0700]: Intel Corporation 5 Series/3400 Series Chipset KT Controller [8086:3b67] (rev 06)
00:19.0 Ethernet controller [0200]: Intel Corporation 82577LM Gigabit Network Connection [8086:10ea] (rev 05)
00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05)
00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05)
00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 [8086:3b44] (rev 05)
00:1c.3 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 [8086:3b48] (rev 05)
00:1d.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation QM57 Chipset LPC Interface Controller [8086:3b07] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b2f] (rev 05)
00:1f.6 Signal processing controller [1180]: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem [8086:3b32] (rev 05)
43:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6200 [8086:4239] (rev 2c)
44:06.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 06)
44:06.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 25)
44:06.2 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev bb)
ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c62] (rev 02)
ff:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2d01] (rev 02)
ff:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2d10] (rev 02)
ff:02.1 Host bridge [0600]: Intel Corporation 1st Generation Core i3/5/7 Processor QPI Physical 0 [8086:2d11] (rev 02)
ff:02.2 Host bridge [0600]: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved [8086:2d12] (rev 02)
ff:02.3 Host bridge [0600]: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved [8086:2d13] (rev 02)

[joe@elitebook ~]$ sudo pacman -Ss ntfs
[sudo] password for joe: 
extra/ntfs-3g 2016.2.22-1 [installed]
    NTFS filesystem driver and utilities

promarbler14 · 2016-09-21 22:18:08

I would place bets on it being the Intel (2D graphics) driver. What do you get with 'pacman -Q | grep xf86' ? Try uninstalling the xf86-video-intel driver if it's present and (if necessary) configure your xorg.conf.d to use the "modesetting" driver. I, personally, haven't had much issue with the driver, but several people (on these forums) have found the modesetting driver preferable due to these random graphical issues. However, the modesetting driver isn't GPU-accelerated (AFAIK), and thus will be marginally slower if you choose to go that path.

Also, for the sleep issue? Try looking at /etc/systemd/logind.conf and specify the lidswitch option. My guess would be that systemd is somehow defying what upower/gnome is trying to enforce and using its own settings instead... I haven't tried it myself, though.

If you're up to it, you could try rebuilding the xorg-server and the xf86-video-intel driver with asserts (debug) enabled, and running that to try and capture a bug.

Other (mildly overkill) options would be adding debug and drm debug flags to the kernel command line. This will provide very verbose details of the kernel and systemd's operations, which could clue you in to the causes of the problems above.

Hope this helps with your issues!

(P.S. add -b, -b -1 flags to your journalctl command to restrict to current, last boots (respectively), or use something like --since -4h to get the last four hours, for example)

jbodhorn · 2016-09-21 22:37:59

promarbler14 wrote:

I would place bets on it being the Intel (2D graphics) driver. What do you get with 'pacman -Q | grep xf86' ? Try uninstalling the xf86-video-intel driver if it's present and (if necessary) configure your xorg.conf.d to use the "modesetting" driver. I, personally, haven't had much issue with the driver, but several people (on these forums) have found the modesetting driver preferable due to these random graphical issues. However, the modesetting driver isn't GPU-accelerated (AFAIK), and thus will be marginally slower if you choose to go that path.
Also, for the sleep issue? Try looking at /etc/systemd/logind.conf and specify the lidswitch option. My guess would be that systemd is somehow defying what upower/gnome is trying to enforce and using its own settings instead... I haven't tried it myself, though.
If you're up to it, you could try rebuilding the xorg-server and the xf86-video-intel driver with asserts (debug) enabled, and running that to try and capture a bug.
Other (mildly overkill) options would be adding debug and drm debug flags to the kernel command line. This will provide very verbose details of the kernel and systemd's operations, which could clue you in to the causes of the problems above.
Hope this helps with your issues!
(P.S. add -b, -b -1 flags to your journalctl command to restrict to current, last boots (respectively), or use something like --since -4h to get the last four hours, for example)

Thanks you much for your response, I'm currently DD'ing a full backup image before I do anything. About the kernel options, is it correct that I'd have to recompile the kernel to add them?

I'm not quite sure which approach I should take atm, I was DD'ing the backup because I was considering trying a different DE. I've only read a bit about the topic but I read that I could leave gnome, disable it, and install another DE alongside. Once DD is done I'm also going to use rsync to make another backup, because I'm thinking it will probably work out better if I remove gnome before installing another DE and I'm thinking I'm thinking an rsync copy might come in real handy if I switch back to gnome

I don't know if there would be any conflicts when installing a DE alongside my existing DE, and honestly I don't really care to find out. I know lots of people like KDE and xfce, my experience with both is very limited, once I found gnome I fell in love. I know there have been lots of improvements since I used either KDE or xfce so maybe I'll get lucky and not hate them as I did in the past.

Seeing as I plan to remove gnome before switching my DE I guess I may as well try your suggestions first. My compiling experience is limited and I'll have to do some reading before I dive in. If you have any links that I should read before taking up this project I'd be grateful to read them

Thanks again for your response

Last edited by jbodhorn (2016-09-21 22:40:17)

R00KIE · 2016-09-21 23:25:28

The modesetting driver _is_ accelerated using glamor. I've been using it here without any problems with an Intel iGPU.

One thing you could try is have a second machine which captures the output of dmesg (this is all done via serial port) as I suspect you may not be catching the last bit of information in the logs and which might have important clues to what the problem may be.

frank604 · 2016-09-22 00:14:42

If you are using any extensions in gnome, please disable them during your testing. I too echo the above advice and try a different DE for a day or until a crash would of occurred in Gnome.

Here's a checklist of items to check:
- Video driver, try modesetting (I believe the above above person is confusing this with nomodeset which does not have acceleration).
- Change DE to eliminate the cause from your current DE
- Try termite (it has a copy and paste built in using cntrl+shift+c/v) I am recommending trying a different terminal just to ensure the issue is not related to gnome-terminal.
- Create a new user and get into X via new user. Do not import your dotfiles. See if crash happens.
- How much ram do you have? Do you have an active swap file/partition?

promarbler14 · 2016-09-22 02:58:24

He mentioned that a crash seems to have occurred without the gnome-terminal program open, so it's unlikely that that software is (solely) to blame.

Is the computer otherwise functional when it "crashes"? That is, can you ssh in, blindly type, or still hear sounds or music for some time?

Assuming that the system is toast upon seeing that screen (seems likely), can you use a serial console (suggested above) or the netconsole facility with an ethernet cable (see here) to try and capture any oopsie or panic?

By kernel command line, I mean the text passed to the linux kernel at boot via grub2 or syslinux (two popular bootloaders). You can view the kernel command line used via cat /proc/cmdline . At boot, you can edit the selected menu item to easily pass parameters to the kernel. No kernel recompilation necessary!

To recompile a package in the repository, one can still use the Arch Build System (abs) and makepkg to build the package from a "PKGBUILD." Simply copy the /var/abs/extra/xf86-video-intel directory (synced by abs) to a preferred directory, and make your tweaks to the PKGBUILD. In this case, you may want to prepend the file with a line ' options=(!strip debug) ', and insert the line '--enable-debug \' right after the line that has "./configure" . Running makepkg -si in that directory should be adequate for you to recompile and reinstall the driver (hopefully with asserts). That's generally how it goes. Keep in mind that asserts will generally make the driver slower.

"Kernel parameters" that will likely assist you in diagnosing the exact issue (esp. w/ an external console/log):

debug drm.debug=0xe log_buf_len=1M ignore_loglevel

(append this to the /boot/vmlinuz-linux line).

Feel free to listen to the advice others have stated above, of course.

jbodhorn · 2016-09-22 03:03:43

frank604 wrote:

If you are using any extensions in gnome, please disable them during your testing. I too echo the above advice and try a different DE for a day or until a crash would of occurred in Gnome.
Here's a checklist of items to check:
- Video driver, try modesetting (I believe the above above person is confusing this with nomodeset which does not have acceleration).
- Change DE to eliminate the cause from your current DE
- Try termite (it has a copy and paste built in using cntrl+shift+c/v) I am recommending trying a different terminal just to ensure the issue is not related to gnome-terminal.
- Create a new user and get into X via new user. Do not import your dotfiles. See if crash happens.
- How much ram do you have? Do you have an active swap file/partition?

I rules out gnome terminal with the last crash, it wasn't being used for the last crash. I never thought to disable extensions, I can do that but should I remove them also or just disable them?

I have 8gb ram and a 2gb swap

jbodhorn · 2016-09-22 03:16:08

promarbler14 wrote:

He mentioned that a crash seems to have occurred without the gnome-terminal program open, so it's unlikely that that software is (solely) to blame.
Is the computer otherwise functional when it "crashes"? That is, can you ssh in, blindly type, or still hear sounds or music for some time?
Assuming that the system is toast upon seeing that screen (seems likely), can you use a serial console (suggested above) or the netconsole facility with an ethernet cable (see here) to try and capture any oopsie or panic?
By kernel command line, I mean the text passed to the linux kernel at boot via grub2 or syslinux (two popular bootloaders). You can view the kernel command line used via cat /proc/cmdline . At boot, you can edit the selected menu item to easily pass parameters to the kernel. No kernel recompilation necessary!
To recompile a package in the repository, one can still use the Arch Build System (abs) and makepkg to build the package from a "PKGBUILD." Simply copy the /var/abs/extra/xf86-video-intel directory (synced by abs) to a preferred directory, and make your tweaks to the PKGBUILD. In this case, you may want to prepend the file with a line ' options=(!strip debug) ', and insert the line '--enable-debug \' right after the line that has "./configure" . Running makepkg -si in that directory should be adequate for you to recompile and reinstall the driver (hopefully with asserts). That's generally how it goes. Keep in mind that asserts will generally make the driver slower.
"Kernel parameters" that will likely assist you in diagnosing the exact issue (esp. w/ an external console/log):
debug drm.debug=0xe log_buf_len=1M ignore_loglevel
(append this to the /boot/vmlinuz-linux line).
Feel free to listen to the advice others have stated above, of course.

Thanks for the tip on trying to ssh in after the crash and all the others. When the laptop crashes everything stops so I doubt I'll be able to get ssh access but I'll try, I'll have to go the Ethernet route although I do have a USB network cable, I'm not sure if it will work with Linux but it might be worth a try.

The crash that inspired my inquiry suggests I won't be able to ssh though, I was trying to get my phone to take a pic of the screen but the computer shut down before I could get my camera app open. The second crash the computer rebooted just after I got the picture so I'll be on a limited time frame.

I'm not too good with grub, but it's the bootloader I'm using and even with my limited skills I think I can do what you have suggested

I've yet to use Abs but I've been wanting to play with it, now I seem to have a good excuse

Thank you all for the help

promarbler14 · 2016-09-22 21:48:10

Also, try installing Intel CPU microcode updates (intel-ucode) from the repositories. You'll need to regenerate the grub config afterwards. Microcode updates generally help performance and fix hardware bugs!

jbodhorn · 2016-09-22 21:49:44

promarbler14 wrote:

Also, try installing Intel CPU microcode updates (intel-ucode) from the repositories. You'll need to regenerate the grub config afterwards. Microcode updates generally help performance and fix hardware bugs!

I've done that already

Arch Linux

#1 2016-09-20 19:42:17

How to figure out what is causing my laptop to crash

#2 2016-09-20 20:00:39

Re: How to figure out what is causing my laptop to crash

#3 2016-09-20 21:22:08

Re: How to figure out what is causing my laptop to crash

#4 2016-09-20 22:01:03

Re: How to figure out what is causing my laptop to crash

#5 2016-09-20 22:15:19

Re: How to figure out what is causing my laptop to crash

#6 2016-09-20 23:05:04

Re: How to figure out what is causing my laptop to crash

#7 2016-09-20 23:22:14

Re: How to figure out what is causing my laptop to crash

#8 2016-09-21 01:18:20

Re: How to figure out what is causing my laptop to crash

#9 2016-09-21 03:29:32

Re: How to figure out what is causing my laptop to crash

#10 2016-09-21 11:00:54

Re: How to figure out what is causing my laptop to crash

#11 2016-09-21 13:34:30

Re: How to figure out what is causing my laptop to crash

#12 2016-09-21 22:18:08

Re: How to figure out what is causing my laptop to crash

#13 2016-09-21 22:37:59

Re: How to figure out what is causing my laptop to crash

#14 2016-09-21 23:25:28

Re: How to figure out what is causing my laptop to crash

#15 2016-09-22 00:14:42

Re: How to figure out what is causing my laptop to crash

#16 2016-09-22 02:58:24

Re: How to figure out what is causing my laptop to crash

#17 2016-09-22 03:03:43

Re: How to figure out what is causing my laptop to crash

#18 2016-09-22 03:16:08

Re: How to figure out what is causing my laptop to crash

#19 2016-09-22 21:48:10

Re: How to figure out what is causing my laptop to crash

#20 2016-09-22 21:49:44

Re: How to figure out what is causing my laptop to crash

Board footer