You are not logged in.

Pages: 1

#1 2018-04-23 11:20:01

Kamikadze
Member
From: London
Registered: 2018-04-22
Posts: 16

Systemd: Failed to add rule for system call (more funcs)()

Here is a log from dmesg:

[   11.931675] systemd[193]: Failed to add rule for system call tuxcall() / 184, ignoring: Numerical argument out of domain
[   11.932012] systemd[193]: Failed to add rule for system call security() / 185, ignoring: Numerical argument out of domain
[   11.932126] systemd[193]: Failed to add rule for system call s390_runtime_instr() / -10196, ignoring: Numerical argument out of domain
[   11.932260] systemd[193]: Failed to add rule for system call rtas() / -10187, ignoring: Numerical argument out of domain
[   11.932603] systemd[193]: Failed to add rule for system call s390_pci_mmio_write() / -10198, ignoring: Numerical argument out of domain
[   11.932696] systemd[193]: Failed to add rule for system call pciconfig_write() / -10088, ignoring: Numerical argument out of domain
[   11.932956] systemd[193]: Failed to add rule for system call pciconfig_read() / -10087, ignoring: Numerical argument out of domain
[   11.933039] systemd[193]: Failed to add rule for system call s390_pci_mmio_read() / -10197, ignoring: Numerical argument out of domain
[   11.933124] systemd[193]: Failed to add rule for system call pciconfig_iobase() / -10086, ignoring: Numerical argument out of domain
[   11.933305] systemd[193]: Failed to add rule for system call spu_run() / -10189, ignoring: Numerical argument out of domain
[   11.933637] systemd[193]: Failed to add rule for system call kexec_file_load() / 320, ignoring: Numerical argument out of domain
[   11.933732] systemd[193]: Failed to add rule for system call switch_endian() / -10191, ignoring: Numerical argument out of domain
[   11.934297] systemd[193]: Failed to add rule for system call break() / -10003, ignoring: Numerical argument out of domain
[   11.934420] systemd[193]: Failed to add rule for system call uselib() / 134, ignoring: Numerical argument out of domain
[   11.934514] systemd[193]: Failed to add rule for system call profil() / -10040, ignoring: Numerical argument out of domain
[   11.934606] systemd[193]: Failed to add rule for system call vm86() / -10071, ignoring: Numerical argument out of domain
[   11.934742] systemd[193]: Failed to add rule for system call mpx() / -10030, ignoring: Numerical argument out of domain
[   11.934882] systemd[193]: Failed to add rule for system call s390_runtime_instr() / -10196, ignoring: Numerical argument out of domain
[   11.934975] systemd[193]: Failed to add rule for system call vm86old() / -10072, ignoring: Numerical argument out of domain
[   11.935087] systemd[193]: Failed to add rule for system call rtas() / -10187, ignoring: Numerical argument out of domain
[   11.935186] systemd[193]: Failed to add rule for system call lock() / -10027, ignoring: Numerical argument out of domain
[   11.935284] systemd[193]: Failed to add rule for system call prof() / -10039, ignoring: Numerical argument out of domain
[   11.935362] systemd[193]: Failed to add rule for system call _sysctl() / 156, ignoring: Numerical argument out of domain
[   11.935457] systemd[193]: Failed to add rule for system call query_module() / 178, ignoring: Numerical argument out of domain
[   11.935544] systemd[193]: Failed to add rule for system call gtty() / -10022, ignoring: Numerical argument out of domain
[   11.935668] systemd[193]: Failed to add rule for system call umount() / -10070, ignoring: Numerical argument out of domain
[   11.935772] systemd[193]: Failed to add rule for system call vserver() / 236, ignoring: Numerical argument out of domain
[   11.935849] systemd[193]: Failed to add rule for system call idle() / -10023, ignoring: Numerical argument out of domain
[   11.935953] systemd[193]: Failed to add rule for system call stty() / -10065, ignoring: Numerical argument out of domain
[   11.936058] systemd[193]: Failed to add rule for system call create_module() / 174, ignoring: Numerical argument out of domain
[   11.936158] systemd[193]: Failed to add rule for system call s390_pci_mmio_write() / -10198, ignoring: Numerical argument out of domain
[   11.936230] systemd[193]: Failed to add rule for system call ftime() / -10013, ignoring: Numerical argument out of domain
[   11.936309] systemd[193]: Failed to add rule for system call pciconfig_write() / -10088, ignoring: Numerical argument out of domain
[   11.936398] systemd[193]: Failed to add rule for system call ulimit() / -10069, ignoring: Numerical argument out of domain
[   11.936553] systemd[193]: Failed to add rule for system call bdflush() / -10002, ignoring: Numerical argument out of domain
[   11.936640] systemd[193]: Failed to add rule for system call get_kernel_syms() / 177, ignoring: Numerical argument out of domain
[   11.936816] systemd[193]: Failed to add rule for system call stime() / -10064, ignoring: Numerical argument out of domain
[   11.936897] systemd[193]: Failed to add rule for system call pciconfig_read() / -10087, ignoring: Numerical argument out of domain
[   11.936979] systemd[193]: Failed to add rule for system call s390_pci_mmio_read() / -10197, ignoring: Numerical argument out of domain
[   11.937064] systemd[193]: Failed to add rule for system call pciconfig_iobase() / -10086, ignoring: Numerical argument out of domain
[   11.937239] systemd[193]: Failed to add rule for system call spu_run() / -10189, ignoring: Numerical argument out of domain
[   11.937329] systemd[193]: Failed to add rule for system call ssetmask() / -10061, ignoring: Numerical argument out of domain
[   11.937472] systemd[193]: Failed to add rule for system call sgetmask() / -10053, ignoring: Numerical argument out of domain
[   11.937574] systemd[193]: Failed to add rule for system call switch_endian() / -10191, ignoring: Numerical argument out of domain
[   11.938026] systemd[193]: Failed to add rule for system call break() / -10003, ignoring: Numerical argument out of domain
[   12.132673] systemd[193]: Failed to add rule for system call profil() / -10040, ignoring: Numerical argument out of domain
[   12.202554] systemd[193]: Failed to add rule for system call vm86() / -10071, ignoring: Numerical argument out of domain
[   12.322444] systemd[193]: Failed to add rule for system call mpx() / -10030, ignoring: Numerical argument out of domain
[   12.475129] systemd[193]: Failed to add rule for system call s390_runtime_instr() / -10196, ignoring: Numerical argument out of domain
[   12.592965] systemd[193]: Failed to add rule for system call vm86old() / -10072, ignoring: Numerical argument out of domain
[   12.799209] systemd[193]: Failed to add rule for system call rtas() / -10187, ignoring: Numerical argument out of domain
[   12.882251] systemd[193]: Failed to add rule for system call lock() / -10027, ignoring: Numerical argument out of domain
[   13.131330] systemd[193]: Failed to add rule for system call prof() / -10039, ignoring: Numerical argument out of domain
[   13.214367] systemd[193]: Failed to add rule for system call gtty() / -10022, ignoring: Numerical argument out of domain
[   13.383630] systemd[193]: Failed to add rule for system call umount() / -10070, ignoring: Numerical argument out of domain
[   13.679228] systemd[193]: Failed to add rule for system call idle() / -10023, ignoring: Numerical argument out of domain
[   14.500489] systemd[193]: Failed to add rule for system call stty() / -10065, ignoring: Numerical argument out of domain
[   14.537037] systemd[193]: Failed to add rule for system call s390_pci_mmio_write() / -10198, ignoring: Numerical argument out of domain
[   14.591834] systemd[193]: Failed to add rule for system call ftime() / -10013, ignoring: Numerical argument out of domain
[   14.665972] systemd[193]: Failed to add rule for system call pciconfig_write() / -10088, ignoring: Numerical argument out of domain
[   14.721738] systemd[193]: Failed to add rule for system call ulimit() / -10069, ignoring: Numerical argument out of domain
[   14.721828] systemd[193]: Failed to add rule for system call bdflush() / -10002, ignoring: Numerical argument out of domain
[   14.797441] systemd[193]: Failed to add rule for system call stime() / -10064, ignoring: Numerical argument out of domain
[   14.835581] systemd[193]: Failed to add rule for system call pciconfig_read() / -10087, ignoring: Numerical argument out of domain
[   14.835651] systemd[193]: Failed to add rule for system call s390_pci_mmio_read() / -10197, ignoring: Numerical argument out of domain
[   14.835715] systemd[193]: Failed to add rule for system call pciconfig_iobase() / -10086, ignoring: Numerical argument out of domain
[   14.835792] systemd[193]: Failed to add rule for system call spu_run() / -10189, ignoring: Numerical argument out of domain
[   14.835859] systemd[193]: Failed to add rule for system call ssetmask() / -10061, ignoring: Numerical argument out of domain
[   15.030547] systemd[193]: Failed to add rule for system call sgetmask() / -10053, ignoring: Numerical argument out of domain
[   15.030621] systemd[193]: Failed to add rule for system call switch_endian() / -10191, ignoring: Numerical argument out of domain

Before that, I did a global update of the entire system.I understand this problem is correct: https://github.com/systemd/systemd/issues/8001But I compiled the source code from there and installed systemd, the problem still remains exactly!

Offline

#2 2018-04-23 15:20:26

HalosGhost
Forum Fellow
From: Twin Cities, MN
Registered: 2012-06-22
Posts: 2,097
Website

Re: Systemd: Failed to add rule for system call (more funcs)()

Reading the issue (your link is broken, by the way), it suggests that the correct issue is actually 8002.

Additionally, that issue was closed as fixed.

What is your actual problem? Does your system fail to boot? what did you do before that happened? what is the output of `uname -a`?

You need to provide more useful information so we can actually help you smile

All the best,

-HG

Code of Conduct

Offline

#3 2018-04-25 20:09:13

Kamikadze
Member
From: London
Registered: 2018-04-22
Posts: 16

Re: Systemd: Failed to add rule for system call (more funcs)()

HalosGhost wrote:

Reading the issue (your link is broken, by the way), it suggests that the correct issue is actually 8002.

Additionally, that issue was closed as fixed.

What is your actual problem? Does your system fail to boot? what did you do before that happened? what is the output of `uname -a`?

You need to provide more useful information so we can actually help you smile

All the best,

-HG

The problem with the link does not match my problem. I ran the kernel with the debug parameter and the problem appeared.
But my system crashes and so I think it's a matter of these mistakes.

1) My actual problem is that the data errors appear in dmesg.
2) I run the kernel with the debug parameter and the error data appeared.
3) Command uname -a:

Linux arch 4.16.2-2-ARCH #1 SMP PREEMPT Tue Apr 17 19:37:34 UTC 2018 x86_64 GNU/Linux

Offline

#4 2018-04-25 20:51:00

HalosGhost
Forum Fellow
From: Twin Cities, MN
Registered: 2012-06-22
Posts: 2,097
Website

Re: Systemd: Failed to add rule for system call (more funcs)()

Kamikadze wrote:

The problem with the link does not match my problem.

Yep, I know, I just wanted to let you know that the link was broken.

But my system crashes

Okay, what do you mean by that? Do you mean that it kernel panics? If so, can you post the kernel panic? If not, what do you mean?

All the best,

-HG

Code of Conduct

Offline

#5 2018-04-25 20:53:25

loqs
Member
Registered: 2014-03-06
Posts: 19,086

Re: Systemd: Failed to add rule for system call (more funcs)()

Specifying debug as a kernel boot option also enables debugging of systemd was that intended?
8001 / 8002 changed one call of  seccomp_syscall_resolve_num_arch to use SCMP_ARCH_NATIVE there is still https://github.com/systemd/systemd/blob … il.c#L1414
The journal should indicate the rule and architecture it failed on if it is that call site please check the journal for such messages.
Edit:
Does the system crash without the use of the debug boot option?  If you pass debug systemd.log_level=info does that restrict systemd logging to the info level?

Last edited by loqs (2018-04-25 20:57:08)

Offline

#6 2018-04-26 21:11:00

Kamikadze
Member
From: London
Registered: 2018-04-22
Posts: 16

Re: Systemd: Failed to add rule for system call (more funcs)()

loqs wrote:

Specifying debug as a kernel boot option also enables debugging of systemd was that intended?
8001 / 8002 changed one call of  seccomp_syscall_resolve_num_arch to use SCMP_ARCH_NATIVE there is still https://github.com/systemd/systemd/blob … il.c#L1414
The journal should indicate the rule and architecture it failed on if it is that call site please check the journal for such messages.
Edit:
Does the system crash without the use of the debug boot option?  If you pass debug systemd.log_level=info does that restrict systemd logging to the info level?

No, the system doesn't crash, but it's acting weird.
Yes, this kernel option restricts logging.

Offline

#7 2018-04-26 21:49:36

loqs
Member
Registered: 2014-03-06
Posts: 19,086

Re: Systemd: Failed to add rule for system call (more funcs)()

Please provide more details than "it's acting weird"  If you want to pursue the systemd debug output you would need to do that with the upstream developers.
If that output is no longer appearing but the issue remains with the amended boot options then it would seem unrelated.
From https://bbs.archlinux.org/viewtopic.php?id=236546 you may have filesystem corruption which you could check for.  Without more specific symptoms I would just be speculating.

Offline

Pages: 1

Board footer

Powered by FluxBB