From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932962AbWFWJb5 (ORCPT ); Fri, 23 Jun 2006 05:31:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932966AbWFWJb5 (ORCPT ); Fri, 23 Jun 2006 05:31:57 -0400 Received: from smtp.osdl.org ([65.172.181.4]:29374 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S932962AbWFWJb4 (ORCPT ); Fri, 23 Jun 2006 05:31:56 -0400 Date: Fri, 23 Jun 2006 02:31:24 -0700 From: Andrew Morton To: Pavel Machek Cc: deweerdt@free.fr, greg@kroah.com, linux-kernel@vger.kernel.org, linux-pm@osdl.org, stern@rowland.harvard.edu Subject: Re: [linux-pm] swsusp regression [Was: 2.6.17-mm1] Message-Id: <20060623023124.138d432f.akpm@osdl.org> In-Reply-To: <20060623091016.GE4940@elf.ucw.cz> References: <20060621034857.35cfe36f.akpm@osdl.org> <4499BE99.6010508@gmail.com> <20060621221445.GB3798@inferi.kami.home> <20060622061905.GD15834@kroah.com> <20060622004648.f1912e34.akpm@osdl.org> <20060622160403.GB2539@slug> <20060622092506.da2a8bf4.akpm@osdl.org> <20060623090206.GA2234@slug> <20060623091016.GE4940@elf.ucw.cz> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 23 Jun 2006 11:10:21 +0200 Pavel Machek wrote: > > Here's what I could hand copy (I've suppressed printk timing information): > > x1b9/0x1be > > sys_write+0x4b/0x75 sysenter_past_esp+0x54/0x75 > > Code: 05 c4 52 43 c0 31 53 43 c0 c3 8b 2d 68 6e 54 c0 8b 1d 60 > > 6e 54 c0 8b 35 6c 6e 54 c0 8b 3d 70 6e 54 c0 ff 35 74 6e 54 c0 9d c3 90 > > 9d 2c ea ff e8 a2 ff ff ff 6a 03 e8 4c ab de ff 83 c4 04 c3 > > EIP: [] do_suspend_lowlevel+0x0/0x15 SS:ESP 0068:f7a0fea4 > > <3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 > > in_atomic():0, irqs_disabled():1 > > show_trace+0x20/0x22 dump_stack+0x1e/0x20 > > __might_sleep+0x9e/0xa6 blocking_notifier_call_chain+0x1e/0x5b > > profile_task_exit+0x21/0x23 do_exit+0x1d/0x483 > > do_divide_error+0x0/0xbf do_page_fault+0x3c4/0x752 > > error_code+0x4f/0x54 suspend_enter+0x2f/0x52 > > enter_state+0x4b/0x8d state_store+0xa0/0xa2 > > subsys_attr_store+0x37/0x41 flush_write_buffer+0x3c/046 > > sysfs_write_file+0x67/0x8b vfs_write+0x1b9/0x1be > > sys_write+0x4b/0x75 sysenter_past_esp+0x54/0x75 > > That is not an oops, rather a kernel BUG(). It's not a BUG(). It's a BUG. IOW, it's just a WARN_ON(). Ingo decided all the scary messages should start with the text "BUG". That doesn't correlate with BUG(). Confused yet? That trace is odd. It kinda looks like we got a segfault when entering the do_suspend_lowlevel() assembly. Or something. > Can you just remove > might_sleep line and see what happens? > > Unfortunately, backtrace does not tell me which notifier chain did > that :-(. Are you using audit or something like that? No, that's all a consequence of something which happened earlier.