Return-Path: <linux-kernel-owner+willy=40w.ods.org-S1755532AbWKQHVr@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755532AbWKQHVr (ORCPT <rfc822;willy@w.ods.org>);
	Fri, 17 Nov 2006 02:21:47 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755534AbWKQHVq
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 17 Nov 2006 02:21:46 -0500
Received: from mx2.mail.elte.hu ([157.181.151.9]:20421 "EHLO mx2.mail.elte.hu")
	by vger.kernel.org with ESMTP id S1755532AbWKQHVp (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 17 Nov 2006 02:21:45 -0500
Date: Fri, 17 Nov 2006 07:52:02 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: sleeping functions called in invalid context during resume
Message-ID: <20061117065202.GA11877@elte.hu>
References: <20061114223002.10c231bd@localhost.localdomain> <20061115012025.13c72fc1.akpm@osdl.org> <20061115093354.GA30813@elte.hu> <20061115100119.460b7a4e@localhost.localdomain> <20061115180436.GB29795@elte.hu> <20061116212158.0ef99842@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20061116212158.0ef99842@localhost.localdomain>
User-Agent: Mutt/1.4.2.2i
X-ELTE-SpamScore: -4.4
X-ELTE-SpamLevel: 
X-ELTE-SpamCheck: no
X-ELTE-SpamVersion: ELTE 2.0 
X-ELTE-SpamCheck-Details: score=-4.4 required=5.9 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=no SpamAssassin version=3.0.3
	-3.3 ALL_TRUSTED            Did not pass through any untrusted hosts
	-2.6 BAYES_00               BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	1.5 AWL                    AWL: From: address is in the auto white-list
X-ELTE-VirusStatus: clean
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1676
Lines: 49


* Stephen Hemminger <shemminger@osdl.org> wrote:

> > > BUG: sleeping function called from invalid context at drivers/base/power/resume.c:99
> > > in_atomic():1, irqs_disabled():0
> > > 
> > > Call Trace:  
> > >  [<ffffffff80266117>] show_trace+0x34/0x47
> > >  [<ffffffff8026613c>] dump_stack+0x12/0x17
> > >  [<ffffffff803734e5>] device_resume+0x19/0x51
> > >  [<ffffffff80292157>] enter_state+0x19b/0x1b5
> > >  [<ffffffff802921cf>] state_store+0x5e/0x79
> > >  [<ffffffff802cc157>] sysfs_write_file+0xc5/0xf8
> > >  [<ffffffff80215059>] vfs_write+0xce/0x174
> > >  [<ffffffff802159a5>] sys_write+0x45/0x6e
> > >  [<ffffffff802593de>] system_call+0x7e/0x83  
> > > DWARF2 unwinder stuck at system_call+0x7e/0x83
> > > 
> 
> Ingo, the later version of your lockdep patch (with the x86_64 fix), 
> worked. There is nothing locked during these errors.
> 
> The problem was the APIC error is leaving preempt-disabled.

ah, that could be the case - do you have a fix-patch for that?

preempt-disabled leaks are only caught via CONFIG_PREEMPT_TRACE (not via 
lockdep), which debug feature you can find in the -rt tree:

  http://redhat.com/~mingo/realtime-preempt/

(there's no easy standalone patch for now.)

it will be enabled if you select CONFIG_DEBUG_PREEMPT.

> I have no idea what causes:
> 
> APIC error on CPU0: 00(00)
> 
> Is it an ACPI problem?

a 00 error code? Never seen that ... How frequently does it happen?

	Ingo
-
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/