Hi all,

I've installed an Oracle11 in Oracle Linux Enterprise (3.10.0-123.el7.x86_64) and it's works fine.

After an OS update, I've had problems in the server reboot and I needed to try differents possibilities (start menu).

When I loged in I found this problem :
...................................................................................................
root 977 0.0 0.0 212056 4556 ? Ss 13:48 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
...................................................................................................


Any idea to solve this?

Thanks in advance
Regards

As I understand it, OEL is a paid for distro, so I'd ask Oracle, especially as this looks like a fundamental/deep issue.
although note it does say its 'only' a WARNING, so the system may continue to run even so.

Thanks chrism01 for your help.

Oracle Linux is a free OS...and...I think isn't a good choice because I'm having "problems" with it.

I know this is only a warning, but I'd like a "clear System" without warnings and without process wich "only use RAM"...maybe it's a "hard task"


regards

Hi,

First, I'm not familiar with this environment (Oracle who?).

Please detail "found this problem" - judging from my glass bowl this printout is from some ps output or so, which appears to simply list a running abrt-watch-log process with various completely unrelated/different filter expressions (-F??) properly specified.
So, I'd say that "possible recursive locking detected" is just *one* out of many different error magics that that analyzer process appears to *usually* be shooting for, and, in closing, I'd hazard a strong guess that there's nothing actually wrong here (without actually knowing this environment, mind you!).

HTH!

Actually I did wonder if its just listing all the possible error codes and not really a problem as such, but I don't know this particular tool I'm afraid, so I was just shooting for safety.

KernelDev0815 and chrism01, thank you very much for your help.

I'm still looking for more details...

In /var/log/messages I found this :
"gnome-session: (gnome-settings-daemon:10896): updates-plugin-WARNING **: failed to get updates: There are unfinished transactions remaining. Please run yum-complete-transaction as root."

could be relation?
I'm going to try this yum command