public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <aystarik@gmail.com>
To: John Sigler <linux.kernel@free.fr>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	robert.moore@intel.com, len.brown@intel.com
Subject: Re: halt does not shut the system down
Date: Mon, 15 Oct 2007 18:03:43 +0400	[thread overview]
Message-ID: <4713733F.7060408@gmail.com> (raw)
In-Reply-To: <47136B2F.9070904@free.fr>

John Sigler wrote:
> Alexey Starikovskiy wrote:
> 
>> John Sigler wrote:
>>
>>> Alexey Starikovskiy wrote:
>>>
>>>> Could you please open bug at bugzilla.kernel.org and put all
>>>> these files there?
>>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=9148
>>>
>>> Writing 15361 (i.e. 0x3C01) to ACPI_REGISTER_PM1A_CONTROL appears
>>> to hang my system in acpi_os_write_port(). What can I do about that?
>>
>> That is supposed to turn your machine off. At least we now know that
>> ACPI did try to turn it off. You could also try different kernel or
>> defconfig.
> 
> What's defconfig? .config? Which option(s) might have an impact?

This is an option to make. It creates .config file with some default settings,
appropriate to most computers.

>>> Is it a BIOS issue? a kernel issue? a hardware issue?
>>
>> I think _other_ OS could turn your machine off just fine, so the
>> issue is not HW, not BIOS. Probably, first thing to try is 2.6.23.1
>> as it was just released and has some changes in power management
>> section...
> 
> I have the same problem in 2.6.23.1 (cf. my bug report in the database)
> 
> I'll ask the manufacturer whether they could get poweroff to work.
> 
> Regards.
> 


  reply	other threads:[~2007-10-15 14:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 16:19 halt does not shut the system down John Sigler
2007-10-09  8:06 ` John Sigler
2007-10-09 20:04   ` Remy Bohmer
2007-10-10  9:56     ` John Sigler
2007-10-12 19:29       ` Remy Bohmer
2007-10-10  9:11 ` John Sigler
2007-10-12  9:58   ` John Sigler
2007-10-12 10:41     ` Alexey Starikovskiy
2007-10-12 13:11       ` John Sigler
2007-10-15 10:36         ` John Sigler
2007-10-15 11:11           ` Alexey Starikovskiy
2007-10-15 13:29             ` John Sigler
2007-10-15 14:03               ` Alexey Starikovskiy [this message]
2007-10-16 10:51           ` John Sigler
2007-10-16 12:37             ` linux-os (Dick Johnson)
2007-10-16 13:08               ` John Sigler
2007-10-16 17:06                 ` Alexey Starikovskiy
2007-10-17  8:09                   ` John Sigler
2007-10-17  8:11                     ` Alexey Starikovskiy
2007-10-17  9:59                       ` John Sigler

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=4713733F.7060408@gmail.com \
    --to=aystarik@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.kernel@free.fr \
    --cc=robert.moore@intel.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