Description of problem: Using shutdown from the menus or even calling poweroff shuts all the system down (it seems it doesn't unmount some filesystems at the end), but the machine continues on. Have to power off by hand. Version-Release number of selected component (if applicable): kernel-2.6.36-0.35.rc7.git0.fc15.x86_64 How reproducible: Always Steps to Reproduce: 1. Shut down... 2. 3. Actual results: System shuts down, machine isn't powered off Expected results: Poweroff Additional info: Has happened on several notebooks (two Toshiba, a Samsung netbook). Several last kernels are affected.
Still the same. Maybe systemd gets stuck, not the kernel's fault at all?
kernel-2.6.36-1.fc15.x86_64 systemd-11-1.fc15.x86_64 Still the same. I saw a final "can't write bytes" scroll by before the system shut down.
Under /sbin "can not write bytes" appears only in plymouthd, here from plymouth-0.8.4-0.20100821.1.fc15.x86_64. It does appear then that this is really systemd's fault (it is called e.g. from /lib/systemd/system/plymouth-halt.service)... perhaps a filesystem is unmounted too soon? Changing to systemd, here systemd-11-1.fc15.x86_64
Hmm, maybe you are using "halt" instead of "poweroff"? In systemd "halt" actually does what the name suggests: it halts the machine. You need to use "poweroff" to actually poweroff.
Nope, I'm using poweroff (by hand and via System --> Shut down --> Poweroff). Strangely this happens with all my machines here, all x86_64 SMP (Toshiba notebook, Samsung netbook, and a no-name oldish dual-core AMD64 box (but that one has an idiotic motherboard which acts up and has to be reset by the big button sometimes as it doesn't shut off or start up properly, so I won't count that one in fully)). Because of the above I suspect this is more widespread...
Perhaps this is due to having /usr on a separate partition (really LVM2 logical volume)?
Now systemd-11-2.fc15.x86_64, still the same. Any way to narrow this down further?
Lately, the Plymouth splash screen stays on (it used to be replaced/overwritten with black-on-black text), the machine reacts to CapsLock and alt-F?, but that's it. I now see a "plymouthd: could not log bootup: Address already in use" on tty1 (from boot?)
Could you retry with v13? This is most likely because of the split /usr. I have added some fixes to deal with that properly.
Just saw this comment, sorry. Yes, systemd-13-1 fixes this. Thanks!
Closing then.