Even after upgrades/updates, laptop freezes[Poss. Resolved]

[wutsinterweb]

It locks up sometimes even with ctrl-alt-esc

[SMG]

It locks up sometimes even with ctrl-alt-esc

How to you resolve the "lock"?

There have been some recent updates to the Cinnamon and related files (within the past few weeks). If you have installed those already, it's probably time to start looking at logs.

Do you have the most recent BIOS version installed?

[wutsinterweb]

The laptop is getting old so no new BIOS and even if it did, I'd have to install Windows to update it, so no go on that.

I don't actually recover but just power down and restart when it locks up, I have no other choice.

How do I post those files so we can look at them?

[SMG]

The laptop is getting old so no new BIOS and even if it did, I'd have to install Windows to update it, so no go on that.

The inxi data seems to indicate you have a "special" computer. I think this is the first time I've seen "INVALID" for a motherboard model. It appears there is only one newer version 5ECN97WW(V9.01) according to G580 Laptop (Lenovo) - Type 20150 . However, the listed fix is "Fix issue: BIOS and boot menu can't be accessd after windows recovery." which I do not expect would help this issue.

Code: Select all

Machine:
  Type: Laptop System: LENOVO product: 20150 v: Lenovo G580 serial: <filter> 
  Chassis: type: 10 v: Lenovo G580 serial: <filter> 
  Mobo: LENOVO model: INVALID v: 31900003WIN8 STD MLT serial: <filter> 
  UEFI: LENOVO v: 5ECN95WW(V9.00) date: 12/19/2012 

I don't actually recover but just power down and restart when it locks up, I have no other choice.

How do I post those files so we can look at them?

You power down because of a freeze. Then you boot up again. After it finishes booting, run the following in a terminal:

Code: Select all

journalctl -rb -1 | nc termbin.com 9999

The command prints the journal log information of the prior boot cycle in reverse order and sends it to termbin. It will return with a url address that you should post in your next reply.

[wutsinterweb]

Thanks, will do!

[wutsinterweb]

BTW, it seems to happen every night between 8 and 9:00

[SMG]

BTW, it seems to happen every night between 8 and 9:00

Then I will probably see it tomorrow as I am adjusting myself to the start of "saving daylight" where the sun is in the wrong place in the sky according to the clock and by body.

[wutsinterweb]

Hahah FOR REAL man!

[SMG]

It's for real for women like me too.

[wutsinterweb]

Ahah! So that is YOU in the Avatar! Cool! There are just not enough women in technology. In Tech College I advocated for more females students as an Ambassador and counseled high school women about going into technology. Most of the best scientists I worked with were women. I miss that work.

[SMG]

Ahah! So that is YOU in the Avatar!

It is me looking up at a thermal imaging camera. My spectacles were cool, but, for some reason, my shoulders must have been really hot that day. It looks like my shoulders were bare, but they were covered with a regular short-sleeve t-shirt.

[wutsinterweb]

May I ask: aare you National Labs or Mil/DoD/E?

[SMG]

The work I have done has all been commercial/private sector.

[wutsinterweb]

You should work at Sandia or something. I did for a while.

[wutsinterweb]

that journal comand ran but didnt return a URL

[SMG]

that journal comand ran but didnt return a URL

That's the first time anyone mentioned that happening, so I'm not sure what the issue might be. We can try a different method. After rebooting because you killed the power due to system freeze, run:

Code: Select all

journalctl -rb -1 | tee >(gzip --stdout > journalctl_$USER.gz)

This command will write the prior system log to the file journalctl_(yourname).gz and to your screen. The file will be located in your /home/login_name directory. I believe the file should be small enough to attach it to a reply on the forum, but if not, maybe you can put the first 20-30 lines between code tags in a reply.

[wutsinterweb]

will do, next time it crashes again.

[wutsinterweb]

Code: Select all

bucky1@bucky1:~$ journalctl -rb -1 | tee >(gzip --stdout > journalctl_$USER.gz)
-- Logs begin at Thu 2020-07-16 17:39:48 EDT, end at Sat 2021-03-20 17:58:22 EDT. --
Mar 17 12:19:43 bucky1 systemd-journald[336]: Journal stopped
Mar 17 12:19:43 bucky1 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 17 12:19:43 bucky1 systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 17 12:19:43 bucky1 systemd[1]: Shutting down.
Mar 17 12:19:43 bucky1 systemd[1]: Reached target Power-Off.
Mar 17 12:19:43 bucky1 systemd[1]: Finished Power-Off.
Mar 17 12:19:43 bucky1 systemd[1]: systemd-poweroff.service: Succeeded.
Mar 17 12:19:43 bucky1 systemd[1]: Reached target Final Step.
Mar 17 12:19:43 bucky1 systemd[1]: Finished Shuts down the "live" preinstalled system cleanly.
Mar 17 12:19:43 bucky1 systemd[1]: casper.service: Succeeded.
Mar 17 12:19:43 bucky1 systemd[1]: Starting Shuts down the "live" preinstalled system cleanly...
Mar 17 12:19:43 bucky1 systemd[1]: Reached target Shutdown.
Mar 17 12:19:43 bucky1 systemd[1]: Stopped Remount Root and Kernel File Systems.
Mar 17 12:19:43 bucky1 systemd[1]: systemd-remount-fs.service: Succeeded.
Mar 17 12:19:43 bucky1 systemd[1]: Reached target Unmount All Filesystems.
Mar 17 12:19:43 bucky1 systemd[1]: Deactivated swap /swapfile.
Mar 17 12:19:43 bucky1 systemd[1]: swapfile.swap: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Mar 17 12:19:42 bucky1 systemd[1]: lvm2-monitor.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Create System Users.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-sysusers.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Create Static Device Nodes in /dev.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Mar 17 12:19:42 bucky1 systemd[1]: Stopped target Local File Systems (Pre).
Mar 17 12:19:42 bucky1 systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/ECD4-B461.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-fsck@dev-disk-by\x2duuid-ECD4\x2dB461.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Unmounted /run/timeshift/backup.
Mar 17 12:19:42 bucky1 systemd[1]: run-timeshift-backup.mount: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Unmounted /boot/efi.
Mar 17 12:19:42 bucky1 systemd[1]: boot-efi.mount: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Unmounting /run/timeshift/backup...
Mar 17 12:19:42 bucky1 systemd[1]: Unmounting /boot/efi...
Mar 17 12:19:42 bucky1 systemd[1]: Stopped target Local File Systems.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Create Volatile Files and Directories.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Network Time Synchronization.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-timesyncd.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Network Name Resolution.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-resolved.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_backlight.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-backlight@backlight:intel_backlight.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-update-utmp.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Mar 17 12:19:42 bucky1 systemd[1]: Stopping Network Time Synchronization...
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Load Kernel Modules.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-modules-load.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Apply Kernel Variables.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-sysctl.service: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:intel_backlight...
Mar 17 12:19:42 bucky1 systemd[1]: Deactivating swap /swapfile...
Mar 17 12:19:42 bucky1 systemd[1]: Stopped target Swap.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-ask-password-wall.path: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped target Local Encrypted Volumes.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped target System Initialization.
Mar 17 12:19:42 bucky1 systemd[1]: Closed UUID daemon activation socket.
Mar 17 12:19:42 bucky1 systemd[1]: uuidd.socket: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Closed Syslog Socket.
Mar 17 12:19:42 bucky1 systemd[1]: syslog.socket: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Closed D-Bus System Message Bus Socket.
Mar 17 12:19:42 bucky1 systemd[1]: dbus.socket: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Closed CUPS Scheduler.
Mar 17 12:19:42 bucky1 systemd[1]: cups.socket: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
Mar 17 12:19:42 bucky1 systemd[1]: avahi-daemon.socket: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Closed ACPID Listen Socket.
Mar 17 12:19:42 bucky1 systemd[1]: acpid.socket: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped target Sockets.
Mar 17 12:19:42 bucky1 systemd[1]: Removed slice User and Session Slice.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped target Slices.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped CUPS Scheduler.
Mar 17 12:19:42 bucky1 systemd[1]: cups.path: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped ACPI Events Check.
Mar 17 12:19:42 bucky1 systemd[1]: acpid.path: Succeeded.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped target Paths.
Mar 17 12:19:42 bucky1 systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
Mar 17 12:19:42 bucky1 systemd[1]: systemd-ask-password-plymouth.path: Succeeded.

[SMG]

Those lines are part of the normal shutdown process and can happen if you pressed the power button to stop the freeze. We'll need to go back further than that. How big is the file? You might be able to post it as an attachment.

[wutsinterweb]

dump1.odt

(113.41 KiB) Downloaded 26 times

ok there it is.