From: Alexey Starikovskiy <aystarik@gmail.com>
To: "Ákos Maróy" <akos@maroy.hu>
Cc: linux-acpi@vger.kernel.org
Subject: Re: how to debug a kernel that does not power off?
Date: Thu, 25 Mar 2010 11:39:44 +0300 [thread overview]
Message-ID: <4BAB2150.3020306@gmail.com> (raw)
In-Reply-To: <4BAAE755.9090509@maroy.hu>
Hi,
Most probably, you have ACPI disabled either in the BIOS or in the
kernel (command line or compiled out). Please check if it is enabled.
Regards,
Alex.
Ákos Maróy пишет:
> Hi,
>
> This might be a lame question, but: how would I debug a kernel that
> simply does not power off a machine? When powering off, on the console I
> get to the message: [...] Poweroff.
>
> but then, the machine actually does not power off. This is an HP Envy 15
> laptop using an intel i7 CPU, and kernel 2.6.32.8..10.
>
> I tried to read up on all sorts of documentation, but could not get more
> debug info out of the kernel :(
>
> any pointers would be welcome..
>
>
> Akos
>
> --
> 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
>
--
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
next prev parent reply other threads:[~2010-03-25 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 4:32 how to debug a kernel that does not power off? Ákos Maróy
2010-03-25 8:39 ` Alexey Starikovskiy [this message]
2010-03-25 16:45 ` Ákos Maróy
-- strict thread matches above, loose matches on Subject: below --
2010-03-23 23:44 Ákos Maróy
2010-03-26 19:56 ` Arnout Vandecappelle
2010-03-27 1:47 ` Robert Hancock
2010-03-27 1:47 ` Robert Hancock
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=4BAB2150.3020306@gmail.com \
--to=aystarik@gmail.com \
--cc=akos@maroy.hu \
--cc=linux-acpi@vger.kernel.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.