FS#46794 - [linux-grsec] System freezing at boot time!

Attached to Project: Community Packages
Opened by Nail (nail) - Monday, 19 October 2015, 07:56 GMT
Last edited by Daniel Micay (thestinger) - Wednesday, 23 December 2015, 12:58 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Daniel Micay (thestinger)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:
System freezing at boot time with last 2 versions: linux-grsec 4.2.3.201510161817-1 and 4.2.3.201510171833-1.
Only restart button helped to reboot other version kernel.
Kernel log - no error: http://pastebin.com/YtEVKi2M
Me downgraded to previous working linux-grsec-4.2.3.201510130858-1 version.
Kernel log for that: http://pastebin.com/46weFK8p

Additional info:
Archlinux 64-bit.
DE: XFCE 4.12
DM: LightDM
/etc/fstab:
-----------------------------------------------------------------------------------------------------------
/dev/sda2 / ext4 rw,noatime,data=ordered 0 1
/dev/sda1 /boot ext2 rw,nodev,nosuid,noexec,noatime,stripe=4 0 2
/dev/sda3 /home ext4 rw,nodev,nosuid,noexec,noatime,data=ordered 0 2
tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0
-----------------------------------------------------------------------------------------------------------
Steps to reproduce:
sudo pacman -S linux-grsec
reboot
   grsec-freeze.txt (61.6 KiB)
This task depends upon

Closed by  Daniel Micay (thestinger)
Wednesday, 23 December 2015, 12:58 GMT
Reason for closing:  No response
Comment by Nail (nail) - Monday, 19 October 2015, 07:57 GMT
Topics about this bug:
https://bbs.archlinux.org/viewtopic.php?id=203973
http://www.wilderssecurity.com/threads/beware-grsecurity-kernel-is-not-booting.380789/

Do you need more additional info or logs ?
Comment by Daniel Micay (thestinger) - Monday, 19 October 2015, 20:04 GMT
Well, there's no error message in those logs so there's nothing to go from. It's probably a SIZE_OVERFLOW false positive, but there's no indication that it's the same issue as the one you've linked to.
Comment by PaX Team (paxteam) - Monday, 19 October 2015, 20:12 GMT
can you capture full dmesg from a non-working kernel? or at least the moments where i believe a size overflow report is printed.
Comment by Daniel Micay (thestinger) - Monday, 19 October 2015, 20:13 GMT
It might help to disable LightDM and just boot to the console.
Comment by Nail (nail) - Monday, 19 October 2015, 20:27 GMT
ok. i will test it now...
Comment by Nail (nail) - Monday, 19 October 2015, 20:59 GMT
PaX Team, you are right: size overflow...
Will this shot be helpfull ?
LightDM is OFF.

PS: i don't know how to enable dmesg logging for crashes and panic.
I have "Disabled clearing of boot messages": https://wiki.archlinux.org/index.php/Disable_clearing_of_boot_messages - but no dmesg logs in journal.
   1.JPG (1.2 MiB)
Comment by Nail (nail) - Monday, 19 October 2015, 21:19 GMT
If it's not difficult - can someone explain how to write dmesg logs to file before system hangs on?

it will be more easy to post bugs here.
Comment by Nail (nail) - Monday, 19 October 2015, 21:26 GMT
Another shot at second try to boot.
   IMG_0830.JPG (1.45 MiB)
Comment by PaX Team (paxteam) - Monday, 19 October 2015, 22:42 GMT
thanks for the info, let's continue this on our forum: https://forums.grsecurity.net/viewtopic.php?f=3&t=4281
Comment by Daniel Micay (thestinger) - Wednesday, 21 October 2015, 06:20 GMT
This will no longer crash with the latest packages, since the detected overflow is a soft failure for now.
Comment by Daniel Micay (thestinger) - Friday, 18 December 2015, 06:58 GMT
Is this still an issue for you?

Loading...