From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S275269AbTHSBBa (ORCPT ); Mon, 18 Aug 2003 21:01:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S275270AbTHSBB3 (ORCPT ); Mon, 18 Aug 2003 21:01:29 -0400 Received: from waste.org ([209.173.204.2]:32923 "EHLO waste.org") by vger.kernel.org with ESMTP id S275269AbTHSBB2 (ORCPT ); Mon, 18 Aug 2003 21:01:28 -0400 Date: Mon, 18 Aug 2003 20:01:19 -0500 From: Matt Mackall To: Dave Jones , "Randy.Dunlap" , akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: Debug: sleeping function called from invalid context Message-ID: <20030819010119.GF16387@waste.org> References: <20030815101856.3eb1e15a.rddunlap@osdl.org> <20030815173246.GB9681@redhat.com> <20030815123053.2f81ec0a.rddunlap@osdl.org> <20030816070652.GG325@waste.org> <20030818140729.2e3b02f2.rddunlap@osdl.org> <20030819001316.GF22433@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030819001316.GF22433@redhat.com> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 19, 2003 at 01:13:16AM +0100, Dave Jones wrote: > On Mon, Aug 18, 2003 at 02:07:29PM -0700, Randy.Dunlap wrote: > > | > | > Debug: sleeping function called from invalid context at include/asm/uaccess.h:473 > > | > | > Call Trace: > > | > | > [] __might_sleep+0x54/0x5b > > | > | > [] save_v86_state+0x71/0x1f0 > > | > | > [] handle_vm86_fault+0xc5/0xa90 > > | > | > [] ext3_file_write+0x28/0xc0 > > | > | > [] __change_page_attr+0x26/0x220 > > | > | > [] do_general_protection+0x0/0x90 > > | > | > [] error_code+0x2d/0x40 > > | > | > [] syscall_call+0x7/0xb > > | > | > > > > I had another occurrence of this yesterday. It doesn't seem to be > > an error condition AFAICT. > > How spooky. now I got one too, (minus the noise). > > Call Trace: > [] __might_sleep+0x5b/0x5f > [] save_v86_state+0x6a/0x1f3 > [] handle_vm86_fault+0xa7/0x897 > [] do_general_protection+0x0/0x93 > [] error_code+0x2d/0x38 > [] syscall_call+0x7/0xb > > By the looks of the logs, it happened as I restarted X, as theres > a bunch of mtrr messages right after this.. What video driver do you use? -- Matt Mackall : http://www.selenic.com : of or relating to the moon