00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03)
Subsystem: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [e4] Vendor Specific Information
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) (prog-if 00 [VGA])
Subsystem: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 7
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at ee000000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 1
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 82) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: ec000000-edffffff
Prefetchable memory behind bridge: 10000000-100fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: Intel Corporation Unknown device 24c2
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=1]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=1]
Region 4: I/O ports at f000 [size=16]
Region 5: Memory at 10100000 (32-bit, non-prefetchable) [size=1K]
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02)
Subsystem: Intel Corporation Unknown device 24c2
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 5
Region 4: I/O ports at 0500 [size=32]
01:02.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05)
Subsystem: Intel Corporation PRO/1000 MT Network Connection
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (63750ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at ed000000 (64-bit, non-prefetchable) [size=128K]
Region 2: Memory at ed080000 (64-bit, non-prefetchable) [size=64K]
Region 4: I/O ports at c000 [size=64]
[virtual] Expansion ROM at 10000000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [e4] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=1
Status: Dev=00:00.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-
Capabilities: [f0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
01:03.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05)
Subsystem: Intel Corporation PRO/1000 MT Network Connection
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (63750ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at ed020000 (64-bit, non-prefetchable) [size=128K]
Region 2: Memory at ed0a0000 (64-bit, non-prefetchable) [size=64K]
Region 4: I/O ports at c400 [size=64]
[virtual] Expansion ROM at 10010000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [e4] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=1
Status: Dev=00:00.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-
Capabilities: [f0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
01:04.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05)
Subsystem: Intel Corporation PRO/1000 MT Network Connection
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (63750ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at ed040000 (64-bit, non-prefetchable) [size=128K]
Region 2: Memory at ed090000 (64-bit, non-prefetchable) [size=64K]
Region 4: I/O ports at c800 [size=64]
[virtual] Expansion ROM at 10020000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [e4] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=1
Status: Dev=00:00.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-
Capabilities: [f0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
01:05.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05)
Subsystem: Intel Corporation PRO/1000 MT Network Connection
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (63750ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 19
Region 0: Memory at ed060000 (64-bit, non-prefetchable) [size=128K]
Region 2: Memory at ed0b0000 (64-bit, non-prefetchable) [size=64K]
Region 4: I/O ports at cc00 [size=64]
[virtual] Expansion ROM at 10030000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [e4] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=1
Status: Dev=00:00.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-
Capabilities: [f0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
01:0f.0 Multimedia video controller: DekTec Digital Video B.V. DTA-105
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (4000ns min, 11750ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 9
Region 0: Memory at ed0c0000 (32-bit, non-prefetchable) [size=2K]
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?
Hello John,
> 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
I have seen this behavior earlier on a system with the SMI interrupt
disabled. I do not know if this the case here, it is just a hint.
By the way, some distros bring the CPU in a halted state on a 'halt'
command, instead of powering off (actually very logical). For real
powering off these distros require the obvious 'poweroff' command.
Some long shots, maybe it helps...
Kind Regards,
Remy
(The original message seems to have been ignored by the mailing list
robot, probably because the attachments made it too large. Re-send with
links instead of attaching the documents to the message.)
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.
>
> 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)
http://linux.kernel.free.fr/halt/config-2.6.22.1-rt9
http://linux.kernel.free.fr/halt/acpidump.txt
http://linux.kernel.free.fr/halt/dmesg.txt
http://linux.kernel.free.fr/halt/halt.txt
http://linux.kernel.free.fr/halt/lspci.txt
Do you know what could be the problem?
(Meanwhile, I will investigate Remy Bohmer's suggestion.)
Regards.
Hello Remy,
Remy Bohmer wrote:
> 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
>
> I have seen this behavior earlier on a system with the SMI interrupt
> disabled. I do not know if this the case here, it is just a hint.
Thanks for the suggestion. I didn't see anything related to SMM in the
BIOS menus. However, the system has real-time constraints. Thus, I'd
turn SMM off if I knew how :-)
Phoenix - AwardBIOS v6.00PG, An Energy Star Ally
Copyright (C) 1984-2003, Phoenix Technologies, LTD
*** NAMB-3140 BIOS V1.20 ***
03/27/2006-i845GV-W83627-6A69VAKHC-00
> By the way, some distros bring the CPU in a halted state on a 'halt'
> command, instead of powering off (actually very logical). For real
> powering off these distros require the obvious 'poweroff' command.
Good suggestion. I'm using sysvinit-2.86
http://freshmeat.net/projects/sysvinit/
AFAIU, poweroff is equivalent to halt -p
halt (no option) calls reboot(RB_HALT);
poweroff or halt -p calls reboot(RB_POWER_OFF);
man 2 reboot
Alas, when I run 'poweroff' the kernel prints the same information:
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
Regards.
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.
>
> http://linux.kernel.free.fr/halt/config-2.6.22.1-rt9
> http://linux.kernel.free.fr/halt/acpidump.txt
> http://linux.kernel.free.fr/halt/dmesg.txt
> http://linux.kernel.free.fr/halt/halt.txt
> http://linux.kernel.free.fr/halt/lspci.txt
Is there something else I can provide that might help in identifying
the problem?
Regards.
Could you please open bug at bugzilla.kernel.org and put all these files there?
Thanks,
Alex.
John Sigler wrote:
> 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.
>>
>> http://linux.kernel.free.fr/halt/config-2.6.22.1-rt9
>> http://linux.kernel.free.fr/halt/acpidump.txt
>> http://linux.kernel.free.fr/halt/dmesg.txt
>> http://linux.kernel.free.fr/halt/halt.txt
>> http://linux.kernel.free.fr/halt/lspci.txt
>
> Is there something else I can provide that might help in identifying
> the problem?
>
> Regards.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
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
(In my browser, halt output is incorrectly displayed in UTF-8.)
Regards.
Hello John,
> Thanks for the suggestion. I didn't see anything related to SMM in the
> BIOS menus. However, the system has real-time constraints. Thus, I'd
> turn SMM off if I knew how :-)
Here you can find a driver that can disable and enable the SMI
interrupt in the chipset. It supports up to the ICH5 chipsets, but by
adding the proper device/vendor IDs you can also make it support newer
chipsets.
http://www.bohmer.net/smi.tar.bz2
> AFAIU, poweroff is equivalent to halt -p
You are right.
Kind Regards,
Remy
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?
Is it a BIOS issue? a kernel issue? a hardware issue?
(All my results are attached to the bug report.)
Regards.
John Sigler 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.
>
> 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...
Regards,
Alex.
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?
>> 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.
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.
>
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?
Another observation: if I connect a screen to the system's VGA port,
when I call 'poweroff' the screen goes into power saving mode. This
seems to indicate that the integrated video card is properly shut down.
So the fans keep spinning, the LEDs keep shining, the LCD keeps
displaying, but the video card is shut down?
Might this help pinpoint the problem?
Regards.
On Tue, 16 Oct 2007, John Sigler 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?
>
> Another observation: if I connect a screen to the system's VGA port,
> when I call 'poweroff' the screen goes into power saving mode. This
> seems to indicate that the integrated video card is properly shut down.
>
> So the fans keep spinning, the LEDs keep shining, the LCD keeps
> displaying, but the video card is shut down?
>
> Might this help pinpoint the problem?
>
> Regards.
> -
Check the BIOS to see if the "Power Button" is configured to
shut the system down. Some BIOS configure APM to do what
the power button does!
Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.59 BogoMips).
My book : http://www.AbominableFirebug.com/
_
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
Dick Johnson wrote:
> John Sigler wrote:
>
>> 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?
>>
>> Another observation: if I connect a screen to the system's VGA port,
>> when I call 'poweroff' the screen goes into power saving mode. This
>> seems to indicate that the integrated video card is properly shut down.
>>
>> So the fans keep spinning, the LEDs keep shining, the LCD keeps
>> displaying, but the video card is shut down?
>>
>> Might this help pinpoint the problem?
>
> Check the BIOS to see if the "Power Button" is configured to
> shut the system down. Some BIOS configure APM to do what
> the power button does!
Here is the relevant BIOS menu.
Phoenix - AwardBIOS CMOS Setup Utility
Power Management Setup
+=====================================================+
| ACPI Function [Enabled] |
| MODEM Use IRQ [NA] |
| Soft-Off by PWR-BTTN [Instant-Off] |
| CPU THRM-Throttling [50.0%] |
| Resume by Alarm [Disabled] |
| x Date(of Month) Alarm 0 |
| x Time(hh:mm:ss) Alarm 0 : 0 : 0 |
| |
| ** Reload Global Timer Events ** |
| Primary IDE 0 [Disabled] |
| Primary IDE 1 [Disabled] |
| Secondary IDE 0 [Disabled] |
| Secondary IDE 1 [Disabled] |
| FDD,COM,LPT Port [Disabled] |
| PCI PIRQ[A-D]# [Disabled] |
| |
+=====================================================+
+===================================+
| Soft-Off by PWR-BTTN |
|-----------------------------------|
| Instant-Off ..... [v] |
| Delay 4 Sec. ..... [ ] |
| |
|-----------------------------------|
| ^V:Move ENTER:Accept ESC:Abort |
+===================================+
'Instant-Off' is the appropriate setting, right?
In a different menu, there are two other (relevant?) options:
PWRON After PWR-Fail [On]
Watch Dog Timer Select [Disabled]
Regards.
John Sigler wrote:
> +===================================+
> | Soft-Off by PWR-BTTN |
> |-----------------------------------|
> | Instant-Off ..... [v] |
> | Delay 4 Sec. ..... [ ] |
> | |
> |-----------------------------------|
> | ^V:Move ENTER:Accept ESC:Abort |
> +===================================+
>
> 'Instant-Off' is the appropriate setting, right?
Actually, default should be 4 sec delay. OS should have
a chance to shut down the system...
Alexey Starikovskiy wrote:
> John Sigler wrote:
>
>> +===================================+
>> | Soft-Off by PWR-BTTN |
>> |-----------------------------------|
>> | Instant-Off ..... [v] |
>> | Delay 4 Sec. ..... [ ] |
>> | |
>> |-----------------------------------|
>> | ^V:Move ENTER:Accept ESC:Abort |
>> +===================================+
>>
>> 'Instant-Off' is the appropriate setting, right?
>
> Actually, default should be 4 sec delay. OS should have
> a chance to shut down the system...
I don't see why this setting would have an impact on the outcome
of the 'halt' and 'poweroff' commands.
John Sigler wrote:
> Alexey Starikovskiy wrote:
>
>> John Sigler wrote:
>>
>>> +===================================+
>>> | Soft-Off by PWR-BTTN |
>>> |-----------------------------------|
>>> | Instant-Off ..... [v] |
>>> | Delay 4 Sec. ..... [ ] |
>>> | |
>>> |-----------------------------------|
>>> | ^V:Move ENTER:Accept ESC:Abort |
>>> +===================================+
>>>
>>> 'Instant-Off' is the appropriate setting, right?
>>
>> Actually, default should be 4 sec delay. OS should have a chance to
>> shut down the system...
>
> I don't see why this setting would have an impact on the outcome
> of the 'halt' and 'poweroff' commands.
>
Well, it is not possible to tell, what BIOS writer have connected to this flag...
Alexey Starikovskiy wrote:
> John Sigler wrote:
>
>> Alexey Starikovskiy wrote:
>>
>>> John Sigler wrote:
>>>
>>>> +===================================+
>>>> | Soft-Off by PWR-BTTN |
>>>> |-----------------------------------|
>>>> | Instant-Off ..... [v] |
>>>> | Delay 4 Sec. ..... [ ] |
>>>> | |
>>>> |-----------------------------------|
>>>> | ^V:Move ENTER:Accept ESC:Abort |
>>>> +===================================+
>>>>
>>>> 'Instant-Off' is the appropriate setting, right?
>>>
>>> Actually, default should be 4 sec delay. OS should have a chance to
>>> shut down the system...
>>
>> I don't see why this setting would have an impact on the outcome
>> of the 'halt' and 'poweroff' commands.
>>
> Well, it is not possible to tell, what BIOS writer have connected to this flag...
(It sucks to be stuck with a closed proprietary BIOS.)
I tested the other setting, and it didn't change anything.
The system remains powered on after executing poweroff.
Len: the system is 100% Intel (Intel CPU, Intel north bridge, Intel
south bridge, Intel integrated network controllers). Have Intel
engineers run into the same problem on a similar platform?
http://bugzilla.kernel.org/show_bug.cgi?id=9148
Regards.