Created attachment 388574 [details] emerge --info Hello, I have crash into dmesg: dmesg --version dmesg from util-linux 2.25.2 Program received signal SIGSEGV, Segmentation fault. 0x2a005f7c in color_fdisable (f=0xb6fc29b8 <_IO_2_1_stdout_>) at /var/tmp/portage/sys-apps/util-linux-2.25.2/work/util-linux-2.25.2/lib/colors.c:695 Same for the stable version. No crash after dmesg --clean Kernel 3.17.2 from gentoo sources + odroid u3 hardware. Into syslog-ng: Nov 5 00:53:32 ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ kernel: [ 0.000000] Booting Linux on physical CPU 0xa00 See my sys info attached.
save the current buffer: dmesg --color=never -r > log then see if it still crashes: dmesg --color=always -F log if so, attach that log file here
dmesg: these options aremutually exclusive: --color --raw dmesg --color=never -> crash dmesg -r > log work, see the attached file dmesg --color=always -F log -> crash
Created attachment 388596 [details] log
dmesg --color=always -F log -> don't crash on my x86, only on my odroid-u3-1 If needed I can open you a private access.
Confirmed on Raspberry Pi B+ model, ARMv6, 512RAM.
Created attachment 391578 [details] emerge --info
I cannot reproduce this :/
Looks like this bug is only reproducible on ARM. Confirming it on Raspberry Pi too.