You are not logged in.

#1 2013-10-02 16:41:53

poseidon
Member
Registered: 2012-06-07
Posts: 58

shutdown: timeout opening/writing control channel /dev/initctl

For about 2 to 3 weeks it sometimes happens, that the system cannot be shutdown. If I shutdwown from w/i KDE, the GUI is shut down and then the systems hangs in the console. Changing to another console and issueing shutdown -h now causes the above message.

The above message is also issued, if I shutdown from w/i a conole in KDE.

It is somehow connected with suspendig the computer (lenove X220). It sometimes happens, that at the resume not the GUI appears but a console instead. I have then to press ctrl-alt-f7 and the GUI appears. If that happens, I know for sure that tha system will not shutdown and I have to press the off/on button. Suspend by closing the lid also stops working, but pm-suspend issued on a console still works.

Anyone else experiencing this behaviour?

Offline

#2 2013-10-03 14:39:34

sanderd17
Member
Registered: 2011-06-11
Posts: 32

Re: shutdown: timeout opening/writing control channel /dev/initctl

I have a similar problem in the following ways: sometimes shutdown -h throws the following message:

Failed to talk to shutdownd, proceeding with immediate shutdown: Connection refused
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.

(which also metions it can't open dev/initctl, while the file is present when I do "ls /dev". It also happens together with not being able to suspend via the hotkeys, but pm-suspend also works.

I use xmonad as WM, and for me it's consistent. When Xmonad is launched, I can only suspend once via the hotkeys. After that, I get the problems mentioned above. If I don't launch Xorg, I can suspend-resume as often as I want it seems.

Offline

#3 2013-10-03 18:06:11

koshak
Member
Registered: 2013-03-13
Posts: 35

Re: shutdown: timeout opening/writing control channel /dev/initctl

i686, guys?

Offline

#4 2013-10-05 16:38:28

ad8
Member
Registered: 2013-10-05
Posts: 3

Re: shutdown: timeout opening/writing control channel /dev/initctl

I am experiencing the same symptoms: after resuming from suspend on my laptop, cannot shutdown. I get the same error message that sanderd17 posted, and the same TTY switching behavior that poseidon described (upon resuming from suspend, TTY1 is displayed (but no error messages), and must ctrl+alt+f7 to return to GUI).

koshak: yes, i686. Machine is an Asus UX31 running archbang (openbox DE).

Using

 sync; reboot -f 

works without having to resort to the power switch.

Offline

#5 2013-10-06 02:43:54

Amarildo
Member
Registered: 2013-09-21
Posts: 246
Website

Re: shutdown: timeout opening/writing control channel /dev/initctl


If it ain't broke, you haven't tweaked it enough...

Offline

#6 2013-10-06 07:11:06

koshak
Member
Registered: 2013-03-13
Posts: 35

Offline

#7 2013-10-06 15:06:27

ad8
Member
Registered: 2013-10-05
Posts: 3

Re: shutdown: timeout opening/writing control channel /dev/initctl

Thanks...

Downgrading the kernel from 3.11 to 3.10 fixes my suspend issues, but unfortunately that upgrade (from 3.10 to 3.11) is what fixed my (more serious) networking issues. Guess i'll just have live without suspend until it's fixed for real.

Offline

#8 2013-10-06 15:32:14

WorMzy
Forum Moderator
From: England
Registered: 2010-06-16
Posts: 4,841

Re: shutdown: timeout opening/writing control channel /dev/initctl

Alternatively, use ABS to backport the network fix to the older kernel.


Sakura:-
Mobo: ASUS P8Z77-V PRO // Processor: Intel Core i7-3770K 3.4GHz // GFX: nVidia GeForce GTX 970 Ti // RAM: 32GB (4x 8GB) Corsair DDR3 (@ 2133MHz) // Storage: 1x 3TB Seagate SATAII 5x 1TB Samsung SATAII, 2x 120GB Corsair SSD

Offline

#9 2013-10-10 05:53:01

poseidon
Member
Registered: 2012-06-07
Posts: 58

Re: shutdown: timeout opening/writing control channel /dev/initctl

ad8 wrote:

Thanks...

Downgrading the kernel from 3.11 to 3.10 fixes my suspend issues, but unfortunately that upgrade (from 3.10 to 3.11) is what fixed my (more serious) networking issues. Guess i'll just have live without suspend until it's fixed for real.

If it only was that... sudo pm-suspend on the console works, but I can't shutdown anymore, I have to sync and switch off my notebook (embarrassing by the way, I'm in a Windows shop). This happens after, say, 5 to 10 times of closing the lid / exec'ing pm-suspend (as described already also by others: If I open the lid and see a console prompt, I know that I will not be able to shutdown the notebook). After a few more pm-suspends the network stops working (still thinking it was a wicd-gtk issue, trying wicd-kde right now, so I will see) and - yes, sync and switch off.

Offline

#10 2013-10-15 01:55:26

ad8
Member
Registered: 2013-10-05
Posts: 3

Re: shutdown: timeout opening/writing control channel /dev/initctl

for what it's worth, this appears to be fixed in the latest version. nevermind... just encountered the same problem again. system survived more suspends than before, however

Last edited by ad8 (2013-10-15 02:17:16)

Offline

Board footer

Powered by FluxBB