From: Pavel Machek <pavel@ucw.cz>
To: "Klaus S. Madsen" <ksm@hjernemadsen.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending
Date: Thu, 28 Feb 2008 08:03:02 +0100 [thread overview]
Message-ID: <20080228070302.GA26007@elf.ucw.cz> (raw)
In-Reply-To: <20080228064756.GT17932@hjernemadsen.org>
On Thu 2008-02-28 07:47:56, Klaus S. Madsen wrote:
> On Wed, Feb 27, 2008 at 23:19:11 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, 27 of February 2008, Klaus S. Madsen wrote:
> > > Hi all,
> > >
> > > I have a Thinkpad T61p, which I'm able to suspend with s2ram on
> > > Linux 2.6.24.3. However when I try to suspend it on 2.6.25-rc3, s2ram
> > > dies after changing to vt1, with a segfault. I'm using s2ram from cvs,
> > > and libx86 version 0.99 from http://www.codon.org.uk/~mjg59/libx86/.
> >
> > There's a known suspend problem with 2.6.25-rc3 that has been fixed
> > already in the Linus' tree. Can you test the current head of the
> > Linus' tree, please?
> I've tested the head of Linus' git as of this morning, and the problem
> still exists. Note however, that I don't even get to the suspend part,
> as s2ram crashes before it initiates the kernel part of STR.
Yes, looks like ingo broke vm86 emulation, or something like that...?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-02-28 7:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 22:10 Regression in 2.6.25-rc3: s2ram segfaults before suspending Klaus S. Madsen
2008-02-27 22:19 ` Rafael J. Wysocki
2008-02-27 22:40 ` Pavel Machek
2008-02-28 6:47 ` Klaus S. Madsen
2008-02-28 7:03 ` Pavel Machek [this message]
2008-02-28 7:08 ` Klaus S. Madsen
2008-02-28 9:16 ` Ingo Molnar
2008-02-28 9:28 ` Klaus S. Madsen
2008-02-28 9:40 ` Ingo Molnar
2008-02-28 15:04 ` Klaus S. Madsen
2008-02-28 17:52 ` H. Peter Anvin
2008-02-28 19:24 ` Klaus S. Madsen
2008-02-28 19:31 ` H. Peter Anvin
2008-02-28 19:49 ` Klaus S. Madsen
2008-02-28 22:45 ` H. Peter Anvin
2008-02-29 7:00 ` Klaus S. Madsen
2008-02-29 21:05 ` H. Peter Anvin
2008-02-29 21:26 ` Ingo Molnar
2008-03-01 9:45 ` Klaus S. Madsen
2008-03-01 19:53 ` H. Peter Anvin
2008-03-03 12:17 ` Pavel Machek
2008-03-03 15:11 ` Klaus S. Madsen
2008-03-03 17:48 ` Ingo Molnar
2008-03-03 17:53 ` H. Peter Anvin
2008-03-03 20:52 ` Klaus S. Madsen
2008-03-03 20:58 ` H. Peter Anvin
2008-03-03 21:05 ` Pavel Machek
2008-03-03 21:06 ` Matthew Garrett
2008-03-03 21:06 ` Pavel Machek
2008-03-03 21:21 ` Klaus S. Madsen
2008-03-04 12:36 ` Ingo Molnar
2008-03-04 21:58 ` Klaus S. Madsen
2008-03-04 22:08 ` H. Peter Anvin
2008-03-04 23:00 ` Jeremy Fitzhardinge
2008-03-04 23:11 ` H. Peter Anvin
2008-03-04 23:21 ` Jeremy Fitzhardinge
2008-03-04 23:30 ` Matthew Garrett
2008-03-04 12:42 ` Ingo Molnar
2008-03-03 15:40 ` Rafael J. Wysocki
2008-03-03 17:10 ` H. Peter Anvin
2008-03-03 17:47 ` Pavel Machek
2008-03-03 17:50 ` H. Peter Anvin
2008-03-03 17:53 ` Ingo Molnar
2008-03-03 17:58 ` H. Peter Anvin
2008-03-01 1:18 ` 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=20080228070302.GA26007@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=ksm@hjernemadsen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).