Re: Not power off after shutdown in Jessie
On 06/10/2018 06:33 PM, The Wanderer wrote: On 2018-05-31 at 02:01, Miroslav Skoric wrote: After upgrading from Wheezy LTS to Jessie, one of my machines having 512 MB RAM, does not power off when it reached target shutdown. It seems some old issue/bug with systemd or else. In fact, everything closes down properly except it does not unmount the following: /run/user/1000 /run/user/106 /var /home /tmp How can you tell that these are still mounted? Because the machine kept reporting 'failed unmount' for these above, something like this: umounting /run/user/1000 failed to umount /run/user/1000 umounting /run/user/106 failed to umount /run/user/106 ... ... (Sorry I forgot the exact syntax of how the machine reported that, because it was last week. But it finally started to poweroff properly after I removed all clamav -related stuff from that machine. In fact, I noticed that all those clam* things still belonged to Wheezy, being in versions ...deb7u1 or so, after I upgraded Wheezy LTS to Jessie.) Could it be a kernel/BIOS incompatibility? (I.e., probably something to do with ACPI tables.) I don't know ... I got that machine some 6-7 years ago, as a second-hand then. So it is probably some 10+ year old at least. The only fix I've found for that problem, aside from reverting to the older kernel, is to upgrade the BIOS on the affected computers. Some of them had BIOS versions dating back to at least 2012, if not 2009; bringing them up to the manufacturer's latest BIOS release for that model got the new environments to shut down and reboot normally. I see. But as I said, removing some packages returned the box to normal shutdown. Furthermore, what wondered me even more is that another *older* box I have here (dated back to the beginning of the previous decade!), that runs with only 224MB RAM on Celeron 400MHz, did not experience failure in poweroff at all.
Re: Not power off after shutdown in Jessie
On 2018-05-31 at 02:01, Miroslav Skoric wrote: > After upgrading from Wheezy LTS to Jessie, one of my machines having 512 > MB RAM, does not power off when it reached target shutdown. It seems > some old issue/bug with systemd or else. In fact, everything closes down > properly except it does not unmount the following: > > /run/user/1000 > /run/user/106 > /var > /home > /tmp How can you tell that these are still mounted? > ... and hangs there forever. That did not happen in Wheezy. Any idea? Could it be a kernel/BIOS incompatibility? (I.e., probably something to do with ACPI tables.) I've recently needed to experiment at work with some new versions of what is basically a LiveCD-type environment; along with various other updates, those new versions have an updated kernel, and I think that's the relevant factor. On some computer models, the new versions of that environment failed to shut down or reboot all the way; they'd get as far (into the shutdown messages) as the point where the screen should go blank for the reboot or shutdown, and then hang there forever. Powering off resulted in a clean boot next time, as if the shutdown had succeeded. On other computer models, everything worked fine. The only fix I've found for that problem, aside from reverting to the older kernel, is to upgrade the BIOS on the affected computers. Some of them had BIOS versions dating back to at least 2012, if not 2009; bringing them up to the manufacturer's latest BIOS release for that model got the new environments to shut down and reboot normally. My best guess is that the newer kernel (and/or some drivers included therein) is relying on updated expectations about what the BIOS will do in response to a given input, and the BIOS on the affected machines doesn't actually satisfy those expectations. I don't know whether what you're seeing is the same behavior, but it could be worth checking on. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Not power off after shutdown in Jessie
On 06/04/2018 03:12 PM, Curt wrote: I'm really too ignorant to be answering questions and should be asking some. However I can't think of any. Except: any clues in the logs? Look here: /usr/share/doc/systemd/README.Debian.gz under Debugging boot/shutdown problems which explains how to create a root debug shell on VT 9 available quite late in the shutdown process; or, failing or in lieu of that, generating a shutdown-log.txt file instead. Good luck. Thank you for ideas. Well I am not an expert into debugging shutdown processes at all. However, systemctl in VT9 returned some "failed" units for boot (as well as many still "active" ones for shutdown), among which I saw "failed" clamd or some else service related to clamav. And since I really did not need any clam* things on that particular machine any more, I went to Synaptic manager and purged them all. (Btw, I noticed that all those clam* things still belonged to Wheezy ... like deb7u1 or so, dunno whether they should had been automatically upgraded to some deb8u* during the distro upgrade Wheezy LTS >> Jessie.) Whatever, the first next shutdown was successful, as well as the subsequent dozen ones, as well as the reboot sessions. Will keep an eye on that ... tnx for now.
Re: Not power off after shutdown in Jessie
Miroslav Skoric wrote: > Any idea? yes this systemd thingie is cursed by design, so I have it pretty stable in few devices where inevitable (phone, tablet etc) But everything else I install sysvinit-core and this makes it explicitly the init process (or add init=/lib/sysvinit/init to grub default kernel command line and recreate initrd) systemd is (still) not in position to handle stuff properly. regards
Re: Not power off after shutdown in Jessie
On 05/31/2018 08:01 AM, Miroslav Skoric wrote: After upgrading from Wheezy LTS to Jessie, one of my machines having 512 MB RAM, does not power off when it reached target shutdown. It seems some old issue/bug with systemd or else. In fact, everything closes down properly except it does not unmount the following: /run/user/1000 /run/user/106 /var /home /tmp ... and hangs there forever. That did not happen in Wheezy. Any idea? Btw, after waiting for at least 3-4 hours for poweroff, I went to tty1 console to try ctrl-alt-del there (because that did not work in tty7 where the system left hanging). It did not help much there too, however I noticed two new lines there: [74199.357014] systemd[1]: var.mount failed to run 'umount' task: Cannot allocate memory [74199.380035] systemd[1]: home.mount failed to run 'umount' task: Cannot allocate memory Any idea?
Re: Not power off after shutdown in Jessie
On 2018-06-03, Miroslav Skoric wrote: > > I did so, and noticed just some few Gnome -related things to be active > for the user 106 - myself? (although I logged out from the Mate desktop > and not from Gnome), as well as a few items active for user 1000 i.e. > root (such as 'sudo su' and 'systemd-cgls'). > > Anyway, to be sure whether any of those processes were needed to run or > not, I did in parallel the same test with another slower machine running > Jessie at only 224MB RAM (also the recent upgrade from Wheezy), but > which one performs proper shutdown/poweroff. > > You bet, at both machines exactly the same processes were listed as > still running for user 106 and user 1000. However, only the better one > box having 512 MB RAM, does not power off when reached target shutdown. > > Any other thing to try? > > I'm really too ignorant to be answering questions and should be asking some. However I can't think of any. Except: any clues in the logs? Look here: /usr/share/doc/systemd/README.Debian.gz under Debugging boot/shutdown problems which explains how to create a root debug shell on VT 9 available quite late in the shutdown process; or, failing or in lieu of that, generating a shutdown-log.txt file instead. Good luck.
Re: Not power off after shutdown in Jessie
On 05/31/2018 04:18 PM, Curt wrote: On 2018-05-31, Miroslav Skoric wrote: After upgrading from Wheezy LTS to Jessie, one of my machines having 512 MB RAM, does not power off when it reached target shutdown. It seems some old issue/bug with systemd or else. In fact, everything closes down properly except it does not unmount the following: /run/user/1000 /run/user/106 /var /home /tmp ... and hangs there forever. That did not happen in Wheezy. Any idea? You could try logging out, I've read somewhere, switching to a console, logging in as root (or another user entirely) and executing 'systemd-cgls' to determine what processes are still running for the user in question (assuming for the moment your problem is related to some program in your session being "stuck.") I did so, and noticed just some few Gnome -related things to be active for the user 106 - myself? (although I logged out from the Mate desktop and not from Gnome), as well as a few items active for user 1000 i.e. root (such as 'sudo su' and 'systemd-cgls'). Anyway, to be sure whether any of those processes were needed to run or not, I did in parallel the same test with another slower machine running Jessie at only 224MB RAM (also the recent upgrade from Wheezy), but which one performs proper shutdown/poweroff. You bet, at both machines exactly the same processes were listed as still running for user 106 and user 1000. However, only the better one box having 512 MB RAM, does not power off when reached target shutdown. Any other thing to try?
Re: Not power off after shutdown in Jessie
Miroslav Skoric wrote: > That did not happen in Wheezy. Any idea? it is not a bug, it is a feature :)
Re: Not power off after shutdown in Jessie
On 2018-05-31, Miroslav Skoric wrote: > After upgrading from Wheezy LTS to Jessie, one of my machines having 512 > MB RAM, does not power off when it reached target shutdown. It seems > some old issue/bug with systemd or else. In fact, everything closes down > properly except it does not unmount the following: > > /run/user/1000 > /run/user/106 > /var > /home > /tmp > > ... and hangs there forever. That did not happen in Wheezy. Any idea? > > You could try logging out, I've read somewhere, switching to a console, logging in as root (or another user entirely) and executing 'systemd-cgls' to determine what processes are still running for the user in question (assuming for the moment your problem is related to some program in your session being "stuck.")
Not power off after shutdown in Jessie
After upgrading from Wheezy LTS to Jessie, one of my machines having 512 MB RAM, does not power off when it reached target shutdown. It seems some old issue/bug with systemd or else. In fact, everything closes down properly except it does not unmount the following: /run/user/1000 /run/user/106 /var /home /tmp ... and hangs there forever. That did not happen in Wheezy. Any idea?
