From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frederik Deweerdt Subject: Re: swsusp regression [Was: 2.6.17-mm1] Date: Fri, 23 Jun 2006 15:47:26 +0200 Message-ID: <20060623134726.GD2234@slug> References: <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> <20060623125658.GB8048@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20060623125658.GB8048@elf.ucw.cz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Pavel Machek Cc: linux-kernel@vger.kernel.org, linux-pm@osdl.org List-Id: linux-pm@vger.kernel.org On Fri, Jun 23, 2006 at 02:57:01PM +0200, Pavel Machek wrote: > 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 anyw= ay... > = > Do you need some kernel command line options? This is s2ram, do I > recall it correctly? I think the options are ok: I'm passing console=3Dtty0 console=3DttyS0,9600= and everything works fine in cu(1). Until the 'echo mem > /sys/power/state', th= at is :) > > esi: 00000003 edit: 00000000 ebp: f6cb9eb8 esp: f6cb9ea4 > > ds: 007b es: 007b ss: 0068 > > Process bash (pid: 9402, threadinfo=3Df6cb8000 task=3Df7a5c570) > = > This stack lines are not really interesting (can you comment them from > sources?) and they make interesting info scroll away :-(. = I'll comment them out and send you the trace, but I won't get the time to do it today, I'll try to get it done by monday. > Or maybe vga=3D1 can help? I've tried it. But somehow, the suspend process resets the resolution to the lowest one. > = > > Stack: c0229b71 00000046 00000000 00000286 c0383ca7 f6cb9ecc c013b242 0= 0000003 > > 00000000 00000003 f6cb9ee0 c013b2e8 00000003 c0436890 f6c9a003 = f6cb9f08 > > c013b481 00000003 00000003 00000246 c1788b00 00000003 c04368a0 = c043692c c0229b71 is in acpi_pm_enter: case PM_SUSPEND_MEM: --> do_suspend_lowlevel(); break; c013b242 is in suspend_enter: } --> error =3D pm_ops->enter(state); device_power_up(); c013b2e8 is in enter_state pr_debug("PM: Entering %s sleep\n", pm_states[state]); --> error =3D suspend_enter(state); c013b481 is in state_store if (state < PM_SUSPEND_MAX && *s) --> error =3D enter_state(state); else > > Call Trace: > > show_stack_log_lvl+0x92/0xb7 show_registers+0x1= a3/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? This disassembles as follows: c043431c : c043431c: e8 6d 38 ea ff call c02d7b8e c0434321: e8 a2 ff ff ff call c04342c8 c0434326: 6a 03 push $0x3 c0434328: e8 ec b6 de ff call c021fa19 c043432d: 83 c4 04 add $0x4,%esp c0434330: c3 ret So it looks like where crashing when calling save_processor_state. = > We recently changed pagetable handling during swsusp, perhaps thats > it? It went to Linus few minutes ago... Sorry, I don't understand what you mean: do you want me to try the latest g= it? Regards, Frederik