i have insane random crashes , it all started when i set laptop lid switch to switch off display and left the laptop running for the night , and i tried to open it , no response , no tty , nothing , just frozen
what i’ve tried :
i changed the kernel from grub i disabled the switch off option , nothing seems to be working
also this happened after the last update , but i don’t know if there is a relation
First the BIOS from 2018 should be installed on a Dell Latitude E6420 with Sandy Bridge and not the old one from 2011. The optimal hardware support for this Dell along with its sleep mode and Touchpad can then be found in Linux419, less so in Linux54 and even worse in Linux 510. That reflects mine Experience with that Dell …
it happens before anything starts , not even the log screen
but anyway ill try that and report
btw , the frequency of these freezes are much less now , but it happens for some reason on random times
ill try that
but fyi , when i freezes , even the keyboard is not responsive , the caps lock lamp even can’t work
and sometimes it blinks
i think it’s not freeze , more like a crash , can i see the log of that crash in journalctl , or all the log data is gone ?
EDIT :
it just crashed and “journalctl -b -1” can’t get to crash time
it crashed at 17:15 , and the last record in journal was 17:06
here it is anyway
>un 25 16:59:22 mohamed-pc kernel: audit: type=1334 audit(1624633162.635:205): prog-id=20 op=LOAD
Jun 25 16:59:22 mohamed-pc kernel: audit: type=1334 audit(1624633162.635:206): prog-id=21 op=LOAD
Jun 25 16:59:22 mohamed-pc kernel: audit: type=1334 audit(1624633162.635:207): prog-id=22 op=LOAD
Jun 25 16:59:22 mohamed-pc audit: BPF prog-id=21 op=LOAD
Jun 25 16:59:22 mohamed-pc audit: BPF prog-id=22 op=LOAD
Jun 25 16:59:22 mohamed-pc systemd[1]: Starting Time & Date Service...
Jun 25 16:59:22 mohamed-pc dbus-daemon[591]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jun 25 16:59:22 mohamed-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
Jun 25 16:59:22 mohamed-pc kernel: audit: type=1130 audit(1624633162.888:208): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr>
Jun 25 16:59:22 mohamed-pc systemd[1]: Started Time & Date Service.
Jun 25 16:59:52 mohamed-pc systemd[1]: systemd-timedated.service: Deactivated successfully.
Jun 25 16:59:53 mohamed-pc kernel: audit: type=1131 audit(1624633192.935:209): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr>
Jun 25 16:59:53 mohamed-pc kernel: audit: type=1334 audit(1624633192.955:210): prog-id=22 op=UNLOAD
Jun 25 16:59:53 mohamed-pc kernel: audit: type=1334 audit(1624633192.955:211): prog-id=21 op=UNLOAD
Jun 25 16:59:53 mohamed-pc kernel: audit: type=1334 audit(1624633192.955:212): prog-id=20 op=UNLOAD
Jun 25 16:59:52 mohamed-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostnam>
Jun 25 16:59:52 mohamed-pc audit: BPF prog-id=22 op=UNLOAD
Jun 25 16:59:52 mohamed-pc audit: BPF prog-id=21 op=UNLOAD
Jun 25 16:59:52 mohamed-pc audit: BPF prog-id=20 op=UNLOAD
Jun 25 17:01:01 mohamed-pc CROND[13400]: (root) CMD (run-parts /etc/cron.hourly)
Jun 25 17:01:01 mohamed-pc CROND[13399]: (root) CMDEND (run-parts /etc/cron.hourly)
Jun 25 17:06:05 mohamed-pc audit[13681]: USER_ACCT pid=13681 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_time acct="mohamed" exe="/usr/bi>
Jun 25 17:06:05 mohamed-pc kernel: audit: type=1101 audit(1624633565.761:213): pid=13681 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_time>
Jun 25 17:06:05 mohamed-pc kernel: audit: type=1103 audit(1624633565.765:214): pid=13681 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:setcred grantors=pam_unix,pam_env acct="mohamed">
Jun 25 17:06:05 mohamed-pc audit[13681]: CRED_ACQ pid=13681 uid=1000 auid=1000 ses=1 subj==unconfined msg='op=PAM:setcred grantors=pam_unix,pam_env acct="mohamed" exe="/usr/bin/crontab" hostn>
Jun 25 17:06:05 mohamed-pc crontab[13681]: (mohamed) LIST (mohamed)
I’m not as smart as fabby, and not sure if this will help you but there is a error in the log that is referenced in this thread on the arch forum with the same symptoms as you descibe, I refer to this error: kernel: i915 0000:00:02.0: [drm] ERROR Atomic update failure on pipe A. There are more people with this error.
There are some possible solutions, the user in the arch thread added a option in their grub config as described in post 5 in that thread. You could try it, it is not a difficult procedure. Make sure you take precautions
i’ll try that , btw , the post you mention says that it has something to do with thermal monitoring widget he had
did the last update has something like that updated / installed ? because it started happening since the last update , i’ve installed manjaro for the past three years , nothing happened , not a single freeze
Checking out the Stable Updates posts for clues might help, there are detailed package lists that are updated. I’m not familiar with your DE so a more experienced user might chime in here to help out.
i found out a workaround , i created a new user and the problem is solved , so im 100% sure that it was the power settings that i edited , but i don’t know exactly what happened to cause all these crashes , it was just changing the lid switch , could this lead to crashes , or is it a bug in the last update ?
So you have an issue in your user profile and finding out which exact setting you changed is going to take weeks if not months, therefore, we’re going to do the following:
Verify that the new user has access to the same groups as your old one by executing groups and comparing the output of both users.
groups k3rnelpanic
groups k3rnelpanic2
(Where obviously, k3rnelpanic is your old user and k3rnelpanic2 is your new one.)
E.G. if k3rnelpanic is a member of operator and k3rnelpanic2 isn’t, execute:
usermod --append --groups operator k3rnelpanic2
Copy all data files from your old profile into your new one
If that worked and you had no errors, remove the documents from your old user:
rm --recursive /home/k3rnelpanic/Documents/*
repeat for:
Pictures
Videos
Music
.thunderbird
.mozilla/firefox/
Templates, and everything else that is important to you.
Linux games like Battle of Wesnoth have their game data stored under ~/.local/share/ E.G. ~/.local/share/wesnoth/
After everything has been copied over, disable the old user so you cannot accidentally log on:
usermod --lock k3rnelpanic
If you would have theming going on, don’t do everything in one day but do this at the rate of 1 application / theme / whatever per day and if the same issue crops up again, roll back your last change and thus you’ve now pinpointed the exact setting that made your old user misbehave.
in 1 month delete the entire home directory of your old user, but don’t delete the user itself so that in 6 months time files still owned by that user will still show up under its username.
If you ever migrate to a new machine, just don’t migrate the old user: only the new one.
From now on, start making backups so you can roll back and never have to do this again:
I’ve marked this answer as the solution to your question as it is by far the best answer you’ll get.
However, if you disagree with my choice, please feel free to take any other answer as the solution to your question or even remove the solution altogether: You are in control! (If you disagree with my choice, just send me a personal message and explain why I shouldn’t have done this or or if you agree)
P.S. In the future, please don’t forget to come back and click the 3 dots below the answer to mark a solution like this below the answer that helped you most:
so that the next person that has the exact same problem you just had will benefit from your post as well as your question will now be in the “solved” status.
or 
if you agree)
