From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964794AbWFWM6Q (ORCPT ); Fri, 23 Jun 2006 08:58:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964796AbWFWM6Q (ORCPT ); Fri, 23 Jun 2006 08:58:16 -0400 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:11495 "EHLO amd.ucw.cz") by vger.kernel.org with ESMTP id S964794AbWFWM6P (ORCPT ); Fri, 23 Jun 2006 08:58:15 -0400 Date: Fri, 23 Jun 2006 14:57:01 +0200 From: Pavel Machek To: Frederik Deweerdt Cc: Andrew Morton , 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: <20060623125658.GB8048@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> <20060623121210.GB2234@slug> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060623121210.GB2234@slug> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.11+cvs20060126 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > > > 2.6.17 wasn't supposed to oops. Do you have details on this? > > > > > > > For some reason, unknown to me, the oops won't display on the serial > > > link :(. > > > > Serial console is currently broken by suspend, resume. _But_ I have a > > patch I'd like you to try.... pretty please? > > > Sure :)... I applied it but the output went to the laptop's screen anyway... Do you need some kernel command line options? This is s2ram, do I recall it correctly? > > That is not an oops, rather a kernel BUG(). 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? > > > > /* > > * lock for reading > > */ > > static inline void down_read(struct rw_semaphore *sem) > > { > > might_sleep(); > > ~~~~~~~~~~~~~~~~~~~~~~ > > rwsemtrace(sem,"Entering down_read"); > > __down_read(sem); > > rwsemtrace(sem,"Leaving down_read"); > > } > > > Here's the (hand copied) dump when the might_sleep is removed: > > esi: 00000003 edit: 00000000 ebp: f6cb9eb8 esp: f6cb9ea4 > ds: 007b es: 007b ss: 0068 > Process bash (pid: 9402, threadinfo=f6cb8000 task=f7a5c570) This stack lines are not really interesting (can you comment them from sources?) and they make interesting info scroll away :-(. Or maybe vga=1 can help? > Stack: c0229b71 00000046 00000000 00000286 c0383ca7 f6cb9ecc c013b242 00000003 > 00000000 00000003 f6cb9ee0 c013b2e8 00000003 c0436890 f6c9a003 f6cb9f08 > c013b481 00000003 00000003 00000246 c1788b00 00000003 c04368a0 c043692c > Call Trace: > show_stack_log_lvl+0x92/0xb7 show_registers+0x1a3/0x21b > die+0x117/0x230 do_page_fault+0x39c/0x72a > 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/0x46 > sysfs_write_file+0x67/0x8b vfs_write+0x1b9/0x1be > sys_write+0x4b/0x75 sysenter_past_esp+0x54/0x75 > > Code: 05 c4 42 43 c0 31 43 43 c0 c3 8b 2d 68 6e 54 c0 8b 1d 60 6e 54 c0 8b 35 6c 6e 54 c0 8b 3d 70 6d 54 c0 ff 35 74 6e 54 c0 9d c3 90 6d 38 ea ff e8 a2 ff ff ff 6a 03 e8 ec b6 de ff 83 c4 04 c3 > EIP: [c043431c>] do_suspend_lowlevel+0x0/0x15 SS:ESP 0068:f6cb6ea4 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ha, wait a moment, this is interesting line. Can you trace down which instruction causes this? We recently changed pagetable handling during swsusp, perhaps thats it? It went to Linus few minutes ago... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html