Try the latest 4.14 LTS kernel
Thanks for the reply.
I am in Korea by the way ^-^
I also suspect the hardware. But the error message is on the screen and I want to use that to diagnose the fault accurately if possible.
97% doesn’t seem good to me because I have never had this kind of critical failure before except a few years ago with a machine that turned out to have a bad stick of RAM.
I’m used to 100% with Linux. I guess I’m spoiled.
I’ve booted Crunchbang++ maybe 20% more than Manjaro on this machine.
Thanks for the reply.
I think that is the kernel I downgraded from as it was giving me problems and I had to start X manually.
I will install this kernel, try again and report back.
You can keep 2-3 kernels or more and switch between them at boot from Grub Boot Menu. Make some tests and see what kernel suits your hardware better.
Without any logs that show something related to this error with comparison to non-error logs, you can never know if the error is fixed or you are just lucky this time and it’s coming back.
My suggestion is, wait until it happens and (after hard reboot) check journalctl. Preferably save that log for further investigation.
journalctl -b -1
Thanks for the reply.
I have booted several times since the error.
If I check journalctl now will I get the relevant info?
Or do I only get one chance and have to check it immediately after the error on the very next reboot?
If you remember about when it happened and if the logs are not overwritten, yes.
-b -1 flag asks for the previous boot logs. For available logs
list-boots IIRC. Check
Thanks for the advice.
Here is the journalctl log for the failed boot
I put them on Hastebin.
Too many chars for the forum.
I have no idea how to examine these logs or what I should look for.
I am no expert either.
So far, where the logs stop, the last thing was
systemd: Starting udev Kernel Device Manager...
which never started.
- Did you try other kernels as advised? What problems did you have that made you use this kernel?
- Crunchbang uses kernel 4.9. Did you ever try that in Manjaro?
- Did you have some USB device, or other devices connected during your failed boots?
I would suggest to try other kernels and maybe troubleshoot them instead.
This is the reason why I downgraded the kernel. X would not start as normal. Would just get a black screen with a flashing cursor.
Had to ctrl F2 (alt?) and start x manually by typing in a terminal ‘startx’.
Not yet, been busy.
I’m not sure - will check and report back.
No. No USB devices connected - no devices connected at all.
This has little or nothing to do with the kernel. GPU drivers, LightDM mostly suspects.
Hi, did you run memtest?
Downgrading the kernel fixed the issues on both Manjaro and Crunchbang installs, so it surely must have had something to do with the kernel.
That issue was on every boot and was fixed immediately once the kernel was downgraded.
Thanks for the reply - no I did not.
Will run today.
To which version did you downgrade?
I thought it was only Manjaro and only rare.
I may have misunderstood…
Is it not early to say it is solved? How many times did you reboot?
I wish you luck!!
Anyway, mark some post as the solution then.
Both are shown in the inxi output on the first post.
Sorry, you have misunderstood.
This was an error I had previously (not a hard lock up) and I fixed it by downgrading both Manjaro and Crunchbang to an older kernel (which you can see listed in the inxi output in the first post).
Thanks for taking the time to reply and trying to help.
It isn’t resolved - but I’m sure we can get there in the end.
Memtest ran for 11 hours today.
Was going to upgrade kernel to the latest again and see what happens.
I have just rebooted for the first time after memtest and what do you know - it hard locked again.
I’d better grab a pic and get the logs.
Failed boot #2
Just did this.
Got the weird bug that I encountered before (maybe I misremembered and I didn’t have to start X manually) where on every boot the screen stays blank until I hit a key or move the touchpad. Weird bug and I can live with it - but it is kind of annoying.
This bug does not happen on
I will leave 4.14 LTS kernel installed and as default for now, and live with the weird bug about having to hit a key or the touchpad to load up the desktop.
Let’s see if the hard lock up occurs under 4.14 LTS.
You can see a video (74mb) of the weird login display bug that occurs on 4.14 LTS.
Note the Conky displayed uptime at the end of the video.
Just realised that if I leave it alone and don’t touch the touchpad or keyboard it does eventually display the desktop on its own after about 40-50 seconds.
I think that is related to
Installed haveged and delay on startup solved.
Will now continue to use 4.14 LTS kernel and see if I encounter a hard lock up on this kernel.
Since upgrading to the latest lts kernel and applying all upgrades as they have been coming out…so far so good.
Will keep this updated if aything changes.