100% CPU millions (!) of messages in syslog (<WARN> nm_error_monitoring_device_link_state(): error monitoring wired ethernet link state: error occurred while waiting for data on socket)

[Jerome Lacoste]

Binary package hint: network-manager

For some reason, NetworkManager got in a bad state:
* 100% CPU
* lots of memory used (VIRT 2800m, REF 800m) according to top

Looking at syslog:

Dec 13 21:19:37 expresso2 kernel: [291197.056347] iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28
Dec 13 21:19:37 expresso2 NetworkManager: <WARN> nm_error_monitoring_device_link_state(): error monitoring wired ethernet link state: error occurr
ed while waiting for data on socket
Dec 13 21:20:01 expresso2 last message repeated 406068 times

etc...

So there's a problem at the kernel driver (iwl3945) level, but NM is probably not handling it in the best way.

Solved by doing /etc/init.d/NetworkManager restart twice + reconnecting to the wireless network.

Full syslog attached.

[Brandon Whaley (redkrieg)]

Having the exact same issue after installing a NetworkManager update last night. NetworkManager process is at 60% usage, syslogd is using all the rest up to 100%.

I also use iwl3945 for networking.

Solved by sudo killall -9 NetworkManager, then gksu NetworkManager

Happens every time I boot.

[Brandon Whaley (redkrieg)]

Correction to my previous comment. I've rebooted around 5 times and now I no longer have this issue. Not sure why not. If anyone needs logs, please contact me.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Thanks you fro taking time to report this bug. Jeremy, do you still have this issue or is it gone (like in Brandon's case)? If yes it would be useful if you can submit more information for it by looking to https://wiki.ubuntu.com/DebuggingNetworkManager , Thanks in advance.

[Jerome Lacoste (jerome-lacoste)]

I had a hard hang today, and saw that the disk was thrashing. I was forced to reset the laptop (couldn't log in text mode neither).

Looking at syslog, the only thing I saw was that the same messages were printed. Not sure if it is a symptom or a consequence of another problem.

So yes I still see that. Will try to debug NM next time.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!