Red Hat Bugzilla – Bug 1280023
ps output shows weird message about fatal kernel error
Last modified: 2017-07-25 11:55:18 EDT
Description of problem:
The "ps awux" command shows this really weird looking process below, is that intentional? If so, it's a really primitive way of alerting user to problem. How about using something like:
# logger -p user.emerg "your message here"
Which will hit all the syslogs and terminals. I agree with comment 5 in bz 976581 BTW.
Version-Release number of selected component (if applicable):
RHEL7.2 nightly dated Nov 5 2015
Linux hp60ds1 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
haven't really tried yet
Steps to Reproduce:
in "ps awux" output:
root 1562 0.0 0.0 207984 160 ? Ss Nov09 0:00 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD
it's already logged in other places such as /var/log/messages, why do this?
This "bug" can be easily fixed by back-porting abrt-dump-journal-oops from Fedora to RHEL but we need to be sure that systemd-journald is the default syslog in RHEL-7.