System loks up after upgrade from 14.04 to 16.04 Post: 302979116

Sponsored Content

Operating Systems Linux Ubuntu System loks up after upgrade from 14.04 to 16.04 Post 302979116 by migurus on Tuesday 9th of August 2016 04:18:13 PM

08-09-2016

Registered User

System loks up after upgrade from 14.04 to 16.04

After upgrading from 14 LTS to 16 LTS the system started getting these hard lockups, where nothing works, can't get to it through ssh, or console.

I have asked for help on Launchpad Ubuntu forum, but so far no replies.

in /var/log/kern.log:

Code:

Aug 7 21:47:26 XPS-8700 kernel: [26947.581772] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [systemd-timesyn:2646]
Aug 7 21:47:26 XPS-8700 kernel: [26947.581774] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) bnep snd_hda_codec_hdmi dcdbas intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel arc4 kvm irqbypass crct10dif_pclmul crc32_pclmul ath9k ath9k_common aesni_intel ath9k_hw aes_x86_64 lrw gf128mul glue_helper ablk_helper ath cryptd mac80211 snd_hda_codec_realtek joydev snd_hda_codec_generic ath3k btusb serio_raw btrtl input_leds btbcm btintel bluetooth snd_hda_intel snd_hda_codec cfg80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event snd_rawmidi snd_pcm mei_me lpc_ich snd_seq mei snd_seq_device snd_timer snd soundcore shpchp mac_hid parport_pc ppdev lp parport autofs4 uas usb_storage hid_generic usbhid hid nouveau i915 mxm_wmi wmi ttm r8169 mii i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt ahci fb_sys_fops libahci drm video fjes

with some more debug dump info.

I re-run memtest and it was OK.

What should I post to get help?

My system is stock DELL XPS 8700 with I7-4790. nothing special about this h/w.

I hope I won't have to revert back to 14.04, as I did have issues with kbd/mouse dead after booting. In 16.04 this problem is gone, but the lockups are even worse. Some day system runs for hours with no problems, then it would lock up within an hour after boot while just reading email.

Any pointers are appreciated.

Last edited by Don Cragun; 08-09-2016 at 06:01 PM.. Reason: Add CODE and ICODE tags.

migurus

View Public Profile for migurus

Find all posts by migurus

4 More Discussions You Might Find Interesting

1. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode

2. UNIX for Advanced & Expert Users

how to make a full system backup excluding data and restoring it to a new system

Hi, In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way : - Make a full system backup excluding the user file system (this...

3. AIX

How to upgrade firmware of a system that doesn't boot?

any ideas ???????

4. AIX

Cloning a system via mksysb backup from one system and restore to new system

Hello All, I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance. Please use CODE tags for sample input, sample output, and for code...

LEARN ABOUT OPENSOLARIS

systemd-fsck

SYSTEMD-FSCK@.SERVICE(8)				       systemd-fsck@.service					  SYSTEMD-FSCK@.SERVICE(8)

NAME

       systemd-fsck@.service, systemd-fsck-root.service, systemd-fsck - File system checker logic

SYNOPSIS

       systemd-fsck@.service

       systemd-fsck-root.service

       /lib/systemd/systemd-fsck

DESCRIPTION

       systemd-fsck@.service and systemd-fsck-root.service are services responsible for file system checks. They are instantiated for each device
       that is configured for file system checking.  systemd-fsck-root.service is responsible for file system checks on the root file system, but
       only if the root filesystem was not checked in the initramfs.  systemd-fsck@.service is used for all other file systems and for the root
       file system in the initramfs.

       These services are started at boot if passno in /etc/fstab for the file system is set to a value greater than zero. The file system check
       for root is performed before the other file systems. Other file systems may be checked in parallel, except when they are on the same
       rotating disk.

       systemd-fsck does not know any details about specific filesystems, and simply executes file system checkers specific to each filesystem
       type (/sbin/fsck.*). This helper will decide if the filesystem should actually be checked based on the time since last check, number of
       mounts, unclean unmount, etc.

       If a file system check fails for a service without nofail, emergency mode is activated, by isolating to emergency.target.

KERNEL COMMAND LINE

       systemd-fsck understands these kernel command line parameters:

       fsck.mode=
	   One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done
	   when the file system checker deems them necessary.  "force" unconditionally results in full file system checks.  "skip" skips any file
	   system checks.

       fsck.repair=
	   One of "preen", "yes", "no". Controls the mode of operation. The default is "preen", and will automatically repair problems that can be
	   safely fixed.  "yes" will answer yes to all questions by fsck and "no" will answer no to all questions.

SEE ALSO

       systemd(1), fsck(8), systemd-quotacheck.service(8), fsck.btrfs(8), fsck.cramfs(8), fsck.ext4(8), fsck.fat(8), fsck.hfsplus(8),
       fsck.minix(8), fsck.ntfs(8), fsck.xfs(8)

systemd 237														  SYSTEMD-FSCK@.SERVICE(8)