http://bugzilla.opensuse.org/show_bug.cgi?id=903560 --- Comment #1 from grant k --- fyi, booting from OpenSUSE 13.1's LiveKDE cd, with kernel 3.11.6-4-desktop, exec of `shutdown -h now` works correctly, powering off the machine completely without subsequent restart. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grantksupport@operamail.com | |, oneukum@suse.com, | |tiwai@suse.com Flags| |needinfo?(grantksupport@ope | |ramail.com) --- Comment #2 from Takashi Iwai --- Could you give more detailed hardware information? At least, hwinfo output would be helpful. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(grantksupport@ope | |ramail.com) --- Comment #4 from Takashi Iwai --- Please attach to Bugzilla. Here is a better place to store the information more persistently. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(grantksupport@ope | |ramail.com) --- Comment #6 from Takashi Iwai --- This looks too short. Is it really an output of hwinfo, i.e. "hwinfo > hwinfo.out" ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(grantksupport@ope | |ramail.com) --- Comment #8 from Takashi Iwai --- The fact that systemctl --force makes things working sounds like some service enables the wakeup, such as WoL. Could you try to unload the Ehternet driver and poweroff? Similarly, try to reduce the hardware components as much as possible and check whether the problem is still seen. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 --- Comment #10 from Takashi Iwai --- (In reply to grant k from comment #9)

Not sure what 'other' hardware you had in mind? Wouldn't the same hardware be active when booting from the LiveKDE dvd, where shutdown works as expected?

In theory, yes, there should be same. But it's not clear whether really the all modules are same in the same way. And, above all, it's helpful to know whether really an h/w component affects or it's just other non-h/w specific kernel stuff. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 --- Comment #12 from Oliver Neukum --- Could you manually go through the wakeup sources in /proc/acpi/wakeup and disable them all? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 --- Comment #14 from grant k --- so far, disabling (modprobe -r) all of async_raid6_recov btrfs btusb button dm_bufio dm_crypt dm_log dm_mirror dm_region_hash dm_snapshot drm drm_kms_helper dummy edd fan fat firewire_core firewire_ohci forcedeth i2c_algo_bit i2c_nforce2 k8temp kvm kvm_amd libcrc32c mxm_wmi nouveau nvidia nv_tco ohci_pci pcspkr processor raid456 serio_raw sha512_generic snd snd_hda_codec snd_hda_codec_generic snd_hda_codec_realtek snd_hda_controller snd_hda_intel snd_hwdep snd_mpu401_uart snd_pcm snd_rawmidi snd_seq_device snd_timer soundcore thermal vboxdrv vboxnetadp vboxnetflt vboxpci vfat wmi xfs leaving modules async_memcpy async_pq async_tx async_xor ata_generic binfmt_misc bluetooth bnep cdrom crc_itu_t dm_mod ecb edac_core edac_mce_amd gameport md_mod ns558 parport parport_pc pata_amd ppdev raid0 raid1 raid10 raid6_pq rfkill sata_nv sg shpchp sr_mod ttm video xor in place has had no effect; system still restarts on shutdown ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 --- Comment #16 from grant k --- Downgrading to an earlier versioned kernel, from repo home:/tiwai:/kernel:/3.14/openSUSE_13.1 installing kernel-desktop-3.14.6-1.1 boots OK, uname -rm 3.14.6-1-desktop x86_64 on shutdown -h now the system STILL reboots instead re-checking when booted from LiveKDE cd, shutdown -h now DOES correctly shutdown, without reboot checking current, rpm -qa | grep -i systemd systemd-210-874.1.x86_64 systemd-devel-210-874.1.x86_64 systemd-sysvinit-210-874.1.x86_64 ... downgrading to rpm -qa | grep -i systemd systemd-208-23.3.x86_64 systemd-devel-208-23.3.x86_64 systemd-sysvinit-208-23.3.x86_64 mkinitrd failing, initially/repeatedly, to shutdown/reboot shutdown -r now Failed to open /dev/initctl: No such device or address Failed to talk to init daemon. systemctl reboot Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused systemctl reboot -f Assertion 'bus' failed at src/shared/dbus-common.c:1359, function bus_method_call_with_reply(). Aborting. Aborted doing a cold reboot, boot to uname -rm 3.17.2-1.g1afb260-desktop x86_64 now shutdown -h now shutsdown correctly, without reboot -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 --- Comment #18 from grant k --- chatting @ #systemd IRC with a dev who's taken a look here, A: You seem to be hitting some assert ... as a result, then most likely things go south A: v210 is a bad version to be on I think. A: v208 was the last one before the libsystemd-bus rewrite, and I don't think all bugs with that were ironed out yet. Q: does that suggest "my" problem is kernel, systmed, opensuse, or other? A: Assertion 'bus' failed at src/shared/dbus-common.c:1359, function bus_method_call_with_reply() A: This implies systemd problem. A: Of course, a "systemd problem" could also be construed to be a distribution problem, since this is most likely fixed in git. suggests that the problem is 'our' systemd, v210. Tho, I'm not sure that that assert wasn't an artifact of the downgrade. If it's the case that it IS systemd, then this ^^^ issue is likely in 13.2's systemd, which IIUC is shipping the same v210, sourced from Base:System I'll NOT (yet) switch this to component=(whatever contains systemd) until there's some additional comment. Bottom line -- on 13.1 here, systemd v210 causes restart-on-shutdown; v208 functions correctly. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 --- Comment #23 from grant k ---

Note that after updating systemd, also libgudev, libudev1, nss-myhostname, systemd-bash-completion, systemd-logger, systemd-sysvinit, typelib, and udev should be updated.

I can certainly test. As you can see above, no updates to any of those packages are offered by zypper, and dependency check via `zypper ve` shows nothing missing What repo(s), specifically, must be added to get the updates you're referencing?

Then, if not done by the rpm them self a mkinitrd is required.

After updates, I've had repeatedly created a new initrd with mkinitrd. Still systemd v208 shutsdown correctly, systemd v210 does not

systemctl daemon-reexec

Neither systemctl daemon-reexec nor a reboot has any effect -- as above, in all cases, systemd v208 shutsdown correctly, systemd v210 does not -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 --- Comment #30 from grant k ---

Run ... and report the result.

find /sys/class/scsi_device/*/device/ -name "manage_start_stop" -o -name "removable" -o -name "vendor" | xargs cat 1 PIONEER 1 0 ATA

Also spin down is disabled ... why this had been done?

it's an old action. afaict, the problem had been while using Mozilla apps, Opensuse systems (not sure, but this may have been back in Opensuse 11X ... not sure WHICH 'Nov 4' the logs below refer to) would get frequent, random multi-cpu 100% lockups for seconds-to-minutes. logs would show dmesg ... Nov 4 11:06:50 prov09 kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 4 11:06:50 prov09 kernel: ata4.00: failed command: FLUSH CACHE EXT Nov 4 11:06:50 prov09 kernel: ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 Nov 4 11:06:50 prov09 kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Nov 4 11:06:50 prov09 kernel: ata4.00: status: { DRDY } Nov 4 11:06:50 prov09 kernel: ata4: hard resetting link Nov 4 11:07:00 prov09 kernel: ata4: softreset failed (1st FIS failed) Nov 4 11:07:00 prov09 kernel: ata4: hard resetting link Nov 4 11:07:10 prov09 kernel: ata4: softreset failed (1st FIS failed) Nov 4 11:07:10 prov09 kernel: ata4: hard resetting link Nov 4 11:07:36 prov09 kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 4 11:07:36 prov09 kernel: ata4.00: configured for UDMA/133 Nov 4 11:07:36 prov09 kernel: ata4.00: retrying FLUSH 0xea Emask 0x4 Nov 4 11:07:36 prov09 kernel: ata4.00: device reported invalid CHS sector 0 Nov 4 11:07:36 prov09 kernel: ata4: EH complete ... This, apparently, was tracked to http://paul.sullivan.za.org/kernel-disables-sata-drive-under-heavy-load-acti... http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625922 disabling spindown / power mgmt on the drives immediately & persistently solved the problem in all cases, and, until now, has never manifested any problems or issues. Other than possible shorter drive lifes ... In any case, drive power mgmt state shouldn't inhibit proper shutdown. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=903560 grant k changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? |needinfo?(werner@suse.com) --- Comment #52 from grant k --- from upstream, @ http://lists.freedesktop.org/archives/systemd-devel/2014-December/025868.htm... "...

https://build.opensuse.org/package/view_file/Base:System/systemd/0001-add-hd...

shutdown now shuts down correctly.

I cannot make any sense out of that commit I must say. I really wish suse would discuss this with us upstream, if there's a bug to fix upstream... Lennart ..." Given the invitation, it might be worthwhile for a dev@suse to check in / discuss with upstream. -- You are receiving this mail because: You are on the CC list for the bug.