On Sat, Dec 7, 2013 at 11:56 AM, Cristian Rodríguez wrote:

El 07/12/13 12:09, Greg Freemyer escribió:

...

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

Is this a 32 bit version right ?

Correct -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, Dec 7, 2013 at 1:17 PM, Cristian Rodríguez wrote:

El 07/12/13 15:01, Greg Freemyer escribió:

...

On Sat, Dec 7, 2013 at 11:56 AM, Cristian Rodríguez wrote:

...

El 07/12/13 12:09, Greg Freemyer escribió:

...

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

Is this a 32 bit version right ?

Correct

it is a known bug that affects 32 bit systems only, no.. it is not a bug in systemd, so resist the urge of shooting the messenger :-P.. it is a kernel regression. fixed in 3.11.8.

hmm... How many users are getting hit by this? I'm running vanilla 13.1 OSS and upgrades as far as this bug is concerned. Is it in bugzilla? This may be the same bug, so I added a comment to it: https://bugzilla.novell.com/show_bug.cgi?id=839170 If you're right, there is no point troubleshooting. Will cycling power fix it? Or at least let me connect to wireless? If not, the only option I can think of off-hand to fix it is to use susestudio to build a custom live CD with a newer kernel (which is already in OBS). Then use that boot CD/DVD to upgrade my laptop in place. That's not as hard as it sounds, but is there a better way? Thanks Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, Dec 7, 2013 at 10:28 PM, Cristian Rodríguez wrote:

El 07/12/13 23:54, Greg Freemyer escribió:

...

Will cycling power fix it? Or at least let me connect to wireless?

Did you suspended the system in the process as well right ? (for a test, or closed the laptop lid and the machine automatically went to sleep )

Yes, it was suspended before I woke it up and realized the wireless lan did not reconnect. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Content-ID: El 2013-12-08 a las 01:00 -0300, Cristian Rodríguez escribió:

Thank you, I was making exactly sure we are talking about the same issue (as you know, nobody 's got psychic powers to guess beforehand that the system was 32 bit or that you used suspended/resume)

the "Failed to open /dev/initctl: No such device or address" thing, and "wireless connections not coming up again", and others, are indeed the same kernel issue I was talking about in previous mails, it is triggered by suspend/resume in 32 bit machines.

fixed in:

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.11.y&id=7668bd83b5e7fd1519b1fd92226a948299692e6b

and

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.11.y&id=83da8ac7ee52d56e9bf5626502cca6e8e169580c

In short epoll() and select() may do stupid things after resume.

There was an announcement of a new kernel today: openSUSE Security Update: kernel to 3.11.10 ______________________________________________________________________________ Announcement ID: openSUSE-SU-2014:0205-1 Rating: important References: #733022 #773058 #838024 #844513 #845621 #846529 #848042 #849021 #850072 #852652 #852656 #852931 #853050 #853051 #853052 #853053 #854175 #854722 #856294 #859804 #860993 Cross-References: CVE-2013-4511 CVE-2013-4563 CVE-2013-4587 CVE-2013-6367 CVE-2013-6368 CVE-2013-6376 CVE-2013-6432 CVE-2014-0038 Affected Products: openSUSE 13.1 ______________________________________________________________________________ But I don't have it clear if this issue is solved here :-? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlLz9N0ACgkQja8UbcUWM1xI0gD+IJMIYEABlm1W56lW16bUCiR/ UtglkL8PG4fG7jRc5r8A/iQeuPAV6u79K3IdivNLZfJh250fYOBQeDVAmR892uf0 =YEnj -----END PGP SIGNATURE-----

On 2013-12-08 05:18, Cristian Rodríguez wrote:

- Use a 64 bit version, this is the recommended solution.

On a 32 bit machine? -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

On Sun, Dec 8, 2013 at 8:32 AM, 黄顺 wrote:

On Sunday, December 08, 2013 02:29:01 PM Carlos E. R. wrote:

...

On 2013-12-08 05:18, Cristian Rodríguez wrote:

...

- Use a 64 bit version, this is the recommended solution.

On a 32 bit machine? cannot shutdown? Isn't there choice to suspend to disk?

systemctl hibernate Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused Remember, this is a more or less vanilla 13.1 32-bit install, so I'm amazed that no one else is saying "me too". And the bugzilla that I found may not even be related issue. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 08/12/13 12:48, Greg Freemyer escribió:

systemctl hibernate Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused

That is exactly the same problem.. you will probably find many other anomalies with systemd as it is uses the epoll API extensively. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/12/13 15:18, Cristian Rodríguez wrote:

El 07/12/13 23:54, Greg Freemyer escribi�:

...

hmm... How many users are getting hit by this?

No idea.

...

Is it in bugzilla?

No idea.

...

That's not as hard as it sounds, but is there a better way?

- Wait for a kernel update (see the thread in opensuse-kernel)

- Use a 64 bit version, this is the recommended solution.

- do not use suspend/resume.

In addition to my earlier message, I am using 64-bit system and I *never* suspend/whatever my system - it's either ON or it's OFF. And with the latest updates performed yesterday evening (my time) the Lenovo will NOT shutdown normally. BC -- Using openSUSE 13.1, KDE 4.11.3 & kernel 3.12.4-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Feb 7, 2014 at 9:33 AM, ianseeks wrote:

I get something similar on 64bit opensuse 13.1 (and previous versions) where the shutdown proceeds, the screen switches from graphical (ctrl-alt f7) to a CLI session on ctrl-alt-F1 which is at the login prompt and it stops there. I just login and type in shutdown or init 0 and it eventually shuts down and switches off. Sometimes i've done a "zypper up" during the sessions and sometimes i've not updated anything so i've never noticed a pattern of when it does it.

I see something like this on mine. I've got a dual monitor config (Nvidia GTX 660 Ti). When I reboot/shutdown, the right monitor switches off, the left monitor switches to text mode and shows a huge, bright-red block that covers most of the screen. If I wait long enough, it will eventually shut down - long enough being upwards of 5 minutes. Hardware is an AMD 965 (64 bit, 3.6GHz Quad core) and a Samsung 840 Pro 256GB SSD.... so it should be fast... not 5 minutes. I've never poked at it though to find out what's hanging it up as I rarely reboot. C -- openSUSE 13.1 x86_64, KDE 4.12 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Feb 7, 2014 at 11:20 AM, Johannes Weberhofer wrote:

...

I see something like this on mine.

I've got a dual monitor config (Nvidia GTX 660 Ti). When I reboot/shutdown, the right monitor switches off, the left monitor switches to text mode and shows a huge, bright-red block that covers most of the screen. If I wait long enough, it will eventually shut down - long enough being upwards of 5 minutes.

Hardware is an AMD 965 (64 bit, 3.6GHz Quad core) and a Samsung 840 Pro 256GB SSD.... so it should be fast... not 5 minutes. I've never poked at it though to find out what's hanging it up as I rarely reboot.

Does pressing <ESC> show something interesting?

Nope, at least not once the bright red screen shows up. If I have time I'll poke at it this weekend... maybe a log file will help the general problem being discussed here? That is of course assuming the issue/annoyance I'm seeing is the same as Greg's... I'm not sure it is though once I re-read the thread here. C. -- openSUSE 13.1 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/12/13 05:17, Cristian Rodríguez wrote:

El 07/12/13 15:01, Greg Freemyer escribi�:

...

On Sat, Dec 7, 2013 at 11:56 AM, Cristian Rodr�guez wrote:

...

El 07/12/13 12:09, Greg Freemyer escribi�:

...

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

Is this a 32 bit version right ? Correct

it is a known bug that affects 32 bit systems only,

WRONG! 'Do not pass GO do not collect $200'. My Lenovo 64-bit suffers from the same thing: the laptop will NOT shutdown. Only way to shut it down is to press the ON switch for several seconds. This didn't have until an update which I did 2 days ago (while travelling interstate).

no.. it is not a bug in systemd, so resist the urge of shooting the messenger :-P.. it is a kernel regression. fixed in 3.11.8.

BC -- Using openSUSE 13.1, KDE 4.11.3 & kernel 3.12.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/12/13 17:30, Cristian Rodríguez wrote:

El 12/12/13 03:10, Basil Chupin escribió:

...

On 08/12/13 05:17, Cristian Rodríguez wrote:

...

El 07/12/13 15:01, Greg Freemyer escribi�:

...

On Sat, Dec 7, 2013 at 11:56 AM, Cristian Rodr�guez wrote:

...

El 07/12/13 12:09, Greg Freemyer escribi�:

...

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

Is this a 32 bit version right ? Correct

it is a known bug that affects 32 bit systems only,

WRONG!

Basil, Stop hijacking threads with problems that have nothing to do with..

...

This didn't have until an update which I did 2 days ago (while travelling interstate).

can't be, there are no kernel updates for 13.1 in the repos neither changes in systemd shutdown.

describe your problem clearly in bugzilla instead.

The Subject Heading reads, "can't shutdown my 13.1 system" and Greg is referring to his laptop which is being affected - so my response was on topic and not hijacking anything. You were banging on about the 32-bit system being affected but not a 64-bit system to which I responded that my Lenovo running a 64-bit oS 13.1 would not shutdown - and this happened after some updates were done while I was travelling interstate. I don't recall mentioning anything about kernel updates, just simply updates. However, this morning there were more updates in the form of some ~55 patches and this appears to cure the problem because the Lenovo now shuts down correctly. BC -- Using openSUSE 13.1, KDE 4.11.3 & kernel 3.12.4-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2013-12-13 at 17:04 -0300, Cristian Rodríguez wrote:

Apparently, kernel 3.11 is going to be phased out from 13.1 and switched to 3.12.x instead due to resource constrains. (3.11 EOL'ed already)

Do you know when? I have 32 bit machines I wish to upgrade to 13.1, and I can't because of this issue. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlKsgKEACgkQtTMYHG2NR9XFaQCfboN2HWqKwXG+sjcG4gqYrrJo apMAn3wNx+UZRMj8tQ5utWV4LTIdTTyn =KYhr -----END PGP SIGNATURE-----

On 2013-12-14 21:51, Greg Freemyer wrote:

On Sat, Dec 14, 2013 at 11:00 AM, Carlos E. R. <> wrote:

...

Do you know when? I have 32 bit machines I wish to upgrade to 13.1, and I can't because of this issue.

I don't think there is anything at all definitive, but here's the thread:

http://markmail.org/message/kzvfaj4vr65eym4j

Yes, I had read some posts of it, but it is so long that I did not find an answer. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)