Manjaro 20.0.3 kernel 5.6.15-1 instability. Crashes with different severity, need help troubleshooting
ManjaroThis forum is for the discussion of Manjaro Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Manjaro 20.0.3 kernel 5.6.15-1 instability. Crashes with different severity, need help troubleshooting
My installation is about 4 days old, the only non standard driver used is one for my USB wifi adapter (https://github.com/aircrack-ng/rtl8812au). Maybe like every 24+ hours or so the system freezes. No input from keyboard/mouse can be given. The two crashes prior to the last one have been fixed by a hard reset, but the most recent one was even more severe. After hard reset button some of the fans started blasting and it seemed like it was stuck on some pre-post loop. Not even five+ second power button to power it off worked. I had to use the power switch on the back of the power supply.
Now; usually you would just look in journalctl and find errors and troubleshoot those. However there are no errors that leads up to this. That is; at least I can't seem to recognize any. As you probably understand I'm not a linux savvy - so I come here for help.
I see that NetworkManager is doing something prior to it crashing so does this indicate it's the non standard wifi apapter driver? As I was typing this the system crashed again. However now it just went black screen into high fan load pre-post loop. And now it worked to just push the power button to turn the pc off.
journalctl for latest crash:
Code:
Jun 08 20:34:11 manjaro msm_notifier[1472]: "qt5-translations"
Jun 08 20:34:13 manjaro dbus-daemon[676]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Jun 08 20:48:13 manjaro systemd[1]: Starting Cleanup of Temporary Directories...
Jun 08 20:48:13 manjaro systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Jun 08 20:48:13 manjaro systemd[1]: Finished Cleanup of Temporary Directories.
Jun 08 20:48:13 manjaro audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" ho>
Jun 08 20:48:13 manjaro audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hos>
Jun 08 20:48:13 manjaro kernel: audit: type=1130 audit(1591642093.091:93): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/>
Jun 08 20:48:13 manjaro kernel: audit: type=1131 audit(1591642093.091:94): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/>
Jun 08 21:01:01 manjaro CROND[3691]: (root) CMD (run-parts /etc/cron.hourly)
-- Reboot --
I can post more of it if needed.
The crashes seem to happen whenever, it's happened two times while I'm afk, and two times while I'm on the pc, but not as a result of running anything as far as I can tell. I have had Chrome, Thunderbird, Discord and a couple of terminals open for probably all the crashes.
RTX2070 on nVidia driver 440.82
Latest BIOS
Last edited by shuv1t; 06-08-2020 at 06:15 PM.
Reason: removed an IP address
First question I'd ask would be, why are you using that driver? Does the 'stock' driver work and connect you, and if so, does it create the same issue?
First question I'd ask would be, why are you using that driver? Does the 'stock' driver work and connect you, and if so, does it create the same issue?
The stock driver doesn't support the adapter, it had to be installed to get my wifi going.
Surprising; you're using the latest Manjaro, not an older one?
I thought I had version listed in thread name but I realize now that's the Kernel version; Release: 20.0.3 is output of lsb_release -a. Sorry about that.
I thought I had version listed in thread name but I realize now that's the Kernel version; Release: 20.0.3 is output of lsb_release -a. Sorry about that.
I don't mind testing this. However, do you read from my logs that the driver/device most likely is the issue?
Honestly unsure, based on what's posted. The only reason I suggested the driver module change is due to it being a non-standard module, and the initial post indicated your suspicions.
Have you checked the /etc/cron.hourly directory? ("ls /etc/cron.hourly"). That's mentioned there too, and the fact you have a --Reboot-- in the logs seems to say your system is rebooting itself. You can try running:
Code:
sudo service anacron stop
sudo service cronie stop
My cron.hourly only contains 0anacron which again only contains this:
Code:
#!/bin/sh
# Check whether 0anacron was run today already
if test -r /var/spool/anacron/cron.daily; then
day=`cat /var/spool/anacron/cron.daily`
fi
if [ `date +%Y%m%d` = "$day" ]; then
exit 0
fi
# Do not run jobs when on battery power
online=1
for psupply in AC ADP{0..9} ; do
sysfile="/sys/class/power_supply/$psupply/online"
if [ -f $sysfile ] ; then
if [ `cat $sysfile 2>/dev/null`x = 1x ]; then
online=1
break
else
online=0
fi
fi
done
if [ $online = 0 ]; then
exit 0
fi
/usr/sbin/anacron -s
So I doubt it's that. I suspect it to be one of the pages I had open in Chrome - because after closing a lot of them I've gone until now with no issues. Still with terminals, Discord and Thunderbird open. I'm going to continue uptime for a couple of more days and then opening some of the pages I thought might have been the culprit and let the system run with them open.
System just rebooted while I was working in Chrome. I guess I can throw out the idea about it being one of the pages I had shut down.
Code:
Jun 10 01:02:52 manjaro dbus-daemon[767]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.6705' (uid=1000 pid=70097 comm="/opt>
Jun 10 01:02:52 manjaro systemd[1]: Condition check resulted in Bluetooth service being skipped.
Jun 10 01:03:17 manjaro dbus-daemon[767]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
-- Reboot --
Jun 10 01:52:44 manjaro kernel: Linux version 5.6.15-1-MANJARO (builder@601a6c674820) (gcc version 10.1.0 (GCC)) #1 SMP PREEMPT Wed May 27 20:38:56 UTC 2020
As you can see from this there is nothing interesting going on here up until the crash. Aka there is almost 50 minutes of absolutely nothing up until the crash.
This is from .xsession-errors.old but tbh I don't see anything here either:
Code:
avaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
[1986:1991:0610/010112.339079:ERROR:ssl_client_socket_impl.cc(959)] handshake failed; returned -1, SSL error code 1, net_error -200
[1986:1991:0610/010112.339193:ERROR:ssl_client_socket_impl.cc(959)] handshake failed; returned -1, SSL error code 1, net_error -200
[1986:1991:0610/010112.340062:ERROR:ssl_client_socket_impl.cc(959)] handshake failed; returned -1, SSL error code 1, net_error -200
[1986:1991:0610/010112.341711:ERROR:ssl_client_socket_impl.cc(959)] handshake failed; returned -1, SSL error code 1, net_error -200
[0610/010252.184409:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly
** Message: 01:12:40.707: tray.vala:130: check updates
** Message: 01:12:40.709: tray.vala:159: 0 updates found
Is there an utility / a tool that I can install that lets me troubleshoot this more efficiently? Journalctl just doesn't seem to catch anything.
I installed rsyslog in desperation, but I guess I need to configure this to be running on the system all the time to log anything: also if I do - is it likely it will catch more than journalctl?
System just rebooted while I was working in Chrome. I guess I can throw out the idea about it being one of the pages I had shut down.
Code:
Jun 10 01:02:52 manjaro dbus-daemon[767]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.6705' (uid=1000 pid=70097 comm="/opt>
Jun 10 01:02:52 manjaro systemd[1]: Condition check resulted in Bluetooth service being skipped.
Jun 10 01:03:17 manjaro dbus-daemon[767]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
-- Reboot --
Jun 10 01:52:44 manjaro kernel: Linux version 5.6.15-1-MANJARO (builder@601a6c674820) (gcc version 10.1.0 (GCC)) #1 SMP PREEMPT Wed May 27 20:38:56 UTC 2020
As you can see from this there is nothing interesting going on here up until the crash. Aka there is almost 50 minutes of absolutely nothing up until the crash. This is from .xsession-errors.old but tbh I don't see anything here either:
Code:
avaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
[1986:1991:0610/010112.339079:ERROR:ssl_client_socket_impl.cc(959)] handshake failed; returned -1, SSL error code 1, net_error -200
[1986:1991:0610/010112.339193:ERROR:ssl_client_socket_impl.cc(959)] handshake failed; returned -1, SSL error code 1, net_error -200
[1986:1991:0610/010112.340062:ERROR:ssl_client_socket_impl.cc(959)] handshake failed; returned -1, SSL error code 1, net_error -200
[1986:1991:0610/010112.341711:ERROR:ssl_client_socket_impl.cc(959)] handshake failed; returned -1, SSL error code 1, net_error -200
[0610/010252.184409:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly
** Message: 01:12:40.707: tray.vala:130: check updates
** Message: 01:12:40.709: tray.vala:159: 0 updates found
Is there an utility / a tool that I can install that lets me troubleshoot this more efficiently? Journalctl just doesn't seem to catch anything. I installed rsyslog in desperation, but I guess I need to configure this to be running on the system all the time to log anything: also if I do - is it likely it will catch more than journalctl?
Well, I'm not sure there's much to catch...the "--Reboot--" says that something is (essentially) rebooting your system. You checked cron...check the anacron facility by running "cat /etc/anacrontab", and see what's in there.
And to ask an obvious question that I should have asked earlier; are you 100% sure the hardware is ok? I take it this is a desktop machine...for a simple experiment, you can try to boot and run a 'live' version of Linux, and I'd suggest something other than Manjaro for the test, like Fedora, Mint, or openSUSE. You can see if things still reboot/crash or if they just run normally. Hard to diagnose issues that don't leave traces in the logs, so sometimes it's easier to shotgun things, and see what sticks.
Well, I'm not sure there's much to catch...the "--Reboot--" says that something is (essentially) rebooting your system. You checked cron...check the anacron facility by running "cat /etc/anacrontab", and see what's in there.
Anacron is different than cron.
Code:
# /etc/anacrontab: configuration file for anacron
# See anacron(8) and anacrontab(5) for details.
SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
# the maximal random delay added to the base delay of the jobs
RANDOM_DELAY=45
# the jobs will be started during the following hours only
START_HOURS_RANGE=3-22
#period in days delay in minutes job-identifier command
1 5 cron.daily nice run-parts /etc/cron.daily
7 25 cron.weekly nice run-parts /etc/cron.weekly
@monthly 45 cron.monthly nice run-parts /etc/cron.monthly
Quote:
And to ask an obvious question that I should have asked earlier; are you 100% sure the hardware is ok? I take it this is a desktop machine...for a simple experiment, you can try to boot and run a 'live' version of Linux, and I'd suggest something other than Manjaro for the test, like Fedora, Mint, or openSUSE. You can see if things still reboot/crash or if they just run normally. Hard to diagnose issues that don't leave traces in the logs, so sometimes it's easier to shotgun things, and see what sticks.
The system has been running Win10 stable for almost a year. I can't say for 100% sure that it's not hardware since I guess an issue could manifest differently on a different OS. I'm still testing with different processes I had open at the time of crash. At this point I have my suspicions again so I'll report back with any findings in a couple of more days. Yes it's incredibly frustrating that I have nothing else to troubleshoot it with than the method of elimination.
Not getting anywhere with this. The system still crashes randomly every day or two with no apparent error messages. Also I believe the reason the system reports --Reboot-- is because I have to hard reset the system so it counts that as a reboot. Do some kind of utility that monitors *everything* exist so I might be able to figure this one out?
First of all, install the wifi driver recommended by Manjaro.
BTW, the fact that you did this outside of package management makes me think what else you might have "tweaked", possibly breaking something.
Is there a pattern to the reboots? I.e. when the system is under stress? Or always at a certain time? Or always X hours after booting? Etc., you get the picture.
You have to think what you did between then (when the system was working OK) and now. You installed a new OS. What else?
As an example, I once had a 64bit system that supported only 4GB of RAM (which I didn't know at first) - when I put in more RAM, it did not complain, everything worked fine until it started utilising more RAM, at which point it froze/crashed (crappy MSI laptop).
Quote:
Originally Posted by shuv1t
Do some kind of utility that monitors *everything* exist so I might be able to figure this one out?
I think in the world of professional system administration something like this exists. Still FOSS though. Monit comes to mind, but I could be wrong there. Needs to be set up beforehand.
I installed the driver recommended and blacklisted the old module like suggested in the thread. Rebooted and everything seems fine. Now it's just wait and see.
Prior to this install I was on Debian for like a week. I had similar issues there. Prior to Debian I have been running Windows 10 with no issues for over a year with the same hardware. The crashes are random, I tried the process of elimination by shutting down more and more programs I had running, but in the end I only had Chrome up with like 10 tabs and was writing an email from gmail when it crashed. I also had it crash under heavier load while playing a game.
All that being said if this fixes it I will be a bit upset at myself for not installing this driver when first recommended it. Thank you for your help so far.
I have no idea what to make of this though. I'm not overclocked.
edit: Okay I've been googling the error and it seems like my CPU might be borked. Quite annoying that it works fine on Windows. But eh, guess it was time for a new one anyway. I ordered a new one and will keep this unsolved until I've tested it.
Last edited by shuv1t; 07-13-2020 at 06:01 AM.
Reason: additional info
First question I'd ask would be, why are you using that driver? Does the 'stock' driver work and connect you, and if so, does it create the same issue?
Tbone relax your coming off rude. Not everyone knows what you know. You know an I know this is a hardware driver manufacture issue.
He will figure it out it is a two way radio and the drivers and the firmware.
Ask our Self what is rtl8812au_aircrack-ng and what it ask that device to do.
You know and I know it isn't finding the firmware from the stock driver.
And through the years the firmware keeps getting moved.
git clone https://github.com/gnab/rtl8812au.git
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
