mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: swsusp hangs on headless resume-from-ram
Date: Sat, 29 Jul 2006 00:00:16 +0300	[thread overview]
Message-ID: <200607290000.16933.a1426z@gawab.com> (raw)
In-Reply-To: <200607282042.51831.rjw@sisk.pl>

Rafael J. Wysocki wrote:
> On Friday 28 July 2006 16:23, Rafael J. Wysocki wrote:
> > On Friday 28 July 2006 15:58, Al Boldi wrote:
> > > Rafael J. Wysocki wrote:
> > > > On Wednesday 26 July 2006 23:34, Al Boldi wrote:
> > > > > Rafael J. Wysocki wrote:
> > > > > > On Wednesday 26 July 2006 21:06, Al Boldi wrote:
> > > > > > > swsusp is really great, most of the time.  But sometimes it
> > > > > > > hangs after coming out of STR.  I suspect it's got something
> > > > > > > to do with display access, as this problem seems hw related. 
> > > > > > > So I removed the display card, and it positively does not
> > > > > > > resume from ram on 2.6.16+.
> > > > > > >
> > > > > > > Any easy fix for this?
> > > > > >
> > > > > > I have one idea, but you'll need a patch to test.  I'll try to
> > > > > > prepare it tomorrow.
> > > > > >
> > > > > > I guess your box is an i386?
> > > > >
> > > > > That should be assumed by default :)
> > > >
> > > > I had hoped I would be able to test it somewhere, but I couldn't.  I
> > > > hope it will compile. :-)
> > > >
> > > > If it does, please send me the output of dmesg after a fresh boot.
> > >
> > > See attached.  patched against 2.6.17.
> >
> > Well, the nosave ranges are the same in both cases, so it doesn't look
> > very promising.
> >
> > Have you tried to suspend with the patch applied?
>
> Ouch, sorry, it won't work.  It will have a chance to work with the
> appended patch applied.
>
> However, I've just noticed you said it didn't resume from RAM and these
> two patches could only fix the resume from disk. ;-)

Actually, I'm using suspend-to-disk to work around this STR problem, and STD 
seems to work fine.  It's STR that sometimes hangs after resuming.

> As far as the
> resume from RAM is concerned, I can only advise you to use a
> newest possible kernel and see if the problem is still there.

Have there been patches that address this issue?

Thanks!

--
Al


  reply	other threads:[~2006-07-28 20:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 19:06 Al Boldi
2006-07-26 20:07 ` Rafael J. Wysocki
2006-07-26 21:34   ` Al Boldi
2006-07-28  8:55     ` Rafael J. Wysocki
2006-07-28 13:58       ` Al Boldi
2006-07-28 14:23         ` Rafael J. Wysocki
2006-07-28 18:42           ` Rafael J. Wysocki
2006-07-28 21:00             ` Al Boldi [this message]
2006-07-28 21:05               ` Rafael J. Wysocki
2006-08-01 20:59       ` Pavel Machek
2006-08-01 21:02 ` Pavel Machek
2006-08-02 13:46   ` Al Boldi
2006-08-16 12:43     ` Pavel Machek

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=200607290000.16933.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®