Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262023AbVCLVTQ (ORCPT ); Sat, 12 Mar 2005 16:19:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261827AbVCLVTP (ORCPT ); Sat, 12 Mar 2005 16:19:15 -0500 Received: from mustang.oldcity.dca.net ([216.158.38.3]:32199 "HELO mustang.oldcity.dca.net") by vger.kernel.org with SMTP id S262023AbVCLVSe (ORCPT ); Sat, 12 Mar 2005 16:18:34 -0500 Subject: Re: spin_lock error in arch/i386/kernel/time.c on APM resume From: Lee Revell To: george@mvista.com Cc: Andrew Morton , "J. Bruce Fields" , Ingo Molnar , "linux-kernel@vger.kernel.org" In-Reply-To: <4233111A.5070807@mvista.com> References: <20050312131143.GA31038@fieldses.org> <4233111A.5070807@mvista.com> Content-Type: text/plain Date: Sat, 12 Mar 2005 16:18:31 -0500 Message-Id: <1110662312.7723.16.camel@mindpipe> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 783 Lines: 24 On Sat, 2005-03-12 at 07:56 -0800, George Anzinger wrote: > J. Bruce Fields wrote: > > On APM resume this morning on my Thinkpad X31, I got a "spin_lock is > > already locked" error; see below. This doesn't happen on every resume, > > though it's happened before. The kernel is 2.6.11 plus a bunch of > > (hopefully unrelated...) NFS patches. > > > > Any ideas? > > > Yesterday's night mare, todays bug :( > Wait, so this is the same theoretical bug you discussed in the do_timer_interrupt thread? Wow, a real schroedinbug... Lee - 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/