Re: oops in 2.4.4-ac9 (mm/slab.c)

2001-05-17 Thread Andreas Franck
Alan Cox wrote: > Its a deliberate debugging trap. > > > #if DEBUG > > if (cachep->flags & SLAB_POISON) > > if (kmem_check_poison_obj(cachep, objp)) > > BUG(); > > ^^ This one is triggered > > Someone freed memory and then

Re: oops in 2.4.4-ac9 (mm/slab.c)

2001-05-17 Thread Andreas Franck
Alan Cox wrote: Its a deliberate debugging trap. #if DEBUG if (cachep-flags SLAB_POISON) if (kmem_check_poison_obj(cachep, objp)) BUG(); ^^ This one is triggered Someone freed memory and then scribbled on it.

Re: oops in 2.4.4-ac9 (mm/slab.c)

2001-05-16 Thread Alan Cox
> when this happened, and I was not able to log in onto any console or > terminal afterwards (probably because tty_open failed very miserably > on the way?) Its a deliberate debugging trap. > #if DEBUG > if (cachep->flags & SLAB_POISON) > if

oops in 2.4.4-ac9 (mm/slab.c)

2001-05-16 Thread Andreas Franck
Hello people, I triggered an "invalid operand" oops in linux-2.4.4-ac9 today, and could trace it back to the line mm/slab.c:1244. I did nothing really special when this happened, and I was not able to log in onto any console or terminal afterwards (probably because tty_open failed very miserably

oops in 2.4.4-ac9 (mm/slab.c)

2001-05-16 Thread Andreas Franck
Hello people, I triggered an invalid operand oops in linux-2.4.4-ac9 today, and could trace it back to the line mm/slab.c:1244. I did nothing really special when this happened, and I was not able to log in onto any console or terminal afterwards (probably because tty_open failed very miserably

Re: oops in 2.4.4-ac9 (mm/slab.c)

2001-05-16 Thread Alan Cox
when this happened, and I was not able to log in onto any console or terminal afterwards (probably because tty_open failed very miserably on the way?) Its a deliberate debugging trap. #if DEBUG if (cachep-flags SLAB_POISON) if (kmem_check_poison_obj(cachep, objp))