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
comm="systemd-logind" name="nvme0n1p1" dev="devtmpfs" ino=17833
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 19:12:41 machine.name audit[805]: SYSCALL arch=c000003e syscall=257 success=no exit=-13
a0=ffffff9c a1=7fffb9486130 a2=80000 a3=0 items=0 ppid=1 pid=805 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 19:12:41 machine.name audit: PROCTITLE
proctitle="/usr/lib/systemd/systemd-logind"
Nov 04 19:12:41 machine.name systemd-logind[805]: Failed to open file system
"/boot/efi": Permission denied
Nov 04 19:12:41 machine.name systemd-logind[805]: Cannot read boot
configuration from ESP, assuming hibernation is not possible.
This is clearly the problem. I don't have any idea why it can't open
the file system. And from the code, my understanding is that it should
fall back to reading /proc/cmdline anyway.
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" dev="devtmpfs" ino=17833
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 19:12:41 machine.name kernel: audit: type=1300 audit(1541380361.892:226): arch=c000003e
syscall=257 success=no exit=-13 a0=ffffff9c a1=7fffb9486130 a2=80000 a3=0 items=0 ppid=1 pid=805
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)
There are a couple of these and it appears that it is the disk device
that it is trying to open. Run "ls -li /dev/nvme0n1*" to verify that.
Sorry, it works, and flawlessly. I am wondering if I should just upgrade the
source rpm and then forget about this mess of systemd.
You don't need to update it. It works fine as it is and it won't go away.
I see. I am using a text console.
Oh, that's surprising.
_______________________________________________
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
