Announcement

Collapse
No announcement yet.

Kubuntu 14.04.4 hangs during startup on two different kernels

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Kubuntu 14.04.4 hangs during startup on two different kernels

    I'm pretty sure this is unrelated to my other question here, but since a power drop today (blown breaker in the house, so shouldn't have involved a surge), when I try to start either current (3.13.0-93-generic or 3.13.0-93-lowlatency, not sure which it's starting) or previous (3.13.0-92-generic) kernels in 14.04.4, the boot process stops fairly far along. I don't think it's a coincidence that both kernel versions hang a dozen or so lines after reporting that samba has produced "exit code 1" with a red "fail" in the right hand column.

    The first startup after the power was restored, the system checked the file system on at least one partition, and didn't report any errors, though something scrolled past pretty rapidly before getting there about orphan blocks -- my OS and /home are on a 256 MB SSD, partitions formatted as EXT4, as is the 16.04.1 that I'm currently using to post this. I don't have the exact error messages (can't screen dump them at that stage), but I can try to look for log files if someone can point me to the correct log, or I can reproduce the error (100% reliable, so far) and photograph the screen and post the image...

    System is Core2Quad, 2.66 GHz, 8 GB RAM, nVidia GTX750 using (in 14.04) the nVidia 352 driver, now apparently correctly compiled into the kernel in both 3.13.0-92-generic and 3.13.0-93-generic (was working fine this morning on the newer kernel, indicating previous problem with incomplete nVidia installation during system update was corrected). Doesn't seem like a hardware problem, or I'd have trouble with 16.04.1 too.

    Suggestions? More information needed? 14.04.4 is my primary production environment; I haven't got 16.04.1 fully customized yet, and haven't had time to chase possible fixes for stuff I don't like in the change to Plasma 5.
    Last edited by Silent Observer; Aug 24, 2016, 02:44 AM.
    Tags: None
    • Top
    • Bottom
    #2
    power dips do not blow breakers. surges and overloads do.

    try getting error messages from journalctl -xe and we might be able to help more .without some errors i really can only guess about what your issues could be .. but a good start would be to boot up to recovery mode and use the attempt to fix broken packages option. you could have some broken / partly installed / upgraded packages if you do that kind of stuff automaticy or it happned to be updateing during the power issue.
    Mark Your Solved Issues [SOLVED]
    (top of thread: thread tools)
    • Top
    • Bottom

    Comment

      #3
      I don't have automatic updates set on any of my Kubuntu installations (14.04.4 on desktop and laptop, 16.04.1 alternate on desktop). This breaker pop was this breaker only, probably due to a mild overload -- not sure what else is on the same breaker, could be something cycled on and got the current draw high enough to pop 20 A. Also possible someone bumped the wrong breaker when switching the air conditioning on or off (thermostat control isn't working, so the unit is "hot-wired" to run whenever the breaker is on).

      I don't have time to dig in journals right now, but I'll do so later and post back. I agree, without some messages there's not really anything to work on, but I haven't any idea on my own what files to examine to look for logs and error messages. I also don't know how to get to recovery mode, but I can probably find that -- though with near-zero chance of a broken package other than a file corrupted by the power drop, I'm not sure what I'd gain that I can't get by digging in the files from 16.04.

      Edit: Oh. journalctl -xe gives lots of information, but it's for the running version I have -- 16.04.1. I can't do anything with it unless or until I can get to safe mode in 14.04.4. Let me dig around for how to get into recovery mode from Legacy Grub...

      Further edit: Well. I kept Legacy Grub because it's not so completely hidden in its operation; I can manually edit the config file and not have it scold me or decide I've corrupted everything and start over. Unfortunately, there's no longer any useful documentation on how to do much of anything with Legacy Grub. I've tried appending
      Code:
      runlevel=5
      and alternatively
      Code:
      runlevel=3
      , and can't get a boot to command line. The only way I know to get Legacy Grub into rescue or recovery mode is to change the UUID of a partition so Grub can't find it -- and for obvious reasons, I'd rather not do that. I'm not sure there's anything useful I can do in that mode, anyway.

      Last edit for tonight: I took a video of the startup (text scroll mode) from power on to the hang. I'll be happy to put it on YouTube if anyone wants to see it; at 160 MB I don't think there's any more practical way to get it to anyone else.
      Last edited by Silent Observer; Aug 24, 2016, 05:06 PM.
      • Top
      • Bottom

      Comment

        #4
        woops try dmesg on the older system and look at logs in /var/log maybe one of them will help
        Mark Your Solved Issues [SOLVED]
        (top of thread: thread tools)
        • Top
        • Bottom

        Comment

          #5
          Sithlord, the older system won't boot, even to a command line, so dmesg isn't going to be much help. I'll see if the logs can tell me anything (most likely I'll need help interpreting what I find).

          Here's what I have in boot.log, from the last attempt I presume (file date is 20160824, which matches my last attempt to boot 14.04).
          Code:
          Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
 * Starting Read required files in advance[ OK ]
 * Starting Mount filesystems on boot[ OK ]
 * Starting Populate /dev filesystem[ OK ]
 * Starting Populate and link to /run filesystem[ OK ]
 * Stopping Populate /dev filesystem[ OK ]
 * Stopping Populate and link to /run filesystem[ OK ]
 * Stopping Track if upstart is running in a container[ OK ]
 * Starting Initialize or finalize resolvconf[ OK ]
 * Starting Read required files in advance (for other mountpoints)[fail]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Starting set console keymap[ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
 * Starting Bridge udev events into upstart[ OK ]
 * Starting Signal sysvinit that remote filesystems are mounted[ OK ]
 * Stopping set console keymap[ OK ]
 * Starting device node and kernel event manager[ OK ]
 * Starting load modules from /etc/modules[ OK ]
 * Starting cold plug devices[ OK ]
 * Starting log initial device creation[ OK ]
 * Stopping Read required files in advance[ OK ]
 * Stopping load modules from /etc/modules[ OK ]
 * Starting Uncomplicated firewall[ OK ]
 * Starting configure network device security[ OK ]
 * Starting configure network device[ OK ]
 * Starting configure network device security[ OK ]
 * Starting Mount network filesystems[ OK ]
 * Stopping Mount network filesystems[ OK ]
 * Starting Bridge socket events into upstart[ OK ]
 * Starting configure network device[ OK ]
 * Starting Signal sysvinit that the rootfs is mounted[ OK ]
 * Starting Clean /tmp directory[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Clean /tmp directory[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[ OK ]
 * Starting Signal sysvinit that local filesystems are mounted[ OK ]
 * Starting restore software rfkill state[ OK ]
 * Stopping restore software rfkill state[ OK ]
 * Starting SMB/CIFS File Server[ OK ]
 * Starting Enabling additional executable binary formats[ OK ]
 * Starting flush early job output to logs[ OK ]
 * Stopping Failsafe Boot Delay[ OK ]
 * Stopping Mount filesystems on boot[ OK ]
 * Starting System V initialisation compatibility[ OK ]
 * Stopping flush early job output to logs[ OK ]
 * Starting Bridge file events into upstart[ OK ]
 * Starting system logging daemon[ OK ]
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
 * Starting AppArmor profiles        
[ OK ]
 * Starting D-Bus system message bus[ OK ]
 * Starting modem connection manager[ OK ]
 * Starting configure network device security[ OK ]
 * Starting SystemD login management service[ OK ]
 * Starting mDNS/DNS-SD daemon[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[ OK ]
 * Stopping Reload cups, upon starting avahi-daemon to make sure remote queues are populated[ OK ]
 * Starting SMB/CIFS File and Active Directory Server[ OK ]
 * Starting bluetooth daemon[ OK ]
 * Setting sensors limits        
[ OK ]
 * Starting network connection manager[ OK ]
 * Setting up X socket directories...        
[ OK ]
 * Stopping System V initialisation compatibility[ OK ]
 * Starting SMB/CIFS File and Active Directory Server[fail]
 * Starting System V runlevel compatibility[ OK ]
 * Starting anac(h)ronistic cron[ OK ]
 * Starting save kernel messages[ OK ]
 * Starting configure network device security[ OK ]
 * Starting ACPI daemon[ OK ]
 * Starting regular background program processing daemon[ OK ]
 * Starting cups-browsed - Bonjour remote printer browsing daemon[ OK ]
 * Starting automatic crash report generation[ OK ]
 * Starting CPU interrupts balancing daemon[ OK ]
 * Stopping Restore Sound Card State[ OK ]
 * Stopping save kernel messages[ OK ]
 * Starting crash report submission daemon[ OK ]
 * Starting configure virtual network devices[ OK ]
          And here's the last part of dmesg:

          Code:
          [   19.717645] hda_intel: Disabling MSI
[   19.717660] hda-intel 0000:01:00.1: Handle VGA-switcheroo audio client
[   19.717740] hda-intel 0000:01:00.1: Disabling 64bit DMA
[   19.721273] hda-intel 0000:01:00.1: Enable delay in RIRB handling
[   19.835544] nvidia: module license 'NVIDIA' taints kernel.
[   19.835549] Disabling lock debugging due to kernel taint
[   19.844600] nvidia: module verification failed: signature and/or  required key missing - tainting kernel
[   19.872864] BUG: unable to handle kernel NULL pointer dereference at           (null)
[   19.872902] IP: [<ffffffff817343a3>] __down_common+0x4c/0xf0
[   19.872928] PGD bb38a067 PUD bb389067 PMD 0 
[   19.872948] Oops: 0002 [#1] PREEMPT SMP 
[   19.872968] Modules linked in: nvidia(POX+) snd_hda_codec_hdmi snd_hda_codec_realtek gpio_ich snd_hda_intel(+) snd_seq_midi snd_hda_codec snd_seq_midi_event snd_hwdep coretemp snd_rawmidi joydev kvm_intel snd_pcm kvm snd_seq drm snd_seq_device parport_pc snd_page_alloc snd_timer serio_raw ppdev shpchp snd lp lpc_ich soundcore asus_atk0110 mac_hid parport hid_generic usbhid hid ahci firewire_ohci firewire_core libahci atl1 aic7xxx crc_itu_t pata_acpi pata_jmicron mii floppy
[   19.873181] CPU: 2 PID: 593 Comm: nvidia-persiste Tainted: P           OX 3.13.0-93-lowlatency #140-Ubuntu
[   19.873217] Hardware name: System manufacturer P5K/P5K, BIOS 1201    10/14/2008
[   19.873244] task: ffff88022ed16080 ti: ffff88003789c000 task.ti: ffff88003789c000
[   19.873271] RIP: 0010:[<ffffffff817343a3>]  [<ffffffff817343a3>] __down_common+0x4c/0xf0
[   19.873302] RSP: 0018:ffff88003789db68  EFLAGS: 00010092
[   19.873323] RAX: 0000000000000000 RBX: 7fffffffffffffff RCX: ffffffffa0aa0428
[   19.873348] RDX: ffff88003789db70 RSI: 0000000000000002 RDI: ffffffffa0aa0420
[   19.873374] RBP: ffff88003789dbc0 R08: 0000000000000282 R09: ffffffffa07b2feb
[   19.873400] R10: 000000000000000a R11: 00000000000000ff R12: ffffffffa0aa0420
[   19.873425] R13: 0000000000000002 R14: 0000000000000000 R15: ffff88022ed16080
[   19.873451] FS:  00007fa9b93d6740(0000) GS:ffff88023fd00000(0000) knlGS:0000000000000000
[   19.873481] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   19.873502] CR2: 0000000000000000 CR3: 00000000bb38b000 CR4: 00000000000407e0
[   19.873527] Stack:
[   19.873536]  ffffffff8115dc17 ffffffffa0aa0428 0000000000000000 0000000000000010
[   19.873567]  ffff8802312dc400 0000000000000000 ffffffffa0aa0420 ffff8800bac18000
[   19.873597]  0000000000000003 ffff88022f1c7238 0000000000000002 ffff88003789dbd0
[   19.873628] Call Trace:
[   19.874178]  [<ffffffff8115dc17>] ? __alloc_pages_nodemask+0x197/0xbd0
[   19.874178]  [<ffffffff81734464>] __down+0x1d/0x1f
[   19.874178]  [<ffffffff810b4a91>] down+0x41/0x50
[   19.874178]  [<ffffffffa07b32e7>] nvidia_open+0x387/0x960 [nvidia]
[   19.874178]  [<ffffffffa07b20c9>] nvidia_frontend_open+0x49/0xa0 [nvidia]
[   19.874178]  [<ffffffff811c8fef>] chrdev_open+0x9f/0x1d0
[   19.874178]  [<ffffffff811c1ad3>] do_dentry_open+0x233/0x2e0
[   19.874178]  [<ffffffff811c8f50>] ? cdev_put+0x30/0x30
[   19.874178]  [<ffffffff811c1e09>] vfs_open+0x49/0x50
[   19.874178]  [<ffffffff811d1742>] do_last+0x562/0x1340
[   19.874178]  [<ffffffff811d428b>] path_openat+0xbb/0x640
[   19.874178]  [<ffffffff811d567a>] do_filp_open+0x3a/0x90
[   19.874178]  [<ffffffff811e26b7>] ? __alloc_fd+0xa7/0x130
[   19.874178]  [<ffffffff811c3949>] do_sys_open+0x129/0x2c0
[   19.874178]  [<ffffffff811c3afe>] SyS_open+0x1e/0x20
[   19.874178]  [<ffffffff8173d91d>] system_call_fastpath+0x1a/0x1f
[   19.874178] Code: e6 81 00 00 00 49 89 fc 53 48 89 d3 48 83 e4 f0 48 83 ec 28 48 8b 47 10 48 8d 54 24 08 48 89 4c 24 08 48 89 44 24 10 48 89 57 10 <48> 89 10 4c 89 e8 4c 89 7c 24 18 83 e0 01 c6 44 24 20 00 48 89 
[   19.874178] RIP  [<ffffffff817343a3>] __down_common+0x4c/0xf0
[   19.874178]  RSP <ffff88003789db68>
[   19.874178] CR2: 0000000000000000
[   19.874178] ---[ end trace 1b4600b81a2f6daa ]---
[   19.874178] note: nvidia-persiste[593] exited with preempt_count 1
[   19.919153] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
[   19.920855] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
[   19.922810] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
[   19.925126] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[   20.417396] EXT4-fs (sda5): re-mounted. Opts: (null)
[   20.486637] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[   20.527567] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[   20.533420] EXT4-fs (sdc6): mounting ext3 file system using the ext4 subsystem
[   20.569339] EXT4-fs (sdc6): warning: checktime reached, running e2fsck is recommended
[   20.571407] EXT4-fs (sdc6): mounted filesystem with ordered data mode. Opts: (null)
[   20.591154] EXT4-fs (sdc7): mounting ext3 file system using the ext4 subsystem
[   20.611985] EXT4-fs (sdc7): warning: checktime reached, running e2fsck is recommended
[   20.613809] EXT4-fs (sdc7): mounted filesystem with ordered data mode. Opts: (null)
[   21.532709] EXT4-fs (sda6): warning: checktime reached, running e2fsck is recommended
[   21.532894] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[   21.538463] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[   21.546846] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
[   21.563314] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[   21.661020] init: failsafe main process (757) killed by TERM signal
[   21.932022] type=1400 audit(1472094006.633:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=854 comm="apparmor_parser"
[   21.934720] type=1400 audit(1472094006.636:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=854 comm="apparmor_parser"
[   21.937480] type=1400 audit(1472094006.639:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=854 comm="apparmor_parser"
[   21.940936] type=1400 audit(1472094006.642:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=854 comm="apparmor_parser"
[   22.436993] init: cups main process (910) killed by HUP signal
[   22.437016] init: cups main process ended, respawning
[   22.532851] Bluetooth: Core ver 2.17
[   22.534792] NET: Registered protocol family 31
[   22.536331] Bluetooth: HCI device and connection manager initialized
[   22.537826] Bluetooth: HCI socket layer initialized
[   22.539356] Bluetooth: L2CAP socket layer initialized
[   22.540767] Bluetooth: SCO socket layer initialized
[   22.559746] Bluetooth: RFCOMM TTY layer initialized
[   22.561195] Bluetooth: RFCOMM socket layer initialized
[   22.562646] Bluetooth: RFCOMM ver 1.11
[   22.578708] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   22.580197] Bluetooth: BNEP filters: protocol multicast
[   22.581550] Bluetooth: BNEP socket layer initialized
[   23.136228] init: samba-ad-dc main process (931) terminated with status 1
          Last edited by Silent Observer; Aug 25, 2016, 03:46 PM.
          • Top
          • Bottom

          Comment

            #6
            Here's the last part of kern.log:

            Code:
            Aug 24 23:00:06 Kubuntu64 kernel: [   19.872864] BUG: unable to handle kernel NULL pointer dereference at           (null)
Aug 24 23:00:06 Kubuntu64 kernel: [   19.872902] IP: [<ffffffff817343a3>] __down_common+0x4c/0xf0
Aug 24 23:00:06 Kubuntu64 kernel: [   19.872928] PGD bb38a067 PUD bb389067 PMD 0 
Aug 24 23:00:06 Kubuntu64 kernel: [   19.872948] Oops: 0002 [#1] PREEMPT SMP 
Aug 24 23:00:06 Kubuntu64 kernel: [   19.872968] Modules linked in: nvidia(POX+) snd_hda_codec_hdmi snd_hda_codec_realtek gpio_ich snd_hda_intel(+) snd_seq_midi snd_hda_codec snd_seq_midi_event snd_hwdep coretemp snd_rawmidi joydev kvm_intel snd_pcm kvm snd_seq drm snd_seq_device parport_pc snd_page_alloc snd_timer serio_raw ppdev shpchp snd lp lpc_ich soundcore asus_atk0110 mac_hid parport hid_generic usbhid hid ahci firewire_ohci firewire_core libahci atl1 aic7xxx crc_itu_t pata_acpi pata_jmicron mii floppy
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873181] CPU: 2 PID: 593 Comm: nvidia-persiste Tainted: P           OX 3.13.0-93-lowlatency #140-Ubuntu
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873217] Hardware name: System manufacturer P5K/P5K, BIOS 1201    10/14/2008
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873244] task: ffff88022ed16080 ti: ffff88003789c000 task.ti: ffff88003789c000
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873271] RIP: 0010:[<ffffffff817343a3>]  [<ffffffff817343a3>] __down_common+0x4c/0xf0
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873302] RSP: 0018:ffff88003789db68  EFLAGS: 00010092
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873323] RAX: 0000000000000000 RBX: 7fffffffffffffff RCX: ffffffffa0aa0428
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873348] RDX: ffff88003789db70 RSI: 0000000000000002 RDI: ffffffffa0aa0420
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873374] RBP: ffff88003789dbc0 R08: 0000000000000282 R09: ffffffffa07b2feb
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873400] R10: 000000000000000a R11: 00000000000000ff R12: ffffffffa0aa0420
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873425] R13: 0000000000000002 R14: 0000000000000000 R15: ffff88022ed16080
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873451] FS:  00007fa9b93d6740(0000) GS:ffff88023fd00000(0000) knlGS:0000000000000000
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873481] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873502] CR2: 0000000000000000 CR3: 00000000bb38b000 CR4: 00000000000407e0
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873527] Stack:
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873536]  ffffffff8115dc17 ffffffffa0aa0428 0000000000000000 0000000000000010
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873567]  ffff8802312dc400 0000000000000000 ffffffffa0aa0420 ffff8800bac18000
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873597]  0000000000000003 ffff88022f1c7238 0000000000000002 ffff88003789dbd0
Aug 24 23:00:06 Kubuntu64 kernel: [   19.873628] Call Trace:
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff8115dc17>] ? __alloc_pages_nodemask+0x197/0xbd0
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff81734464>] __down+0x1d/0x1f
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff810b4a91>] down+0x41/0x50
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffffa07b32e7>] nvidia_open+0x387/0x960 [nvidia]
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffffa07b20c9>] nvidia_frontend_open+0x49/0xa0 [nvidia]
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811c8fef>] chrdev_open+0x9f/0x1d0
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811c1ad3>] do_dentry_open+0x233/0x2e0
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811c8f50>] ? cdev_put+0x30/0x30
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811c1e09>] vfs_open+0x49/0x50
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811d1742>] do_last+0x562/0x1340
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811d428b>] path_openat+0xbb/0x640
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811d567a>] do_filp_open+0x3a/0x90
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811e26b7>] ? __alloc_fd+0xa7/0x130
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811c3949>] do_sys_open+0x129/0x2c0
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff811c3afe>] SyS_open+0x1e/0x20
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  [<ffffffff8173d91d>] system_call_fastpath+0x1a/0x1f
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178] Code: e6 81 00 00 00 49 89 fc 53 48 89 d3 48 83 e4 f0 48 83 ec 28 48 8b 47 10 48 8d 54 24 08 48 89 4c 24 08 48 89 44 24 10 48 89 57 10 <48> 89 10 4c 89 e8 4c 89 7c 24 18 83 e0 01 c6 44 24 20 00 48 89 
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178] RIP  [<ffffffff817343a3>] __down_common+0x4c/0xf0
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178]  RSP <ffff88003789db68>
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178] CR2: 0000000000000000
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178] ---[ end trace 1b4600b81a2f6daa ]---
Aug 24 23:00:06 Kubuntu64 kernel: [   19.874178] note: nvidia-persiste[593] exited with preempt_count 1
Aug 24 23:00:06 Kubuntu64 kernel: [   19.919153] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
Aug 24 23:00:06 Kubuntu64 kernel: [   19.920855] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
Aug 24 23:00:06 Kubuntu64 kernel: [   19.922810] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
Aug 24 23:00:06 Kubuntu64 kernel: [   19.925126] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
Aug 24 23:00:06 Kubuntu64 kernel: [   20.417396] EXT4-fs (sda5): re-mounted. Opts: (null)
Aug 24 23:00:06 Kubuntu64 kernel: [   20.486637] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro
Aug 24 23:00:06 Kubuntu64 kernel: [   20.527567] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
Aug 24 23:00:06 Kubuntu64 kernel: [   20.533420] EXT4-fs (sdc6): mounting ext3 file system using the ext4 subsystem
Aug 24 23:00:06 Kubuntu64 kernel: [   20.569339] EXT4-fs (sdc6): warning: checktime reached, running e2fsck is recommended
Aug 24 23:00:06 Kubuntu64 kernel: [   20.571407] EXT4-fs (sdc6): mounted filesystem with ordered data mode. Opts: (null)
Aug 24 23:00:06 Kubuntu64 kernel: [   20.591154] EXT4-fs (sdc7): mounting ext3 file system using the ext4 subsystem
Aug 24 23:00:06 Kubuntu64 kernel: [   20.611985] EXT4-fs (sdc7): warning: checktime reached, running e2fsck is recommended
Aug 24 23:00:06 Kubuntu64 kernel: [   20.613809] EXT4-fs (sdc7): mounted filesystem with ordered data mode. Opts: (null)
Aug 24 23:00:06 Kubuntu64 kernel: [   21.532709] EXT4-fs (sda6): warning: checktime reached, running e2fsck is recommended
Aug 24 23:00:06 Kubuntu64 kernel: [   21.532894] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
Aug 24 23:00:06 Kubuntu64 kernel: [   21.538463] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
Aug 24 23:00:06 Kubuntu64 kernel: [   21.546846] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
Aug 24 23:00:06 Kubuntu64 kernel: [   21.563314] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
Aug 24 23:00:06 Kubuntu64 kernel: [   21.932022] type=1400 audit(1472094006.633:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=854 comm="apparmor_parser"
Aug 24 23:00:06 Kubuntu64 kernel: [   21.934720] type=1400 audit(1472094006.636:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=854 comm="apparmor_parser"
Aug 24 23:00:06 Kubuntu64 kernel: [   21.937480] type=1400 audit(1472094006.639:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=854 comm="apparmor_parser"
Aug 24 23:00:06 Kubuntu64 kernel: [   21.940936] type=1400 audit(1472094006.642:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=854 comm="apparmor_parser"
Aug 24 23:00:07 Kubuntu64 kernel: [   22.532851] Bluetooth: Core ver 2.17
Aug 24 23:00:07 Kubuntu64 kernel: [   22.534792] NET: Registered protocol family 31
Aug 24 23:00:07 Kubuntu64 kernel: [   22.536331] Bluetooth: HCI device and connection manager initialized
Aug 24 23:00:07 Kubuntu64 kernel: [   22.537826] Bluetooth: HCI socket layer initialized
Aug 24 23:00:07 Kubuntu64 kernel: [   22.539356] Bluetooth: L2CAP socket layer initialized
Aug 24 23:00:07 Kubuntu64 kernel: [   22.540767] Bluetooth: SCO socket layer initialized
Aug 24 23:00:07 Kubuntu64 kernel: [   22.559746] Bluetooth: RFCOMM TTY layer initialized
Aug 24 23:00:07 Kubuntu64 kernel: [   22.561195] Bluetooth: RFCOMM socket layer initialized
Aug 24 23:00:07 Kubuntu64 kernel: [   22.562646] Bluetooth: RFCOMM ver 1.11
Aug 24 23:00:07 Kubuntu64 kernel: [   22.578708] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Aug 24 23:00:07 Kubuntu64 kernel: [   22.580197] Bluetooth: BNEP filters: protocol multicast
Aug 24 23:00:07 Kubuntu64 kernel: [   22.581550] Bluetooth: BNEP socket layer initialized
Aug 24 23:00:08 Kubuntu64 kernel: [   23.302673] atl1 0000:02:00.0: irq 46 for MSI/MSI-X
Aug 24 23:00:08 Kubuntu64 kernel: [   23.304438] atl1 0000:02:00.0: eth1 link is up 100 Mbps full duplex
Aug 24 23:00:08 Kubuntu64 kernel: [   23.304516] atl1 0000:02:00.0: eth1 link is up 1000 Mbps full duplex
Aug 24 19:00:36 Kubuntu64 kernel: [   52.374824] audit_printk_skb: 159 callbacks suppressed
Aug 24 19:00:36 Kubuntu64 kernel: [   52.374829] type=1400 audit(1472079636.741:65): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1591 comm="apparmor_parser"
Aug 24 19:00:36 Kubuntu64 kernel: [   52.374837] type=1400 audit(1472079636.741:66): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1591 comm="apparmor_parser"
Aug 24 19:00:36 Kubuntu64 kernel: [   52.375252] type=1400 audit(1472079636.742:67): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1591 comm="apparmor_parser"
            And the last part of syslog:

            Code:
            Aug 24 23:00:08 Kubuntu64 dbus[885]: [system] Activating service name='org.freedesktop.Accounts' (using servicehelper)
Aug 24 23:00:08 Kubuntu64 accounts-daemon[1203]: started daemon version 0.6.35
Aug 24 23:00:08 Kubuntu64 dbus[885]: [system] Successfully activated service 'org.freedesktop.Accounts'
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <info> (eth1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <info> Activation (eth1) Stage 5 of 5 (IPv4 Commit) complete.
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <info> (eth1): device state change: secondaries -> activated (reason 'none') [90 100 0]
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <info> NetworkManager state is now CONNECTED_GLOBAL
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <info> Policy set 'Wired connection 2' (eth1) as default for IPv4 routing and DNS.
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <info> DNS: starting dnsmasq...
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <warn> dnsmasq not available on the bus, can't update servers.
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <error> [1472094009.281774] [nm-dns-dnsmasq.c:396] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <warn> DNS: plugin dnsmasq update failed
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <info> Writing DNS information to /sbin/resolvconf
Aug 24 23:00:09 Kubuntu64 dnsmasq[1214]: started, version 2.68 cache disabled
Aug 24 23:00:09 Kubuntu64 dnsmasq[1214]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth
Aug 24 23:00:09 Kubuntu64 dnsmasq[1214]: DBus support enabled: connected to system bus
Aug 24 23:00:09 Kubuntu64 dnsmasq[1214]: warning: no upstream servers configured
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <info> Activation (eth1) successful, device activated.
Aug 24 23:00:09 Kubuntu64 dbus[885]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <warn> dnsmasq appeared on DBus: :1.13
Aug 24 23:00:09 Kubuntu64 NetworkManager[959]: <info> Writing DNS information to /sbin/resolvconf
Aug 24 23:00:09 Kubuntu64 dnsmasq[1214]: setting upstream servers from DBus
Aug 24 23:00:09 Kubuntu64 dnsmasq[1214]: using nameserver 209.18.47.62#53
Aug 24 23:00:09 Kubuntu64 dnsmasq[1214]: using nameserver 209.18.47.61#53
Aug 24 23:00:09 Kubuntu64 dbus[885]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 24 23:00:09 Kubuntu64 whoopsie[1147]: online
Aug 24 23:00:09 Kubuntu64 avahi-daemon[922]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::21d:60ff:fe0d:9649.
Aug 24 23:00:09 Kubuntu64 avahi-daemon[922]: New relevant interface eth1.IPv6 for mDNS.
Aug 24 23:00:09 Kubuntu64 avahi-daemon[922]: Registering new address record for fe80::21d:60ff:fe0d:9649 on eth1.*.
Aug 24 23:00:09 Kubuntu64 ModemManager[899]: <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0': not supported by any plugin
Aug 24 23:00:10 Kubuntu64 avahi-daemon[922]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::21d:60ff:fe0d:9649.
Aug 24 23:00:10 Kubuntu64 avahi-daemon[922]: Joining mDNS multicast group on interface eth1.IPv6 with address 2606:a000:87c4:d700:50ac:2bed:127c:7a7.
Aug 24 23:00:10 Kubuntu64 avahi-daemon[922]: Registering new address record for 2606:a000:87c4:d700:50ac:2bed:127c:7a7 on eth1.*.
Aug 24 23:00:10 Kubuntu64 avahi-daemon[922]: Withdrawing address record for fe80::21d:60ff:fe0d:9649 on eth1.
Aug 24 23:00:10 Kubuntu64 NetworkManager[959]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
Aug 24 23:00:10 Kubuntu64 NetworkManager[959]: <info> Activation (eth1) Beginning DHCPv6 transaction (timeout in 45 seconds)
Aug 24 23:00:10 Kubuntu64 NetworkManager[959]: <info> dhclient started with pid 1364
Aug 24 23:00:10 Kubuntu64 dhclient: Internet Systems Consortium DHCP Client 4.2.4
Aug 24 23:00:10 Kubuntu64 dhclient: Copyright 2004-2012 Internet Systems Consortium.
Aug 24 23:00:10 Kubuntu64 dhclient: All rights reserved.
Aug 24 23:00:10 Kubuntu64 dhclient: For info, please visit https://www.isc.org/software/dhcp/
Aug 24 23:00:10 Kubuntu64 dhclient: 
Aug 24 23:00:10 Kubuntu64 dhclient: Bound to *:546
Aug 24 23:00:10 Kubuntu64 dhclient: Listening on Socket/eth1
Aug 24 23:00:10 Kubuntu64 dhclient: Sending on   Socket/eth1
Aug 24 23:00:11 Kubuntu64 dhclient: XMT: Info-Request on eth1, interval 920ms.
Aug 24 23:00:11 Kubuntu64 avahi-daemon[922]: Registering new address record for 2606:a000:87c4:d700:21d:60ff:fe0d:9649 on eth1.*.
Aug 24 23:00:12 Kubuntu64 dhclient: XMT: Info-Request on eth1, interval 1830ms.
Aug 24 23:00:14 Kubuntu64 dhclient: XMT: Info-Request on eth1, interval 3640ms.
Aug 24 19:00:15 Kubuntu64 ntpdate[1312]: step time server 91.189.91.157 offset -14400.335566 sec
Aug 24 19:00:18 Kubuntu64 NetworkManager[959]: <info> WiFi hardware radio set enabled
Aug 24 19:00:36 Kubuntu64 kernel: [   52.374824] audit_printk_skb: 159 callbacks suppressed
Aug 24 19:00:36 Kubuntu64 kernel: [   52.374829] type=1400 audit(1472079636.741:65): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1591 comm="apparmor_parser"
Aug 24 19:00:36 Kubuntu64 kernel: [   52.374837] type=1400 audit(1472079636.741:66): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1591 comm="apparmor_parser"
Aug 24 19:00:36 Kubuntu64 kernel: [   52.375252] type=1400 audit(1472079636.742:67): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1591 comm="apparmor_parser"
Aug 24 19:00:55 Kubuntu64 NetworkManager[959]: <warn> (eth1): DHCPv6 request timed out.
Aug 24 19:00:55 Kubuntu64 NetworkManager[959]: <info> (eth1): canceled DHCP transaction, DHCP client pid 1364
Aug 24 19:00:55 Kubuntu64 NetworkManager[959]: <info> Activation (eth1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Aug 24 19:00:55 Kubuntu64 NetworkManager[959]: <info> Activation (eth1) Stage 4 of 5 (IPv6 Configure Timeout) started...
Aug 24 19:00:55 Kubuntu64 NetworkManager[959]: <info> Activation (eth1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
            • Top
            • Bottom

            Comment

              #7
              Hmmm. No suggestions, eh? Anyone know of something I've read a mention of, of Ubuntu (and presumably Kubuntu) being able to reinstall without overwriting installed programs? I know I can keep the user ~/ folder, but is there (at least) a way to extract the list of installed packages, so they can be automatically reinstalled by Synaptic, and/or keep that process from overwriting all configuration information?
              • Top
              • Bottom

              Comment

                #8
                Yes, you can generate a list of installed packages on your system. Oshunluvr, IIRC, has posts here on that. Take a look at ListInstalledPackages on the Debian Wiki; it describes the process.
                Windows no longer obstructs my view.
                Using Kubuntu Linux since March 23, 2007.
                "It is a capital mistake to theorize before one has data." - Sherlock Holmes​
                • Top
                • Bottom

                Comment

                  #9
                  Here is how.
                  "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                  – John F. Kennedy, February 26, 1962.
                  • Top
                  • Bottom

                  Comment

                    #10
                    Okay, that, as much as the ability of Synaptic to export the installed packages list (which I already knew about), would work fine if I could boot that partition -- but since this thread is about a partition that won't boot, that's not much help. The list of installed packages must be stored in a file somewhere -- is there a way to extract it from a partition that won't boot, into a form that can be used to automatically reinstall everything on the list? I don't see anything in the referenced ubuntuforums thread (though I didn't read every post to the end of 8-9 pages), and the one on Debian Wiki won't even open for me.

                    What about that ability to reinstall (K)Ubuntu without undoing all the installations (and customizations?) since original install?
                    • Top
                    • Bottom

                    Comment

                      #11
                      Can you, from the Grub menu, choose Advanced (I believe that is right; regardless, it's the next entry down) and boot into Recovery mode (Single User). That boots to a command line only, as root. System will be read only, but that can be changed if necessary.
                      Windows no longer obstructs my view.
                      Using Kubuntu Linux since March 23, 2007.
                      "It is a capital mistake to theorize before one has data." - Sherlock Holmes​
                      • Top
                      • Bottom

                      Comment

                        #12
                        Snowhog, I'm using Legacy Grub (0.97, as I recall), but I found a way to get the system booting in 14.04 again. First, I used a root privilege Dolphin (from my 16.04 partition) to locate the menu.lst in the /boot/grub folder that actually starts my system, then manually edited to add an entry for the oldest kernel I have -- 3.13.0-24-generic, which as i recall is the one originally distributed with 14.04 back in April-May 2014. That one, for whatever reason, started up without protest. Once I had that, I was able to uninstall the latest updated kernel (3.13.0-93-generic) and its lowlatency variant, which had installed along with it due to an insufficiently specific apt-get command when I was trying to fix the problem in my other recent thread. I then reinstalled the generic only for 3.13.0-93, and that booted -- but only a single time after installation, same as 3.13.0-93 did the first time, after it installed as part of a routine update. A little further jiggering, and I adjusted the links I actually use (vmlinuz and vmlinuz.old, initrd.img and initrd.img.old) to support booting the current and newest previous kernels from Grub. Now, with 3.13.0-93-generic still installed, I'm booted from 3.13.0-92-generic, which ran fine for several weeks before the last kernel update.

                        At this point, I'm pretty sure there's something not quite right with 3.13.0-93-generic. I'm not sure how to characterize it, but the logs up the thread should include the information some could use to see what it's doing. It's very possible (fairly likely, even) that this is idiosyncratic to my system; I have a few modifications in place, such as having set a root password. This gives me a little extra backup, and makes things that little bit safer, since I can't reflex-type my user password to authorize a root privilege action; it also allows root privileged programs to run with a different color scheme; another "be careful, you can hose yourself" precaution left over from running MEPIS 11. I'm pretty confident this isn't video driver issues, because the last two reinstalls of 3.13.0-93 kernel correctly compiled in the nVidia 352 driver that Ubuntu currently recommends (though my 16.04 is running nVidia 361; I might give that a try), and the crash/hang is happening quite a bit before the system ought to be starting X -- I'm not even getting a command line login when it fails.

                        At present, even though I'm not certain 3.13.0-92 will keep booting properly, I seem to be able to start reliably in the oldest kernel, so I can at least fiddle with it without having to mess with accessing from another partition/login/major version.
                        • Top
                        • Bottom

                        Comment

                        Previous template Next
                        Working...
                        X