From: Frederik Deweerdt <deweerdt@free.fr>
To: Andrew Morton <akpm@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>,
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]
Date: Mon, 26 Jun 2006 11:00:41 +0200 [thread overview]
Message-ID: <20060626090041.GA3686@slug> (raw)
In-Reply-To: <20060623125706.69dafffd.akpm@osdl.org>
On Fri, Jun 23, 2006 at 12:57:06PM -0700, Andrew Morton wrote:
> On Fri, 23 Jun 2006 14:57:01 +0200
> Pavel Machek <pavel@ucw.cz> wrote:
>
> > > 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:
> > > <c0103eea> show_stack_log_lvl+0x92/0xb7 <c0104100> show_registers+0x1a3/0x21b
> > > <c0104319> die+0x117/0x230 <c03627a6> do_page_fault+0x39c/0x72a
> > > <c0103b2f> error_code+0x4f/0x54 <c013b242> suspend_enter+0x2f/0x52
> > > <c013b2e8> enter_state+0x4b/0x8d <c013b481> state_store+0xa0/0xa2
> > > <c01a5151> subsys_attr_store+0x37/0x41 <c01a53d2> flush_write_buffer+0x3c/0x46
> > > <c01a5443> sysfs_write_file+0x67/0x8b <c0166bb6> vfs_write+0x1b9/0x1be
> > > <c0166c7b> sys_write+0x4b/0x75 <c010300f> 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 <e8> 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...
>
> That's a good possibility. It does appear to be oopsing at the first
> instruction of arch/i386/kernel/acpi/wakeup.S:do_suspend_lowlevel().
> Perhaps there's enough info in that oops trace to tell us whether it was
> the instruction fetch which oopsed.
>
> One wonders whether this will help...
>
I've tried 2.6.17-git10 which appears to have the fix and the laptop
suspends correctly. Looks like that was it :).
Thanks,
Frederik
next prev parent reply other threads:[~2006-06-26 9:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060621034857.35cfe36f.akpm@osdl.org>
2006-06-21 21:48 ` swsusp regression [Was: 2.6.17-mm1] Jiri Slaby
2006-06-21 22:14 ` Mattia Dongili
2006-06-21 22:18 ` Mattia Dongili
2006-06-22 6:19 ` Greg KH
2006-06-22 7:46 ` [linux-pm] " Andrew Morton
2006-06-22 8:25 ` Jeremy Fitzhardinge
2006-06-22 15:51 ` Alan Stern
2006-06-22 17:17 ` Jeremy Fitzhardinge
2006-06-22 18:46 ` Greg KH
2006-06-22 19:07 ` [linux-pm] " Greg KH
2006-06-22 19:57 ` Alan Stern
2006-06-22 20:22 ` Greg KH
2006-06-22 20:38 ` Jiri Slaby
2006-06-22 21:09 ` Alan Stern
2006-06-22 21:11 ` Greg KH
2006-06-22 16:04 ` [linux-pm] " Frederik Deweerdt
2006-06-22 16:25 ` Andrew Morton
2006-06-22 19:07 ` [linux-pm] " Frederik Deweerdt
2006-06-23 9:02 ` Frederik Deweerdt
2006-06-23 9:10 ` [linux-pm] " Pavel Machek
2006-06-23 9:31 ` Andrew Morton
2006-06-23 12:12 ` Frederik Deweerdt
2006-06-23 12:57 ` Pavel Machek
2006-06-23 13:47 ` Frederik Deweerdt
2006-06-23 19:57 ` Andrew Morton
2006-06-26 9:00 ` Frederik Deweerdt [this message]
2006-06-23 19:41 ` [linux-pm] " Russell King
2006-06-23 20:22 ` Dave Jones
2006-06-23 21:10 ` Rafael J. Wysocki
2006-06-23 22:11 ` Pavel Machek
2006-06-23 23:53 ` [linux-pm] " Frederik Deweerdt
2006-06-24 17:16 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060626090041.GA3686@slug \
--to=deweerdt@free.fr \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=pavel@ucw.cz \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox