From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 8 Oct 2002 12:17:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 8 Oct 2002 12:17:48 -0400 Received: from e32.co.us.ibm.com ([32.97.110.130]:43138 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id ; Tue, 8 Oct 2002 12:17:47 -0400 Message-ID: <3DA30668.1010807@us.ibm.com> Date: Tue, 08 Oct 2002 09:23:04 -0700 From: Dave Hansen User-Agent: Mozilla/5.0 (compatible; MSIE5.5; Windows 98; X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ingo Molnar CC: Andrew Morton , lkml , "linux-mm@kvack.org" Subject: Re: 2.5.40-mm2 References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ingo Molnar wrote: > On Sun, 6 Oct 2002, Dave Hansen wrote: > >>cc'ing Ingo, because I think this might be related to the timer bh >>removal. > > could you try the attached patch against 2.5.41, does it help? It fixes > the bugs found so far plus makes del_timer_sync() a bit more robust by > re-checking timer pending-ness before exiting. There is one type of code > that might have relied on this kind of behavior of the old timer code. Well, I gave it a shot. I haven't seen any more of the __run_timers oopses yet, but I haven't been able to stay up for very long before it freezes, so time will tell. But, for now, I'm pretty sure that it is quite a bit better. -- Dave Hansen haveblue@us.ibm.com