linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Sigler <linux.kernel@free.fr>
To: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: robert.moore@intel.com, len.brown@intel.com
Subject: Re: halt does not shut the system down
Date: Tue, 09 Oct 2007 10:06:07 +0200	[thread overview]
Message-ID: <470B366F.4030306@free.fr> (raw)
In-Reply-To: <470A58AF.9080402@free.fr>

John Sigler wrote:

> When I run 'halt' the kernel prints:
> 
> Halting.
> Shutdown: hdc
> ACPI: PCI interrupt for device 0000:01:05.0 disabled
> ACPI: PCI interrupt for device 0000:01:04.0 disabled
> ACPI: PCI interrupt for device 0000:01:03.0 disabled
> ACPI: PCI interrupt for device 0000:01:02.0 disabled
> Power down.
> acpi_power_off called
> 
> But the system does not shut down. (The fans keep spinning, the LEDs 
> keep shining, the LCD keeps displaying.) Basically, the motherboard is 
> still providing power to every component, as if the power supply had 
> refused to stop.

If I disable the 4 integrated NICs in the BIOS, then the kernel prints:

Halting.
Shutdown: hdc
Power down.
acpi_power_off called
  hwsleep-0322 [01] enter_sleep_state     : Entering sleep state [S5]

But the system does not power down.

> Kernel is 2.6.22.1-rt9
> 
> I followed the instructions given here:
> http://bugzilla.kernel.org/show_bug.cgi?id=6431
> 
> # cat /sys/module/acpi/parameters/debug_layer
> Description                     Hex        SET
> ACPI_UTILITIES                  0x00000001 [*]
> ACPI_HARDWARE                   0x00000002 [*]
> ACPI_EVENTS                     0x00000004 [*]
> ACPI_TABLES                     0x00000008 [*]
> ACPI_NAMESPACE                  0x00000010 [*]
> ACPI_PARSER                     0x00000020 [*]
> ACPI_DISPATCHER                 0x00000040 [*]
> ACPI_EXECUTER                   0x00000080 [*]
> ACPI_RESOURCES                  0x00000100 [*]
> ACPI_CA_DEBUGGER                0x00000200 [*]
> ACPI_OS_SERVICES                0x00000400 [*]
> ACPI_CA_DISASSEMBLER            0x00000800 [*]
> ACPI_COMPILER                   0x00001000 [*]
> ACPI_TOOLS                      0x00002000 [*]
> ACPI_ALL_DRIVERS                0xFFFF0000 [*]
> -- 
> debug_layer = 0xFFFF3FFF ( * = enabled)
> 
> # cat /sys/module/acpi/parameters/debug_level
> Description                     Hex        SET
> ACPI_LV_ERROR                   0x00000001 [*]
> ACPI_LV_WARN                    0x00000002 [*]
> ACPI_LV_INIT                    0x00000004 [*]
> ACPI_LV_DEBUG_OBJECT            0x00000008 [*]
> ACPI_LV_INFO                    0x00000010 [*]
> ACPI_LV_INIT_NAMES              0x00000020 [*]
> ACPI_LV_PARSE                   0x00000040 [*]
> ACPI_LV_LOAD                    0x00000080 [*]
> ACPI_LV_DISPATCH                0x00000100 [*]
> ACPI_LV_EXEC                    0x00000200 [*]
> ACPI_LV_NAMES                   0x00000400 [*]
> ACPI_LV_OPREGION                0x00000800 [*]
> ACPI_LV_BFIELD                  0x00001000 [*]
> ACPI_LV_TABLES                  0x00002000 [*]
> ACPI_LV_VALUES                  0x00004000 [*]
> ACPI_LV_OBJECTS                 0x00008000 [*]
> ACPI_LV_RESOURCES               0x00010000 [*]
> ACPI_LV_USER_REQUESTS           0x00020000 [*]
> ACPI_LV_PACKAGE                 0x00040000 [*]
> ACPI_LV_ALLOCATIONS             0x00100000 [*]
> ACPI_LV_FUNCTIONS               0x00200000 [*]
> ACPI_LV_OPTIMIZATIONS           0x00400000 [*]
> ACPI_LV_MUTEX                   0x01000000 [*]
> ACPI_LV_THREADS                 0x02000000 [*]
> ACPI_LV_IO                      0x04000000 [*]
> ACPI_LV_INTERRUPTS              0x08000000 [*]
> ACPI_LV_AML_DISASSEMBLE         0x10000000 [*]
> ACPI_LV_VERBOSE_INFO            0x20000000 [*]
> ACPI_LV_FULL_TABLES             0x40000000 [*]
> ACPI_LV_EVENTS                  0x80000000 [*]
> -- 
> debug_level = 0xFFFFFFFF (* = enabled)
> 
> I've attached my .config and the output of the following commands:
> dmesg, lspci, acpidump, halt
> 
> Do you have any idea what the problem is?

       reply	other threads:[~2007-10-09  8:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <470A58AF.9080402@free.fr>
2007-10-09  8:06 ` John Sigler [this message]
2007-10-09 20:04   ` halt does not shut the system down 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
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=470B366F.4030306@free.fr \
    --to=linux.kernel@free.fr \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).