[SOLVED] 5 Beta 3, Kernel 3.19 hard crashing

[paultgg]

[SOLVED] Recent updates to Beta 3 seem to have fixed the issue.

[UPDATE] Having this issue with beta 3 as well.

I've been having problems with stability after the upgrade to the 3.19 kernel. Started with the rc kernels, and now with the release. Computer crashes hard (have to hold down the power button to reboot). Sometimes it crashes on boot, other times after being at the desktop for a while. The 3.18 kernel has been stable. How do you troubleshoot hard crashes?

[doktor5000]

After the reboot, check the complete logs of the last boot with

Code: Select all

journalctl -a -b-1 --no-pager

or post them here. This needs to be run as root, or you need to add your user to the systemd-journal group, see https://wiki.mageia.org/en/Mageia_4_Errata#journalctl

[paultgg]

Thanks. Happened again this morning. Computer crashed once after idling on the desktop. Rebooted, and it crashed a second time before I could open a terminal, su, and get the command entered. Results are attached.

[doktor5000]

Hmmm, the major part of that file is about that /usr filesystem cannot be unmounted during boot,
that is from line 978 to line 6309. It looks really funny and weird ...

Code: Select all

Feb 12 07:20:09 lappy systemd[1]: Unit usr.mount is bound to inactive service. Stopping, too.
Feb 12 07:20:09 lappy systemd[1]: Unmounting /usr...
Feb 12 07:20:09 lappy kernel: EXT4-fs (sda5): re-mounted. Opts: acl
Feb 12 07:20:09 lappy kernel: EXT4-fs (sda7): re-mounted. Opts: acl
Feb 12 07:20:09 lappy systemd[1]: Started Remount Root and Kernel File Systems.
Feb 12 07:20:09 lappy systemd[1]: Starting Configure read-only root support...
Feb 12 07:20:09 lappy systemd[1]: Started Rebuild Hardware Database.
Feb 12 07:20:09 lappy systemd[1]: Started First Boot Wizard.
Feb 12 07:20:09 lappy systemd[1]: Started Rebuild Dynamic Linker Cache.
Feb 12 07:20:09 lappy systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Feb 12 07:20:09 lappy systemd[1]: Started Create System Users.
Feb 12 07:20:09 lappy systemd[1]: Starting Create Static Device Nodes in /dev...
Feb 12 07:20:09 lappy systemd[1]: Started Import network configuration from initramfs.
Feb 12 07:20:09 lappy umount[529]: umount: /usr: target is busy
Feb 12 07:20:09 lappy umount[529]: (In some cases useful info about processes that
Feb 12 07:20:09 lappy umount[529]: use the device is found by lsof(8) or fuser(1).)
Feb 12 07:20:09 lappy systemd[1]: usr.mount mount process exited, code=exited status=32
Feb 12 07:20:09 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:09 lappy systemd[1]: Unit usr.mount is bound to inactive service. Stopping, too.
Feb 12 07:20:09 lappy systemd[1]: Unmounting /usr...

[...]

Feb 12 07:20:10 lappy systemd[1]: Unmounting /usr...
Feb 12 07:20:10 lappy umount[1465]: umount: /usr: target is busy
Feb 12 07:20:10 lappy umount[1465]: (In some cases useful info about processes that
Feb 12 07:20:10 lappy umount[1465]: use the device is found by lsof(8) or fuser(1).)
Feb 12 07:20:10 lappy systemd[1]: usr.mount mount process exited, code=exited status=32
Feb 12 07:20:10 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:10 lappy systemd[1]: Unit usr.mount is bound to inactive service. Stopping, too.
Feb 12 07:20:10 lappy systemd[1]: Unmounting /usr...
Feb 12 07:20:10 lappy umount[1467]: umount: /usr: target is busy
Feb 12 07:20:10 lappy umount[1467]: (In some cases useful info about processes that
Feb 12 07:20:10 lappy umount[1467]: use the device is found by lsof(8) or fuser(1).)
Feb 12 07:20:10 lappy systemd[1]: usr.mount mount process exited, code=exited status=32
Feb 12 07:20:10 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:10 lappy systemd[1]: Unit usr.mount is bound to inactive service. Stopping, too.
Feb 12 07:20:10 lappy systemd[1]: Unmounting /usr...
Feb 12 07:20:10 lappy umount[1469]: umount: /usr: target is busy
Feb 12 07:20:10 lappy umount[1469]: (In some cases useful info about processes that
Feb 12 07:20:10 lappy umount[1469]: use the device is found by lsof(8) or fuser(1).)
Feb 12 07:20:10 lappy systemd[1]: Failed unmounting /usr.

[...]

Feb 12 07:20:12 lappy umount[3470]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3472]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3474]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3476]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy kernel: cfg80211: Regulatory domain changed to country: CA
Feb 12 07:20:12 lappy kernel: cfg80211:  DFS Master region: FCC
Feb 12 07:20:12 lappy kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Feb 12 07:20:12 lappy kernel: cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Feb 12 07:20:12 lappy kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
Feb 12 07:20:12 lappy umount[3478]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3481]: umount: /usr: target is busy
Feb 12 07:20:12 lappy kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2400 mBm), (0 s)
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy kernel: cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2400 mBm), (0 s)
Feb 12 07:20:12 lappy kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
Feb 12 07:20:12 lappy umount[3484]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3486]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3488]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3490]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3492]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3494]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3496]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3498]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3500]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3501]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3504]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3506]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3508]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3510]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3512]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3515]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3517]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3519]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3522]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3525]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3527]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3529]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3533]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3535]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3537]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3539]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3541]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3543]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3545]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3547]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3549]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3551]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3553]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3555]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3557]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3559]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3561]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3563]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3565]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3567]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3569]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3571]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3573]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3575]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3577]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3579]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3581]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3583]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3585]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3587]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3589]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3591]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3593]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.
Feb 12 07:20:12 lappy umount[3596]: umount: /usr: target is busy
Feb 12 07:20:12 lappy systemd[1]: Failed unmounting /usr.

Could you show the output as root of

Code: Select all

lsblk -fl
cat /etc/fstab

[paultgg]

Here are the output of the commands, and another journalctl output after another crash. The crash this time happened before the desktop showed up, although while I'm writing this, I'm booted into 3.19 and everything's been okay for a few minutes.

[ITA84]

I'm not entirely sure the problem lies with /usr, since he says there's no issue with kernel 3.18. Do those 'Failed unmounting /usr.' messages appear in the journal when you boot with 3.18? I ask also because there seems to be a similar bug on Fedora 20, but without crashes/panics:

https://bugzilla.redhat.com/show_bug.cgi?id=1159648

Although I don't see any other particular errors in the journal...

[paultgg]

Unfortunately, I didn't try the live version of beta 3 - I went right to the installer, so I don't remember if I had the /usr mount error on the 3.18 kernel. That said, I've tried a few reinstalls of beta 3. I've only managed to get beta 3 to boot to a desktop once. Most of the time now, it boots to emergency mode. I'm able to start X as root from there, but it still crashes after a time. I've attached another boot journal. The only thing I see hanging for any period of time is around these lines:

Code: Select all

Feb 15 16:31:58 lappy kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
Feb 15 16:31:58 lappy kernel: ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM


Any other thoughts?

[MadmanRB]

Is kernel 3.19 the kernel Mageia 5 is offering for the final may I ask?
As I have seen some major concerns for 3.19 as its hot off the press.

[doktor5000]

Yes it will be at least 3.19.

[paultgg]

Uploading a few more log files. I tried changing the clocksource, since the computer crashed twice after the "clocksource tsc unstable" error, but the system still crashes within a minute or two. I see there are a couple of other 3.19 freezing bugs in bugzilla. Not sure if I should open another...

[MadmanRB]

Hmm, not sure if I like that.
Why not use kernel 3.18? I only ask as I have doubts about 3.19 right now. The above report is one of the ones I heard of, that worry me.

[paultgg]

Here's a picture of the clocksource error.

[doktor5000]

Well, it seems the crash happens before, after a nouveau crash.

Also, how and to which clocksource did you try to change?

[paultgg]

I tried using "clocksource=acpi-pm" in the boot options.

[doktor5000]

Better try clocksource=jiffies or clocksource=hpet

[paultgg]

I tried both clocksources, and had crashes with both. The hpet option seemed to work better on its first boot, but I noticed the clock was out. When I started the chrony service, had a hard crash. On reboot, it crashed before it brought me to the usual emergency console login.

[doktor5000]

As mentioned before, I don't think the clocksource is the problem, but rather the graphics driver ...

[paultgg]

How can I confirm and/or fix the driver issue? I'm not familiar with nouveau.

[doktor5000]

Try xdriver=vesa kernel boot option or maybe rd.blacklist=nouveau rd.blacklist=nvidia xdriver=vesa

[paultgg]

Tried both with no change. I also tried reinstalling with the legacy boot version, and had better luck getting to the desktop. Everything seemed solid after the first boot, but after doing some updates and rebooting, the crashes returned. Any other ideas?

I also noticed that, after the updates and reboot, that my clock is out. During the install, I set the clock to synchronize using chrony, and my system clock is set to local time. I'm dual-booting, and when I went into windows, I saw that my clock was off. I also noticed that chrony was one of the updates I did before the crashes started after rebooting (I don't know if the clock was out before the reboots, since I didn't have a clock on the screen). Don't know if that makes any difference.

[paultgg]

Looks like the recent kernel, video driver, and whatever-else updates have fixed whatever the issue was.