On 2017-06-01, Adam Borowski wrote: >> In the last few days, pm-powersave is being called roughly once per >> second, which is logging to /var/log/pm-powersave.log until there's no >> disk space left. I don't think I have any custom configuration of >> pm-utils or related software. > > I'm trying to reproduce this on every x86 piece of hardware I have, without > success. Could you say more especially about "in the last few days"? What > did change? It's a little hard to know, because there are no timestamps in the pm-powersave.log file, it just gradually grew without me noticing until it was multiple gigabytes... so I have no real idea how long it's been an issue. > I assume you don't reboot daily, so the real reason is time > shifted. Correct. > Still, because of the freeze, changes don't happen often, so the > packaged I'd suspect are systemd and the kernel, with a strong hunch about > the former. If the bug is readily reproducible for you, would you care to > downgrade either systemd or the kernel and check then? Will give some systematic downgrading a try... >> Init: systemd (via /run/systemd/system) > > This may be the issue: systemd has a NIH implementation of pm stuff, which > might be fighting with that of pm-utils. > > Generally, on systemd machines, keeping pm-utils is kind of pointless, while > it is vital on any x86 box that gets suspended and uses other inits. Ah, that would explain things a bit if two things are fighting over resume events somehow... > As you filed this bug just days before the total freeze, there's rather > little time to find out what might be wrong -- especially that no one else > seems to have this problem. Understood; will try to find out more... live well, vagrant
Attachment:
signature.asc
Description: PGP signature