All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: michal.k.k.piotrowski@gmail.com, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org, mingo@elte.hu, lists4me@web.de,
	jeff.chua.linux@gmail.com, adaplas@gmail.com, lenb@kernel.org,
	dth@dth.net, linux-fsdevel@vger.kernel.org,
	nfs@lists.sourceforge.net, Trond.Myklebust@netapp.com,
	andrew@digital-domain.net, peter.kovar@gmail.com
Subject: Re: [2/4] 2.6.23-rc5: known regressions
Date: Mon, 3 Sep 2007 05:46:02 -0700	[thread overview]
Message-ID: <20070903054602.68ddd468.akpm@linux-foundation.org> (raw)
In-Reply-To: <46DBE660.9020309@zytor.com>

> On Mon, 03 Sep 2007 11:48:00 +0100 "H. Peter Anvin" <hpa@zytor.com> wrote:
> Michal Piotrowski wrote:
> > 
> > Unclassified
> > 
> > Subject         : console is messed up after resume from s2ram or switching to console from X
> > References      : http://lkml.org/lkml/2007/8/4/6
> > Last known good : ?
> > Submitter       : Jeff Chua <jeff.chua.linux@gmail.com>
> > Caused-By       : ?
> > Handled-By      : H. Peter Anvin <hpa@zytor.com>
> >                   Antonino A. Daplas <adaplas@gmail.com>
> > Workaround      : "s2ram --force --acpi_sleep 1 --vbe_mode"
> > Status          : problem is being debugged
> > 
> 
> I'm inclined to write this one off as general STR weirdness.

Both suspend-to-ram and suspend-to-disk are broken on this Vaio.  Running
2.6.23-rc4.


suspend-to-RAM:

a) sometimes hangs during suspend

b) frequently hangs during resume

c) occasionally acts weird after resume.  system requires repeated
   keypresses to make forward progress.

d) on those occasions where resume-from-RAM _does_ work, it takes much
   longer to resume than it used to.

suspend-to-disk:

a) always hangs when netconsole-over-e100 is enabled (might have been a
   2.6.21->2.6.22 regression).

b) usually hangs during suspend


Apart from suspend-to-disk's a), all of the above are post-2.6.21
regressions.



  reply	other threads:[~2007-09-03 12:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46DBD982.3080102@googlemail.com>
2007-09-03 10:10 ` [2/4] 2.6.23-rc5: known regressions Michal Piotrowski
2007-09-03 10:10 ` Michal Piotrowski
2007-09-03 10:48   ` H. Peter Anvin
2007-09-03 12:46     ` Andrew Morton [this message]
2007-09-03 12:57       ` Andrew Morton
2007-09-03 12:57       ` Andrew Morton
2007-09-03 12:57         ` Andrew Morton
2007-09-07 22:52       ` Michal Piotrowski
2007-09-03 12:36   ` Jeff Chua
2007-09-03 12:51     ` Andrew Morton
2007-09-03 13:08       ` H. Peter Anvin
2007-09-03 10:10 ` [3/4] " Michal Piotrowski
2007-09-03 10:11 ` [4/4] " Michal Piotrowski
2007-09-03 10:11   ` Michal Piotrowski
2007-09-05  7:25   ` slow resume (was Re: [4/4] 2.6.23-rc5: known regressions) 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=20070903054602.68ddd468.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=adaplas@gmail.com \
    --cc=andrew@digital-domain.net \
    --cc=dth@dth.net \
    --cc=hpa@zytor.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists4me@web.de \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mingo@elte.hu \
    --cc=nfs@lists.sourceforge.net \
    --cc=peter.kovar@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.