Greetings,

Thread title should have been 'ps-ef message' sorry about the mistake.

I have this CentOS 7 Linux system which I haven’t used in about 6 months.

I had a need to do some work with my Linux system, booted it up and decided to update it using ‘yum update’.

To no surprise yum stated that there were 811 updates that needed to be applied so I ran the entire 811 updates which went in without any issues.

I never issued the “ps -ef” cmmand before. When I ran the command this time I saw the following and I would like to know if anyone can advise me if this message needs to be addressed further and if so how to resolve it and if not to just ignore this.

Thanks.

root 777 1 0 10:06 ? 00:00: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: e
ar stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! pa
ge_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler typ
e mismatch Kernel panic - not syncing: 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

Please use code tags around your posted output. That will preserve line breaks and prevent wrapping. I’m not sure what your post says...

did you execute a reboot after that update?

Thanks all for you replies and offers to help.

What are code tags and where are they located?

Yes I did reboot the system after applying all the update...same results.

The system works fine so I'll keep using it as is.

BTW, system is now much slower after applying all these updates.

Did I also mention that CentOS is running under a Windows 7 guest in VMware Server. Doubt that this would make a difference. Thanks again

the code tags explained here: just see the links in post #2.
If it was a VM probably it is out of resources.

Thanks again for your replies.

BTW, the CentOS system running under VMware Server has enough resources to kill a horse, maybe more then is needed.

so in that case would be nice to explain what do you mean by this: "system is now much slower after applying all these updates."