Control: forwarded -1 https://github.com/systemd/systemd/issues/2930
On 1 Apr 2016 04:43, "Frank Heckenbach" wrote:
>
> > On 28 March 2016 at 12:18, Frank Heckenbach
wrote:
> > > Felipe Sateler wrote:
> > >
> > >> BTW, systemd has been uploaded to proposed-updates[1] fixing #805133.
> > >> Could
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/2930
Bug #788303 [systemd] systemd: Hangs indefinitely on >90% of reboot attempts
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/2930'.
--
788303: http://bugs.debian.org/cgi-bin/bug
> On 28 March 2016 at 12:18, Frank Heckenbach wrote:
> > Felipe Sateler wrote:
> >
> >> BTW, systemd has been uploaded to proposed-updates[1] fixing #805133.
> >> Could you please upgrade to that version and try using the
> >> After=swap.target workaround?
> >
> > Actually, I'm not sure if it work
On 28 March 2016 at 12:18, Frank Heckenbach wrote:
> Felipe Sateler wrote:
>
>> BTW, systemd has been uploaded to proposed-updates[1] fixing #805133.
>> Could you please upgrade to that version and try using the
>> After=swap.target workaround?
>
> Actually, I'm not sure if it works. I could not r
On 15 January 2016 at 11:09, Frank Heckenbach wrote:
>> > This seems to work. However, given that this single line is now >1
>> > KB and more than 3 times as long as my work-around service, and
>> > heavily depends on the system configuration, I doubt whether it's
>> > actually less hackish. (I do
> > This seems to work. However, given that this single line is now >1
> > KB and more than 3 times as long as my work-around service, and
> > heavily depends on the system configuration, I doubt whether it's
> > actually less hackish. (I do occasionally change my swap partitions.
> > I also build
On 14 January 2016 at 14:35, Frank Heckenbach wrote:
>> Due to the other bug I linked, this may not be sufficient. Please list
>> all the swap units listed in
>>
>> % systemctl list-units '*.swap'
>>
>> You'll see that there are multiple units each of the different ways
>> you can access the under
> Due to the other bug I linked, this may not be sufficient. Please list
> all the swap units listed in
>
> % systemctl list-units '*.swap'
>
> You'll see that there are multiple units each of the different ways
> you can access the underlying partition (by uuid, did, wwm and sdX
> name).
>
> I
On 14 January 2016 at 12:29, Frank Heckenbach wrote:
>> What if instead of this service, you add an:
>>
>> After=swap.target
>>
>> To your tmp.mount ?
>
> Doesn't work. Also, systemctl still lists tmp.mount before the swap
> targets, which means (I suppose) it will be stopped after them.
>
> I tho
> What if instead of this service, you add an:
>
> After=swap.target
>
> To your tmp.mount ?
Doesn't work. Also, systemctl still lists tmp.mount before the swap
targets, which means (I suppose) it will be stopped after them.
I thought maybe swap.target is just a virtual target that depends on
t
On 14 January 2016 at 10:21, Frank Heckenbach wrote:
>
> As a work around, I've put the following in
> /etc/systemd/system/workaround-788303.service and activated it with
> systemctl enable workaround-788303
>
> This seems to work for me for now. Of course, I'd prefer a real
> bugfix. (And so shou
As a work around, I've put the following in
/etc/systemd/system/workaround-788303.service and activated it with
systemctl enable workaround-788303
This seems to work for me for now. Of course, I'd prefer a real
bugfix. (And so should the systemd author, seeing how much he hates
using the shell ...
> On 6 Jan 2016 02:45, "Frank Heckenbach" wrote:
> >
> > I did some more debugging, and found out some things:
> >
> > - In a debug shell after the failed shutdown, I did:
> >
> > systemctl status `systemctl | grep failed | grep swap | awk '{print
> $2}'`
> >
> > and found an error message lik
On 6 Jan 2016 02:45, "Frank Heckenbach" wrote:
>
> I did some more debugging, and found out some things:
>
> - In a debug shell after the failed shutdown, I did:
>
> systemctl status `systemctl | grep failed | grep swap | awk '{print
$2}'`
>
> and found an error message like this:
>
> swapof
I can confirm this behaviour on my system exactly as described.
Besides the message
swapoff: /dev/sdxx: swapoff failed: Cannot allocate memory
there are also these lines:
dev-sdxx.swap swap process exited, code=exited status=255
Unit dev-sdxx.swap entered failed state.
I also have set overcomm
I did some more debugging, and found out some things:
- In a debug shell after the failed shutdown, I did:
systemctl status `systemctl | grep failed | grep swap | awk '{print $2}'`
and found an error message like this:
swapoff: /dev/sdxx: swapoff failed: Cannot allocate memory
- Manually
Just saying me too (also to get informed about news on this front).
It happenes both on reboot and shutdown attempts.
I can also offer to help debugging it, if there's something specific
I can do (in jessie).
Also, I'd suggest to increase the severity, since, you know, not
shutting down the syste
17 matches
Mail list logo
