Re: [Fwd: [pre PATCH] freezes]

From: Roger Larsson (
Date: Wed Feb 28 2001 - 08:17:12 EST

On the numlock issue...

There was a week when I got no freezes, that was after 2.4.2-pre1
so I looked around and tried to find the reason (2.4.1 freezed)
The only thing I could find was this...

But now they have reappeared!!!

I have started to use xosview on top to get a feel for what is happening.
The situation after freeze has been similar (2 captures with xosview this far
one with KTimeMon

_Programs running_
term (konsole) running
(started in quickly one after another)

Load above 1 (latest CPU0 has been different 100% and 9%)
MEM 91M (both times!)
SWAP 0 (could be a rounding problem in xosview)
INTS 0,4 (one time 15 the other time 12)

The MEM & SWAP is interesting.
I have 96M RAM. Lots and lots of swap space
"Adding Swap: 530136k swap-space (priority -1)
 Adding Swap: 133048k swap-space (priority -2)"
Cache was about as big as USED+SHARE, BUFF only
a few precent about the size of FREE.

When the freeze happened MEM was rising, I wonder if
I got the freeze when hitting swap...

I retry with wider xosview...


On Wednesday 28 February 2001 13:04, Andrew Morton wrote:
> Alan, this 2.2 patch seems very sane to me.
> If we take a page fault in (say) the get_user() in write_chan()
> then handle_mm_fault() will run in state TASK_INTERRUPTIBLE. If
> a filesystem calls schedule() without setting task->state it's
> lights out. reiserfs_get_block() is one such.
> It can't hurt.
> But I don't see why this should cause numlock to
> stop working...
> -------- Original Message --------
> Subject: [pre PATCH] freezes
> Date: Thu, 15 Feb 2001 15:29:12 +0100
> From: Roger Larsson <>
> To: Linux Kernel Mailing List <>
> --------------Boundary-00=_OWYSLVSP7YK356P9A2LT
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 8bit
> Hi,
> I have had occasional freezes (complete NumLock won't work) for some time.
> I blamed HW, irq conflicts, temperature problems, ...
> But suddenly with 2.4.2-pre1 the problems disappeared!
> Since 2.4.2-pre1 was rather short I took the time to try to find out what
> could be the fix.
> I found one candidate, the setting of TASK_RUNNING in handle_mm_fault.
> Since the problem had appeared on both 2.4 and 2.2.18 I started to try to
> reproduce the problem in an unpatched 2.2 - it took some time, got the
> freeze today.
> During this time I have tried to collect information of the freezes on KDE
> mailing lists - I do now have three additional reports (one running 2.2.17)
> Hardware has varied.
> I have now compiled and installed this patch but since it can't be proven
> to fix the problem I submit it now.
> /RogerL

Home page:
  none currently
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed Feb 28 2001 - 21:00:16 EST