[SOLVED] System stuck on suspend/shutdown

Hi guys,
I recently set up a new system with Arch Linux, and everything's working perfectly fine - except for one thing: When shutting the computer down, the system gets all the way to the end of the shutdown cycle and displays "Rebooting" - and just stays there, the computer doesn't turn off (even after almost an hour, no change). It does tell me just before that, that it failed to unmount /oldroot/dev, however, it claims to be ignoring that problem...? And everytime, just before it unmounts (or tries to at least) all the /oldroot/ stuff, it gets stuck shortly while trying to terminate some "tee" process (it eventually sends a SIGKILL signal and proceeds shortly after).
Could this maybe cause some problem when powering off? Because also when I try to suspend my system, the screen turns blank (with a blinking cursor in the top left), and shortly after it displays the message "Freezing of tasks failed after 20.005 seconds (3 tasks refusing to freeze, wq_busy=0)" and goes back to my desktop. Using dmesg, I found that, again, "tee" is the process causing problems. When I list all running processes, it displays 3 of these "tee" processes, and under CPU% it says "disk sleep" for all of them...
Here is an extract of dmesg that displays the suspend/freezing problem:
[ 2519.042907] Freezing user space processes ...
[ 2539.053497] Freezing of tasks failed after 20.005 seconds (3 tasks refusing to freeze, wq_busy=0):
[ 2539.053587] tee D 0000000000000000 0 2919 1 0x00000004
[ 2539.053593] ffff8800a664fdc0 0000000000000000 ffff88012524f010 0000000000000000
[ 2539.053599] ffff8800a664ffd8 0000000000000000 ffff88012524f010 ffffffff811cfefa
[ 2539.053601] ffff88012524f010 ffff88012524f010 ffff8800a9454900 ffff880131a6f000
[ 2539.053603] Call Trace:
[ 2539.053613] [<ffffffff811cfefa>] ? do_last.isra.36+0x1ba/0xe50
[ 2539.053617] [<ffffffff811c4808>] ? __sb_start_write+0x58/0x110
[ 2539.053620] [<ffffffff811c4781>] ? __sb_end_write+0x31/0x60
[ 2539.053623] [<ffffffff8152d289>] schedule+0x29/0x70
[ 2539.053625] [<ffffffff8152d6f6>] schedule_preempt_disabled+0x16/0x20
[ 2539.053628] [<ffffffff8152f075>] __mutex_lock_slowpath+0xe5/0x230
[ 2539.053630] [<ffffffff8152f1d7>] mutex_lock+0x17/0x30
[ 2539.053634] [<ffffffff813ab548>] control_store+0x48/0xd0
[ 2539.053638] [<ffffffff812010bc>] ? fsnotify+0x28c/0x370
[ 2539.053642] [<ffffffff8139fee8>] dev_attr_store+0x18/0x30
[ 2539.053647] [<ffffffff8123885a>] sysfs_kf_write+0x3a/0x50
[ 2539.053649] [<ffffffff81237dce>] kernfs_fop_write+0xee/0x180
[ 2539.053651] [<ffffffff811c1f97>] vfs_write+0xb7/0x200
[ 2539.053653] [<ffffffff811c1eac>] ? vfs_read+0x13c/0x170
[ 2539.053654] [<ffffffff811c2c09>] SyS_write+0x59/0xd0
[ 2539.053657] [<ffffffff81531129>] system_call_fastpath+0x16/0x1b
[ 2539.053658] tee D 0000000000000000 0 3352 2935 0x00000004
[ 2539.053660] ffff8800857cbdc0 0000000000000000 ffff88008573b2f0 0000000000000000
[ 2539.053662] ffff8800857cbfd8 0000000000000000 ffff88008573b2f0 ffffffff811cfefa
[ 2539.053664] ffff88008573b2f0 ffff88008573b2f0 ffff8800a9454900 ffff8800856bc300
[ 2539.053666] Call Trace:
[ 2539.053668] [<ffffffff811cfefa>] ? do_last.isra.36+0x1ba/0xe50
[ 2539.053674] [<ffffffff810725b2>] ? current_fs_time+0x12/0x60
[ 2539.053675] [<ffffffff8152d289>] schedule+0x29/0x70
[ 2539.053677] [<ffffffff8152d6f6>] schedule_preempt_disabled+0x16/0x20
[ 2539.053679] [<ffffffff8152f075>] __mutex_lock_slowpath+0xe5/0x230
[ 2539.053681] [<ffffffff8152f1d7>] mutex_lock+0x17/0x30
[ 2539.053682] [<ffffffff813ab548>] control_store+0x48/0xd0
[ 2539.053684] [<ffffffff812010bc>] ? fsnotify+0x28c/0x370
[ 2539.053686] [<ffffffff8139fee8>] dev_attr_store+0x18/0x30
[ 2539.053688] [<ffffffff8123885a>] sysfs_kf_write+0x3a/0x50
[ 2539.053690] [<ffffffff81237dce>] kernfs_fop_write+0xee/0x180
[ 2539.053692] [<ffffffff811c1f97>] vfs_write+0xb7/0x200
[ 2539.053694] [<ffffffff811c1eac>] ? vfs_read+0x13c/0x170
[ 2539.053695] [<ffffffff811c2c09>] SyS_write+0x59/0xd0
[ 2539.053697] [<ffffffff81531129>] system_call_fastpath+0x16/0x1b
[ 2539.053699] tee D 0000000000000000 0 3806 1 0x00000004
[ 2539.053701] ffff8800a643bdc0 0000000000000000 ffff880085739460 0000000000000000
[ 2539.053703] ffff8800a643bfd8 0000000000000000 ffff880085739460 ffffffff811cfefa
[ 2539.053704] ffff880085739460 ffff880085739460 ffff8800a9454900 ffff8800a4abf000
[ 2539.053706] Call Trace:
[ 2539.053708] [<ffffffff811cfefa>] ? do_last.isra.36+0x1ba/0xe50
[ 2539.053710] [<ffffffff810725b2>] ? current_fs_time+0x12/0x60
[ 2539.053712] [<ffffffff8152d289>] schedule+0x29/0x70
[ 2539.053713] [<ffffffff8152d6f6>] schedule_preempt_disabled+0x16/0x20
[ 2539.053715] [<ffffffff8152f075>] __mutex_lock_slowpath+0xe5/0x230
[ 2539.053717] [<ffffffff8152f1d7>] mutex_lock+0x17/0x30
[ 2539.053719] [<ffffffff813ab548>] control_store+0x48/0xd0
[ 2539.053721] [<ffffffff812010bc>] ? fsnotify+0x28c/0x370
[ 2539.053722] [<ffffffff8139fee8>] dev_attr_store+0x18/0x30
[ 2539.053724] [<ffffffff8123885a>] sysfs_kf_write+0x3a/0x50
[ 2539.053726] [<ffffffff81237dce>] kernfs_fop_write+0xee/0x180
[ 2539.053728] [<ffffffff811c1f97>] vfs_write+0xb7/0x200
[ 2539.053730] [<ffffffff811c1eac>] ? vfs_read+0x13c/0x170
[ 2539.053732] [<ffffffff811c2c09>] SyS_write+0x59/0xd0
[ 2539.053734] [<ffffffff81531129>] system_call_fastpath+0x16/0x1b
Don't know if that's in any way related to the above problem(s), but I also have loads of such messages in dmesg:
[ 1321.983088] INFO: task kworker/u16:3:91 blocked for more than 120 seconds.
[ 1321.983096] Not tainted 3.16.3-1-ARCH #1
[ 1321.983098] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1321.983100] kworker/u16:3 D 0000000000000000 0 91 2 0x00000000
[ 1321.983112] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
[ 1321.983115] ffff88003793baa0 0000000000000000 ffff88003764d180 0000000000000000
[ 1321.983119] ffff88003793bfd8 0000000000000000 ffff88003764d180 000000005a1a7d0b
[ 1321.983123] 0000000000000000 0000000000000000 0000000000000000 ffffffffa0585f7d
[ 1321.983127] Call Trace:
[ 1321.983148] [<ffffffff813a11de>] ? __dev_printk+0x3e/0x90
[ 1321.983152] [<ffffffff813a16fc>] ? _dev_info+0x6c/0x90
[ 1321.983160] [<ffffffff812a7fb7>] ? ___ratelimit+0x87/0x100
[ 1321.983166] [<ffffffff8152d289>] schedule+0x29/0x70
[ 1321.983169] [<ffffffff8152c479>] schedule_timeout+0x1b9/0x240
[ 1321.983175] [<ffffffff8139d730>] ? vga_switcheroo_show+0x140/0x140
[ 1321.983179] [<ffffffff8152dd3f>] wait_for_common+0xcf/0x190
[ 1321.983184] [<ffffffff810a2ce0>] ? wake_up_process+0x50/0x50
[ 1321.983188] [<ffffffff8152de1d>] wait_for_completion+0x1d/0x20
[ 1321.983204] [<ffffffffa02dffc3>] snd_card_free+0x63/0x90 [snd]
[ 1321.983212] [<ffffffffa058277a>] azx_remove+0x1a/0x20 [snd_hda_intel]
[ 1321.983216] [<ffffffff812df88b>] pci_device_remove+0x3b/0xc0
[ 1321.983219] [<ffffffff813a500f>] __device_release_driver+0x7f/0xf0
[ 1321.983220] [<ffffffff813a50a3>] device_release_driver+0x23/0x30
[ 1321.983224] [<ffffffff812d9a04>] pci_stop_bus_device+0x94/0xa0
[ 1321.983226] [<ffffffff812d99a5>] pci_stop_bus_device+0x35/0xa0
[ 1321.983228] [<ffffffff812d9b22>] pci_stop_and_remove_bus_device+0x12/0x20
[ 1321.983231] [<ffffffff812f9d47>] disable_slot+0x57/0xb0
[ 1321.983233] [<ffffffff812fa538>] acpiphp_check_bridge.part.9+0xf8/0x100
[ 1321.983235] [<ffffffff812fb008>] acpiphp_check_host_bridge+0x78/0xc0
[ 1321.983238] [<ffffffff813255d9>] acpi_pci_root_scan_dependent+0xe/0x12
[ 1321.983241] [<ffffffff81321c34>] acpi_scan_bus_check+0x42/0xa2
[ 1321.983243] [<ffffffff81321d3c>] acpi_device_hotplug+0xa8/0x408
[ 1321.983245] [<ffffffff8131b702>] acpi_hotplug_work_fn+0x1e/0x29
[ 1321.983249] [<ffffffff8108afa8>] process_one_work+0x168/0x450
[ 1321.983251] [<ffffffff8108b5db>] worker_thread+0x6b/0x550
[ 1321.983253] [<ffffffff8108b570>] ? init_pwq.part.22+0x10/0x10
[ 1321.983256] [<ffffffff81091cea>] kthread+0xea/0x100
[ 1321.983258] [<ffffffff81091c00>] ? kthread_create_on_node+0x1b0/0x1b0
[ 1321.983261] [<ffffffff8153107c>] ret_from_fork+0x7c/0xb0
[ 1321.983263] [<ffffffff81091c00>] ? kthread_create_on_node+0x1b0/0x1b0
My system:
Linux keineeile 3.16.3-1-ARCH #1 SMP PREEMPT Wed Sep 17 21:54:13 CEST 2014 x86_64 GNU/Linux
I'm using KDE as my DE, should that matter at all... I don't have laptop-mode-tools or pm-utils installed, but I do have the powerdown scripts (though they don't seem to be working right now for me - but one thing after the other).
Any help in solving this issue(s) is very much appreciated!!
Kindest Regards
keineeile
Last edited by keineeile (2014-10-01 15:59:58)

Well, I tried it both ways, suspending from KDE and from the command line using "systemctl suspend" and "echo mem > /sys/power/state", it all produces the same result.
However, I think I have stumbled upon something in lspci:
# lspci | grep 01:00.1
pcilib: Cannot open /sys/bus/pci/devices/0000:01:00.1/config
lspci: Unable to read the standard configuration space header of device 0000:01:00.1
There exists a device 01:00.0, though. This is my discrete radeon graphics card. Maybe it's connected to the following (?):
My laptop comes with an Intel graphics chip and a radeon graphics card. I want to use the Intel chip for powersaving and for having a cooler laptop. However, the DynPwr feature of the newest kernel (I think it was introduced in 3.15?) doesn't seem to work for me, my laptop just gets really hot. Plus the system kept freezing randomly (in such a way that I had to force turn off the laptop), which according to what I found online had something to do with NetworkManager and my radeon graphics card (I don't really understand how that's possible though). So what I did: In Grub I added "radeon.runpm=0" to the kernel line and upon logging in to KDE, I automatically execute:
echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
sleep 2
systemctl start NetworkManager
Since then I have no troubles with my laptop overheating and my system isn't freezing anymore. Since I did all that right as I set up a new system, I'm not completely sure if that's related to the laptop not suspending/shutting down anymore or not (I'll go ahead now and try reversing it and see if it works then)...
Oh, and I'm unable to remove the three "tee" processes in any way. I can't kill them, terminate them, nothing, they simply stay there...
Last edited by keineeile (2014-09-30 01:03:36)

Similar Messages

[SOLVED] New slim, can't shutdown|reboot|suspend anymore

Hi!
I just upgraded slim, and i notice that i cannot suspend, shutdown and reboot anymore.
And to mount usb drive, i am asked for my password.
After the upgrade i changed /etc/slim.conf,pacnew to suit my needs and then sudo mv /etc/slim.conf.pacnew /etc/slim.conf .
My .xinitrc is the same, so, where is the problem?
here there are my slim.conf:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions xfce4,icewm-session,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user federico
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password no
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login yes
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
and my .xinitrc:
#!/bin/bash
export BROWSER=chromium
export DE=xfce
exec ck-launch-session dbus-launch startxfce4
Thanks!
Last edited by nierro (2012-05-08 18:42:44)

From later in this thread:
Solution
Ok, do:
ck-list-sessions
There were two sessions for myself. So, the new slim is starting your exec line already with a console kit session. This is new behavior. It didn't before.
So, I modified my exec line to remove "ck-launch-session" in .xinitrc to:
exec dbus-launch --exit-with-session startxfce4
Reverted the changes I made to the shutdown/restart policy and rebooted. Shutdown, restart, mounting USB drive: they all work again now.
Edit: from even later on in this thread, just:
exec startxfce4
As your .xinitrc exec line should be sufficient for practically anyone. "startxfce4" does the dbus-launch itself.
Original post here:
Changed in my /etc/slim.conf:
default_path /bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin
Same issue, in Action buttons Shutdown and Restart grayed out.
in .xinitrc, launch line:
exec ck-launch-session startxfce4
Launch line was:
exec ck-launch-session dbus-launch --exit-with-session startxfce4
But, same issue with that launch line. Was googling and I found results saying dbus-launch is contained within startxfce4.
Last edited by headkase (2012-05-09 02:23:48)

[SOLVED] Xfce4 Lock after suspend

Hello everyone,
I know that there was it already asked, but in my question is something different. Is there any option to lock screen with LightDM in Xfce4 when is system going to suspend ? I already edited /usr/bin/xflock4 and it locks screen when is executed from terminal or simply locked from xfce panel, but it doesn't lock screen when i suspend computer. In power manager and in session settings is option already ticked to lock the screen after suspend.
PS: I know that "dm-tool lock" doesn't really lock the screen only redirect you to tty2.
EDIT: Now it works so here is solution:
1. Install light-locker
pacman -S light-locker
2. Create systemd service
nano /etc/systemd/system/lock.service
[Unit]
Description=Lock X session
Before=suspend.target
[Service]
Type=oneshot
ExecStart=/usr/bin/xflock4
[Install]
WantedBy=suspend.target
3. Enable systemd service
systemctl enable lock
4. Add light-locker to xflock4 script
nano /usr/bin/xflock4
#!/bin/sh
light-locker-command -l
Last edited by mako2580 (2014-05-07 16:46:26)

You should place [SOLVED] in the Title.

Wls_forms stuck in suspending mode

It seems to be a very not good idea to ever go into the weblogic console and tell it to
shutdown wls_forms. It is now stuck in "suspending" mode. If anyone has any ideas
on how to recover from this I'd love to hear it.
forms 11.1.1.4, weblogic 10.3.4 on windows 2008 r2 64.
Edited by: lake on May 31, 2011 7:50 PM

Ok 10 hours later it has shutdown! Yeah! I don't know how long it took but definitely longer
than 45 minutes. All I can say is if wls_forms seems to be stuck in suspending don't totally give up hope. I guess I can try the force option next time.

Office 2013 - Word cannot establish a connection with this document after the system resumed from suspend mode

Hiya!
This issue has been answered numerous times for Office 2010 and Office 2007, but I have yet to any solutions or Hotfixes that work for Office 2013 (x64) on Win7.
How to replicate the issue:
Open a file from a network share.
Edit file.
Leave computer on with file open. Computer goes to sleep or into stand-by mode.
Wait a bit
Wake up computer
CPU opens file in Read-Only mode and gives you the following error "Word cannot establish a network connection with this document after the system resumed from suspend mode. Save the document into a different file to keep any changes."
What I've tried:
http://support.microsoft.com/kb/2434898 - Office 2007 registry fixes. Does not apply.
http://support.microsoft.com/kb/2413659 - Office 2010 problem. This exact issue. Says 'No microsoft products that match this hotfix are installed'
Work Around:
I can saving new versions of these files overrides this issue, but this is sometimes not possible for end-users who only have specific access to ONE SPECIFIC FILE in a particular network share.
Please let me know how I can alleviate this issue!
Thanks
-Chris

Hi,
Are those problematic documents created via previous versions of Office?
Please also try to run a repair of your Office 2013 installtion and check if it helps. See:
http://office.microsoft.com/en-in/excel-help/repair-office-programs-HA010357402.aspx
Regards,
Steve Fan
TechNet Community Support

Trying to reinstall Acrobat Pro X from disc onto win 8.1 system. (Previous installation got corrupted) Continually getting message 'Acrobat has detected another process which has not yet completed-'. Have now closed system both cold (full shutdown) and wa

Trying to reinstall Acrobat Pro X from disc onto win 8.1 system. (Previous installation got corrupted) Continually getting message ‘Acrobat has detected another process which has not yet completed…’. Have now closed system both cold (full shutdown) and warm (restart) over 10 times. Every time I go to reinstall I get message.

I would run http://labs.adobe.com/downloads/acrobatcleaner.html and delete any Acrobat folders that have been created, then try again. Be sure to log in as the administrator and disable anti-virus when you have problems like this.

T410 - WinXP Pro Taskbar hangs and system takes forever to shutdown

Hi,
I've been having a weird issue with my T410. I created 3 partition on the HDD, one ntfs which i install WinXP Pro, that i downgraded using IBM recovery disk (since mine came with Win7 x86). My 2nd partition, is using ntfs with win7 x64, which i clean installed using a different license. Im reserving my 3rd partition to install my linux soon. Win7 on my machine works awesome. On the other hand, my XP is running nuts, the taskbar hangs every other minute and the system takes forever to shutdown (sometimes i just dont bother to wait,i'd just force shutdown). After I click Start>Shutdown, some of the programs will start to slowly close, and then it just hangs there. If i try to open any programs, i get an error message saying that the system has initiated shutdown, but it just hangs there for like good 5 minutes. Task manager wont open during that time too...I've tried uninstalling some programs that i thought might be distrupting the shudown to no avail. Can anyone suggest me anything else that i can do?
On the worse case scenario where i **might** need to reinstall my XP using the recovery disk again, would it be possible to keep my other partitions intact? I dont remember seeing that option in any of the IBM's that i've worked with. That option came standard with my old toshiba..
Btw, im running a T410, i5 540, 4gigs DDR3 RAM, if that helps.
Thanks
Huz

How much free space on the startup disk?
Right or control click the MacintoshHD icon. Click Get Info. In the Get Info window you will see Capacity and Available. Make sure you have a minimum of 15% free disk space.
Check for Login Items
Open System Preferences/Accounts then select the Login Items tab. Delete any files or apps you have listed there.
And go to /Library/Startup Items. Move any files in the Startup Items folder to the Trash
If there's enough disk space and login items aren't an issue, launch Disk Utility. The startup disk may need repairing.
Select MacintoshHD in the panel on the left then select the First Aid tab.
Select: Verify Disk (not Verify Disk Permissions).
If the disk needs repairing >
Using Disk Utility to verify or repair disks

System freezes after suspend

Hi All,I thought its an ubuntu issue; they say its a Lenovo Kernel issue.What do you think? thanks!SealFrom:Seth Arnold [email protected]:[email protected]:[Bug 1482618] Re: After suspending - SYSTEM FREEZESDate:augusztus 7, 2015 11:06There's a kernel stack dump in the logs and IO errors to block devices, this is probably a kernel or hardware issue instead of X11 issue. ** Package changed: xorg (Ubuntu) => linux (Ubuntu)--You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1482618 Title: After suspending - SYSTEM FREEZES Status in linux package in Ubuntu: New Bug description: Dear Developers, suspending function does not work.. When I manually suspend the system (pressing the suspend button, clicking the suspend logo that appears), when I open the screen next time, the system freezes many times. - At least, the screen is fully black, nothing happens. The computer is a Lenovo Yoga 3 with u15.04. Can you please help in this ? many thanks Seal ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Aug 7 13:30:46 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3906] InstallationDate: Installed on 2015-07-27 (10 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 80HE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=4fff414d-6c5a-4304-bdda-4c1932e1cafd ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A6CN50WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 3 Pro-1370 dmi.modalias: dmi:bvnLENOVO:bvrA6CN50WW:bd04/29/2015:svnLENOVOn80HEvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370: dmi.product.name: 80HE dmi.product.version: Lenovo YOGA 3 Pro-1370 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Aug 7 10:28:02 2015 xserver.configfile: default xserver.errors: [dix] ATML1000:00 03EB:8A10: unable to find touch point 0 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17226 vendor SDC xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482618/+subscriptions

kokoko3k wrote:
from hdparm:
AdvancedPM=yes: unknown setting WriteCache=enabled
Maybe the disk goes to sleep too often; this is bad even for your hdd life.
Do you set hdparm at boot or maybe a Power managment script does that?
Remember that hdparm settings are lost on hibernation/suspend, so you need to rerun it when the pc wakes up.
Anyway,at wakeup, try to run
sudo hdparm -B 255 /dev/sda
To disable power managment.
It works like a charm! Thanks for your reply. This question really drove me crazy for long time. It really caused by wrong setting of APM.From your reply then I follow the instruction of hdparm wiki and make it automated.

[SOLVED]System freezes when trying to suspend

Hi everyone,
I have a hard time to make suspend-to-ram working. Under Debian a
echo mem > /sys/power/state
would put my computer to sleep without any problems. On Arch the same command freezes the system. Both screens stay on and show exactly the same picture as before entering the command, but the system is completely unresponsive and the only way to use it again is to turn off the power and reboot.
I then tried to suspend using uswsusp (s2ram), after installing it as described in the wiki. This yields exactly the same results. I have also tried all of the options for s2ram (-f -p -s etc.) listed here.
My system is as follows:
Arch x86_64
Mainboard: EP43-S3L (Note: the options listed here don't work either)
Graphics card: ATI RADEON HD 5800 (using the catalyst driver)
I suspect that I have overlooked something and that it isn't really a problem with my hardware, as (like I said) suspend worked flawlessly under Debian.
Thank you very much for your help!
Last edited by bugfix (2012-07-19 08:36:44)

Problem solved. Turns out, there was nothing wrong with the suspend process itself, rather it was the catalyst driver causing the trouble.
I fixed this by adding nomodeset and vga=0 to my start-up options in GRUB's menu.lst.
kernel /vmlinuz-linux root=/dev/sda6 ro nomodeset vga=0
nomodeset disables KMS which was responsible for freezing my system when trying to suspend. As I found out, it also froze when trying to shutdown or to switch from X to a Terminal.
vga=0 disables the framebuffer. When the framebuffer is activated with catalyst, the system will suspend properly but show a black screen on resume.

[SOLVED] After resume from suspend to RAM, system is slow / unstable

Hello,
I have come across some strangeness when trying to suspend my system. The
computer is a lenovo U350. I have read a lot of threads on these subjects,
but I never found one that quite matched the experiences I'm having, so I felt
compelled to make a new post.
Here's what's going on: I boot into the terminal, and then run pm-suspend.
Within a few seconds, the computer goes to sleep, just as I had hoped. The
problem is that my computer seems a little groggy when I wake it back up.
Usually, when running a command like ps aux | less, the screen fills up very
quickly. After I resume from sleep, running ps aux | less is noticeably slow.
It takes a full second (+/- epsilon) to fill the screen. Other symptoms: if I
suspend / resume in the terminal, and then start a window manager (KDE), the
graphics will be slow and choppy, and when I try to exit the window manager, I
usually end up having to perform the dreaded REISUB after getting stuck on a
blank screen with a non-blinking cursor in the upper left hand corner.
Suspend / resume from KDE will result in either the black, non-responsive
screen as soon as I try to resume, or in the choppy graphics, followed by the
non-responsive black screen when I log out.
I looked at the process list before and after, and noticed that when the
system is first resumed, there are around 50-60 additional kworker processes
running than when I put it to sleep. I don't know if this is normal or not.
Also, hci0 has been killed, and a new hci0 process has taken its place. The
same goes for one of the udevd processes. About 40-50 of the kworker
processes finish after a few minutes, but this does not change the slowness of
ps aux | less, nor does it help with my window manager issues.
I ran a few (not so precise) performance tests before and after doing a
suspend, and got the same results (the test was just to compile some LaTeX,
which took about 4-5 seconds either way).
I examined the pm-suspend.log, and everything looked peachy. All of the
hooks returned success for the suspend, as well as the resume. I'm happy to
post this if needed. I did not change any of the default settings for
pm-suspend.
Anyhow, I've read a lot of threads, and seen a lot of suggestions, e.g.:
https://bbs.archlinux.org/viewtopic.php?id=137682
https://bbs.archlinux.org/viewtopic.php?id=136292 (use vbetool?)
https://bbs.archlinux.org/viewtopic.php?id=126174 (suspend tons of modules?)
https://bbs.archlinux.org/viewtopic.php?id=131827 (hpet=disable ?)
However, I'm not that confident in any of them, since no one had quite the
same issue. I was hoping that someone could point me in the right direction
before I start blindly walking through all the candidate fixes and risk
unleashing chaos into my system. Many thanks in advance for your help.
Oh, and in case this post was not yet long enough, here is some system
information:
lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
08:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
lsmod:
Module Size Used by
aes_x86_64 7508 3
cryptd 8309 0
aes_generic 26138 1 aes_x86_64
coretemp 5590 0
cpufreq_ondemand 6164 2
acpi_cpufreq 5877 1
mperf 1275 1 acpi_cpufreq
freq_table 2515 2 acpi_cpufreq,cpufreq_ondemand
arc4 1410 2
joydev 9895 0
snd_hda_codec_hdmi 24121 1
iwlwifi 248196 0
i915 420018 3
snd_hda_codec_conexant 47300 1
uvcvideo 64311 0
mac80211 228527 1 iwlwifi
videodev 82101 1 uvcvideo
snd_hda_intel 23375 0
snd_hda_codec 89389 3 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
broadcom 7270 0
tg3 134884 0
ideapad_laptop 8534 0
snd_hwdep 6389 1 snd_hda_codec
snd_pcm 74780 3 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi
snd_page_alloc 7153 2 snd_pcm,snd_hda_intel
snd_timer 19544 1 snd_pcm
snd 59214 7 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
iTCO_wdt 11885 0
v4l2_compat_ioctl32 8316 1 videodev
i2c_i801 8187 0
i2c_algo_bit 5263 1 i915
drm_kms_helper 26137 1 i915
intel_agp 10904 1 i915
btusb 11385 0
cfg80211 172260 2 mac80211,iwlwifi
bluetooth 151999 1 btusb
sparse_keymap 3120 1 ideapad_laptop
soundcore 6210 1 snd
drm 188499 4 drm_kms_helper,i915
rfkill 15498 3 bluetooth,cfg80211,ideapad_laptop
serio_raw 4429 0
iTCO_vendor_support 1961 1 iTCO_wdt
media 10597 2 videodev,uvcvideo
psmouse 61311 0
libphy 16985 2 tg3,broadcom
i2c_core 20492 6 drm,drm_kms_helper,i2c_algo_bit,i2c_i801,videodev,i915
intel_gtt 14519 3 intel_agp,i915
pcspkr 1819 0
evdev 9530 8
thermal 7799 0
wmi 8475 0
battery 6453 0
ac 2344 0
video 11164 1 i915
button 4470 1 i915
processor 25582 3 acpi_cpufreq
ext4 420412 3
crc16 1359 2 ext4,bluetooth
jbd2 71499 1 ext4
mbcache 5881 1 ext4
sd_mod 28307 5
ahci 20037 4
libahci 19559 1 ahci
libata 166654 2 libahci,ahci
scsi_mod 133676 2 libata,sd_mod
uhci_hcd 23116 0
ehci_hcd 40698 0
usbcore 146113 5 ehci_hcd,uhci_hcd,btusb,uvcvideo
usb_common 954 1 usbcore
Last edited by wes (2012-04-06 21:34:43)

I did try reinstalling, actually. But I did not think to remove the battery and the ram... I'm very curious now: what is the rationale / intuition for that? Or is it just that empirical evidence suggests this may be a good idea?
Anyhow, the reinstall by itself did not help. I tried it out with a pretty bare-bones setup and had the same results. Here are a few other things I noticed:
- After the suspend, one of the cores is always running at the maximum clock frequency, according to powertop (although, according to ps aux, no one is doing any work).
- Even if I ssh to a nearby machine, I get the same experience when running `ls`. The screen fills very slowly. That narrows things down a little bit, but I was already guessing it would be graphics-related.
I have also tried a few random kernel boot parameters after reading things online, but none of those worked, and several stopped the machine from booting at all.
Thanks for your help.

[SOLVED] Systemd stuck at "Starting File system check"

Hi all
Backstory
My hardware:
Mobo: Gigabyte X99 2011v3 with UEFI and dual bios.
GFX: MSI GTX 970 4GB Gaming OC
HDD: Samsung 850 Pro 1TB SSD
CPU: intel 5820k
I have been using arch for about 2 years now. I recently bought new hardware, Gigabyte X99 motherboard uefi dual bios. I have tried a couple of times to install arch the old way, i.e. legacy mode or normal bios mode, however after a successful install, when I reboot my bios says "Select Proper Boot Device". Then I decided to put everything in UEFI mode and install arch using the uefi install disc. At first, I was not very successful, because I followed the arch wiki to the bone but when it comes to UEFI, instructions are a bit vague. In any case, I managed to install Arch and get uefi to work 100% by using this guide http://jorisvandijk.com/2014/installing … pt-system/ .
Problem
After installing arch successfully using UEFI mode, arch starts booting up, everything shows [OK] at the side, no errors, however, it hangs after a line that reads "Starting File system check ". I am not at home right now, however I thought I could start troubleshooting and maybe get some ideas.
I have tried the following.
- Chrooted back into my arch install using the live cd and mounting my partitions.
- Updated and synced pacman.
- Removed all journal log files.
- reinstalled Systemd.
- rebuilt kernel modules.
none of the above worked. It still hangs at "Starting fiel system check"
Any ideas.
SOLUTION
Solved by using
nolapic
Still had other problems after that, however, the initial problem was solved.
Last edited by janpansa (2015-02-26 20:04:24)

jasonwryan wrote:Taking the time to read through the relevant pages and working through the Beginners' Guide methodically is the best (and only) way to both install Arch and also bed in a sound understanding of how your system is put together. It is an investment that will continue to pay you back as long as you run a Linux/UNIX box.
Hi Jason,
thx for your help so far. I have printed out the Arch beginners install and followed it to the bone and focusing on the UEFI parts. Arch installed without a single error, everything went smooth. Aftwerwards, I exited from the chroot environmount, unmount and reboot and again, it hangs on the startup. This time I took screenshots.
I present to the board, exhibit A, arch starting up after a fresh install :
http://oi61.tinypic.com/2m4x82o.jpg
I now present to the board, exhibit B, arch starting up for a second time, after restarting the pc :
http://oi59.tinypic.com/10ehvki.jpg
Afterwards, I restarted again. Went into bios setup and checked my boot priorities. This is what I saw:
I now present exhibit C, my bios boot options :
http://oi62.tinypic.com/24ys0bd.jpg
I tried all the options listed for my Samsung SSD, with and without UEFI as well as the option that was the default aka Linux boot manage". Each one did exactly the same.
I have a few ideas :
1.) Leave out swap.
2.) Disable fscheck.
3.) I have a feeling that my SSD is reading/writing too fast and that fscheck is having trouble ?
I am now trying option 1. In other words, I am reinstalling arch, again, following the beginners guide to the bone and focusing specifically on the UEFI parts. This time, I am leaving out swap. (I have 16GB of DDR4 memory). I have about a 70% feeling that the outcome will be the same. However, I will be back after that to comment on the outcome. Please leave feedback and help me through this where you can ! Thanks
Last edited by jasonwryan (2015-02-23 19:34:21)

[SOLVED] System upgrade broke pm-resume (kernel problem?)

It now seems every other time I suspend to RAM, it fails to come back. I just get a blank screen, no backlight, with a completely unresponsive keyboard. At this point, the only thing I do that has any effect is a hard shutdown by holding down the power button. I had no problems before I upgraded on April 10. I didn't post this immediately because I wanted to see if the new xorg-server and associated updates would fix it, but it didn't.
Here is pm-suspend.log:
Initial commandline parameters:
Tue Apr 14 03:46:54 PDT 2009: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: Adding quirks from HAL: --quirk-dpms-on --quirk-dpms-suspend --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3
success.
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux helium 2.6.29-ARCH #1 SMP PREEMPT Wed Apr 8 12:47:56 UTC 2009 i686 Intel(R) Pentium(R) M processor 2.00GHz GenuineIntel GNU/Linux
Module Size Used by
radeon 144928 2
drm 138240 3 radeon
arc4 1556 2
ecb 2452 2
lib80211_crypt_wep 3476 1
snd_seq_oss 29888 0
snd_seq_midi_event 5972 1 snd_seq_oss
joydev 9600 0
snd_seq 48176 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 6080 2 snd_seq_oss,snd_seq
pcmcia 33388 0
snd_pcm_oss 38112 0
snd_mixer_oss 14388 1 snd_pcm_oss
irtty_sir 4852 0
btusb 11720 0
wacom 19836 0
sir_dev 11224 1 irtty_sir
bluetooth 52292 1 btusb
psmouse 54536 0
ppdev 7192 0
lp 8964 0
usbhid 35136 0
hid 39744 1 usbhid
thinkpad_acpi 59736 0
rfkill 9392 2 thinkpad_acpi
led_class 3384 1 thinkpad_acpi
nvram 6336 1 thinkpad_acpi
serio_raw 5048 0
ipw2200 139808 0
libipw 26136 1 ipw2200
lib80211 5208 3 lib80211_crypt_wep,ipw2200,libipw
yenta_socket 23840 1
rsrc_nonstatic 10868 1 yenta_socket
pcmcia_core 32328 3 pcmcia,yenta_socket,rsrc_nonstatic
snd_intel8x0 28688 2
snd_intel8x0m 13312 0
snd_ac97_codec 100120 2 snd_intel8x0,snd_intel8x0m
ac97_bus 1364 1 snd_ac97_codec
video 16484 0
output 2388 1 video
snd_pcm 67992 4 snd_pcm_oss,snd_intel8x0,snd_intel8x0m,snd_ac97_codec
snd_timer 19260 2 snd_seq,snd_pcm
nsc_ircc 16208 0
parport_pc 35556 1
parport 30924 3 ppdev,lp,parport_pc
iTCO_wdt 10680 0
iTCO_vendor_support 2840 1 iTCO_wdt
uhci_hcd 22500 0
snd 51460 14 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_intel8x0m,snd_ac97_codec,snd_pcm,snd_timer
soundcore 6080 1 snd
snd_page_alloc 8092 3 snd_intel8x0,snd_intel8x0m,snd_pcm
irda 110648 2 sir_dev,nsc_ircc
crc_ccitt 1620 1 irda
sg 24712 0
ehci_hcd 35424 0
i2c_i801 8904 0
i2c_core 20648 2 drm,i2c_i801
usbcore 137232 6 btusb,wacom,usbhid,uhci_hcd,ehci_hcd
tg3 109176 0
libphy 17780 1 tg3
intel_agp 25628 0
agpgart 29492 2 drm,intel_agp
evdev 9248 11
thermal 15120 0
fan 4056 0
button 5700 0
battery 9880 0
ac 3832 0
cpufreq_powersave 1268 1
cpufreq_ondemand 6752 0
acpi_cpufreq 7584 0
freq_table 3412 2 cpufreq_ondemand,acpi_cpufreq
processor 39136 3 thermal,acpi_cpufreq
rtc_cmos 10188 0
rtc_core 16304 1 rtc_cmos
rtc_lib 2324 1 rtc_core
ext3 126556 4
jbd 45512 1 ext3
mbcache 6488 1 ext3
dm_mod 53640 9
sr_mod 14596 0
cdrom 33600 1 sr_mod
sd_mod 25072 3
ata_generic 4504 0
pata_acpi 3828 0
ata_piix 22136 2
ahci 30116 0
libata 157036 4 ata_generic,pata_acpi,ata_piix,ahci
scsi_mod 100500 4 sg,sr_mod,sd_mod,libata
total used free shared buffers cached
Mem: 2073804 1381928 691876 0 130512 929756
-/+ buffers/cache: 321660 1752144
Swap: 729080 0 729080
success.
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: /bin/stty: standard input: Inappropriate ioctl for device
:: home-wireless down [BUSY] [DONE]
success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/99video suspend suspend: kernel.acpi_video_flags = 0
Allocated buffer at 0x2010 (base is 0x0)
ES: 0x0201 EBX: 0x0000
success.
Tue Apr 14 03:46:56 PDT 2009: performing suspend
Not very informative as far as I can see. Here is what I upgraded on that day (from pacman.log):
[2009-04-10 22:51] synchronizing package lists
[2009-04-10 22:51] starting full system upgrade
[2009-04-10 22:57] starting full system upgrade
[2009-04-10 22:57] upgraded fftw (3.2-1 -> 3.2.1-1)
[2009-04-10 22:57] upgraded gpgme (1.1.7-2 -> 1.1.8-1)
[2009-04-10 22:57] upgraded hdparm (9.12-1 -> 9.14-1)
[2009-04-10 22:57] upgraded ipw2200-fw (3.0-2 -> 3.1-1)
[2009-04-10 22:57] upgraded kbproto (1.0.3-1 -> 1.0.3-2)
[2009-04-10 22:57] upgraded kernel26-firmware (2.6.28-1 -> 2.6.29-1)
[2009-04-10 22:57] >>> Updating module dependencies. Please wait ...
[2009-04-10 22:57] >>> MKINITCPIO SETUP
[2009-04-10 22:57] >>> ----------------
[2009-04-10 22:57] >>> If you use LVM2, Encrypted root or software RAID,
[2009-04-10 22:57] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2009-04-10 22:57] >>> More information about mkinitcpio setup can be found here:
[2009-04-10 22:57] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2009-04-10 22:57]
[2009-04-10 22:57] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2009-04-10 22:57] ==> Building image "default"
[2009-04-10 22:57] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2009-04-10 22:57] :: Begin dry run
[2009-04-10 22:57] :: Parsing hook [base]
[2009-04-10 22:57] :: Parsing hook [udev]
[2009-04-10 22:57] :: Parsing hook [autodetect]
[2009-04-10 22:57] :: Parsing hook [pata]
[2009-04-10 22:57] :: Parsing hook [scsi]
[2009-04-10 22:57] :: Parsing hook [sata]
[2009-04-10 22:58] :: Parsing hook [lvm2]
[2009-04-10 22:58] :: Parsing hook [filesystems]
[2009-04-10 22:58] :: Generating module dependencies
[2009-04-10 22:58] :: Generating image '/boot/kernel26.img'...SUCCESS
[2009-04-10 22:58] ==> SUCCESS
[2009-04-10 22:58] ==> Building image "fallback"
[2009-04-10 22:58] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2009-04-10 22:58] :: Begin dry run
[2009-04-10 22:58] :: Parsing hook [base]
[2009-04-10 22:58] :: Parsing hook [udev]
[2009-04-10 22:58] :: Parsing hook [pata]
[2009-04-10 22:58] :: Parsing hook [scsi]
[2009-04-10 22:58] :: Parsing hook [sata]
[2009-04-10 22:58] :: Parsing hook [lvm2]
[2009-04-10 22:58] :: Parsing hook [filesystems]
[2009-04-10 22:59] :: Generating module dependencies
[2009-04-10 22:59] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2009-04-10 22:59] ==> SUCCESS
[2009-04-10 22:59] upgraded kernel26 (2.6.28.8-1 -> 2.6.29.1-3)
[2009-04-10 22:59] upgraded klibc-udev (140-1 -> 141-1)
[2009-04-10 22:59] upgraded libdvdread (0.9.7-1 -> 0.9.7-2)
[2009-04-10 22:59] upgraded libfontenc (1.0.4-1 -> 1.0.4-2)
[2009-04-10 22:59] upgraded libid3tag (0.15.1b-2 -> 0.15.1b-3)
[2009-04-10 22:59] upgraded libmatroska (0.8.1-1 -> 0.8.1-2)
[2009-04-10 22:59] upgraded libofa (0.9.3-1 -> 0.9.3-2)
[2009-04-10 22:59] upgraded libogg (1.1.3-1 -> 1.1.3-2)
[2009-04-10 22:59] installed libftdi (0.15-1)
[2009-04-10 22:59] upgraded lirc-utils (0.8.4-1 -> 0.8.5pre2-1)
[2009-04-10 22:59] upgraded m4 (1.4.12-1 -> 1.4.13-1)
[2009-04-10 22:59] upgraded man-db (2.5.4-2 -> 2.5.5-1)
[2009-04-10 22:59] upgraded man-pages (3.19-1 -> 3.20-1)
[2009-04-10 22:59] upgraded python-numpy (1.2.1-4 -> 1.3.0-1)
[2009-04-10 22:59] upgraded tzdata (2009d-1 -> 2009e-1)
[2009-04-10 22:59] upgraded udev (140-2 -> 141-1)
The kernel was upgraded then. Is that the most likely culprit? Generally, how can I help debug this?
Thanks...
Last edited by Lux Perpetua (2009-07-08 04:20:11)

Hi there. Me here with the same problem. Well I think it to be so...
I can not suspend/resume for the second time - when I resume the backlight turns on, but the suspend LED is not turned off, HDD works, CPU, fans work. My computer is Thinkpad T43p. And older kernel does solve the problems.
I am considering one more issue about this problem is that the drivers may conflict with the newest kernel (for example my opensource ati drivers). Any suggestions?
By the way, if someone needs older packages, you can use 'Arch Rollback Machine' (ARM - http://bbs.archlinux.org/viewtopic.php?id=53665)

Chromium doesn't start and suspend, shutdown don't work occassionally

Hello,
I have this problem on my laptop but since chromium doesn't start on my desktop either, I don't think it's specific to laptops.
When I try to start chromium in a terminal, I get a blank window (I can tell because I use spectrwm):
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[25148:25148:0215/130205:ERROR:background_mode_manager_aura.cc(14)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool)
I temporarily resorted to using Firefox instead, but at times it just freezes up while opening some pages. After that point, even killing firefox doesn't help: the system load level keeps on rising. I used pidof to check if firefox is still running, but I had no output from pidof. After having firefox to freeze, shutdown, suspend, etc don't work. The laptop goes to a black screen state, but the power LED remains on indefinitely.
These might be two separate issues, but they started together on my laptop.
Thanks in advance!
Last edited by SgrA (2015-02-15 09:47:08)

I also have issues wich starting up chromium (google-chrome and opera too).
Feb 15 10:09:58 localhost kernel: [ 102.301038] chromium[786]: segfault at 7ffffd294ff8 ip 00007fb4386962b2 sp 00007ffffd295000 error 6 in chromium[7fb43371e000+66c6000]
Feb 15 10:12:16 localhost kernel: [ 240.102784] chromium D 0000000000000000 0 786 1 0x00000104
Feb 15 10:12:16 localhost kernel: [ 240.102789] ffff8800c2d5bb68 0000000000000082 ffff8800c5635a90 0000000000013640
Feb 15 10:12:16 localhost kernel: [ 240.102793] ffff8800c2d5bfd8 0000000000013640 ffffffff81818540 ffff8800c5635a90
Feb 15 10:12:16 localhost kernel: [ 240.102796] ffff8800c2d5bb78 0000000000000246 ffffffff81a52047 ffff88042f5eeb08
Feb 15 10:12:16 localhost kernel: [ 240.102799] Call Trace:
Feb 15 10:12:16 localhost kernel: [ 240.102809] [<ffffffff8109e777>] ? try_to_wake_up+0x1e7/0x380
Feb 15 10:12:16 localhost kernel: [ 240.102814] [<ffffffff81551599>] schedule+0x29/0x70
Feb 15 10:12:16 localhost kernel: [ 240.102818] [<ffffffff81553e25>] rwsem_down_write_failed+0x175/0x360
Feb 15 10:12:16 localhost kernel: [ 240.102823] [<ffffffff812c0e63>] call_rwsem_down_write_failed+0x13/0x20
Feb 15 10:12:16 localhost kernel: [ 240.102827] [<ffffffff81553604>] ? down_write+0x24/0x40
Feb 15 10:12:16 localhost kernel: [ 240.102832] [<ffffffff8122c5cd>] do_coredump+0x16d/0xf30
Feb 15 10:12:16 localhost kernel: [ 240.102837] [<ffffffff81080524>] ? force_sig_info+0xd4/0xf0
Feb 15 10:12:16 localhost kernel: [ 240.102841] [<ffffffff8107e3d7>] ? __sigqueue_free.part.15+0x37/0x40
Feb 15 10:12:16 localhost kernel: [ 240.102846] [<ffffffff8108180c>] get_signal+0x38c/0x710
Feb 15 10:12:16 localhost kernel: [ 240.102852] [<ffffffff81014617>] do_signal+0x37/0x800
Feb 15 10:12:16 localhost kernel: [ 240.102855] [<ffffffff81550f08>] ? __schedule+0x3e8/0xa50
Feb 15 10:12:16 localhost kernel: [ 240.102859] [<ffffffff81014e48>] do_notify_resume+0x68/0xa0
Feb 15 10:12:16 localhost kernel: [ 240.102863] [<ffffffff81556322>] retint_signal+0x48/0x86
Feb 15 10:12:16 localhost kernel: [ 240.102871] Watchdog D 0000000000000004 0 794 1 0x00000104
Feb 15 10:12:16 localhost kernel: [ 240.102874] ffff880402757d40 0000000000000082 ffff8800c5632840 0000000000013640
Feb 15 10:12:16 localhost kernel: [ 240.102877] ffff880402757fd8 0000000000013640 ffff880418841420 ffff8800c5632840
Feb 15 10:12:16 localhost kernel: [ 240.102880] ffff880402757ce8 ffff880402757e70 00000000ffffff92 ffff880402757c98
Feb 15 10:12:16 localhost kernel: [ 240.102883] Call Trace:
Feb 15 10:12:16 localhost kernel: [ 240.102888] [<ffffffff810dbe32>] ? hrtimer_cancel+0x22/0x30
Feb 15 10:12:16 localhost kernel: [ 240.102893] [<ffffffff810ed4e6>] ? futex_wait+0x206/0x280
Feb 15 10:12:16 localhost kernel: [ 240.102897] [<ffffffff810dbbc0>] ? __run_hrtimer+0x250/0x250
Feb 15 10:12:16 localhost kernel: [ 240.102900] [<ffffffff81551599>] schedule+0x29/0x70
Feb 15 10:12:16 localhost kernel: [ 240.102903] [<ffffffff81553c65>] rwsem_down_read_failed+0xe5/0x130
Feb 15 10:12:16 localhost kernel: [ 240.102906] [<ffffffff810ed0d0>] ? futex_wake+0x80/0x160
Feb 15 10:12:16 localhost kernel: [ 240.102910] [<ffffffff812c0e34>] call_rwsem_down_read_failed+0x14/0x30
Feb 15 10:12:16 localhost kernel: [ 240.102913] [<ffffffff815535d7>] ? down_read+0x17/0x20
Feb 15 10:12:16 localhost kernel: [ 240.102918] [<ffffffff81060aed>] __do_page_fault+0x1ed/0x600
Feb 15 10:12:16 localhost kernel: [ 240.102923] [<ffffffff8110e7f9>] ? seccomp_phase1+0x99/0x210
Feb 15 10:12:16 localhost kernel: [ 240.102927] [<ffffffff81060f22>] do_page_fault+0x22/0x30
Feb 15 10:12:16 localhost kernel: [ 240.102930] [<ffffffff81557598>] page_fault+0x28/0x30
Feb 15 10:12:43 localhost kernel: [ 267.288947] chromium[920]: segfault at 7fff3faceff8 ip 00007fa90fcc62bc sp 00007fff3facf000 error 6 in chromium[7fa90ad4e000+66c6000]
It started happening after upgrade:
[2015-02-15 09:43] [ALPM] upgraded chromium (40.0.2214.94-1 -> 40.0.2214.111-1)
I was wondering if it has anything to do with some X-related upgrades:
[2015-02-15 09:42] [ALPM] upgraded xorg-server-common (1.16.3-2 -> 1.16.4-1)
[2015-02-15 09:43] [ALPM] upgraded xorg-server (1.16.3-2 -> 1.16.4-1)
[2015-02-15 09:48] [ALPM] upgraded xorg-server-devel (1.16.3-2 -> 1.16.4-1)
[2015-02-15 09:45] [ALPM] upgraded nvidia (346.35-5 -> 346.35-6)
I tried to downgrade chromimu to 40.0.2214.94-1 and it didn't help. I tried to downgrade nvidia, xorg-server and xorg-server-devel to previous versions, when everything worked and X chouldn't start.
Other observations are that if I start chromium, the ps command hangs and I have to reboot the system to be able to use ps command again.
Linux lisa 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64 GNU/Linux
It's worth mentioning that I also run spectrwm, like SgrA, however i don't have other issues with freezing on shutdown etc.

[SOLVED] how to prevent suspending/sleeping when closing laptop lid

Hi all,
My laptop, a Lenovo Thinkpad T430u, suspends whenever I close the lid. It's been doing this since I first installed Arch. I want to turn this feature off. How can I do it?
Relevant information:
acpid is installed
the configuration file /etc/acpi/handler.sh
#!/bin/bash
# Default acpi script that takes an entry for all actions
case "$1" in
button/power)
case "$2" in
PBTN|PWRF)
logger 'PowerButton pressed'
logger "ACPI action undefined: $2"
esac
button/sleep)
case "$2" in
SLPB|SBTN)
logger 'SleepButton pressed'
logger "ACPI action undefined: $2"
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
logger 'AC unpluged'
00000001)
logger 'AC pluged'
esac
logger "ACPI action undefined: $2"
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
00000001)
logger 'Battery offline'
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
logger 'LID closed'
open)
logger 'LID opened'
logger "ACPI action undefined: $3"
esac
case $(cat /proc/acpi/button/lid/LID0/state | awk '{print $2}') in
closed) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force off ;;
open) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force on ;;
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:
dmesg output:
[ 1530.790532] PM: Syncing filesystems ... done.
[ 1530.805678] PM: Preparing system for mem sleep
[ 1530.844445] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 1530.856658] Freezing remaining freezable tasks ... (elapsed 0.10 seconds) done.
[ 1530.963435] PM: Entering mem sleep
[ 1530.963572] Suspending console(s) (use no_console_suspend to debug)
[ 1531.123543] iwlwifi 0000:03:00.0: iwl_pcie_cmdq_reclaim: Read index for DMA queue txq id (9), index 207 is out of range [0-256] 208 208.
[ 1531.124216] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1531.124579] sd 0:0:0:0: [sda] Stopping disk
[ 1531.360682] mei 0000:00:16.0: suspend
[ 1531.440517] ahci 0000:00:1f.2: power state changed by ACPI to D3hot
[ 1531.687309] PM: suspend of devices complete after 722.490 msecs
[ 1531.687784] PM: late suspend of devices complete after 0.469 msecs
[ 1531.688232] pcieport 0000:00:1c.3: System wakeup enabled by ACPI
[ 1531.714222] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 1531.727619] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 1531.754015] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 1531.767422] PM: noirq suspend of devices complete after 79.565 msecs
[ 1531.768301] ACPI: Preparing to enter system sleep state S3
[ 1531.797647] PM: Saving platform NVS memory
[ 1531.799282] Disabling non-boot CPUs ...
[ 1531.900721] smpboot: CPU 1 is now offline
[ 1532.004162] smpboot: CPU 2 is now offline
[ 1532.107554] smpboot: CPU 3 is now offline
I have pmutils and tlpinstalled
tlp config
# tlp - Parameters for power save
# Hint: some features are disabled by default, remove the leading # to enable them
# Set to 0 to disable/1 to enable TLP
TLP_ENABLE=1
# Seconds laptop mode has to to wait after the disk goes idle before doing a sync.
# Non-zero value enables, zero disables laptop mode.
DISK_IDLE_SECS_ON_AC=0
DISK_IDLE_SECS_ON_BAT=2
# Dirty page values (timeouts in secs).
MAX_LOST_WORK_SECS_ON_AC=15
MAX_LOST_WORK_SECS_ON_BAT=60
# Select a cpu frequency scaling governor: ondemand/powersave/performance/conservative
# Important:
# - You *must* disable your distribution's governor settings or conflicts will occur
# - ondemand is sufficient for *almost all* workloads, you should know what you're doing!
#CPU_SCALING_GOVERNOR_ON_AC=ondemand
#CPU_SCALING_GOVERNOR_ON_BAT=ondemand
# Set the min/max frequency available for the scaling governor.
# Possible values strongly depend on your cpu. For available frequencies see
# tlp-stat output, Section "+++ Processor".
# Hint: Parameters are disabled by default, remove the leading # to enable them,
# otherwise kernel default values are used.
#CPU_SCALING_MIN_FREQ_ON_AC=0
#CPU_SCALING_MAX_FREQ_ON_AC=0
#CPU_SCALING_MIN_FREQ_ON_BAT=0
#CPU_SCALING_MAX_FREQ_ON_BAT=0
# Set the cpu "turbo boost" feature: 0=disable / 1=allow
# Requires an Intel Core i processor and kernel 3.7 or later.
# Important:
# - This may conflict with your distribution's governor settings
# - A value of 1 does *not* activate boosting, it just allows it
#CPU_BOOST_ON_AC=1
#CPU_BOOST_ON_BAT=0
# Minimize number of used cpu cores/hyper-threads under light load conditions
SCHED_POWERSAVE_ON_AC=0
SCHED_POWERSAVE_ON_BAT=1
# Kernel NMI Watchdog
# 0=disable (default, saves power) / 1=enable (for kernel debugging only)
NMI_WATCHDOG=0
# Change CPU voltages aka "undervolting" - Kernel with PHC patch required
# Freq:voltage pairs are written to /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
# CAUTION: only use this, if you thoroughly understand what you are doing!
#PHC_CONTROLS="F:V F:V F:V F:V"
# Hard disk devices, separate multiple devices with spaces (default: sda).
# Devices can be specified by disk id too (lookup with: tlp diskid).
DISK_DEVICES="sda sdb"
# Hard disk advanced power management level: 1(max saving)..254(off)
# Levels 1..127 may spin down the disk.
# Separate values for multiple devices with spaces.
DISK_APM_LEVEL_ON_AC="254 254"
DISK_APM_LEVEL_ON_BAT="128 128"
# Hard disk spin down timeout:
# 0: spin down disabled
# 1..240: timeouts from 5s to 20min (in units of 5s)
# 241..251: timeouts from 30min to 5.5 hours (in units of 30min)
# (see 'man hdparm' for details)
#DISK_SPINDOWN_TIMEOUT_ON_AC="0 0"
#DISK_SPINDOWN_TIMEOUT_ON_BAT="0 0"
# Select io scheduler for the disk devices: noop/deadline/cfq (Default: cfq)
# Separate values for multiple devices with spaces.
#DISK_IOSCHED="cfq cfq"
# SATA aggressive link power management (ALPM):
# min_power/medium_power/max_performance
SATA_LINKPWR_ON_AC=max_performance
SATA_LINKPWR_ON_BAT=min_power
# PCI Express Active State Power Management (PCIe ASPM):
# default/performance/powersave
# Hint: needs kernel boot option pcie_aspm=force on some machines
PCIE_ASPM_ON_AC=performance
PCIE_ASPM_ON_BAT=powersave
# Radeon graphics clock speed (profile method): low/mid/high/auto/default
# auto = mid on BAT, high on AC; default = use hardware defaults
# (Kernel >= 2.6.35 only, not with fglrx driver!)
RADEON_POWER_PROFILE_ON_AC=high
RADEON_POWER_PROFILE_ON_BAT=low
# WiFi power saving mode: 1=disable/5=enable
# (Linux 2.6.32 and later, some adapters only!)
WIFI_PWR_ON_AC=1
WIFI_PWR_ON_BAT=5
# Disable wake on lan: Y/N
WOL_DISABLE=Y
# Enable audio power saving for Intel HDA, AC97 devices (timeout in secs).
# A value of 0 disables / >=1 enables power save.
SOUND_POWER_SAVE=1
# Disable controller too (HDA only): Y/N
SOUND_POWER_SAVE_CONTROLLER=Y
# Set to 1 to power off optical drive in UltraBay (ThinkPads only)
# when running on battery. A value of 0 disables this Feature (Default).
# Drive can be powered on again by releasing (and reinserting) the
# eject lever or by pressing the disc eject button on newer models.
# Note: an UltraBay hard disk is never powered off.
BAY_POWEROFF_ON_BAT=0
# Optical drive device to power off (default sr0)
BAY_DEVICE="sr0"
# Runtime Power Management for pci(e) bus devices
# (Kernel >= 2.6.35 only): on=disable/auto=enable
RUNTIME_PM_ON_AC=on
RUNTIME_PM_ON_BAT=auto
# Runtime PM for *all* pci(e) bus devices: 0=disable / 1=enable
# Warning: experimental option, could cause system instabilities
RUNTIME_PM_ALL=0
# Set to 0 to disable/1 to enable usb autosuspend feature
USB_AUTOSUSPEND=1
# Devices from the following list are excluded from usb autosuspend
# (separate with spaces). Use lsusb to get the id's.
# Note: input devices (usbhid) are excluded automatically
#USB_BLACKLIST="1111:2222 3333:4444"
# Set to 1 to disable autosuspend before shutdown/0 to do nothing
# (workaround for usb devices that cause shutdown problems)
#USB_AUTOSUSPEND_DISABLE_ON_SHUTDOWN=1
# Restore radio device state (bluetooth, wifi, wwan) from previous shutdown
# on system startup: 0=disable/1=enable
# Hint: the parameters DEVICES_TO_DISABLE/ENABLE_ON_STARTUP/SHUTDOWN below
# are ignored when this is enabled!
RESTORE_DEVICE_STATE_ON_STARTUP=0
# Radio devices to disable on startup: bluetooth wifi wwan
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
# Radio devices to enable on startup: bluetooth wifi wwan
#DEVICES_TO_ENABLE_ON_STARTUP="wifi"
# Radio devices to disable on shutdown: bluetooth wifi wwan
# (workaround for devices that are blocking shutdown)
#DEVICES_TO_DISABLE_ON_SHUTDOWN="bluetooth wifi wwan"
# Radio devices to enable on shutdown: bluetooth wifi wwan
# (to prevent other operating systems from missing radios)
#DEVICES_TO_ENABLE_ON_SHUTDOWN="wwan"
# Radio devices to enable when wireless radio switch is turned on:
# bluetooth wifi wwan (Ubuntu + ThinkPad only)
#DEVICES_TO_ENABLE_ON_RADIOSW="wifi wwan"
# Battery charge thresholds (ThinkPad only, tp-smapi or acpi-call kernel module required)
# Charging starts when the remaining capacity falls below the START_CHARGE_TRESH
# value and stops when exceeding the STOP_CHARGE_TRESH value.
# Main battery (values in %)
#START_CHARGE_THRESH_BAT0=75
#STOP_CHARGE_THRESH_BAT0=80
# Ultrabay or slice battery (values in %)
#START_CHARGE_THRESH_BAT1=75
#STOP_CHARGE_THRESH_BAT1=80
# Set to 1 to disable use of tpacpi-bat on Sandy Bridge or newer Thinkpads
# and force usage of tp-smapi instead
#DISABLE_TPACPIBAT=1
# tlp-rdw - Parameters for the radio device wizard
# Possible devices: bluetooth/wifi/wwan
# Hint: parameters are disabled by default, remove the leading # to enable them
# Radio devices to disable on connect
DEVICES_TO_DISABLE_ON_LAN_CONNECT="wifi wwan"
DEVICES_TO_DISABLE_ON_WIFI_CONNECT="wwan"
DEVICES_TO_DISABLE_ON_WWAN_CONNECT="wifi"
# Radio devices to enable on disconnect
DEVICES_TO_ENABLE_ON_LAN_DISCONNECT="wifi wwan"
#DEVICES_TO_ENABLE_ON_WIFI_DISCONNECT=""
#DEVICES_TO_ENABLE_ON_WWAN_DISCONNECT=""
# Radio devices to enable/disable when docked
#DEVICES_TO_ENABLE_ON_DOCK=""
#DEVICES_TO_DISABLE_ON_DOCK=""
# Radio devices to enable/disable when undocked
#DEVICES_TO_ENABLE_ON_UNDOCK="wifi"
#DEVICES_TO_DISABLE_ON_UNDOCK=""
thanks guys
I love arch
Last edited by beitme (2013-06-08 10:05:37)

@ Karol, done
@ 65kid, here's my logind.conf
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min

[Solved] /bin/mount hanging, preventing shutdown

Hi,
Upgraded my system today - got a problem with symbolic links to /var/run and /var/somethingelse which I solved using the solution in another post. But now mount shows a continuous 100% system load, and I am unable to kill (even -9) it. It also prevents me to shutdown the machine.
I just have two HDs in the computer, no USB disks or sticks. Booting seems OK, except for the message that /bin/mount is timing out (or something) and will be killed (which I guess it isn't).
Any ideas?
-peter
Last edited by durian (2012-06-15 06:18:15)

I am not sure if the mount showing 100% and not being able to shutdown are related or not.
but here's another thread -- not being able to shutdown. :: https://bbs.archlinux.org/viewtopic.php?id=143113
As for your mount issue -- are you using any nfs shares? if so, do you have the netfs daemon in your DAEMONS array?

[SOLVED] System stuck on suspend/shutdown

Similar Messages

Maybe you are looking for