Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 528292 - sys-apps/util-linux-2.25.2 - dmesg --version: segmentation fault in color_fdisable (f=0xb6fc29b8 <_IO_2_1_stdout_>) at .../work/util-linux-2.25.2/lib/colors.c:695
Summary: sys-apps/util-linux-2.25.2 - dmesg --version: segmentation fault in color_fdi...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Gentoo's Team for Core System packages
Depends on:
Blocks: 536906
  Show dependency tree
Reported: 2014-11-05 10:19 UTC by BRULE Herman
Modified: 2015-04-28 08:18 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---

emerge --info (emerge-info.txt,4.92 KB, text/plain)
2014-11-05 10:19 UTC, BRULE Herman
log (log,21.64 KB, text/plain)
2014-11-05 16:37 UTC, BRULE Herman
emerge --info (emerge_info,4.19 KB, text/plain)
2014-12-13 15:47 UTC, Biser Milanov

Note You need to log in before you can comment on or make changes to this bug.
Description BRULE Herman 2014-11-05 10:19:49 UTC
Created attachment 388574 [details]
emerge --info


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.
Comment 1 SpanKY gentoo-dev 2014-11-05 16:28:36 UTC
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
Comment 2 BRULE Herman 2014-11-05 16:36:42 UTC
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
Comment 3 BRULE Herman 2014-11-05 16:37:08 UTC
Created attachment 388596 [details]
Comment 4 BRULE Herman 2014-11-05 16:38:32 UTC
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.
Comment 5 Biser Milanov 2014-12-13 15:47:07 UTC
Confirmed on Raspberry Pi B+ model, ARMv6, 512RAM.
Comment 6 Biser Milanov 2014-12-13 15:47:30 UTC
Created attachment 391578 [details]
emerge --info
Comment 7 Pacho Ramos gentoo-dev 2015-01-18 13:55:03 UTC
I cannot reproduce this :/
Comment 8 Alexander Tsoy 2015-01-18 15:17:59 UTC
Looks like this bug is only reproducible on ARM. Confirming it on Raspberry Pi too.