public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: "Ákos Maróy" <akos@maroy.hu>,
	"Kernel development list" <linux-kernel@vger.kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: how to debug a kernel that does not power off?
Date: Fri, 26 Mar 2010 19:47:52 -0600	[thread overview]
Message-ID: <4BAD63C8.6070401@gmail.com> (raw)
In-Reply-To: <201003262056.11231.arnout@mind.be>

On 03/26/2010 01:56 PM, Arnout Vandecappelle wrote:
>   Take a look at the pm_power_off functions in arch/x86/kernel/apm_32.c
>
>   Regards,
>   Arnout

Any modern machine will be using ACPI functions to power off, not APM.. 
CCing the linux-acpi list.

>
> On Wednesday 24 March 2010 00:44:30, Ákos Maróy wrote:
>> 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.9.
>>
>> 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-kernel"
>> in the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
>


      reply	other threads:[~2010-03-27  1:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 23:44 how to debug a kernel that does not power off? Ákos Maróy
2010-03-26 19:56 ` Arnout Vandecappelle
2010-03-27  1:47   ` Robert Hancock [this message]

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=4BAD63C8.6070401@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=akos@maroy.hu \
    --cc=arnout@mind.be \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox