From: Jason Stubbs <jstubbs@work-at.co.jp>
Organization: Work@ Inc
To: Andrew Morton <akpm@osdl.org>
Subject: Re: PROBLEM: Consistent lock up on >=2.6.8
Date: Tue, 5 Oct 2004 10:53:09 +0900
User-Agent: KMail/1.7
Cc: linux-kernel@vger.kernel.org
References: <200410041611.17000.jstubbs@work-at.co.jp> <200410041931.00159.jstubbs@work-at.co.jp> <20041004120535.3c68115a.akpm@osdl.org>
In-Reply-To: <20041004120535.3c68115a.akpm@osdl.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200410051053.09587.jstubbs@work-at.co.jp>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 774
Lines: 20

On Tuesday 05 October 2004 04:05, Andrew Morton wrote:
> update_defense_level() is calling si_meminfo() from timer context.  But
> si_meminfo takes non-irq-safe locks.
>
> Move it all to keventd context.

That appears to have fixed it. I'm running my regular test and, while 
interactivity is non-existent, it hasn't locked. I'll leave it going for 
another few hours and report back to confirm.

Much gratitude. I should go out and buy a kernel book so that I may some day 
be able to repay the favour. :)

Regards,
Jason Stubbs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/