public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Cc: "Vladimir Pouzanov" <farcaller@gmail.com>,
	"Len Brown" <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ACPI Power Down is broken in 2.6.21.1
Date: Sun, 13 May 2007 09:22:27 -0700	[thread overview]
Message-ID: <20070513092227.6d87e60d@freepuppy> (raw)
In-Reply-To: <6bffcb0e0705130729n2c47f0f4h6791ac4b74b9bb62@mail.gmail.com>

On Sun, 13 May 2007 16:29:25 +0200
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote:

> Hi Vladimir,
> 
> [adding Len and ACPI gurus to CC]
> 
> On 08/05/07, Vladimir Pouzanov <farcaller@gmail.com> wrote:
> > Hi all,
> >
> > I have got a problem with Asus F3T notebook and 2.6.21.1 kernel. When I
> > perform powerdown (with user-space app or alt+sysrq+o) I get "Power Down."
> > message, but the notebook doesn't turn off. Everything is ok on 2.6.20.
> >
> > There seem to be no changes in acpi/sleep/poweroff.c so I don't know where
> > should I start looking for a bug.
> >
> > F3T is based on Thrion64 X2 CPU (I'm running it in x86 mode with SMP and
> > PREEMPT).
> >
> > Sincerely,
> > Vladimir "Farcaller" Pouzanov
> > http://hackndev.com
> >
> 
> I added this bug to the list of known regressions.
> (http://kernelnewbies.org/known_regressions)
> 
> Regards,
> Michal
> 

Is the network still connected? Maybe there is a wake on lan
problem with the network device.

-- 
Stephen Hemminger <shemminger@linux-foundation.org>

  reply	other threads:[~2007-05-13 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 16:01 ACPI Power Down is broken in 2.6.21.1 Vladimir Pouzanov
2007-05-13 14:29 ` Michal Piotrowski
2007-05-13 16:22   ` Stephen Hemminger [this message]
2007-05-13 19:36 ` 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=20070513092227.6d87e60d@freepuppy \
    --to=shemminger@linux-foundation.org \
    --cc=farcaller@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    /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