ps -ef stack overflow fedora 20 fully updated

[Ger van Dijck]

Hi Folks,


When doing a ps -ef on a fully updated Fedora 20 OS I get the following
message:

/usr/bin/abrt-watch-log -F BUG : WARNING : at WARNING : CPU :INFO:
possoble recurcive locking detected kernel BUG at list_del corruption
list_add corruption do_IRQ :stack overflow : ear stack overflow (cur:
general protection fault enable to handle kernel double fault : RTNL :
assertion failed eek! page_mapcount(page) went nagative! madness at NETDEV
WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch
Machine Chek Exeption : Machine check events logged devide error : bounds
: coprosessor overrun : invalid TSS : segment not present : invalid upcode
: aligment check : stack segment : fpu exeption : simd exeption : iret
exeption : /var/log/messages -- /usr/bin/abrt-dump-oops -xtD

You want more ??

Suddenly I cannot scan (HP4620) anymore  and the Dell Inspiron Laptop is
behaving unpredictabel

I have not been encountered with a slach overflow for years

I cannot imagine that nobody has not seen this error doing ps -ef

Any help or commend would be usefull


Greetings


Ger van Dijck.

-- 
Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/

[Ed Greshko]

On 09/30/14 20:41, Ger van Dijck wrote:
>  When doing a ps -ef on a fully updated Fedora 20 OS I get the
> following
>  message:
>
>  /usr/bin/abrt-watch-log -F BUG : WARNING : at WARNING : CPU :INFO:
>  possoble recurcive locking detected kernel BUG at list_del corruption
>  list_add corruption do_IRQ :stack overflow : ear stack overflow (cur:
>  general protection fault enable to handle kernel double fault : RTNL :
>  assertion failed eek! page_mapcount(page) went nagative! madness at NETDEV
>  WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch
>  Machine Chek Exeption : Machine check events logged devide error : bounds
>  : coprosessor overrun : invalid TSS : segment not present : invalid upcode
>  : aligment check : stack segment : fpu exeption : simd exeption : iret
>  exeption : /var/log/messages -- /usr/bin/abrt-dump-oops -xtD  
You didn't get any message.  This is part of the output of ps -ef.

The command running is "/usr/bin/abrt-watch-log -F"

The file being watched is /var/log/messages.  If any string defined by -F is detected in
that file then run /usr/bin/abrt-dump-oops -xtD .

This process is started by abrt-oops.service.   If you want, you can stop that service and
notice you won't have that output in your "ps -ef".

The problem with your scanner is unrelated.

-- 
If you can't laugh at yourself, others will gladly oblige.

[jarmo]

Fri, 03 Oct 2014 12:54:24 +0200
"Ger van Dijck" <ger.vandijck(a)dommel.be&gt; kirjoitti:

>  Hi Folks,
>  
>  
>  When doing a ps -ef on a fully updated Fedora 20 OS I get the
>  following message:
>  
>  /usr/bin/abrt-watch-log -F BUG : WARNING : at WARNING : CPU :INFO: 
I have fully updated F20 and "ps -ef" command works fine..

Jarmo

[Jon Ingason]

Den 2014-09-30 14:41, Ger van Dijck skrev:
>  Hi Folks,
>  
>  
>  When doing a ps -ef on a fully updated Fedora 20 OS I get the following
>  message:
>  
>  /usr/bin/abrt-watch-log -F BUG : WARNING : at WARNING : CPU :INFO:
>  possoble recurcive locking detected kernel BUG at list_del corruption
>  list_add corruption do_IRQ :stack overflow : ear stack overflow (cur:
>  general protection fault enable to handle kernel double fault : RTNL :
>  assertion failed eek! page_mapcount(page) went nagative! madness at NETDEV
>  WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch
>  Machine Chek Exeption : Machine check events logged devide error : bounds
>  : coprosessor overrun : invalid TSS : segment not present : invalid upcode
>  : aligment check : stack segment : fpu exeption : simd exeption : iret
>  exeption : /var/log/messages -- /usr/bin/abrt-dump-oops -xtD
>  
>  You want more ?? 
Do man abrt-watch-log and it explans what is going on.

>  
>  Suddenly I cannot scan (HP4620) anymore  and the Dell Inspiron Laptop is
>  behaving unpredictabel
>  
>  I have not been encountered with a slach overflow for years
>  
>  I cannot imagine that nobody has not seen this error doing ps -ef
>  
>  Any help or commend would be usefull
>  
>  
>  Greetings
>  
>  
>  Ger van Dijck.
>   

-- Regards

Jon Ingason