You are not logged in.

#1 2020-12-10 13:05:06

superos
New Member
Registered: 2020-12-06
Posts: 3

Laptop crash then instant poweroff

Hi great people
I installed bunsenlabs a week ago. No problems during install and my first test run messing around for 1 hour upgrading system, testing some applications etc was just fine. Next day I got a crash after less than one hour use. It now crashes in less than 2 hours. The crash is a total poweroff and sometimes I get some screen artefacts to the left for one second then a total poweroff.

My first thought was temperature, but after checking with sensors and listening to my fan I could not make sense of it so I tried to look at graphics problems. So I killall -9 compton process (now I see there is a menu for that). But no luck, it still crash.

I than ran memtest for 7-8 hours. All fine.

Then I thought about graphics driver issues. Reading a little bit about it I found I was using i915

superos@ux:~$ inxi -G
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.3.6

So if my understanding is correct this is included in the kernel which led me to try another kernel at boot (I got these two installed).

ii  linux-image-4.19.0-12-amd64
ii  linux-image-4.19.0-13-amd64

But no luck so then I did something I have never done before and downloaded an older kernel from debian stretch, then installed using using dpkg -i .

So now I boot this one:
ii  linux-image-4.9.0-14-amd64

This seems to have solved the problem. No crash for two days. Happy days!

I also considered just moving the i915.ko file from the old kernel over to the newer kernel overwriting /lib/modules/4.19.0-13-amd64/kernel/drivers/gpu/drm/i915/i915.ko , but that is probably not a good idea.

Using journal for the first time trying to see the reason for the crash I got no sensible information (at least for an amateur like me). My crash was at 13:24, then a reboot at 13:26.

Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.37' (uid=1000 pid=4754 comm="xfce4-screenshooter ")
Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.37' (uid=1000 pid=4754 comm="xfce4-screenshooter ")
Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Activating service name='org.gtk.vfs.GoaVolumeMonitor' requested by ':1.37' (uid=1000 pid=4754 comm="xfce4-screenshooter ")
Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Activating service name='org.gtk.vfs.AfcVolumeMonitor' requested by ':1.37' (uid=1000 pid=4754 comm="xfce4-screenshooter ")
Dec 10 13:21:06 ux org.gtk.vfs.AfcVolumeMonitor[1081]: Volume monitor alive
Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Activating service name='org.gtk.vfs.GPhoto2VolumeMonitor' requested by ':1.37' (uid=1000 pid=4754 comm="xfce4-screenshooter ")
Dec 10 13:21:06 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Dec 10 13:21:06 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:06 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:07 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:08 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:09 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:10 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:11 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:12 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:13 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:14 ux org.gtk.vfs.Daemon[1081]: mkdir failed on directory /var/cache/samba: Permission denied
Dec 10 13:21:54 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Activating service name='org.gtk.vfs.Metadata' requested by ':1.6' (uid=1000 pid=1135 comm="thunar --daemon ")
Dec 10 13:21:54 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Successfully activated service 'org.gtk.vfs.Metadata'
Dec 10 13:21:54 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.6' (uid=1000 pid=1135 comm="thunar --daemon ")
Dec 10 13:21:54 ux org.freedesktop.thumbnails.Thumbnailer1[1081]: Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Dec 10 13:21:54 ux org.freedesktop.thumbnails.Thumbnailer1[1081]: Registered thumbailer evince-thumbnailer -s %s %u %o
Dec 10 13:21:54 ux dbus-daemon[1081]: [session uid=1000 pid=1079] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
-- Reboot --
Dec 10 13:26:30 ux systemd[846]: Reached target Paths.

What more can I do to troubleshoot this?

Regards
superos

Last edited by superos (2020-12-10 17:25:41)

Offline

#2 2020-12-10 14:05:59

damo
....moderator....
Registered: 2015-08-20
Posts: 6,498

Re: Laptop crash then instant poweroff

superos wrote:

...

What more can I do to troubleshoot this?

Regards
superos

I'm not sure, but it would be lots easier for us to read the terminal output if you used "[ code ]" tags.


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

Board footer

Powered by FluxBB