[SOLVED]Poweroff, shutdown, reboot, ctrl+fx make desktop reboot

Hi,
I experiencing some strange issue with my new computer.
This is some part:
Gigabyte GeForce GTX 770 (Graphics card)
Gigabyte GA-H81-D3 ATX (Motherboard)
Intel Core i5 I5-4460 (proc)
My screen is connect to HDMI with the gtx
My laptop work really fine without any issue with bumblebee and other stuff.
But on the desktop, if I press
Ctrl+f1 or f2 or f whatever, my screen stop(no input signal) and the desktop reboot and my screen never come back the LCD say no input signal
Same think if I do a terminal, shutdown, reboot or poweroff.
When the desktop reboot I listen the bip for motherboard but the LCD always say no input, and my usb keyboard and mouse don't respond (press Num. Lock de nothing).
I have only one choice is to press the reset button from my case.
I don't know what append.
this is a fresh dmesg:
http://pastebin.com/vmsK9nzz
this is after a forced reboot, look the same:
http://pastebin.com/ZKCQeykK
I try to blacklist uvesafb and vesafb in modprob but the NVRM message stay.
I boot with uefi.
there is Xorg.0.log: http://pastebin.com/wkMfHcg4
the Xorg.0.log.old: http://pastebin.com/gSu2GCTR
And my journaltl from fresh to a reboot:
http://pastebin.com/UpPpLL0h
What do the mess in this desktop?
I try to find some clue but nothing for now.
Thanks
Last edited by Badrocklo (2014-08-08 10:02:22)

The title has a max char limit, that's why it's appearing to be read only. You'll have to shorten your title to squeeze in the [solved] part. Sometimes I really wish the arch bbs had some more features like labels or polls.
edit: I see you figured it out
Last edited by Soukyuu (2014-08-08 10:06:57)

Similar Messages

  • IPhone 4 still gets crashed even after ios 7.1 update, & sometimes fails to reboot! However it gets rebooted after 30 to 60 mins later by itself. "HELP" please somebody

    iPhone 4 still gets crashed even after ios 7.1 update, & sometimes fails to reboot! However it gets rebooted after 30 to 60 mins later by itself. "HELP" please somebody

    1: Connect the device to Your computer and open iTunes.
    2: If the device appears in iTunes, select and click Restore on the Summary pane.
    Restoring  >  http://support.apple.com/kb/HT1414
    Make sure you have the Latest Version of iTunes (v11.1.5) Installed on your computer
    iTunes free download from www.itunes.com/download
    Note:
    Also consider Deleting any Apps you have Purchased / Downloaded but you now never use...

  • Problems rebooting: "couldn't lock for reboot: Resource busy"

    Hi there,
    I'm having trouble rebooting my Xserve G4. The server has been up for 128 days, and a previous admin had installed some software updates, and I recently applied several new ones including 'Java for Mac OS X 10.5 Update 5', QuickTime 7.6.6 and Safari 4.0.5.
    It appears it's been trying to reboot ever since the first set of updates, but is not able to. What is strange is that even after having applied the updates mentioned, Server Admin still lists these same software updates as new, uninstalled updates, and asks me to install them.
    Also, the CPU usage is running at around 60%, and diskarbitrationd and kextcache seem to be the main CPU hogs.
    I have tried asking the machine to reboot through Server Monitor, and it fails, stating:
    14/05/2010 10:32:42: Starting remote hardware monitoring for ‘laramie.gcal.ac.uk’
    14/05/2010 10:32:43: Server contacted successfully
    14/05/2010 10:32:43: Connection to server established
    14/05/2010 10:33:01: Restart request sent, waiting for confirmation…
    14/05/2010 10:33:01: Server restarting
    14/05/2010 10:33:12: Failed to contact server
    14/05/2010 10:38:46: Restart request sent, waiting for confirmation…
    14/05/2010 10:39:10: Server restarting
    14/05/2010 10:49:18: Configuration sent, waiting for confirmation…
    14/05/2010 10:49:19: Configuration sent, waiting for confirmation…
    14/05/2010 10:49:24: Configuration received by server and now active
    14/05/2010 10:49:24: Configuration received by server and now active
    But the server never actually reboots.
    I've also tried 'sudo reboot' at the shell, and this generates:
    laramie:~ swadmin$ sudo reboot
    reboot: / is busy updating; waiting for lock
    reboot: couldn't lock for reboot: Resource busy
    Here's what's in /var/log/system.log, on a continuous loop:
    May 14 11:04:36 laramie servermgrd[55638]: --Module servermgr_xserve's response has retain count of 1.
    May 14 11:04:37 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:04:37 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:04:38 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter[39316]): Exited with exit code: 1
    May 14 11:04:38 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 9 seconds
    May 14 11:04:40 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 7 seconds
    May 14 11:04:41 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:04:41 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:04:42 laramie com.apple.launchd[353] ([0x0-0x1540c3f7].com.apple.finder[39326]): Exited with exit code: 1
    May 14 11:04:44 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 3 seconds
    May 14 11:04:45 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:04:45 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:04:48 laramie servermgrd[55638]: --Module servermgr_xserve's response has retain count of 1.
    May 14 11:04:48 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:04:48 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:04:49 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter[39346]): Exited with exit code: 1
    May 14 11:04:49 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 8 seconds
    May 14 11:04:50 laramie com.apple.launchd[353] ([0x0-0x1540e3f9].com.apple.finder[39347]): Exited with exit code: 1
    May 14 11:04:51 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 7 seconds
    May 14 11:04:52 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:04:52 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:04:54 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 4 seconds
    May 14 11:04:55 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:04:55 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:04:57 laramie com.apple.launchd[353] ([0x0-0x154113fc].com.apple.finder[39370]): Exited with exit code: 1
    May 14 11:04:57 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 1 seconds
    May 14 11:04:58 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:04:58 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:04:59 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter[39378]): Exited with exit code: 1
    May 14 11:04:59 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 9 seconds
    May 14 11:05:00 laramie servermgrd[55638]: --Module servermgr_xserve's response has retain count of 1.
    May 14 11:05:00 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 8 seconds
    May 14 11:05:01 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:01 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:03 laramie com.apple.launchd[353] ([0x0-0x154143ff].com.apple.finder[39392]): Exited with exit code: 1
    May 14 11:05:04 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 4 seconds
    May 14 11:05:04 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:04 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:06 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 2 seconds
    May 14 11:05:07 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:07 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:10 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter[39413]): Exited with exit code: 1
    May 14 11:05:10 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 9 seconds
    May 14 11:05:10 laramie com.apple.launchd[353] ([0x0-0x15416401].com.apple.finder[39415]): Exited with exit code: 1
    May 14 11:05:10 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 8 seconds
    May 14 11:05:11 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:11 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:14 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 4 seconds
    May 14 11:05:15 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:15 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:17 laramie com.apple.launchd[353] ([0x0-0x15419404].com.apple.finder[39433]): Exited with exit code: 1
    May 14 11:05:18 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 1 seconds
    May 14 11:05:18 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:18 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:21 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter[39445]): Exited with exit code: 1
    May 14 11:05:21 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 9 seconds
    May 14 11:05:22: --- last message repeated 1 time ---
    May 14 11:05:22 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:22 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:24 laramie com.apple.launchd[353] ([0x0-0x1541c407].com.apple.finder[39454]): Exited with exit code: 1
    May 14 11:05:24 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 5 seconds
    May 14 11:05:25 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:25 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:27 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 3 seconds
    May 14 11:05:28 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:28 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:30 laramie com.apple.launchd[353] ([0x0-0x1541e409].com.apple.finder[39477]): Exited with exit code: 1
    May 14 11:05:31 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:31 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:31 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter[39480]): Exited with exit code: 1
    May 14 11:05:31 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 9 seconds
    May 14 11:05:33 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 7 seconds
    May 14 11:05:34 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:34 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:37 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 3 seconds
    May 14 11:05:37 laramie com.apple.launchd[353] ([0x0-0x1542140c].com.apple.finder[39498]): Exited with exit code: 1
    May 14 11:05:37 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:37 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:03 laramie com.apple.launchd[353] ([0x0-0x154143ff].com.apple.finder[39392]): Exited with exit code: 1
    May 14 11:05:04 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 4 seconds
    May 14 11:05:04 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:04 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:06 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 2 seconds
    May 14 11:05:07 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:07 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:10 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter[39413]): Exited with exit code: 1
    May 14 11:05:10 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 9 seconds
    May 14 11:05:10 laramie com.apple.launchd[353] ([0x0-0x15416401].com.apple.finder[39415]): Exited with exit code: 1
    May 14 11:05:10 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 8 seconds
    May 14 11:05:11 laramie kextd[24]: 0x17ad40 exited without unlocking '/'
    May 14 11:05:11 laramie kextd[24]: / is still busy, delaying reboot
    May 14 11:05:14 laramie com.apple.launchd[1] (com.apple.UserNotificationCenter): Throttling respawn: Will start in 4 seconds
    Here's the output of 'kextstat':
    kextstat
    Index Refs Address Size Wired Name (Version) <Linked Against>
    1 1 0x0 0x0 0x0 com.apple.kernel (9.8.0)
    2 26 0x0 0x0 0x0 com.apple.kpi.bsd (9.8.0)
    3 3 0x0 0x0 0x0 com.apple.kpi.dsep (9.8.0)
    4 33 0x0 0x0 0x0 com.apple.kpi.iokit (9.8.0)
    5 35 0x0 0x0 0x0 com.apple.kpi.libkern (9.8.0)
    6 34 0x0 0x0 0x0 com.apple.kpi.mach (9.8.0)
    7 18 0x0 0x0 0x0 com.apple.kpi.unsupported (9.8.0)
    8 1 0x0 0x0 0x0 com.apple.iokit.IONVRAMFamily (9.8.0)
    9 1 0x0 0x0 0x0 com.apple.driver.AppleNMI (9.8.0)
    10 1 0x0 0x0 0x0 com.apple.iokit.IOSystemManagementFamily (9.8.0)
    11 1 0x0 0x0 0x0 com.apple.iokit.ApplePlatformFamily (9.8.0)
    12 29 0x0 0x0 0x0 com.apple.kernel.6.0 (7.9.9)
    13 1 0x0 0x0 0x0 com.apple.kernel.bsd (7.9.9)
    14 1 0x0 0x0 0x0 com.apple.kernel.iokit (7.9.9)
    15 1 0x0 0x0 0x0 com.apple.kernel.libkern (7.9.9)
    16 1 0x0 0x0 0x0 com.apple.kernel.mach (7.9.9)
    17 14 0x35594000 0x14000 0x13000 com.apple.iokit.IOPCIFamily (2.6) <7 6 5 4>
    18 4 0x355ae000 0x5000 0x4000 com.apple.driver.IOPlatformFunction (1.8.7d5) <12>
    19 0 0x355c5000 0x10000 0xf000 com.apple.driver.AppleMacRISC2PE (1.8.7d5) <18 17 12 7 5 4>
    20 0 0x35688000 0x6000 0x5000 com.apple.BootCache (30.4) <7 6 5 4 2>
    21 1 0x3578e000 0x4c000 0x4b000 com.apple.iokit.IOHIDFamily (1.5.5) <7 6 5 4 2>
    22 0 0x357e2000 0x4000 0x3000 com.apple.security.TMSafetyNet (3) <7 6 5 3 2>
    23 0 0x35806000 0xb000 0xa000 com.apple.nke.applicationfirewall (1.6.77) <7 6 5 4 2>
    24 0 0x35860000 0x1e000 0x1d000 com.apple.security.seatbelt (107.12) <7 6 5 3 2>
    25 0 0x3a2f0000 0x4000 0x3000 com.apple.driver.AppleFlashNVRAM (1.0.5) <12>
    27 0 0x3a376000 0xa000 0x9000 com.apple.driver.AppleMacRiscPCI (3.4.0) <17 12>
    28 0 0x3b39b000 0x8000 0x7000 com.apple.driver.AppleI2C (4.0.0d2) <12>
    29 0 0x3b3b3000 0x4000 0x3000 com.apple.driver.AppleCPUThermo (2.0.0a0) <12>
    30 0 0x3b44f000 0x6000 0x5000 com.apple.driver.AppleKiwiRoot (1.0.5f1) <17 12>
    31 2 0x3b673000 0x5b000 0x5a000 com.apple.iokit.IOFireWireFamily (3.4.9) <6 5 4 2>
    32 0 0x3b712000 0x2f000 0x2e000 com.apple.driver.AppleFWOHCI (3.9.7) <31 17 7 6 5 4 2>
    33 1 0x3b7e3000 0x5000 0x4000 com.apple.iokit.IOKeyLargo (1.7.2f1) <12>
    34 0 0x3b7fc000 0x7000 0x6000 com.apple.driver.AppleKeyLargo (1.7.2f1) <33 18 17 12>
    35 3 0x3b966000 0x37000 0x36000 com.apple.iokit.IOUSBFamily (3.4.9) <7 6 5 4 2>
    36 0 0x3ba59000 0xe000 0xd000 com.apple.driver.AppleUSBOHCI (3.4.6) <35 17 6 5 4>
    37 0 0x3ba76000 0x3000 0x2000 com.apple.driver.AppleBlower (2.0.0) <12>
    38 0 0x3ba87000 0x4000 0x3000 com.apple.driver.MacIOGPIO (1.3.0d0) <12>
    39 0 0x3ba9c000 0x5000 0x4000 com.apple.driver.I2CGPIO (1.3.0d0) <12>
    40 2 0x3bb84000 0x22000 0x21000 com.apple.iokit.IOSCSIArchitectureModelFamily (2.1.1) <6 5 4 2>
    41 1 0x3bbb7000 0xc000 0xb000 com.apple.iokit.IOSCSIParallelFamily (1.5.2) <40 6 5 4 2>
    42 0 0x3bbfb000 0x18000 0x17000 com.apple.driver.AppleLSIFusionMPT (2.0.3) <41 17 6 5 4 2>
    43 0 0x3bc27000 0x3000 0x2000 com.apple.driver.AppleKeyswitch (1.0.4d1) <12>
    44 0 0x3bc86000 0x4000 0x3000 com.apple.driver.AppleMPIC (1.5.3) <17 12>
    45 2 0x3bd0e000 0x12000 0x11000 com.apple.iokit.IOATAFamily (2.0.1) <6 5 4 2>
    48 0 0x3bd4e000 0x4000 0x3000 com.apple.driver.AppleVIA (1.5.1d1) <12>
    49 0 0x3bd6a000 0x4000 0x3000 com.apple.driver.AppleGPIO (1.3.0d0) <18 12>
    50 0 0x3be74000 0x16000 0x15000 com.apple.driver.ApplePMU (2.5.6d2) <21 12 7 6 5 4>
    51 0 0x3bee6000 0x3000 0x2000 com.apple.iokit.IOUSBUserClient (3.4.9) <35 6 5 4>
    52 0 0x3bf9b000 0x10000 0xf000 com.apple.driver.AppleUSBHub (3.4.9) <35 6 5 4>
    53 0 0x3c029000 0x4000 0x3000 com.apple.driver.AppleKiwiATA (1.0.2f1) <45 17 12>
    55 5 0x3c13f000 0x21000 0x20000 com.apple.iokit.IOStorageFamily (1.5.6) <7 6 5 4 2>
    56 0 0x3c19c000 0x13000 0x12000 com.apple.iokit.IOATABlockStorage (2.0.6) <55 45 6 5 4 2>
    58 0 0x3c2f5000 0x6000 0x5000 com.apple.driver.XsanFilter (2.7.91) <55 12>
    60 0 0x3c4f4000 0x24000 0x23000 com.apple.driver.AppleRAID (3.0.19) <55 6 5 4>
    61 2 0x356c5000 0x26000 0x25000 com.apple.iokit.IOGraphicsFamily (1.7.3) <17 7 6 5 4>
    62 1 0x356eb000 0x18000 0x17000 com.apple.iokit.IONDRVSupport (1.7.3) <61 17 7 6 5 4>
    63 0 0x3567d000 0x3000 0x2000 com.apple.driver.AppleI2S (1.0.1f1) <12>
    64 1 0x35703000 0xc000 0xb000 com.apple.iokit.IOSerialFamily (9.4) <7 6 5 4 2>
    65 0 0x3570f000 0x9000 0x8000 com.apple.driver.AppleRS574Serial (1.3b7) <64 12>
    66 0 0x35718000 0x4000 0x3000 com.apple.driver.AppleLED (2.0.0a2) <12>
    67 0 0x3571c000 0x4000 0x3000 com.apple.driver.AppleLM87 (2.0.0) <12>
    69 0 0x357e6000 0xf000 0xe000 com.apple.driver.AppleVSP (2.2.2) <12>
    70 3 0x35811000 0x1f000 0x1e000 com.apple.iokit.IONetworkingFamily (1.6.1) <7 6 5 4 2>
    71 0 0x35830000 0xb000 0xa000 com.apple.iokit.IOFireWireIP (1.7.7) <70 31 6 5 4 2>
    72 1 0x35723000 0x4000 0x3000 com.apple.kext.OSvKernDSPLib (1.1) <6 5>
    73 2 0x3b49d000 0x20000 0x1f000 com.apple.iokit.IOAudioFamily (1.6.9fc5) <72 6 5 4 2>
    74 0 0x35727000 0x5000 0x4000 com.apple.driver.VirtualAudioDriver (2.5.8f1) <73 12>
    79 0 0x3b4bd000 0x17000 0x16000 com.apple.iokit.AppleBCM5701Ethernet (2.2.3b1) <70 17 6 5 4 2>
    80 0 0x3b3f5000 0xb000 0xa000 com.apple.iokit.AppleGMACEthernet (1.5.9f1) <70 17 6 5 4 2>
    82 0 0x3a2f8000 0x3000 0x2000 com.apple.driver.AppleFPButton (1.0.5a1) <12>
    83 0 0x3a31a000 0x3000 0x2000 com.apple.driver.AppleHWClock (1.5.2d0) <18 12>
    84 0 0x3b4df000 0x44000 0x43000 com.apple.ATIRadeon (5.4.8) <62 61 17 12 4 2>
    86 0 0x3b400000 0x5000 0x4000 com.apple.driver.AudioIPCDriver (1.0.6) <73 6 5 4 2>
    90 0 0x3b57b000 0x16000 0x15000 com.apple.driver.DiskImages (199) <55 7 6 5 4 2>
    91 0 0x3bd9a000 0xd000 0xc000 com.apple.filesystems.autofs (2.0.2) <7 6 5 4 2>
    92 1 0x22c9d000 0xe000 0xe000 com.apple.driver.ndrv.ATY,BlueStar.0x22ca6248 (1.0.0f251)
    93 0 0x3b555000 0x1b000 0x1a000 com.apple.iokit.IOSCSIBlockCommandsDevice (2.1.1) <55 40 6 5 4 2>
    I'd be grateful for any help or advice in clari
    Message was edited by: gregariousfruit

    I got sick of the error so hard-rebooted the server manually. Seems to be fine now, and software updates work as normal.

  • After reinstalling MAC OS 10.6.8, config the permissions to read/write/no access, my MacMini [mid 2010] refuses to reboot. I tried to reboot in safe mode with fsck, but after the steps to be taken, it says fscs not done, root device is read only

    After reinstalling MAC OS 10.6.8, I config the permissions to read/write/no access, my MacMini [mid 2010] refuses to reboot. I tried to reboot in safe mode with Command+S and fsck, but after the steps to be taken, it says fscs not done, root device is read only. I also tried to bypass the Mac firmware password by taking one Ram card out and reboot the macmini while holding COMMAND+OPTION+P+R. But no luck. The macmini is not able to see the mac OSX installation CD.
    Please help ??

    f.fromleiden wrote:
    After reinstalling MAC OS 10.6.8, I config the permissions to read/write/no access, my MacMini [mid 2010] refuses to reboot.
    How and where did you change which permissions? And what was the goal?
    Do you have a complete backup of your system? and more importantly data files?
    What happened that prompted the need to reinstall the 10.6.8 update?
    The immediate road forward would be to boot from the optical drive and revert the changes you made.
    What happens when you boot with the install cd and hold down C or hold down the option key?
    [Off topic: I've been to Leiden a few times ]

  • 8900 Keeps Rebooting half way through a Reboot.

    Hi,
    I use my BlackBerry for Business, it's my primary phone for both work and personal. Recently I got a brand new 8900 and worked great. One night while away on business it froze for the first time, I pulled out the battery and rebooted it and it kept rebooting half way through. I could not connect it to a PC at all.
    T-Mobile offered no help and sent me to a third party repair guy who told me it would fix it for 60 dollars. This is frustrating as this phone for one is expensive and brand new and should not fail, and secondly, t-mobile offers no support.
    Now for the kicker, my roomate has the same phone and went and got the Droid. He leant me his 8900, also brand new sub 6 months where my first one is sub 3 months old.
    Well tonight, I installed the new bbm and it rebooted the phone and guess what....same thing. Now I have no phone and of course, no support from my carrier. What in gods name is going on with these phones?

    If there is no error message on the phone display that indicates what is going on ("AppError", "JVM Error", both with codes), then we must guess. You might have some luck with this article:
    http://crackberry.com/blackberry-101-lecture-12-how-reload-operating-system-nuked-blackberry
    As for support, front line support for BB's is, by contract, not provided by RIM. The carriers and authorized resellers are responsible for front line formal support to end users. It is possible to bypass your carrier and seek assistance direct from RIM, but such involves fees since you are bypassing your support agreement with your carrier. The "Support and Services" tab toward the top of these forum pages provide information about that. But, if you do go through your carrier for support, they can escalate into RIM at no fee to you if they so choose to.
    Good luck and let us know!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • When I try to start Firefox, I get the error message "Your computer must be restarted to complete a previous upgrade of Firefox. Do you want to reboot now?" I have rebooted several times to no avail. Get the same message when I try to uninstall Firefox

    When I try to start Firefox, I get the error message "Your computer must be restarted to complete a previous upgrade of Firefox. Do you want to reboot now?" I have rebooted several times to no avail. Get the same message when I try to uninstall Firefox

    Just had this same problem. Based on other suggestions I found on the web, went to C:\Program Files\Mozilla Firefox and deleted all files that ended with upgrade and/or delete. Then I was able to uninstall Firefox and then reinstalled. Hope this helps!

  • My computer was dropped yesterday and it will not turn on past this gray screen that tells me to reboot it but everytime I reboot it, it just goes back to that same screen and tells me to do it again. Anyone know how to fix this?

    My computer was dropped yesterday and it will not turn on past this gray screen that tells me to reboot it, but everytime I reboot it, it just goes back to that same screen and tells me to do it again. Anyone know how to fix this?

    When you jar or drop a hard drive when it's operating the heads strike the platters and ruin sectors and the data on them.
    Your getting the spinning wheel because the OS has been damaged and/or quite possibly the drive.
    You'll first have to determine if it's a hardware issue
    Do #3 Hardware Test and #5 Disk Utlity Repair Disk/Permissions here (check the SMART status)
    Step by Step to fix your Mac
    If the drive is fine and you don't have a recent copy of your data off the machine then also do this
    Create a data recovery/undelete external boot drive
    Then proceed with fixing the damaged software, likley by #8 your problem will be fixed.
    Step by Step to fix your Mac

  • [SOLVED] LXDM Shutdown/Reboot Issues

    Under "vanilla" conditions (unmodified /etc/lxdm/lxdm.conf), I have no trouble logging in and out and powering off/rebooting using LXDM.
    My problem seems to arise when I set my main user account to autologin.  The autologin works as expected, and I log back out to LXDM just fine.  After logging out, there is a "username" text field replacing the large user boxes, which is a little out-of-place but isn't my main concern.
    If I try to shutdown or reboot, nothing will happen, and I give it a second just to make sure it isn't taking place in a tty or something odd like that (checked my running tty's just to be sure).  Afterward, I log back in to my main account, and upon logging out once more, the system proceeds to power off.
    The only time I've been able to reproduce it was with the autologin enabled.  Possibly worth noting is my /etc/lxdm/PostLogout, which contains this snippet from the LXDM ArchWiki Page:
    #!/bin/sh
    # Kills all your processes when you log out.
    killall --user $USER -TERM
    May not be very much related, but it is the only other change I have made to LXDM.  However, it had no adverse effects on the shutdown/reboot post-logout functionality with the autologin disabled.
    I would be very grateful if someone could point me in the right direction for fixing this bizarre behavior.
    Last edited by mellowmaroon (2012-06-11 15:18:34)

    I ended up adding /sbin/reboot to /etc/lxdm/PreReboot, and /sbin/poweroff to /etc/lxdm/PreShutdown.
    It's more of a workaround than a solution, but it seems like the easiest and most effective solution so far.  No problems with it yet.

  • [Solved] Clean shutdown/reboot/suspend,wakeup no longer possible.

    No matter how I try to shut down my arch system, via systemctl poweroff, or through the GUI, or using /sbin/shutdown, my system will hang while shutting down. Forcing me to hold the power key down for a forced shutdown. This is the log from the last time this happened.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Starting Shutdown.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Starting Shutdown.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Reached target Shutdown.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Reached target Shutdown.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopping Default.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Starting Exit the Session...
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopped target Default.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopping Basic System.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopped target Basic System.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopping Timers.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopped target Timers.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopping Default.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopped target Default.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopping Basic System.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopping Sockets.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopped target Sockets.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopping Paths.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopped target Basic System.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Stopped target Paths.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopping Timers.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Starting Exit the Session...
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopped target Timers.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopping Sockets.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopped target Sockets.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopping Paths.
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Stopped target Paths.
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopped Network Manager.
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopped Login Service.
    Jan 30 13:24:12 Steves-MacBook systemd[257]: Received SIGRTMIN+24 from PID 596 (kill).
    Jan 30 13:24:12 Steves-MacBook systemd[272]: Received SIGRTMIN+24 from PID 595 (kill).
    Jan 30 13:24:12 Steves-MacBook systemd[258]: pam_unix(systemd-user:session): session closed for user sddm
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopped User Manager for UID 997.
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopping user-997.slice.
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Removed slice user-997.slice.
    Jan 30 13:24:12 Steves-MacBook systemd[273]: pam_unix(systemd-user:session): session closed for user steve
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopped User Manager for UID 501.
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopping Permit User Sessions...
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopping user-501.slice.
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Removed slice user-501.slice.
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopped Permit User Sessions.
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopping Remote File Systems.
    Jan 30 13:24:12 Steves-MacBook systemd[1]: Stopped target Remote File Systems.
    Jan 30 13:24:12 Steves-MacBook mkinitcpio[574]: ==> Starting build: none
    Jan 30 13:24:12 Steves-MacBook mkinitcpio[574]: -> Running build hook: [sd-shutdown]
    Jan 30 13:24:13 Steves-MacBook mkinitcpio[574]: ==> Build complete.
    Jan 30 13:24:13 Steves-MacBook systemd[1]: Started Generate shutdown-ramfs.
    Jan 30 13:24:26 Steves-MacBook kernel: INFO: task krunner:355 blocked for more than 120 seconds.
    Jan 30 13:24:26 Steves-MacBook kernel: Tainted: G W 3.18.4-1-ARCH #1
    Jan 30 13:24:26 Steves-MacBook kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 30 13:24:26 Steves-MacBook kernel: krunner D 00000001 0 355 1 0x00000004
    Jan 30 13:24:26 Steves-MacBook kernel: f721bcf4 00000082 c1637280 00000001 00000001 c16deb00 c1637dc4 00000000
    Jan 30 13:24:26 Steves-MacBook kernel: c16deb00 00000000 f13c3340 0000001d f5711b00 f0da8c80 c155985e f721bcb4
    Jan 30 13:24:26 Steves-MacBook kernel: c104b43a 00000001 f5d46b40 00000001 f5d46b40 f721bd30 c112698d 00000001
    Jan 30 13:24:26 Steves-MacBook kernel: Call Trace:
    Jan 30 13:24:26 Steves-MacBook kernel: [<c104b43a>] ? kmap_atomic_prot+0x3a/0xe0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c112698d>] ? get_page_from_freelist+0x37d/0x5f0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c10920ca>] ? mutex_optimistic_spin+0x4a/0x1a0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1476833>] schedule+0x23/0x60
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1476c14>] schedule_preempt_disabled+0x14/0x20
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1477fa2>] __mutex_lock_slowpath+0xb2/0x120
    Jan 30 13:24:26 Steves-MacBook kernel: [<c14775e5>] mutex_lock+0x15/0x30
    Jan 30 13:24:26 Steves-MacBook kernel: [<f89ba2eb>] acpi_smbus_transaction+0x58/0x267 [sbshc]
    Jan 30 13:24:26 Steves-MacBook kernel: [<c100985e>] ? poke_int3_handler+0x3e/0x60
    Jan 30 13:24:26 Steves-MacBook kernel: [<c104b43a>] ? kmap_atomic_prot+0x3a/0xe0
    Jan 30 13:24:26 Steves-MacBook kernel: [<f89ba518>] acpi_smbus_read+0x1e/0x23 [sbshc]
    Jan 30 13:24:26 Steves-MacBook kernel: [<f89cd111>] acpi_battery_get_state+0x60/0x88 [sbs]
    Jan 30 13:24:26 Steves-MacBook kernel: [<f89cd848>] acpi_sbs_battery_get_property+0x2f/0x3ff [sbs]
    Jan 30 13:24:26 Steves-MacBook kernel: [<c134ea4a>] power_supply_show_property+0x4a/0x260
    Jan 30 13:24:26 Steves-MacBook kernel: [<c134ed68>] power_supply_uevent+0xc8/0x2a0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1186b8f>] ? terminate_walk+0x4f/0x60
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1318bb1>] dev_uevent+0xb1/0x2f0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11669e4>] ? kmem_cache_alloc_trace+0x124/0x140
    Jan 30 13:24:26 Steves-MacBook kernel: [<c124b3f0>] ? lockref_put_or_lock+0x20/0x40
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1316c5c>] ? uevent_show+0x6c/0xf0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1316c74>] uevent_show+0x84/0xf0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c114b5ea>] ? __vma_link_rb+0x5a/0x70
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1316bf0>] ? dev_show+0x40/0x40
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1317170>] ? dev_driver_string+0x20/0x20
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1317188>] dev_attr_show+0x18/0x40
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11e0861>] sysfs_kf_seq_show+0xb1/0x170
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11df53d>] kernfs_seq_show+0x1d/0x30
    Jan 30 13:24:26 Steves-MacBook kernel: [<c119bcd2>] seq_read+0x92/0x3a0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11dfcf6>] kernfs_fop_read+0xd6/0x130
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11389cb>] ? vm_mmap_pgoff+0x9b/0xc0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11dfc20>] ? kernfs_fop_write+0x160/0x160
    Jan 30 13:24:26 Steves-MacBook kernel: [<c117c2b8>] vfs_read+0x78/0x170
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11962e2>] ? __fget_light+0x22/0x60
    Jan 30 13:24:26 Steves-MacBook kernel: [<c117c9c7>] SyS_read+0x57/0xc0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c147a057>] sysenter_do_call+0x12/0x12
    Jan 30 13:24:26 Steves-MacBook kernel: INFO: task plasmashell:357 blocked for more than 120 seconds.
    Jan 30 13:24:26 Steves-MacBook kernel: Tainted: G W 3.18.4-1-ARCH #1
    Jan 30 13:24:26 Steves-MacBook kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 30 13:24:26 Steves-MacBook kernel: plasmashell D 00000141 0 357 1 0x00000004
    Jan 30 13:24:26 Steves-MacBook kernel: f0c99cf4 00000082 00000002 00000141 000267f3 c16deb00 c1637dc4 00000001
    Jan 30 13:24:26 Steves-MacBook kernel: c16deb00 00000000 f13c2380 0000001e f5711b00 f122cb00 c155985e f0c99cb4
    Jan 30 13:24:26 Steves-MacBook kernel: c104b43a 00000001 f5d5aec0 00000001 f5d5aec0 f0c99d30 c112698d 00000001
    Jan 30 13:24:26 Steves-MacBook kernel: Call Trace:
    Jan 30 13:24:26 Steves-MacBook kernel: [<c104b43a>] ? kmap_atomic_prot+0x3a/0xe0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c112698d>] ? get_page_from_freelist+0x37d/0x5f0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c10920ca>] ? mutex_optimistic_spin+0x4a/0x1a0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1476833>] schedule+0x23/0x60
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1476c14>] schedule_preempt_disabled+0x14/0x20
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1477fa2>] __mutex_lock_slowpath+0xb2/0x120
    Jan 30 13:24:26 Steves-MacBook kernel: [<c14775e5>] mutex_lock+0x15/0x30
    Jan 30 13:24:26 Steves-MacBook kernel: [<f89ba2eb>] acpi_smbus_transaction+0x58/0x267 [sbshc]
    Jan 30 13:24:26 Steves-MacBook kernel: [<c100985e>] ? poke_int3_handler+0x3e/0x60
    Jan 30 13:24:26 Steves-MacBook kernel: [<c104b43a>] ? kmap_atomic_prot+0x3a/0xe0
    Jan 30 13:24:26 Steves-MacBook kernel: [<f89ba518>] acpi_smbus_read+0x1e/0x23 [sbshc]
    Jan 30 13:24:26 Steves-MacBook kernel: [<f89cd111>] acpi_battery_get_state+0x60/0x88 [sbs]
    Jan 30 13:24:26 Steves-MacBook kernel: [<f89cd848>] acpi_sbs_battery_get_property+0x2f/0x3ff [sbs]
    Jan 30 13:24:26 Steves-MacBook kernel: [<c134ea4a>] power_supply_show_property+0x4a/0x260
    Jan 30 13:24:26 Steves-MacBook kernel: [<c134ed68>] power_supply_uevent+0xc8/0x2a0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1186b8f>] ? terminate_walk+0x4f/0x60
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1318bb1>] dev_uevent+0xb1/0x2f0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11669e4>] ? kmem_cache_alloc_trace+0x124/0x140
    Jan 30 13:24:26 Steves-MacBook kernel: [<c124b3f0>] ? lockref_put_or_lock+0x20/0x40
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1316c5c>] ? uevent_show+0x6c/0xf0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1316c74>] uevent_show+0x84/0xf0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c114b5ea>] ? __vma_link_rb+0x5a/0x70
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1316bf0>] ? dev_show+0x40/0x40
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1317170>] ? dev_driver_string+0x20/0x20
    Jan 30 13:24:26 Steves-MacBook kernel: [<c1317188>] dev_attr_show+0x18/0x40
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11e0861>] sysfs_kf_seq_show+0xb1/0x170
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11df53d>] kernfs_seq_show+0x1d/0x30
    Jan 30 13:24:26 Steves-MacBook kernel: [<c119bcd2>] seq_read+0x92/0x3a0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11dfcf6>] kernfs_fop_read+0xd6/0x130
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11389cb>] ? vm_mmap_pgoff+0x9b/0xc0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11dfc20>] ? kernfs_fop_write+0x160/0x160
    Jan 30 13:24:26 Steves-MacBook kernel: [<c117c2b8>] vfs_read+0x78/0x170
    Jan 30 13:24:26 Steves-MacBook kernel: [<c11962e2>] ? __fget_light+0x22/0x60
    Jan 30 13:24:26 Steves-MacBook kernel: [<c117c9c7>] SyS_read+0x57/0xc0
    Jan 30 13:24:26 Steves-MacBook kernel: [<c147a057>] sysenter_do_call+0x12/0x12
    Jan 30 13:25:42 Steves-MacBook systemd[1]: upower.service stop-sigterm timed out. Killing.
    Jan 30 13:26:26 Steves-MacBook kernel: INFO: task krunner:355 blocked for more than 120 seconds.
    Jan 30 13:26:26 Steves-MacBook kernel: Tainted: G W 3.18.4-1-ARCH #1
    Jan 30 13:26:26 Steves-MacBook kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 30 13:26:26 Steves-MacBook kernel: krunner D 00000001 0 355 1 0x00000004
    Jan 30 13:26:26 Steves-MacBook kernel: f721bcf4 00000082 c1637280 00000001 00000001 c16deb00 c1637dc4 00000000
    Jan 30 13:26:26 Steves-MacBook kernel: c16deb00 00000000 f13c3340 0000001d f5711b00 f0da8c80 c155985e f721bcb4
    Jan 30 13:26:26 Steves-MacBook kernel: c104b43a 00000001 f5d46b40 00000001 f5d46b40 f721bd30 c112698d 00000001
    Jan 30 13:26:26 Steves-MacBook kernel: Call Trace:
    Jan 30 13:26:26 Steves-MacBook kernel: [<c104b43a>] ? kmap_atomic_prot+0x3a/0xe0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c112698d>] ? get_page_from_freelist+0x37d/0x5f0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c10920ca>] ? mutex_optimistic_spin+0x4a/0x1a0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1476833>] schedule+0x23/0x60
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1476c14>] schedule_preempt_disabled+0x14/0x20
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1477fa2>] __mutex_lock_slowpath+0xb2/0x120
    Jan 30 13:26:26 Steves-MacBook kernel: [<c14775e5>] mutex_lock+0x15/0x30
    Jan 30 13:26:26 Steves-MacBook kernel: [<f89ba2eb>] acpi_smbus_transaction+0x58/0x267 [sbshc]
    Jan 30 13:26:26 Steves-MacBook kernel: [<c100985e>] ? poke_int3_handler+0x3e/0x60
    Jan 30 13:26:26 Steves-MacBook kernel: [<c104b43a>] ? kmap_atomic_prot+0x3a/0xe0
    Jan 30 13:26:26 Steves-MacBook kernel: [<f89ba518>] acpi_smbus_read+0x1e/0x23 [sbshc]
    Jan 30 13:26:26 Steves-MacBook kernel: [<f89cd111>] acpi_battery_get_state+0x60/0x88 [sbs]
    Jan 30 13:26:26 Steves-MacBook kernel: [<f89cd848>] acpi_sbs_battery_get_property+0x2f/0x3ff [sbs]
    Jan 30 13:26:26 Steves-MacBook kernel: [<c134ea4a>] power_supply_show_property+0x4a/0x260
    Jan 30 13:26:26 Steves-MacBook kernel: [<c134ed68>] power_supply_uevent+0xc8/0x2a0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1186b8f>] ? terminate_walk+0x4f/0x60
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1318bb1>] dev_uevent+0xb1/0x2f0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11669e4>] ? kmem_cache_alloc_trace+0x124/0x140
    Jan 30 13:26:26 Steves-MacBook kernel: [<c124b3f0>] ? lockref_put_or_lock+0x20/0x40
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1316c5c>] ? uevent_show+0x6c/0xf0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1316c74>] uevent_show+0x84/0xf0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c114b5ea>] ? __vma_link_rb+0x5a/0x70
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1316bf0>] ? dev_show+0x40/0x40
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1317170>] ? dev_driver_string+0x20/0x20
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1317188>] dev_attr_show+0x18/0x40
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11e0861>] sysfs_kf_seq_show+0xb1/0x170
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11df53d>] kernfs_seq_show+0x1d/0x30
    Jan 30 13:26:26 Steves-MacBook kernel: [<c119bcd2>] seq_read+0x92/0x3a0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11dfcf6>] kernfs_fop_read+0xd6/0x130
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11389cb>] ? vm_mmap_pgoff+0x9b/0xc0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11dfc20>] ? kernfs_fop_write+0x160/0x160
    Jan 30 13:26:26 Steves-MacBook kernel: [<c117c2b8>] vfs_read+0x78/0x170
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11962e2>] ? __fget_light+0x22/0x60
    Jan 30 13:26:26 Steves-MacBook kernel: [<c117c9c7>] SyS_read+0x57/0xc0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c147a057>] sysenter_do_call+0x12/0x12
    Jan 30 13:26:26 Steves-MacBook kernel: INFO: task plasmashell:357 blocked for more than 120 seconds.
    Jan 30 13:26:26 Steves-MacBook kernel: Tainted: G W 3.18.4-1-ARCH #1
    Jan 30 13:26:26 Steves-MacBook kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Jan 30 13:26:26 Steves-MacBook kernel: plasmashell D 00000141 0 357 1 0x00000004
    Jan 30 13:26:26 Steves-MacBook kernel: f0c99cf4 00000082 00000002 00000141 000267f3 c16deb00 c1637dc4 00000001
    Jan 30 13:26:26 Steves-MacBook kernel: c16deb00 00000000 f13c2380 0000001e f5711b00 f122cb00 c155985e f0c99cb4
    Jan 30 13:26:26 Steves-MacBook kernel: c104b43a 00000001 f5d5aec0 00000001 f5d5aec0 f0c99d30 c112698d 00000001
    Jan 30 13:26:26 Steves-MacBook kernel: Call Trace:
    Jan 30 13:26:26 Steves-MacBook kernel: [<c104b43a>] ? kmap_atomic_prot+0x3a/0xe0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c112698d>] ? get_page_from_freelist+0x37d/0x5f0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c10920ca>] ? mutex_optimistic_spin+0x4a/0x1a0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1476833>] schedule+0x23/0x60
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1476c14>] schedule_preempt_disabled+0x14/0x20
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1477fa2>] __mutex_lock_slowpath+0xb2/0x120
    Jan 30 13:26:26 Steves-MacBook kernel: [<c14775e5>] mutex_lock+0x15/0x30
    Jan 30 13:26:26 Steves-MacBook kernel: [<f89ba2eb>] acpi_smbus_transaction+0x58/0x267 [sbshc]
    Jan 30 13:26:26 Steves-MacBook kernel: [<c100985e>] ? poke_int3_handler+0x3e/0x60
    Jan 30 13:26:26 Steves-MacBook kernel: [<c104b43a>] ? kmap_atomic_prot+0x3a/0xe0
    Jan 30 13:26:26 Steves-MacBook kernel: [<f89ba518>] acpi_smbus_read+0x1e/0x23 [sbshc]
    Jan 30 13:26:26 Steves-MacBook kernel: [<f89cd111>] acpi_battery_get_state+0x60/0x88 [sbs]
    Jan 30 13:26:26 Steves-MacBook kernel: [<f89cd848>] acpi_sbs_battery_get_property+0x2f/0x3ff [sbs]
    Jan 30 13:26:26 Steves-MacBook kernel: [<c134ea4a>] power_supply_show_property+0x4a/0x260
    Jan 30 13:26:26 Steves-MacBook kernel: [<c134ed68>] power_supply_uevent+0xc8/0x2a0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1186b8f>] ? terminate_walk+0x4f/0x60
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1318bb1>] dev_uevent+0xb1/0x2f0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11669e4>] ? kmem_cache_alloc_trace+0x124/0x140
    Jan 30 13:26:26 Steves-MacBook kernel: [<c124b3f0>] ? lockref_put_or_lock+0x20/0x40
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1316c5c>] ? uevent_show+0x6c/0xf0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1316c74>] uevent_show+0x84/0xf0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c114b5ea>] ? __vma_link_rb+0x5a/0x70
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1316bf0>] ? dev_show+0x40/0x40
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1317170>] ? dev_driver_string+0x20/0x20
    Jan 30 13:26:26 Steves-MacBook kernel: [<c1317188>] dev_attr_show+0x18/0x40
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11e0861>] sysfs_kf_seq_show+0xb1/0x170
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11df53d>] kernfs_seq_show+0x1d/0x30
    Jan 30 13:26:26 Steves-MacBook kernel: [<c119bcd2>] seq_read+0x92/0x3a0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11dfcf6>] kernfs_fop_read+0xd6/0x130
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11389cb>] ? vm_mmap_pgoff+0x9b/0xc0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11dfc20>] ? kernfs_fop_write+0x160/0x160
    Jan 30 13:26:26 Steves-MacBook kernel: [<c117c2b8>] vfs_read+0x78/0x170
    Jan 30 13:26:26 Steves-MacBook kernel: [<c11962e2>] ? __fget_light+0x22/0x60
    Jan 30 13:26:26 Steves-MacBook kernel: [<c117c9c7>] SyS_read+0x57/0xc0
    Jan 30 13:26:26 Steves-MacBook kernel: [<c147a057>] sysenter_do_call+0x12/0x12
    -- Reboot --
    I'm using a 2006 32 bit MacBook, with KDE Plasma 5.2 as my GUI. The problem began about 2 weeks ago, but I'm unable to pinpoint the software update that started this.
    Suspending has also become a problem because when my laptop wakes up from sleep mode, nothing happens (the system is inaccessible over the network, display never comes on, no log entries are added to the journal). The usual solution, hold down the power button. I can say that this isn't a hardware problem because suspend/wakeup works perfectly on OSX and Windows.
    Any help will be appreciated.
    Last edited by stevedes (2015-01-31 06:45:22)

    Head_on_a_Stick wrote:
    stevedes wrote:Any suggestions on what to do next?
    Either keep trying the new kernel versions as they filter down or switch to the 3.14 LTS kernel (if that works).
    I'll do that, thanks for the help.

  • [SOLVED] Poweroff and Reboot without Sudo

    How can I Poweroff and Reboot my system without using sudo?
    Last edited by aldoiljazi (2013-09-18 06:52:28)

    Stebalien wrote:
    @karol: systemd assumes that anyone with console access can shutdown/reboot the computer anyway (as they are sitting at the computer). Therefore, he should be able to issue `systemctl poweroff` etc. iff his session is setup correctly.
    What is the output of `loginctl show-session $XDG_SESSION_ID`?
    $ loginctl show-session $XDG_SESSION_ID
    Id=1
    Timestamp=Mon 2013-09-16 21:11:47 EEST
    TimestampMonotonic=13019390
    DefaultControlGroup=systemd:/user/1000.user/1.session
    VTNr=1
    TTY=tty1
    Remote=no
    Service=login
    Leader=130
    Audit=1
    Type=tty
    Class=user
    Active=yes
    State=active
    KillProcesses=no
    IdleHint=yes
    IdleSinceHint=1379355104466900
    IdleSinceHintMonotonic=10330073
    Name=aldo
    mine.
    Last edited by aldoiljazi (2013-09-16 19:47:04)

  • [SOLVED]Disable Shutdown and Reboot from XFCE

    Hi all
    I would like to disable the shutdown and reboot buttons from XFCE (4.10) or to do disable shutdown/reboot systemwide.
    I searched for specific xfce instructions and all i could find was using xfconf-query[1] and afaik it can only disable hibernate and suspend buttons
    [1]http://forum.xfce.org/viewtopic.php?id=4781
    Last edited by boriscougar (2012-09-11 21:51:22)

    @nadman10
    it had no change to remove my users from the power group
    @2ManyDogs
    Creating that file (/etc/xdg/xfce4/kiosk/kioskrc) and setting which users could shutdown solved the problem
    Thanks for your time

  • [SOLVED] XFCE shutdown and reboot buttons only dump out to prompt

    Recently, after an update, the XFCE shutdown and reboot buttons began not working as expected.  Both are present, and I can click them.   They seem to try to do what they should, XFCE does terminate, but I am dumped out to a shell prompt rather than the shutdown or reboot happening.   What might be a possible cause of this behaviour that I can check and correct?
    Thanks,
    Bill
    Last edited by wallenpb (2012-11-20 21:00:19)

    Are you running systemd or still a sysv/initscript setup?
    If it is the latter take into account that consolekit has been dropped. Therefore, as far as I understand it, you are not 'authenticated' and thus not allowed to either shutdown or reboot.
    Consider switching to systemd and a good start would be to comply with the 1st step of the systemd installation featured in the wiki to regain control of shutdown/reboot. Afterwards start investigating for the rest as initscripts support has ended.

  • [SOLVED]Openbox shutdown issue

    I have added shutdown and reboot capabilities to a standard openbox menu. The reboot works fine but the shutdown has some issues. When I select "Shutdown" my X stops responding and the only thing i can do is kill X (Ctrl+Alt+Backspace) and then issue a shutdown command manually.
    This is my relevant openbox menu entry
    <menu id="quit-menu" label="Quit">
    <item label="Log Out">
    <action name="Exit">
    <prompt>yes</prompt>
    </action>
    </item>
    <item label="Reboot">
    <action name="Execute">
    <command>sudo shutdown -r now</command>
    </action>
    </item>
    <item label="Shutdown">
    <action name="Execute">
    <command>sudo shutdown -h now</command>
    </action>
    </item>
    </menu>
    and I have added this line at the end of the sudoers file
    inxsible ALL=NOPASSWD:/sbin/shutdown
    Why is it that reboot works and shutdown doesn't?
    Last edited by Inxsible (2009-01-23 00:30:14)

    B wrote:
    Well I have it here anyway so...
    [stijn@hermes ~]$ cat /etc/acpi/events/power
    # This is called when the user presses the power button
    event=button/power (PWR.||PBTN)
    action=/sbin/poweroff
    Restart acpid and enjoy .
    It's also funny to have people see you press that button and everything goes out. 'Oh no you cannot do that! That is bad for your system!'
    Windows users eeh .
    Already got it from the Wiki. acpid doesnt seem to wanna start. it says device or resource busy.
    I will try a reboot and see.
    Hopefully it should work. BUT it still irks me that the /sbin/shutdown option doesn't work for shutdown but works for reboot. GRRRRRRRRRR !!!!

  • [solved] systemd shutdown scripts

    I'm trying to configure network-ups-tools to properly shutdown UPS after system is halted, so UPS and server could restart when the line power is regained. network-ups-tools contains /usr/lib/systemd/system-shutdown/nutshutdown shell script which checks if shutdown was caused by nut-monitor daemon and in this case shuts down the UPS. Unfortunately it seems that script isn't executed.
    According to man systemd-shutdown:
    Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in /usr/lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen action.
    It sounds logical to use this feature rather than service executed at shutdown as this script will immediately cut the power.
    I've created /usr/lib/systemd/system-shutdown/test.sh which writes echo $1 to file, but it also does not seem to be executed. What am I doing wrong?
    Last edited by denn (2013-11-29 07:12:20)

    Right, I use this feature also for my UPS (APC). Did you set the right file mode (0755) ?
    In my case:
    /usr/lib/systemd/system-shutdown/apc_killpower
    #!/bin/sh
    if [ -f /etc/apcupsd/powerfail -a "$1" = "poweroff" ]; then
    /etc/apcupsd/apccontrol killpower
    fi
    At that point / is mounted ro, your file should be writed to /run for example, then from "initramfs" after pivot_root (if you have enabled shutdown hook) you can see it (just execute "ash" in /run/initramfs/shutdown at some point , ie just before poweroff

  • [SOLVED]Keyboard and touchpad doesn't work after reboot from Arch

    Excuse me, but i'm a newbie. I'm not sure if this is an arch problem, but i will just post it here.
    I've beening using Arch64 and it works just fine. However, every time i reboot from arch into Windows 7 (32bit), the keyboard and touchpad will stop responding just when the Win7 splash screen shows, however the mouse works fine. Then when you shutdown the computer (from win7 now) it will take apparently longer time, and sometimes i have to press the power key 5 seconds to make it shutdown.
    It seems the correct way (to reboot from arch to win7) is to shutdown down the computer first and start it again, and everything will work fine.
    And rebooting from win7 to win7 or arch to arch or win7 to arch will work fine too.
    I'm glad to post extra information, but I've got no clue and i'm not sure what to put here.
    The laptop is a Lenovo Y450 with Intel Core Dual P7540, 4G Memory, NV GT240M. Kernel version of Arch is 3.0.6 (but the problem existed long since earlier versions) I don't have a swap partition. If you need extra information, please mention the item.
    Thanks a lot!
    Last edited by crlf0710 (2011-11-15 10:29:38)

    Hi!
    That is indeed strange. Since your external mouse works fine (which probably is connected via USB, right?) it appears that the problem lies somewhere around the internal keyboard/touchpad access. I'm not sure how this works with a Lenovo Y450, but just try to enter BIOS (in case you have not been there, you probably have to hit F1 or F2 during startup - less likely it would be delete or escape ...) and look for your keyboard/touchpad options.
    You should probably find something like "... legacy support ...". This is a relic from PS/2 times and emulates your internal input devices as PS/2 devices. So - when found, just change the setting (you cannot mess anything up, and both systems will probably not even pop up a message). My guess is it is set to "enabled" and Arch somehow messes with the PS/2 emulation in your case .... so just turn it off.
    good luck

Maybe you are looking for