Arch Linux

ramboman

Member

Registered: 2010-01-23

Posts: 35

Shutdown freezes and Caps Lock blinks, in X11 using linux-grsec

When I am in X11, if I do:

sudo systemctl poweroff
# or
sudo systemctl reboot

the system freezes and the Caps Lock LED blinks continuously.
The last time I tried to shutdown that way, it was at 2015-04-02 05:57:01.

Here are some more information:

# journalctl -xn 1000
...
Apr 02 05:56:27 bell systemd[936]: Startup finished in 189ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required KERNEL_USEC microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 189259 microseconds.
-- Reboot --
Apr 02 05:58:56 bell systemd-journal[189]: Runtime journal is using 8.0M (max allowed 194.3M, trying to leave 291.4M free of 1.8G available → current limit 194.3M).
Apr 02 05:58:56 bell systemd-journal[189]: Runtime journal is using 8.0M (max allowed 194.3M, trying to leave 291.4M free of 1.8G available → current limit 194.3M).
Apr 02 05:58:56 bell kernel: CPU0 microcode updated early to revision 0xa0b, date = 2010-09-28
Apr 02 05:58:56 bell kernel: Initializing cgroup subsys cpuset
Apr 02 05:58:56 bell kernel: Initializing cgroup subsys cpu
Apr 02 05:58:56 bell kernel: Initializing cgroup subsys cpuacct
Apr 02 05:58:56 bell kernel: Linux version 3.19.3.201503270049-1-grsec (builduser@strcat) (gcc version 4.9.2 20150304 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Mar 27 01:27:11 EDT 2015
Apr 02 05:58:56 bell kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-grsec root=/dev/mapper/root_crypt rw ...
Apr 02 05:58:56 bell kernel: e820: BIOS-provided physical RAM map:
...

The information printed only shows events happening before Apr 02 05:56:27 and after Apr 02 05:58:56.

The last time I have updated was 2 days ago.
This is the latest version of linux-grsec in the repository (3.19.3.201503270049-1-grsec).
When using the default kernel (3.19.2-1), I don't have that problem.
The /etc/grsec policies are left untouched. I have not done any learning mode yet.
gradm and paxd are installed.

At boot time, these messages appears:

[   37.927976] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/syslog-ng[syslog-
ng:904] uid/euid:0/0 gid/egid:0/0, parent /usr/lib/systemd/systemd[systemd:1] uid/euid:0/0
 gid/egid:0/0
[   37.930757] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/syslog-ng[syslog-
ng:904] uid/euid:0/0 gid/egid:0/0, parent /usr/lib/systemd/systemd[systemd:1] uid/euid:0/0
 gid/egid:0/0
[   37.933624] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/syslog-ng[syslog-
ng:904] uid/euid:0/0 gid/egid:0/0, parent /usr/lib/systemd/systemd[systemd:1] uid/euid:0/0
 gid/egid:0/0
[   37.936510] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/syslog-ng[syslog-
ng:904] uid/euid:0/0 gid/egid:0/0, parent /usr/lib/systemd/systemd[systemd:1] uid/euid:0/0
 gid/egid:0/0
[   37.939612] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/syslog-ng[syslog-
ng:904] uid/euid:0/0 gid/egid:0/0, parent /usr/lib/systemd/systemd[systemd:1] uid/euid:0/0
 gid/egid:0/0
[   37.944548] grsec: denied RWX mmap of <anonymous mapping> by /usr/bin/syslog-ng[syslog-
ng:904] uid/euid:0/0 gid/egid:0/0, parent /usr/lib/systemd/systemd[systemd:1] uid/euid:0/0
 gid/egid:0/0

I am still a newbie when it comes to grsecurity, so does anybody know what is happening?

Last edited by ramboman (2015-04-02 10:33:30)