On 12/1/18 12:37 AM, Ranjan Maitra wrote:
The F28 systemd is fine, and even the F29 is so if you do not use EFI boot. It
is the F29 systemd that has problems. Today, I had a different problem: my
system slowed down to a crawl for at least an hour. I think that the disk
decided to get
The F28 systemd is fine, and even the F29 is so if you do not use EFI boot. It
is the F29 systemd that has problems. Today, I had a different problem: my
system slowed down to a crawl for at least an hour. I think that the disk
decided to get checked in the background, but that is a guess. I
I saw the same thing when upgrading from F27 to F28. "systemctl hibernate"
just prints the "Failed to hibernate system via logind" error, and
"pm-hibernate" (still around from F22 pm-utils) starts the shutdown and
then hangs.
In my case at least, it appears to be a kernel bug. The upgrade also
On 11/5/18 8:18 PM, Ranjan Maitra wrote:
On Sun, 4 Nov 2018 22:53:46 -0800 Samuel Sieb wrote:
Try running "sudo setenforce off" and then try "systemctl hibernate".
See if that works.
I suspect that you meant
sudo sentenforce 0
Oops, I should have checked the man page before posting.
On Sun, 4 Nov 2018 22:53:46 -0800 Samuel Sieb wrote:
> On 11/4/18 7:09 PM, Ranjan Maitra wrote:
> > On Sun, 4 Nov 2018 18:46:28 -0800 Samuel Sieb wrote:
> >> On 11/4/18 5:21 PM, Ranjan Maitra wrote:
> >>> Nov 04 19:12:41 machine.name kernel: audit: type=1400
> >>> audit(1541380361.892:226):
On 11/5/18 2:53 PM, Samuel Sieb wrote:
> The numbers don't match, but I just realized why. The inode numbers on a
> tmpfs are
> temporary. I would need to see the log line and the inode numbers from the
> same boot.
> I'm now wondering if it's an selinux issue. Try running "sudo setenforce
On 11/4/18 7:09 PM, Ranjan Maitra wrote:
On Sun, 4 Nov 2018 18:46:28 -0800 Samuel Sieb wrote:
On 11/4/18 5:21 PM, Ranjan Maitra wrote:
Nov 04 19:12:41 machine.name kernel: audit: type=1400 audit(1541380361.892:226): avc: denied { read } for
pid=805 comm="systemd-logind" name="nvme0n1p1"
On Sun, 4 Nov 2018 18:46:28 -0800 Samuel Sieb wrote:
> On 11/4/18 5:21 PM, Ranjan Maitra wrote:
> > Nov 04 19:12:41 machine.name systemd-logind[805]: Enough swap for
> > hibernation, Active(anon)=234032 kB, size=20967420 kB, used=0 kB,
> > threshold=98%
>
> Your swap is fine.
>
> > Nov 04
On 11/4/18 5:21 PM, Ranjan Maitra wrote:
Nov 04 19:12:41 machine.name systemd-logind[805]: Enough swap for hibernation,
Active(anon)=234032 kB, size=20967420 kB, used=0 kB, threshold=98%
Your swap is fine.
Nov 04 19:12:41 machine.name audit[805]: AVC avc: denied { read } for pid=805
Hi Sam,
Thanks very much again!
On Sun, 4 Nov 2018 16:52:13 -0800 Samuel Sieb wrote:
> On 11/4/18 3:08 PM, Ranjan Maitra wrote:
> > On Sun, 4 Nov 2018 13:25:47 -0800 Samuel Sieb wrote:
> >> These definitely seem relevant. You said it's an EFI system. Is
> >> /boot/efi mounted correctly?
> >
On 11/4/18 3:08 PM, Ranjan Maitra wrote:
On Sun, 4 Nov 2018 13:25:47 -0800 Samuel Sieb wrote:
These definitely seem relevant. You said it's an EFI system. Is
/boot/efi mounted correctly?
Thanks! I would guess so, given that it worked as expected with F28 (systemd
238-9).
df -h
On Sun, 4 Nov 2018 13:25:47 -0800 Samuel Sieb wrote:
> On 11/4/18 5:25 AM, Ranjan Maitra wrote:
> > On Sat, 3 Nov 2018 22:34:00 -0700 Samuel Sieb wrote:
> >
> >> On 11/3/18 9:48 PM, Ranjan Maitra wrote:
> >>> On Sat, 3 Nov 2018 21:39:41 -0700 Samuel Sieb wrote:
> That is a likely cause.
On 11/4/18 5:25 AM, Ranjan Maitra wrote:
On Sat, 3 Nov 2018 22:34:00 -0700 Samuel Sieb wrote:
On 11/3/18 9:48 PM, Ranjan Maitra wrote:
On Sat, 3 Nov 2018 21:39:41 -0700 Samuel Sieb wrote:
That is a likely cause. Are there any other lines from logind in the
journal? What is in
On Sat, 3 Nov 2018 22:34:00 -0700 Samuel Sieb wrote:
> On 11/3/18 9:48 PM, Ranjan Maitra wrote:
> > On Sat, 3 Nov 2018 21:39:41 -0700 Samuel Sieb wrote:
> >> That is a likely cause. Are there any other lines from logind in the
> >> journal? What is in /proc/cmdline?
> >
> > I don't know hoe
On 11/3/18 9:48 PM, Ranjan Maitra wrote:
On Sat, 3 Nov 2018 21:39:41 -0700 Samuel Sieb wrote:
That is a likely cause. Are there any other lines from logind in the
journal? What is in /proc/cmdline?
I don't know hoe to look in the journal. With regard to /proc/cmdline:
In one terminal
On Sat, 3 Nov 2018 21:39:41 -0700 Samuel Sieb wrote:
> On 11/3/18 6:38 PM, Ranjan Maitra wrote:
> > On Sat, 3 Nov 2018 17:05:38 -0700 Samuel Sieb wrote:
> >> It appears to be a systemd bug:
> >> https://github.com/systemd/systemd/issues/10613
> >>
> >> Try running "pm-hibernate". For some
On Sun, 04 Nov 2018 14:36:53 +1030 Tim via users
wrote:
> Allegedly, on or about 3 November 2018, Ranjan Maitra sent:
> > So, I wanted to mention that the following is what I have on my
> > /etc/default/grub
> >
> > GRUB_TIMEOUT=5
> > GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g'
On 11/3/18 6:38 PM, Ranjan Maitra wrote:
On Sat, 3 Nov 2018 17:05:38 -0700 Samuel Sieb wrote:
It appears to be a systemd bug:
https://github.com/systemd/systemd/issues/10613
Try running "pm-hibernate". For some reason, I don't see that program
on this laptop and I don't know where it came
Allegedly, on or about 3 November 2018, Ranjan Maitra sent:
> So, I wanted to mention that the following is what I have on my
> /etc/default/grub
>
> GRUB_TIMEOUT=5
> GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
> GRUB_DEFAULT=saved
> GRUB_DISABLE_SUBMENU=true
>
On Sat, 3 Nov 2018 17:05:38 -0700 Samuel Sieb wrote:
> On 11/3/18 7:01 AM, Ranjan Maitra wrote:
> > systemctl hibernate
> >
> > and I get:
> >
> > Failed to hibernate system via logind: Resume not configured, can't
> > hibernate
> >
> > I have never previously had to configure anything on an
On 11/4/18 8:05 AM, Samuel Sieb wrote:
> On 11/3/18 7:01 AM, Ranjan Maitra wrote:
>> systemctl hibernate
>>
>> and I get:
>>
>> Failed to hibernate system via logind: Resume not configured, can't hibernate
>>
>> I have never previously had to configure anything on an upgraded system
>> already
On 11/3/18 7:01 AM, Ranjan Maitra wrote:
systemctl hibernate
and I get:
Failed to hibernate system via logind: Resume not configured, can't hibernate
I have never previously had to configure anything on an upgraded system already
capable of hibernating (once hibernated). Has something
On Sat, 3 Nov 2018 10:43:08 -0700 stan wrote:
> On Sat, 3 Nov 2018 09:01:19 -0500
> Ranjan Maitra wrote:
>
> > I tried the following:
> >
> > systemctl hibernate
> >
> > and I get:
> >
> > Failed to hibernate system via logind: Resume not configured, can't
> > hibernate
> >
> > I have
On Sat, 3 Nov 2018 17:59:00 + Patrick O'Callaghan
wrote:
> On Sat, 2018-11-03 at 09:01 -0500, Ranjan Maitra wrote:
> > Hi,
> >
> > I tried the following:
> >
> > systemctl hibernate
> >
> > and I get:
> >
> > Failed to hibernate system via logind: Resume not configured, can't
> >
On Sat, 2018-11-03 at 09:01 -0500, Ranjan Maitra wrote:
> Hi,
>
> I tried the following:
>
> systemctl hibernate
>
> and I get:
>
> Failed to hibernate system via logind: Resume not configured, can't hibernate
>
> I have never previously had to configure anything on an upgraded system
>
On Sat, 3 Nov 2018 09:01:19 -0500
Ranjan Maitra wrote:
> I tried the following:
>
> systemctl hibernate
>
> and I get:
>
> Failed to hibernate system via logind: Resume not configured, can't
> hibernate
>
> I have never previously had to configure anything on an upgraded
> system already
Hi,
I tried the following:
systemctl hibernate
and I get:
Failed to hibernate system via logind: Resume not configured, can't hibernate
I have never previously had to configure anything on an upgraded system already
capable of hibernating (once hibernated). Has something changed? What do I
27 matches
Mail list logo
