Suddenly unable to boot, stuck at 'Stopping save udev log'

arnoldlayne42 · 01-25-2014, 05:29 AM

Everything was normal until a while back, but I just booted my computer and I'm getting the screen below. It hangs/freezes here, and I've no clue what to do. Any ideas?

http://i.stack.imgur.com/gAOxf.jpg

arnoldlayne42 · 01-25-2014, 01:15 PM

Any help? It's really urgent, this is my primary computer

business_kid · 01-25-2014, 01:53 PM

I'd suggest booting with "init=/bin/bash" (without the quotes)as a kernel boot parameter. Instead of starting up as normal, you'll get one root console. Some useful stuff to get going might be

Code:

/sbin/mount -o remount,rw /
export PATH=/sbin:/usr/sbin:/bin:/usr/bin;

That should give you a bare bones machine, *nothing* running. You are starting an awful lot of servers. Is this box online or something? If it's just your own box, you hardly need mysql, samba netbios, or apache unless you know you need them.

Some of the stuff that init starts is giving you issues. Where to go next depends on what distro you have. cd to /var/log and look for errors in a big file called messages, or syslog near the end. Also run dmesg |less. Post anything suspicious. (100 words max, not a massive copy/paste please).
Try 'man systemctl' ; if it's there, read it.

arnoldlayne42 · 01-26-2014, 01:16 AM

Quote:

Originally Posted by business_kid

I'd suggest booting with "init=/bin/bash" (without the quotes)as a kernel boot parameter. Instead of starting up as normal, you'll get one root console. Some useful stuff to get going might be

Code:

/sbin/mount -o remount,rw /
export PATH=/sbin:/usr/sbin:/bin:/usr/bin;

That should give you a bare bones machine, *nothing* running. You are starting an awful lot of servers. Is this box online or something? If it's just your own box, you hardly need mysql, samba netbios, or apache unless you know you need them.

Some of the stuff that init starts is giving you issues. Where to go next depends on what distro you have. cd to /var/log and look for errors in a big file called messages, or syslog near the end. Also run dmesg |less. Post anything suspicious. (100 words max, not a massive copy/paste please).
Try 'man systemctl' ; if it's there, read it.

[Linux Mint 16 64bit]

Yeah I do need those services. One thing I should point out is that at the point where the system gets stuck, I can CtrlAltF2 into the text console, login, and then I'm able to simply 'startx' to get into Cinnamon. Strangely, it shows 'Software Rendering Mode' but still operates in full resolution unlike my previous experiences with Software Rendering Mode.

'dmesg | less'

Quote:

[ 19.563805] cfg80211: Calling CRDA to update world regulatory domain
[ 19.579899] Support for cores revisions 0x17 and 0x18 disabled by module param allhwsupport=0. Try b43.allhwsupport=1
[ 19.579941] b43: probe of bcma0:0 failed with error -524
[ 19.579960] Broadcom 43xx driver loaded [ Features: PNL ]
[ 19.588461] brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 17
[ 19.592020] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 19.592265] ieee80211 phy0: registered radio enabled led device: brcmsmac-phy0:radio gpio: 243
[ 19.609045] microcode: CPU1 sig=0x206a7, pf=0x10, revision=0x1a
[ 19.609532] microcode: CPU2 sig=0x206a7, pf=0x10, revision=0x1a
[ 19.609992] microcode: CPU3 sig=0x206a7, pf=0x10, revision=0x1a
[ 19.610427] microcode: CPU4 sig=0x206a7, pf=0x10, revision=0x1a
[ 19.610851] microcode: CPU5 sig=0x206a7, pf=0x10, revision=0x1a
[ 19.611267] microcode: CPU6 sig=0x206a7, pf=0x10, revision=0x1a
[ 19.611706] microcode: CPU7 sig=0x206a7, pf=0x10, revision=0x1a
[ 19.612222] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 19.620198] kvm: disabled by bios
[ 19.635620] EXT3-fs (sda3): using internal journal
[ 19.652405] kvm: disabled by bios
[ 19.837656] cfg80211: World regulatory domain updated:
[ 19.837659] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 19.837661] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.837662] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.837663] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 19.837665] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.837666] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.837673] cfg80211: Calling CRDA for country: US
[ 19.839580] cfg80211: Regulatory domain changed to country: US
[ 19.839582] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 19.839584] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 19.839585] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 19.839587] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.839588] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.839589] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.839590] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 19.839591] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm)
[ 19.939768] lis3lv02d: 8 bits 3DC sensor found
[ 19.947447] usb 2-1.5: new full-speed USB device number 4 using ehci-pci
[ 19.960711] init: failsafe main process (738) killed by TERM signal
[ 20.047815] usb 2-1.5: New USB device found, idVendor=0a5c, idProduct=21b4
[ 20.047818] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 20.047819] usb 2-1.5: Product: Broadcom 2070 Bluetooth
[ 20.047821] usb 2-1.5: Manufacturer: Broadcom Corp
[ 20.047822] usb 2-1.5: SerialNumber: CC52AFA47679
[ 20.061657] Bluetooth: Core ver 2.16
[ 20.061676] NET: Registered protocol family 31
[ 20.061678] Bluetooth: HCI device and connection manager initialized
[ 20.061686] Bluetooth: HCI socket layer initialized
[ 20.061690] Bluetooth: L2CAP socket layer initialized
[ 20.061697] Bluetooth: SCO socket layer initialized
[ 20.228800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 20.228803] Bluetooth: BNEP filters: protocol multicast
[ 20.228813] Bluetooth: BNEP socket layer initialized
[ 20.230087] Bluetooth: RFCOMM TTY layer initialized
[ 20.230096] Bluetooth: RFCOMM socket layer initialized
[ 20.230097] Bluetooth: RFCOMM ver 1.11
[ 20.351131] init: avahi-cups-reload main process (810) terminated with status 1
[ 20.363805] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.5, id: 0x1e0b1, caps: 0xd00073/0x240000/0xa0400, board id: 1680, fw id: 726294
[ 20.383853] ppdev: user-space parallel port driver
[ 20.409909] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input13
[ 20.619422] usbcore: registered new interface driver btusb
[ 20.799182] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input14
[ 21.596833] r8169 0000:07:00.0 eth0: link down
[ 21.596844] r8169 0000:07:00.0 eth0: link down
[ 21.596886] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 21.597219] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 21.598848] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 22.626492] Bluetooth: hci0 command 0x1009 tx timeout
[ 23.148772] r8169 0000:07:00.0 eth0: link up
[ 23.148779] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 23.901256] init: mdm main process (1205) terminated with status 1
[ 25.393807] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
[ 25.394481] brcmsmac bcma0:0: brcms_ops_config: change power-save mode: false (implement)
[ 25.395296] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

These lines might be relevant to my problem.

Here's a segment of /var/log/syslog, Sorry I'm not really able to identify a specific suspicious portion.

http://pastebin.com/7cRwAqGJ

And

Quote:

$ man systemctl
No manual entry for systemctl

business_kid · 01-26-2014, 09:14 AM

For a box running all those servers, you really need to clear up who your box thiniks it is. Set a hostname.

In the dmesg log there3 are things "terminating with status 1". That's baling out with dignity, as opposed to a crash, but they are not working. Software rendering is bad if you set up hardware rendering. In short, finish setting it up, and post details on the box, & video card if thei thread continues.