PROBLEM: Total lockup with 2.3.12 (during heavy mmap activity)

Steve Dodd (dirk@loth.demon.co.uk)
Mon, 9 Aug 1999 02:21:25 +0100

Maybe someone's already aware of this, or perhaps it's fixed in 2.3.13-pre,
but I've not seen it mentioned (which doesn't mean it wasn't, of course)..
Err..

I was running tin compiled with electric fence - lots mmap()ing going on -
and got a total lockup, no response to pings, sysrq, nothing. Strangely
similar to what happened with that mmap / msync exploit someone posted
recently.

Of course, it could also be due to the horrible heat and a potentially dodgy
CPU fan, but the temperature alarms haven't gone off (yet).

What else might relevant? Kernel compiled with egcs-1.1.2, for UP. I'll
try with 2.3.13-preN and see what happens.

processor : 0
vendor_id : CyrixInstead
cpu family : 6
model : 1
model name : 6x86MX 2.5x Core/Bus Clock
stepping : 4
cpu MHz : 187.504111
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : yes
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu de tsc msr cx8 mtrr pge cmov mmx
bogomips : 187.19

-- 
If it's tourist season, why can't we shoot them?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/