public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Dave Airlie <airlied@linux.ie>, Len Brown <lenb@kernel.org>,
	Jeff Chua <jeff.chua.linux@gmail.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
	"Li, Shaohua" <shaohua.li@intel.com>
Subject: Re: Occasional (too common) suspend problem
Date: Mon, 24 Jan 2011 16:09:17 +0800	[thread overview]
Message-ID: <1295856557.1866.802.camel@rui> (raw)
In-Reply-To: <AANLkTimSv5Myv14Kys2OTgm=wH=8DFPFeeUSkEfg-+b1@mail.gmail.com>

On Mon, 2011-01-24 at 15:22 +0800, Linus Torvalds wrote:
> On Mon, Jan 24, 2011 at 7:29 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >
> > There's one more thing that may be related.  Apparently, we've made something
> > recently that's causing lots of problems with boot and poweroff for Asus
> > machines (https://lkml.org/lkml/2011/1/23/54).  The Asus BIOSes evidently
> > don't like something we do, but I have no idea what that may be at this point.
> 
> Yeah, I think there's something there. In fact, I'm getting pretty
> sure of it. Because I have now twice seen the _shutdown_ end up
> halting, and guess what? When I press a key, it then finishes the
> shutdown.
> 
> Sound familiar?
> 
> The last thing printed is the "Disabling non-boot CPU's" thing or
> whatever. I didn't take a picture, and it obviously doesn't get logged
> (since it's after the processes have been killed), but it definitely
> smelled like "Uhhuh, same problem as with suspend".
> 
https://patchwork.kernel.org/patch/500501/
does this patch help?

thanks,
rui

>                    Linus
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2011-01-24  8:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  4:50 Occasional (too common) suspend problem Linus Torvalds
     [not found] ` <AANLkTi=LyufFJ-zqMWdGnSnZ-iW+ONbQ8mLfTn1O5WVi@mail.gmail.com>
2011-01-21  5:26   ` [linux-pm] " Lin Ming
2011-01-21 16:28     ` Linus Torvalds
2011-01-21 17:09       ` [linux-pm] " Jeff Chua
2011-01-21 20:54       ` Rafael J. Wysocki
2011-01-21  7:26 ` Zhang Rui
2011-01-21 21:00 ` Len Brown
2011-01-21 21:08   ` Rafael J. Wysocki
2011-01-21 22:25   ` Len Brown
2011-01-21 22:33     ` Linus Torvalds
2011-01-21 22:42       ` Rafael J. Wysocki
2011-01-21 22:55         ` Linus Torvalds
2011-01-21 23:16           ` Rafael J. Wysocki
2011-01-21 23:28             ` [linux-pm] " Rafael J. Wysocki
2011-01-22  0:23             ` Linus Torvalds
2011-01-22  0:31               ` Rafael J. Wysocki
2011-01-22  0:56                 ` Linus Torvalds
2011-01-22  1:14               ` Linus Torvalds
2011-01-22 10:10                 ` Rafael J. Wysocki
2011-01-22 15:11                   ` Linus Torvalds
2011-01-22 16:27                     ` Linus Torvalds
2011-01-22 17:13                       ` Jeff Chua
2011-01-22 18:22                         ` Linus Torvalds
2011-01-22 19:17                       ` Rafael J. Wysocki
2011-01-22 19:42                         ` Linus Torvalds
2011-01-23 21:29                           ` Rafael J. Wysocki
2011-01-23 21:47                             ` [linux-pm] " Rafael J. Wysocki
2011-01-24  7:22                             ` Linus Torvalds
2011-01-24  8:09                               ` Zhang Rui [this message]
2011-01-24  9:43                                 ` Linus Torvalds
2011-01-23  1:02                       ` Dave Airlie

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=1295856557.1866.802.camel@rui \
    --to=rui.zhang@intel.com \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jeff.chua.linux@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    --cc=shaohua.li@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox