[solved] Networkmanager failed on shutdown
Hi!
Second post
Well, I try to install quick-init but I have a lot of problems and when I uninstalled it and restore all (I hope so) I see that when I shutdown a FAIL on networkmanager, can anybody help me, please?
And tell me how can I give you more information about it?
Thanks a lot!
Last edited by thearcher (2010-05-17 07:31:33)
For the first question, It happens everytime I shutdown the PC but everythings seems to runs well.
In my modules I don't know what cause I'm out of my office now but I think dbus is installed cause docky ask me for it when I installed it.
(excuse my poor english)
Edited: I connect with ssh and see this on my rc.conf: DAEMONS=(syslog-ng hal !network networkmanager @netfs @noip @sshd @crond @alsa @samba @smartd @fam @dnsmasq @preload)
My MODULES are this: MODULES=(!rt2800usb !rt2x00usb)
It's possibly to view a log for the networkmanager?
Thanks for the fast answers!
Last edited by thearcher (2010-05-14 13:39:23)
Similar Messages
-
[SOLVED] NetworkManager failing to connect to wifi networks
Up until yesterday NetworkManager had been working fine on my network. Then yesterday it began dropping internet access (but still reporting that it was connected to the network) and eventually dropping the connection entirely. This has been happening whenever I attempt to connect to the network.
Now, nm will not even connect to the network, it appears to attempt authentication but fails. Ethernet however, works perfectly.
Here are some of my logs:
journalctl
dmesg
lspci
Last edited by tormund (2015-04-19 19:26:06)Xabre wrote:
Apr 19 11:52:22 tormund NetworkManager[352]: <info> (wlp1s0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Is ip-config available on your system?
ip-config isn't a program/package (on linux at least). This message just means that DHCP is timing out.
This thread may be relevant: https://bbs.archlinux.org/viewtopic.php?id=146261. You could also try a different dhcp client. -
Stopping NetworkManager [FAIL] on shutdown.
Any idea why every time I shut down I get that error message? Everything else stops just fine, except that. I don't like the word "Fail" every time i turn of the comp. haha.
What might be the issue?Actaully, I followed that link that bangkoks gave me and it worked. It was so simple: Add dbus in front of hal in rc.conf DAEMONS!
The wiki page on HAL and the Beginner's Guide need these details. I those manuals, i remember it saying that you don't need dbus in your DAEMONS because HAL automatically loads it.
But adding one extra little word won't harm anything and will prevent the user from seeing "FAIL" everytime he shuts down, so they should include it, just for the best possible experience. I'm gunna go find where it says that and add it. -
[SOLVED] Networkmanager fails in WIFI on DHCPDISCOVER
Hello,
I have two computers running Arch. Each is up to date. When I use a WIFI usb key to connect to the same SSID, one is working fine and the other isn't.
*edit*
On second thought, there is no difference, I think drivers are to blame
Thank you!
Last edited by ivanoff (2015-04-11 16:13:15)Problem inexplicably solved itself with an update over the past couple of days. Possibly a systemd or a kernel update?
-
Iplanet 4.1 server failed to shutdown
OK I have IPlanet web server 4.2 with SP7 and in the admin screens I want to turn the server off and back on. When I click "off" I get...
server failed to shutdown (0: unknown early startup error)
What in the world is going on? I deleted the wdnotify file and this didn't solve the problem. I could probably do a kill -9 and try to restart it, but what if I get a "could not start" error. Anyone dealt with this before?ok, I grew some balls and reboot the entire UNIX box. Took down all 5 websites! It restarted without a hitch. After the reboot I WAS able to stop and restart the server as many times as needed. No problems.
Here's the thing. I am trying to install the MS SQL Server JDBC driver so my jsp's can connect to a database. From what I read you can just add the path to the jar's in the JVM12.conf file. Well I go to the 'Servlets' tab and hit the 'Configure JVM Attributes' button and scroll over to the JVM Classpath to put the path to my jdbc jars. I did that and tried to stop and restart the server and I am back in the same boat. I tried to shutdown the server and I get a shutdown error. Everything worked until I tried to edit the JVM12.conf file. Now I probably have to reboot to get this thing to work again. My question is....
Why would editing the jvm12.conf file make me have a shutdown failure? Nothing about this failure is entered into the error log or I would post the contents. -
Failed to shutdown DBConsole Gracefully
Hi everyone... I can't stop my dbconsole, this is my output
----Failed to shutdown DBConsole Gracefully----
Failed
My OS is linux, my database is 10.2.0.1.0 and it's a production server...
Has anybody an idea....?
Regards
Carlos Julio.See this note on metalink:
Database Control emctl stop dbconsole failing with error: Failed to shutdown DBConsole Gracefully
Doc ID:335532.1
Werner -
Server failed to shutdown. (0: unknown early startup error
I am running iPlanet 4.1 SP8 on Solaris 8. I receive the following error message when trying to shut down the server via the Administration console:
server failed to shutdown. (0: unknown early startup error
Any ideas?Hi
There is not error message in the Admin Server Logs. In fact, I only see the following:
Status:
[https-compartido]: server failed to shutdown. (0: unknown early startup error)
Error
An error occurred during shutdown.
If I shutdown from the script there is no problem. Only when I try shutdown it from the Admin Server I'm using Solaris 5.8.
Regards -
System fails to shutdown and restart in addition to keyboard freezing HELP!
System fails to shutdown and restart in addition to keyboard freezing HELP!
Try resetting your SMC.
Resetting the System Management Controller >>
Boot from your system CD, run Disk First Aid from your Disk Utility and repair your permissions.
-Bmer
Mac Owners Support Group - Join us @ MacOSG.com
Mac611 Mobile Mac Support - about.Mac611.com
iTunes:MacOSG Podcast | YouTube.MacOSG.com
An Apple User Group -
[SOLVED] Networkmanager prints ugly errors to console on shutdown
When shutting down or rebooting, the system goes to the console for some seconds, and then networkmanager prints a lot of errors, which make the normal shutdown sequence look ugly. How can I fix that?
EDIT: Adding quiet to the boot line in grub fixed it
Last edited by fifafrazer (2008-08-25 19:14:55)After I'm finally connected, dmesg gives me this:
eileen@vaio ~ $ dmesg | grep iwlwifi
[ 15.089340] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 15.089499] iwlwifi 0000:02:00.0: irq 44 for MSI/MSI-X
[ 15.190528] iwlwifi 0000:02:00.0: Direct firmware load failed with error -2
[ 15.190531] iwlwifi 0000:02:00.0: Falling back to user helper
[ 75.324699] iwlwifi 0000:02:00.0: Direct firmware load failed with error -2
[ 75.324705] iwlwifi 0000:02:00.0: Falling back to user helper
[ 135.843224] iwlwifi 0000:02:00.0: loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm
[ 135.926866] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 135.926874] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 135.926879] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 135.926885] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Advanced-N 6200 AGN, REV=0x74
[ 135.926991] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[ 136.063045] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[ 136.069775] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
[ 136.288670] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[ 136.295360] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
Notice the firmware load failures at 15 and 75 seconds after boot, and the fact that it's not until 135 seconds that the firmware for the wireless card is finally loaded.
This suggests to me that the culprit is either the kernel (and/or its iwlwifi module) or the actual firmware. I will try different versions of these packages (linux, linux-lts, and linux-firmware) and will report back.
Last edited by bdantas (2014-12-09 12:31:55) -
[SOLVED] Wireless fails after suspending (Realtek 8192se)
This problem is already solved on the first post: I spent so long trying to solve it that I thought people should know the solution.
I have a Lenovo X100e with a Realtek 8192SE wireless card. I'm running kernel 3.0. The machine has, since upgrading to the 3.0 kernel had the annoying problem of failing wireless connections after suspending: I'll have a running wireless connection, then suspend the machine, and then wake the machine up and the machine cannot connect to any wireless network (perhaps the same one I was connected to before, in the same place).
Things that did not work:
Installing the Realtek drivers from their website
Downgrading the kernel from 3.1 to 3.0
Using wicd instead of networkmanager
Walking around
Other distributions
The solution was to put an entry in /etc/pm/config.d/config:
SUSPEND_MODULES="rtl8192se rtlwifi mac80211 cfg80211"
Now the machine reconnects with no problems.
This may be the solution to the other big problem I was having with the 3.1 kernel: I would suspend the machine by any means and the screen goes black and the machine becomes non-responsive without actually suspending. I may try upgrading to the 3.1 kernel and adding radeon to the SUSPEND_MODULES list above.Found out more which might be significant for madwifi users:
According to the wiki I loaded the following modules in rc.conf: ath-hal, ath9k, wlan
Beside this one line in the modprobe.conf should be added: alias ath0 ath_pci. This way wicd as well as networkmanager used ath0 for connecting to wireless.
After the update I noticed that there is another wifi device in ifconfig listed: wlan0. So I suspected that 2 devices pointing at the same hardware may cause the instability, but de-activating one by ifconfig didn't help. Now I noticed by loading the modules one by one that the new ath9k is already defining wlan0 and the wireless starts working without loading the module wlan. It looks stable so far, but if I should be right I'm impossibly the only one having this trouble.
Confirmation would be nice, but I will mark this thread "solved" now. -
[SOLVED] NetworkManager dumped core
Symptoms: WiFi randomly drops out.
More specifically: NetworkManager core dumps and network-manager-applet stops (Gnome 3.8)
If anyone has suggestions, I'd be grateful. I'm at a loss, other than disabling NetworkManager and enabling netctl. Details follow below.
Thanks so much!
uname -r
3.9.0-2-ARCH
uname -m
x86_64
lspci -v
Network controller: Intel Corporation Centrino Advanced-N 6205
rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
iwconfig
enp0s25 no wireless extensions.
wlp3s0 IEEE 802.11abgn ESSID:"The Way 5GHz"
Mode:Managed Frequency:5.18 GHz Access Point: 00:26:F2:F2:E7:D5
Bit Rate=65 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=54/70 Signal level=-56 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:230 Invalid misc:113 Missed beacon:0
lo no wireless extensions.
journalctl -u NetworkManager --since=today
-- Reboot --
May 04 14:04:19 arch systemd[1]: Starting Network Manager...
May 04 14:04:20 arch NetworkManager[284]: <info> NetworkManager (version 0.9.8.0) is starting...
May 04 14:04:20 arch NetworkManager[284]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
May 04 14:04:20 arch NetworkManager[284]: <info> WEXT support is enabled
May 04 14:04:21 arch NetworkManager[284]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager ma
May 04 14:04:21 arch NetworkManager[284]: keyfile: parsing Auto The Way 5GHz ...
May 04 14:04:21 arch NetworkManager[284]: keyfile: read connection 'Auto The Way 5GHz'
May 04 14:04:21 arch NetworkManager[284]: <info> monitoring kernel firmware directory '/lib/firmware'.
May 04 14:04:21 arch NetworkManager[284]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/
May 04 14:04:21 arch NetworkManager[284]: <info> WiFi hardware radio set enabled
May 04 14:04:21 arch systemd[1]: Started Network Manager.
May 04 14:04:21 arch NetworkManager[284]: <info> WiFi enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> WWAN enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> WiMAX enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> Networking is enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <warn> failed to allocate link cache: (-10) Operation not supported
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): carrier is OFF
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): new Ethernet device (driver: 'e1000e' ifindex: 3)
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): exported as /org/freedesktop/NetworkManager/Devices/0
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): bringing up device.
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): preparing device.
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): deactivating device (reason 'managed') [2]
May 04 14:04:21 arch NetworkManager[284]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:19.0/net/enp0
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): using nl80211 for WiFi device control
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): driver supports Access Point (AP) mode
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 2)
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/1
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): bringing up device.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): preparing device.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): deactivating device (reason 'managed') [2]
May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
May 04 14:04:21 arch NetworkManager[284]: <warn> error poking ModemManager: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop
May 04 14:04:21 arch NetworkManager[284]: <info> wpa_supplicant started
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
May 04 14:04:21 arch NetworkManager[284]: <warn> Trying to remove a non-existant call id.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: starting -> ready
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: ready -> disconnected
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
May 04 14:04:25 arch NetworkManager[284]: <info> Auto-activating connection 'Auto The Way 5GHz'.
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) starting connection 'Auto The Way 5GHz'
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless): connection 'Auto The Way 5GHz' has security, and secrets exist. No new
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'ssid' value 'The Way 5GHz'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'scan_ssid' value '1'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'auth_alg' value 'OPEN'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'psk' value '<omitted>'
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
May 04 14:04:25 arch NetworkManager[284]: <info> Config: set interface ap_scan to 1
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: inactive -> scanning
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: scanning -> authenticating
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: authenticating -> associating
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associating -> associated
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associated -> completed
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless netwo
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled.
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started...
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 04 14:04:28 arch NetworkManager[284]: <info> dhcpcd started with pid 447
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning IP6 addrconf.
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete.
May 04 14:04:28 arch dhcpcd[447]: version 5.6.8 starting
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:28 arch dhcpcd[447]: [color=#FF0000]wlp3s0: sendmsg: Cannot assign requested address[/color]
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: rebinding lease of 192.168.10.59
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: acknowledged 192.168.10.59 from 192.168.10.1
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: checking for 192.168.10.59
May 04 14:04:32 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:33 arch dhcpcd[447]: wlp3s0: leased 192.168.10.59 for 86400 seconds
May 04 14:04:33 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed preinit -> bound
May 04 14:04:33 arch NetworkManager[284]: <info> address 192.168.10.59
May 04 14:04:33 arch NetworkManager[284]: <info> prefix 24 (255.255.255.0)
May 04 14:04:33 arch NetworkManager[284]: <info> gateway 192.168.10.1
May 04 14:04:33 arch NetworkManager[284]: <info> nameserver '192.168.10.1'
May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) started...
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) complete.
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 04 14:04:34 arch NetworkManager[284]: <info> Policy set 'Auto The Way 5GHz' (wlp3s0) as default for IPv4 routing and DNS.
May 04 14:04:34 arch NetworkManager[284]: <info> Writing DNS information to /usr/sbin/resolvconf
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): roamed from BSSID 90:27:E4:5E:98:24 (The Way 5GHz) to 00:26:F2:F2:E7:D5 (The Way 5GHz)
May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) successful, device activated.
May 04 14:04:36 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:40 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:40 arch dhcpcd[447]: wlp3s0: no IPv6 Routers available
May 04 21:04:49 arch NetworkManager[284]: <info> (wlp3s0): IP6 addrconf timed out or failed.
May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
May 04 21:04:50 arch systemd[1]: NetworkManager.service: main process exited, code=dumped, status=6/ABRT
May 04 21:04:50 arch systemd[1]: MESSAGE=Unit NetworkManager.service entered failed state.
May 04 21:04:50 arch systemd-coredump[1036]: [color=#FF0000]Process 284 (NetworkManager) dumped core.[/color]
journalctl -u wpa_supplicant --since=today
-- Reboot --
May 04 14:04:21 arch systemd[1]: Starting WPA supplicant...
See dmesg at Pastebin
[edited May 7, 2013]
I'm marking this topic SOLVED, though more accurately, I should say that I've worked around the problem.
I achieved a stable wireless connection by changing APs, which leads me to believe that the underlying problem is upstream. Specifically, the problem is most likely that NetworkManager is not compatible with all APs. In my case, when I connect to a Netgear NDR3700v1 running dd-wrt, NetworkManager and nn-applet crashed randomly and frequently. However, after changing to an Apple Airport AP, I achieved a stable connection without crashes.
Bottomline: if you experience wireless connection troubles with NetworkManager and nm-applet, the problem may be that NetworkManager is not "compatible" with your AP hardware.
Last edited by hcra (2013-05-07 20:50:36)b1tgl0w wrote:Is it normal for crond to run as the root user?
Completely normal. I'd be asking the question "was I hacked" if I found cron NOT running as root.
I'd say your computer just crashed. -
Hi All,
After a update of my laptop, it does not fully wakes after going into suspend. It does not react to numlock anymore. I have to push the power button for 10 seconds to shut it down.
/var/log/everything.log, normal operations:
Jul 21 03:42:38 localhost dhcpcd[1029]: wlan0: sending IPv6 Router Solicitation
Jul 21 03:42:38 localhost dhcpcd[1029]: wlan0: sendmsg: Cannot assign requested address
Jul 21 03:42:38 localhost dhcpcd[1029]: wlan0: no IPv6 Routers available
Jul 21 03:42:45 localhost dbus[533]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jul 21 03:42:45 localhost dbus[533]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jul 21 03:42:45 localhost acpid: client connected from 1134[0:1000]
Jul 21 03:42:45 localhost acpid: 1 client rule loaded
Jul 21 03:42:46 localhost NetworkManager[559]: <info> (wlan0): IP6 addrconf timed out or failed.
Jul 21 03:42:46 localhost NetworkManager[559]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jul 21 03:42:46 localhost NetworkManager[559]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jul 21 03:42:46 localhost NetworkManager[559]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 21 03:42:50 localhost acpid: client connected from 1134[0:1000]
Jul 21 03:42:50 localhost acpid: 1 client rule loaded
Jul 21 03:42:55 localhost kernel: [ 48.812457] fuse init (API version 7.18)
Jul 21 03:42:59 localhost dbus[533]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
Jul 21 03:42:59 localhost udisksd[1209]: udisks daemon version 1.94.0 starting
Jul 21 03:42:59 localhost dbus[533]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Jul 21 03:42:59 localhost udisksd[1209]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jul 21 04:01:01 localhost /USR/SBIN/CROND[1363]: (root) CMD (run-parts /etc/cron.hourly)
Jul 21 04:01:01 localhost anacron[1369]: Anacron started on 2012-07-21
Jul 21 04:01:01 localhost anacron[1369]: Will run job `cron.daily' in 42 min.
Jul 21 04:01:01 localhost anacron[1369]: Jobs will be executed sequentially
Jul 21 04:21:01 localhost -- MARK --
/var/log/everything.log, after starting suspend:
Jul 21 04:21:13 localhost kernel: [ 2346.821030] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:21:13 localhost kernel: [ 2347.000872] EXT4-fs (sda8): re-mounted. Opts: commit=0
Jul 21 04:25:10 localhost kernel: [ 2349.512404] PM: Syncing filesystems ... done.
Jul 21 04:25:10 localhost kernel: [ 2349.514874] PM: Preparing system for mem sleep
Jul 21 04:25:10 localhost kernel: [ 2349.514891] Freezing user space processes ... (elapsed 0.01 seconds) done.
Jul 21 04:25:10 localhost kernel: [ 2349.526541] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Jul 21 04:25:10 localhost kernel: [ 2349.539896] PM: Entering mem sleep
Jul 21 04:25:10 localhost kernel: [ 2349.539930] Suspending console(s) (use no_console_suspend to debug)
Jul 21 04:25:10 localhost kernel: [ 2349.573787] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 21 04:25:10 localhost kernel: [ 2349.611052] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:10 localhost kernel: [ 2349.613512] sd 0:0:0:0: [sda] Stopping disk
Jul 21 04:25:10 localhost kernel: [ 2350.236650] PM: suspend of devices complete after 696.314 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.236925] PM: late suspend of devices complete after 0.270 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.237272] r8169 0000:08:00.0: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.266603] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.303271] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.326605] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.343218] ehci_hcd 0000:00:1a.7: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.379942] uhci_hcd 0000:00:1a.2: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.403292] uhci_hcd 0000:00:1a.1: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.426606] uhci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.426678] PM: noirq suspend of devices complete after 189.749 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.427140] ACPI: Preparing to enter system sleep state S3
Jul 21 04:25:10 localhost kernel: [ 2350.519991] PM: Saving platform NVS memory
Jul 21 04:25:10 localhost kernel: [ 2350.520810] Disabling non-boot CPUs ...
Jul 21 04:25:10 localhost kernel: [ 2350.623205] CPU 1 is now offline
Jul 21 04:25:10 localhost kernel: [ 2350.623688] Extended CMOS year: 2000
Jul 21 04:25:10 localhost kernel: [ 2350.623688] ACPI: Low-level resume complete
Jul 21 04:25:10 localhost kernel: [ 2350.623688] PM: Restoring platform NVS memory
Jul 21 04:25:10 localhost kernel: [ 2350.623688] Extended CMOS year: 2000
Jul 21 04:25:10 localhost kernel: [ 2350.623688] Enabling non-boot CPUs ...
Jul 21 04:25:10 localhost kernel: [ 2350.630554] Booting Node 0 Processor 1 APIC 0x1
Jul 21 04:25:10 localhost kernel: [ 2350.641916] NMI watchdog: enabled, takes one hw-pmu counter.
Jul 21 04:25:10 localhost kernel: [ 2350.645407] CPU1 is up
Jul 21 04:25:10 localhost kernel: [ 2350.647122] ACPI: Waking up from system sleep state S3
Jul 21 04:25:10 localhost kernel: [ 2350.653227] uhci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.659889] uhci_hcd 0000:00:1a.1: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.666555] uhci_hcd 0000:00:1a.2: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.683204] ehci_hcd 0000:00:1a.7: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.689888] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.696556] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.713204] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.715075] PM: noirq resume of devices complete after 67.761 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.715286] PM: early resume of devices complete after 0.105 msecs
Jul 21 04:25:10 localhost kernel: [ 2350.715344] uhci_hcd 0000:00:1a.0: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715373] usb usb1: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715391] uhci_hcd 0000:00:1a.1: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715421] usb usb2: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715437] uhci_hcd 0000:00:1a.2: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715465] usb usb3: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715480] ehci_hcd 0000:00:1a.7: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715521] uhci_hcd 0000:00:1d.0: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715540] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X
Jul 21 04:25:10 localhost kernel: [ 2350.715550] usb usb4: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715571] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715601] usb usb5: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715611] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715623] ehci_hcd 0000:00:1d.7: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715639] usb usb6: root hub lost power or was reset
Jul 21 04:25:10 localhost kernel: [ 2350.715647] pci 0000:00:1e.0: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715663] ata_piix 0000:00:1f.2: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715667] ata_piix 0000:00:1f.5: setting latency timer to 64
Jul 21 04:25:10 localhost kernel: [ 2350.715690] r8169 0000:08:00.0: wake-up capability disabled by ACPI
Jul 21 04:25:10 localhost kernel: [ 2350.723377] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:10 localhost kernel: [ 2350.723395] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:10 localhost kernel: [ 2350.816609] r8169 0000:08:00.0: eth0: link down
Jul 21 04:25:10 localhost kernel: [ 2351.111777] ata4: SATA link down (SStatus 0 SControl 300)
Jul 21 04:25:10 localhost kernel: [ 2351.128460] ata3: SATA link down (SStatus 0 SControl 300)
Jul 21 04:25:10 localhost kernel: [ 2351.199920] usb 2-1: reset low-speed USB device number 2 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2351.263475] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jul 21 04:25:10 localhost kernel: [ 2351.276859] firewire_core 0000:1a:00.0: rediscovered device fw0
Jul 21 04:25:10 localhost kernel: [ 2351.283960] ata2.00: configured for UDMA/100
Jul 21 04:25:10 localhost kernel: [ 2351.739942] usb 2-2: reset low-speed USB device number 3 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.129932] usb 8-2: reset high-speed USB device number 2 using ehci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.359839] usb 6-1: reset full-speed USB device number 2 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.784239] usb 6-1.1: reset full-speed USB device number 3 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.883229] btusb 6-1.1:1.0: no reset_resume for driver btusb?
Jul 21 04:25:10 localhost kernel: [ 2352.883233] btusb 6-1.1:1.1: no reset_resume for driver btusb?
Jul 21 04:25:10 localhost kernel: [ 2352.941243] usb 6-1.2: reset full-speed USB device number 4 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2352.969919] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 21 04:25:10 localhost kernel: [ 2353.101249] usb 6-1.3: reset full-speed USB device number 5 using uhci_hcd
Jul 21 04:25:10 localhost kernel: [ 2353.181194] ata1.00: configured for UDMA/133
Jul 21 04:25:10 localhost kernel: [ 2353.181463] sd 0:0:0:0: [sda] Starting disk
Jul 21 04:25:10 localhost kernel: [ 2353.436737] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jul 21 04:25:10 localhost kernel: [ 2358.057138] PM: resume of devices complete after 7341.844 msecs
Jul 21 04:25:10 localhost kernel: [ 2358.057602] PM: Finishing wakeup.
Jul 21 04:25:10 localhost kernel: [ 2358.057604] Restarting tasks ... done.
Jul 21 04:25:10 localhost kernel: [ 2358.064234] video LNXVIDEO:00: Restoring backlight state
Jul 21 04:25:11 localhost kernel: [ 2358.233575] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:11 localhost kernel: [ 2358.272368] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:11 localhost kernel: [ 2358.309721] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:11 localhost kernel: [ 2358.349601] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:25:13 localhost kernel: [ 2360.644416] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:25:13 localhost kernel: [ 2360.648163] EXT4-fs (sda8): re-mounted. Opts: commit=0
Jul 21 04:25:13 localhost acpid: client 1134[0:1000] has disconnected
Jul 21 04:25:13 localhost acpid: client 1134[0:1000] has disconnected
Jul 21 04:25:13 localhost acpid: client connected from 1134[0:1000]
Jul 21 04:25:13 localhost acpid: 1 client rule loaded
Jul 21 04:25:26 localhost kernel: [ 2373.415894] NVRM: Xid (0000:01:00): 8, Channel 0000007e
Jul 21 04:25:26 localhost kernel: [ 2373.700350] hrtimer: interrupt took 91847280 ns
Jul 21 04:25:26 localhost kernel: [ 2373.700352] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
Jul 21 04:28:36 localhost kernel: [ 2563.568752] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:28:36 localhost kernel: [ 2563.573610] EXT4-fs (sda8): re-mounted. Opts: commit=0
What does this message mean?
Jul 21 04:25:26 localhost kernel: [ 2373.700352] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
What can i do to solve this?
Best regards,
Cedric
Last edited by cdwijs (2012-08-09 18:33:34)I did a quick google search. This page suggested that I set my videocard in persistend mode:
http://scientificlinuxforum.org/index.p … topic=1469
So i did the following:
]# /usr/bin/nvidia-smi -pm 1
Enabled persistence mode for GPU 0000:01:00.0.
All done.
# /usr/bin/nvidia-smi -q
==============NVSMI LOG==============
Timestamp : Sat Jul 21 04:58:55 2012
Driver Version : 302.17
Attached GPUs : 1
GPU 0000:01:00.0
Product Name : GeForce 9600M GS
Display Mode : N/A
Persistence Mode : Enabled
Driver Model
Current : N/A
Pending : N/A
Serial Number : N/A
GPU UUID : N/A
VBIOS Version : 62.94.8D.00.0B
Inforom Version
OEM Object : N/A
ECC Object : N/A
Power Management Object : N/A
PCI
Bus : 0x01
Device : 0x00
Domain : 0x0000
Device Id : 0x064810DE
Bus Id : 0000:01:00.0
Sub System Id : 0x02C01028
GPU Link Info
PCIe Generation
Max : N/A
Current : N/A
Link Width
Max : N/A
Current : N/A
Fan Speed : N/A
Performance State : N/A
Memory Usage
Total : 511 MB
Used : 30 MB
Free : 480 MB
Compute Mode : Default
Utilization
Gpu : N/A
Memory : N/A
Ecc Mode
Current : N/A
Pending : N/A
ECC Errors
Volatile
Single Bit
Device Memory : N/A
Register File : N/A
L1 Cache : N/A
L2 Cache : N/A
Total : N/A
Double Bit
Device Memory : N/A
Register File : N/A
L1 Cache : N/A
L2 Cache : N/A
Total : N/A
Aggregate
Single Bit
Device Memory : N/A
Register File : N/A
L1 Cache : N/A
L2 Cache : N/A
Total : N/A
Double Bit
Device Memory : N/A
Register File : N/A
L1 Cache : N/A
L2 Cache : N/A
Total : N/A
Temperature
Gpu : 61 C
Power Readings
Power Management : N/A
Power Draw : N/A
Power Limit : N/A
Clocks
Graphics : N/A
SM : N/A
Memory : N/A
Max Clocks
Graphics : N/A
SM : N/A
Memory : N/A
Compute Processes : Not Supported
This did not solve the issue. The laptop goes into suspend (the power LED starts blinking), but when the power button is then briefly pressed, the machine does power-up, but after hearing 2 clicks from the speaker, i get a black screen, a full-running CPU fan, and no reaction to numlock.
/var/log/everything.log:
Jul 21 04:30:13 localhost NetworkManager[565]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 21 04:50:40 localhost -- MARK --
Jul 21 04:54:46 localhost kernel: [ 1516.765698] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:54:46 localhost kernel: [ 1516.942964] EXT4-fs (sda8): re-mounted. Opts: commit=0
Jul 21 04:55:02 localhost kernel: [ 1519.654895] PM: Syncing filesystems ... done.
Jul 21 04:55:02 localhost kernel: [ 1519.657049] PM: Preparing system for mem sleep
Jul 21 04:55:02 localhost kernel: [ 1519.657066] Freezing user space processes ... (elapsed 0.01 seconds) done.
Jul 21 04:55:02 localhost kernel: [ 1519.669943] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Jul 21 04:55:02 localhost kernel: [ 1519.683296] PM: Entering mem sleep
Jul 21 04:55:02 localhost kernel: [ 1519.683337] Suspending console(s) (use no_console_suspend to debug)
Jul 21 04:55:02 localhost kernel: [ 1519.717139] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 21 04:55:02 localhost kernel: [ 1519.749832] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1519.786781] sd 0:0:0:0: [sda] Stopping disk
Jul 21 04:55:02 localhost kernel: [ 1520.410064] PM: suspend of devices complete after 726.343 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.410337] PM: late suspend of devices complete after 0.266 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.410678] r8169 0000:08:00.0: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.440024] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.476689] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.500023] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.516685] ehci_hcd 0000:00:1a.7: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.553353] uhci_hcd 0000:00:1a.2: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.576688] uhci_hcd 0000:00:1a.1: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.603354] uhci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.603426] PM: noirq suspend of devices complete after 193.085 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.603888] ACPI: Preparing to enter system sleep state S3
Jul 21 04:55:02 localhost kernel: [ 1520.693403] PM: Saving platform NVS memory
Jul 21 04:55:02 localhost kernel: [ 1520.694218] Disabling non-boot CPUs ...
Jul 21 04:55:02 localhost kernel: [ 1520.796623] CPU 1 is now offline
Jul 21 04:55:02 localhost kernel: [ 1520.797088] Extended CMOS year: 2000
Jul 21 04:55:02 localhost kernel: [ 1520.797088] ACPI: Low-level resume complete
Jul 21 04:55:02 localhost kernel: [ 1520.797088] PM: Restoring platform NVS memory
Jul 21 04:55:02 localhost kernel: [ 1520.797088] Extended CMOS year: 2000
Jul 21 04:55:02 localhost kernel: [ 1520.797088] Enabling non-boot CPUs ...
Jul 21 04:55:02 localhost kernel: [ 1520.803951] Booting Node 0 Processor 1 APIC 0x1
Jul 21 04:55:02 localhost kernel: [ 1520.815303] NMI watchdog: enabled, takes one hw-pmu counter.
Jul 21 04:55:02 localhost kernel: [ 1520.816608] CPU1 is up
Jul 21 04:55:02 localhost kernel: [ 1520.818293] ACPI: Waking up from system sleep state S3
Jul 21 04:55:02 localhost kernel: [ 1520.823322] uhci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.829975] uhci_hcd 0000:00:1a.1: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.836638] uhci_hcd 0000:00:1a.2: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.853290] ehci_hcd 0000:00:1a.7: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.859971] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.866638] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.883290] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.885162] PM: noirq resume of devices complete after 66.681 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.885372] PM: early resume of devices complete after 0.105 msecs
Jul 21 04:55:02 localhost kernel: [ 1520.885432] uhci_hcd 0000:00:1a.0: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885432] uhci_hcd 0000:00:1a.1: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885465] usb usb1: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885466] usb usb2: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885487] uhci_hcd 0000:00:1a.2: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885490] ehci_hcd 0000:00:1a.7: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885518] usb usb3: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885549] uhci_hcd 0000:00:1d.0: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885582] usb usb4: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885582] snd_hda_intel 0000:00:1b.0: irq 48 for MSI/MSI-X
Jul 21 04:55:02 localhost kernel: [ 1520.885600] uhci_hcd 0000:00:1d.1: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885629] usb usb5: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885648] uhci_hcd 0000:00:1d.2: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885653] ehci_hcd 0000:00:1d.7: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885680] pci 0000:00:1e.0: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885679] usb usb6: root hub lost power or was reset
Jul 21 04:55:02 localhost kernel: [ 1520.885698] ata_piix 0000:00:1f.2: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885713] ata_piix 0000:00:1f.5: setting latency timer to 64
Jul 21 04:55:02 localhost kernel: [ 1520.885736] r8169 0000:08:00.0: wake-up capability disabled by ACPI
Jul 21 04:55:02 localhost kernel: [ 1520.890553] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1520.891048] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1520.960285] r8169 0000:08:00.0: eth0: link down
Jul 21 04:55:02 localhost kernel: [ 1521.281391] ata3: SATA link down (SStatus 0 SControl 300)
Jul 21 04:55:02 localhost kernel: [ 1521.297666] ata4: SATA link down (SStatus 0 SControl 300)
Jul 21 04:55:02 localhost kernel: [ 1521.332377] Extended CMOS year: 2000
Jul 21 04:55:02 localhost kernel: [ 1521.376657] usb 2-1: reset low-speed USB device number 2 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1521.406940] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jul 21 04:55:02 localhost kernel: [ 1521.427670] ata2.00: configured for UDMA/100
Jul 21 04:55:02 localhost acpid: client 1147[0:1000] has disconnected
Jul 21 04:55:02 localhost acpid: client 1147[0:1000] has disconnected
Jul 21 04:55:02 localhost kernel: [ 1521.453328] firewire_core 0000:1a:00.0: rediscovered device fw0
Jul 21 04:55:02 localhost kernel: [ 1521.915219] usb 2-2: reset low-speed USB device number 3 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1522.303337] usb 8-2: reset high-speed USB device number 2 using ehci_hcd
Jul 21 04:55:02 localhost kernel: [ 1522.533339] usb 6-1: reset full-speed USB device number 2 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1522.955078] usb 6-1.1: reset full-speed USB device number 3 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1523.057065] btusb 6-1.1:1.0: no reset_resume for driver btusb?
Jul 21 04:55:02 localhost kernel: [ 1523.057070] btusb 6-1.1:1.1: no reset_resume for driver btusb?
Jul 21 04:55:02 localhost kernel: [ 1523.113342] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 21 04:55:02 localhost kernel: [ 1523.115078] usb 6-1.2: reset full-speed USB device number 4 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1523.278082] usb 6-1.3: reset full-speed USB device number 5 using uhci_hcd
Jul 21 04:55:02 localhost kernel: [ 1523.321369] ata1.00: configured for UDMA/133
Jul 21 04:55:02 localhost kernel: [ 1523.321637] sd 0:0:0:0: [sda] Starting disk
Jul 21 04:55:02 localhost kernel: [ 1523.613501] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jul 21 04:55:02 localhost kernel: [ 1528.234017] PM: resume of devices complete after 7348.637 msecs
Jul 21 04:55:02 localhost kernel: [ 1528.234472] PM: Finishing wakeup.
Jul 21 04:55:02 localhost kernel: [ 1528.234474] Restarting tasks ... done.
Jul 21 04:55:02 localhost kernel: [ 1528.239320] video LNXVIDEO:00: Restoring backlight state
Jul 21 04:55:02 localhost acpid: client connected from 1147[0:1000]
Jul 21 04:55:02 localhost acpid: 1 client rule loaded
Jul 21 04:55:02 localhost kernel: [ 1528.396372] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1528.433245] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1528.469720] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:02 localhost kernel: [ 1528.506634] sdhci-pci 0000:1a:00.1: Will use DMA mode even though HW doesn't fully claim to support it.
Jul 21 04:55:03 localhost kernel: [ 1530.007718] EXT4-fs (sda5): re-mounted. Opts: commit=0
Jul 21 04:55:04 localhost kernel: [ 1530.271879] EXT4-fs (sda8): re-mounted. Opts: commit=0
Jul 21 04:55:55 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset
Jul 21 04:55:55 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu
Interestingly, the message that the GPU has fallen off the bus is no longer present. Something else is going on as well :-)
Best regards,
Cedric -
[SOLVED] Redis failing to start on boot
Content of redis.service:
[Unit]
Description=Advanced key-value store
After=network.target
[Service]
User=redis
Group=redis
ExecStart=/usr/bin/redis-server /etc/redis.conf
ExecStop=/usr/bin/redis-cli shutdown
CapabilityBoundingSet=
PrivateTmp=true
PrivateDevices=true
ProtectSystem=full
ProtectHome=true
NoNewPrivileges=true
RuntimeDirectory=redis
RuntimeDirectoryMode=700
[Install]
WantedBy=multi-user.target
On every boot:
Mar 09 10:03:17 carpo systemd[1]: redis.service: main process exited, code=exited, status=233/RUNTIME_DIRECTORY
Mar 09 10:03:17 carpo systemd[702]: Failed at step RUNTIME_DIRECTORY spawning /usr/bin/redis-cli: File exists
Mar 09 10:03:17 carpo systemd[1]: redis.service: control process exited, code=exited status=233
Mar 09 10:03:17 carpo systemd[1]: Unit redis.service entered failed state.
Mar 09 10:03:17 carpo systemd[1]: redis.service failed.
Restarting it manually after the boot starts it properly. RuntimeDirectory was added recently by the package. Directory /run is not persistant:
# mount | grep -e '^run'
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
I am stuck on figuring out what happens here. Did anybody else have this issue?
Last edited by kotnik (2015-03-18 09:44:48)sharow wrote:related: https://bugs.archlinux.org/task/44067
Thank you for pointing me to that issue.
Issue is solved in version 2.8.19-4. -
[solved] networkmanager-vpnc
Hello everyone,
I added a vpnc using networkmanager-vpnc but when i try to activate it i get the following message:
Jun 27 19:35:55 himmel NetworkManager[333]: <warn> connection /org/freedesktop/NetworkManager/Settings/2 failed to activate: (2) The VPN service 'org.freedesktop.NetworkManager.vpnc' was not installed.
i checked the boards but couldn't find anything to help me solve this issue, has anyone encountered this before?
Thanks in advanced for your time and assistance.
Zerosoul.
Last edited by zerosoul13 (2012-06-29 03:52:41)this is odd, seems that those packages were already installed on the machine
[angel@himmel ~]$ sudo pacman -S networkmanager-vpnc vpnc
warning: networkmanager-vpnc-0.9.4.0-1 is up to date -- reinstalling
warning: vpnc-0.5.3.svn516-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (2): networkmanager-vpnc-0.9.4.0-1 vpnc-0.5.3.svn516-2
Total Installed Size: 0.80 MiB
Net Upgrade Size: 0.00 MiB
Proceed with installation? [Y/n] Y
(2/2) checking package integrity [--------------------------------------------------------] 100%
(2/2) loading package files [--------------------------------------------------------] 100%
(2/2) checking for file conflicts [--------------------------------------------------------] 100%
(2/2) checking available disk space [--------------------------------------------------------] 100%
(1/2) upgrading vpnc [--------------------------------------------------------] 100%
(2/2) upgrading networkmanager-vpnc [--------------------------------------------------------] 100%
[angel@himmel ~]$ sudo /etc/rc.d/networkmanager restart
:: Stopping NetworkManager [DONE]
:: Starting NetworkManager
After this, i was able to connect to VPN, ill do a reboot and see if it works without having to restart the networkmanager daemon.
# Issue solved.
Last edited by zerosoul13 (2012-06-29 03:52:02) -
[SOLVED] NetworkManager keeps on reconnecting
My NetworkManager keeps on reconnecting no matter whether I use wired or wireless network. This annoys me a few days.
I find that `sudo systemctl restart NetworkManager` could solve this problem temporarily. After reboot the problem arises again.
My system is up to date. And I am using Gnome 3.
Any idea why does it happen and how could I get rid of it?
Last edited by vanitas (2015-02-04 04:01:10)@frank604, I didn't enabled dhcpcd, netctl, or wicd.
I ran `journalctl -u NetworkManager.service` and noticed these lines:
Feb 04 10:36:52 xbull NetworkManager[4339]: <warn> the dhcpcd backend does not support IPv6.
Feb 04 10:36:52 xbull NetworkManager[4339]: <info> (enp4s0): device state change: activated -> failed (reason 'dhcp-start-failed') [100 120 15]
After some googling, I find this post: dhcpcd not work with NetworkManager 1.0.
Someone metions that NetworkManager 1.0 embed an internal DHCP client, and the DHCP client does not support IPv6 yet.
I edit the connection and disable IPv6, then the problem disappears.
Thanks for your help!
Maybe you are looking for
-
Hi Everyone While burning a DVDSP3 disk of about 3.5 gigs, I get this error message: "error while encoding file". This happens about 7 hours into the burn. I have tried it twice. The second time after fixing preferences, etc. I am using a G-4 laptop
-
I'm new to the forums so not quite sure how to begin, but here goes. Recently bought and loaded PSE11. Everything loaded fine except for Camera Raw. No evidence that ACR ever loaded. Went to update and it downloaded and updated to 7.4 (so it said)
-
For a couple days now an icon that is a white envelope with a blackberry symbol in the middle and a white and red exclamation point and been on my home screen. i am not able to open the icon and do no know how to get rid of it! someone please help!
-
PO header conditions doubling up.
I am having a problem with the price determination on PO. I have created 19 custom condition types, of these some are header and some are item level. Problem 1. The header level condions are doubling up as per increase in line items. For ex.My Z head
-
I lost my photos when I reset my iPad
I needed to change my apple I'd as the email was discontinued ,In the proses I reset the iPad which went well except all my photos went missing ,A full backup was quit resent Can anybody help.