On Sat, 3 Nov 2018 22:34:00 -0700 Samuel Sieb <sam...@sieb.net> wrote:
> On 11/3/18 9:48 PM, Ranjan Maitra wrote:
> > On Sat, 3 Nov 2018 21:39:41 -0700 Samuel Sieb <sam...@sieb.net> 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 window, run "sudo journalctl -fa". In another one, try
> to hibernate. See what lines get printed in the first terminal.
Nov 04 07:19:29 machine.name polkitd[800]: Registered Authentication Agent for
unix-process:2334:95259 (system bus name :1.175 [/usr/bin/pkttyagent
--notify-fd 5 --fallback], object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Nov 04 07:19:29 machine.name audit[827]: AVC avc: denied { read } for
pid=827 comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17625
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
Nov 04 07:19:29 machine.name audit[827]: SYSCALL arch=c000003e syscall=257
success=no exit=-13 a0=ffffff9c a1=7ffe3533e050 a2=80000 a3=0 items=0 ppid=1
pid=827 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
tty=(none) ses=4294967295 comm="systemd-logind"
exe="/usr/lib/systemd/systemd-logind"
subj=system_u:system_r:systemd_logind_t:s0 key=(null)
Nov 04 07:19:29 machine.name audit: PROCTITLE
proctitle="/usr/lib/systemd/systemd-logind"
Nov 04 07:19:29 machine.name systemd-logind[827]: Failed to open file system
"/boot/efi": Permission denied
Nov 04 07:19:29 machine.name polkitd[800]: Unregistered Authentication Agent
for unix-process:2334:95259 (system bus name :1.175, object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
(disconnected from bus)
Nov 04 07:19:29 machine.name kernel: audit: type=1400
audit(1541337569.994:258): avc: denied { read } for pid=827
comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17625
scontext=system_u:system_r:systemd_logind_t:s0
tcontext=system_u:object_r:nvme_device_t:s0 tclass=blk_file permissive=0
Nov 04 07:19:29 machine.name kernel: audit: type=1300
audit(1541337569.994:258): arch=c000003e syscall=257 success=no exit=-13
a0=ffffff9c a1=7ffe3533e050 a2=80000 a3=0 items=0 ppid=1 pid=827
auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
tty=(none) ses=4294967295 comm="systemd-logind"
exe="/usr/lib/systemd/systemd-logind"
subj=system_u:system_r:systemd_logind_t:s0 key=(null)
Nov 04 07:19:29 machine.name kernel: audit: type=1327
audit(1541337569.994:258): proctitle="/usr/lib/systemd/systemd-logind"
Is it time for a BZ report? However, this is probably a systemd bug upstream
given the information that I think you dug out here:
https://github.com/systemd/systemd/issues/10613
But it might help to know that Fedora like Arch also reports this problem.
I was thinking of downgrading systemd, but then I am not sure what all
components need to be downgrading, since there are many.
> > $ m /proc/cmdline
> > BOOT_IMAGE=/boot/vmlinuz-4.18.16-300.fc29.x86_64
> > root=UUID=bfae51c6-7f8c-4b0b-8b3b-af6af9ae5446 ro
> > resume=UUID=a83ac239-cc10-43a6-be54-de4ce7050605 rhgb quiet LANG=en_US.UTF-8
> >
> > and:
> >
> > This is the relevant part from sudo blkid:
> >
> > /dev/nvme0n1p4: UUID="a83ac239-cc10-43a6-be54-de4ce7050605" TYPE="swap"
> > PARTUUID="1b80fbac-938f-41f1-82bc-3e0dee5ffef1"
>
> Those look fine.
>
> You could try installing pm-utils from:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=691608
>
> See if "pm-hibernate" works.
Thanks, does this work with efi systems?
Many thanks,
Ranjan
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
