LinuxQuestions.org - Hangs at the end of shutdown

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - Hangs at the end of shutdown (https://www.linuxquestions.org/questions/linux-general-1/hangs-at-the-end-of-shutdown-586050/)

Hangs at the end of shutdown

My computer hangs at the very end of the shutdown procedure.
It gets as far as
"The computer will be halted immediately..." then a flashing marker _ and then it freezes.
I have to manually power it off by either cutting the power or pressing the power button for some seconds.

I have found a few threads dealing with the same or similar problems. Some suggest acpi problems, others some problem related to KDE and sound drivers. The latter seems to be more correct, cf. this thread.
The solution mentioned there does not seem to work for me though. I have tried
unloading snd_hda_intel and snd_hda_codec both in runlevel 3 and 1 before shutting down, but it still won't power off. Some have also managed to shut down properly by disabling alsa e.g. in yast before shutting down, but this does not work for me either.

I use SuSE 10.2 with an intel DG965WHMKR motherboard.
'uname -a' gives:
Linux monster 2.6.18.8-0.5-default #1 SMP Fri Jun 22 12:17:53 UTC 2007 i686 i686 i386 GNU/Linux

I appreciate any help :)

In my case I solved this problem by adding "acpi=force" as boot parameter of the boot manager, e.g.:

Code:

title=Gentoo Linux 2.6.21-gentoo-r4

root (hd0,0)

kernel /boot/kernel-2.6.21-gentoo-r4 root=/dev/sda3 acpi=force vga=791 console=tty1

ACPI has worked for me in the past too. I might suggest to rule it out in your mind, change your run level to boot up into console mode (no KDE) and shutdown form there. If it still hangs you at least know that there is a problem outside of KDE.

Thanks for helpful replys.

I tried setting acpi=force as a boot parameter with no effect. I also tried booting to runlevel 3 and then using
# poweroff to power the machine off. Exactly the same happened. This at least signifies that KDE has got nothing to do with my problem. It seems like it is an acpi-related problem. I checked the BIOS too, just to be sure, but found nothing useful there.

Also a friend of mine remembered that computers used to turn themselves off like this some years ago, before they managed to control their own power. You had to turn them off manually using the power button when they had shut down. I don't remember this but this is exactly what mine now requires. Another point in favour of acpi.

Any ideas ? I'm not very familiar with acpi. I had a look at /var/log/acpid but found nothing useful. It mostly looks like repetitions of this:

Sep 21 09:24:42 monster [acpid]: starting up
Sep 21 09:24:42 monster [acpid]: 0 rules loaded
Sep 21 09:24:44 monster [acpid]: client connected from 3693[101:102]
Sep 21 09:24:44 monster [acpid]: 1 client rule loaded
Sep 21 09:24:46 monster [acpid]: client connected from 4117[0:0]
Sep 21 09:24:46 monster [acpid]: 1 client rule loaded
Sep 21 09:24:48 monster [acpid]: client connected from 4385[0:0]
Sep 21 09:24:48 monster [acpid]: 1 client rule loaded

I really don't know - perhaps you could doublecheck if "PnP OS" is switched off in your bios - PnP is linked to ACPI for resource management. Otherwise you could try to manually remove all modules (do an lsmod to list the module names and remove each of them with modprobe -r <modulename>) just before powering off - it it still does not work you'll know that's not because of something hanging while removing modules during powerdown phase...

I guess this will have to be done in a very particular order, but I am not sure which. Can't seem to find any shutdown script either, since '/sbin/shutdown' is a binary file.
I had another look at my BIOS configuration, but there were actually no options mentioning PnP or Plug and Play.

Below is the output from

Code:

grep -i acpi /var/log/boot.msg >/tmp/boot.msg

It seems like PnP is up and working, but this is not my area of expertice...

There is a line that might hint at a solution towards the middle of the file though:
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present

I did a quick web search but got nothing particular out of it.

Code:



<4> BIOS-e820: 000000007ee68000 - 000000007eeac000 (ACPI NVS)

<4> BIOS-e820: 000000007eeac000 - 000000007eeaf000 (ACPI data)

<4> BIOS-e820: 000000007eeaf000 - 000000007eef2000 (ACPI NVS)

<4> BIOS-e820: 000000007eef2000 - 000000007eeff000 (ACPI data)

<7>ACPI: RSDP (v000 INTEL                                ) @ 0x000fe020

<7>ACPI: RSDT (v001 INTEL  DG965WH  0x00000330      0x01000013) @ 0x7eefd038

<7>ACPI: FADT (v001 INTEL  DG965WH  0x00000330 MSFT 0x01000013) @ 0x7eefc000

<7>ACPI: MADT (v001 INTEL  DG965WH  0x00000330 MSFT 0x01000013) @ 0x7eef7000

<7>ACPI: WDDT (v001 INTEL  DG965WH  0x00000330 MSFT 0x01000013) @ 0x7eef6000

<7>ACPI: MCFG (v001 INTEL  DG965WH  0x00000330 MSFT 0x01000013) @ 0x7eef5000

<7>ACPI: ASF! (v032 INTEL  DG965WH  0x00000330 MSFT 0x01000013) @ 0x7eef4000

<7>ACPI: SSDT (v001 INTEL    CpuPm 0x00000330 MSFT 0x01000013) @ 0x7eef3000

<7>ACPI: SSDT (v001 INTEL  Cpu0Ist 0x00000330 MSFT 0x01000013) @ 0x7eef2000

<7>ACPI: SSDT (v001 INTEL  Cpu1Ist 0x00000330 MSFT 0x01000013) @ 0x7eeae000

<7>ACPI: SSDT (v001 INTEL  Cpu2Ist 0x00000330 MSFT 0x01000013) @ 0x7eead000

<7>ACPI: SSDT (v001 INTEL  Cpu3Ist 0x00000330 MSFT 0x01000013) @ 0x7eeac000

<7>ACPI: DSDT (v001 INTEL  DG965WH  0x00000330 MSFT 0x01000013) @ 0x00000000

<6>ACPI: PM-Timer IO Port: 0x408

<7>ACPI: Local APIC address 0xfee00000

<6>ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)

<6>ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)

<6>ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)

<6>ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)

<6>ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])

<6>ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])

<6>ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])

<6>ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)

<6>ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)

<7>ACPI: IRQ0 used by override.

<7>ACPI: IRQ2 used by override.

<7>ACPI: IRQ9 used by override.

<6>Using ACPI (MADT) for SMP configuration information

<6>ACPI: Core revision 20060707

<6>ACPI: bus type pci registered

<6>ACPI: Interpreter enabled

<6>ACPI: Using IOAPIC for interrupt routing

<6>ACPI: PCI Root Bridge [PCI0] (0000:00)

<6>ACPI: Assume root bridge [\_SB_.PCI0] bus is 0

<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]

<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT]

<4>ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)

<4>ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 *10 11 12)

<4>ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 *11 12)

<4>ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)

<4>ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 *9 10 11 12)

<4>ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 *10 11 12)

<4>ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 *9 10 11 12)

<4>ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 *11 12)

<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]

<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]

<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]

<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]

<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]

<6>pnp: PnP ACPI init

<6>pnp: PnP ACPI: found 11 devices

<6>PnPBIOS: Disabled by ACPI PNP

<6>PCI: Using ACPI for IRQ routing

<6>ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 169

<6>ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 177

<6>ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 16 (level, low) -> IRQ 169

<6>ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 185

<6>ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 193

<6>ACPI: PCI Interrupt 0000:00:1c.4[A] -> GSI 17 (level, low) -> IRQ 177

<6>ACPI: (supports S0 S3 S4 S5)

<6>ACPI: Processor [CPU0] (supports 8 throttling states)

<6>ACPI: Processor [CPU1] (supports 8 throttling states)

<4>ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]

<3>ACPI: Getting cpuindex for acpiid 0x3

<4>ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]

<3>ACPI: Getting cpuindex for acpiid 0x4

<6>ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 19 (level, low) -> IRQ 193

<6>ACPI: PCI Interrupt 0000:00:1f.5[A] -> GSI 19 (level, low) -> IRQ 193

<6>ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 177

<6>ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 21 (level, low) -> IRQ 66

<6>ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 74

<6>ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 82

<6>ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 16 (level, low) -> IRQ 169

<6>ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 21 (level, low) -> IRQ 66

<6>ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 90

<6>ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 193

<6>ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 185

<6>ACPI: PCI Interrupt 0000:07:03.0[A] -> GSI 19 (level, low) -> IRQ 193

<6>ACPI: PCI Interrupt 0000:00:1a.7[C] -> GSI 18 (level, low) -> IRQ 185

<6>ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 169

<6>ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 90

<notice>startproc: execve (/sbin/acpid) [ /sbin/acpid ], [ CONSOLE=/dev/console ROOTFS_FSTYPE=ext3 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.86 REDIRECT=/dev/tty1 COLUMNS=156 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x31a RUNLEVEL=5 PWD=/ SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1280x1024.cfg PREVLEVEL=N LINES=60 HOME=/ SHLVL=2 splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/md0 _=/sbin/startproc DAEMON=/sbin/acpid ]

acpid: loading ACPI modules ( ac battery button ) done

acpid: will not skip unsupported modules

acpid: loading ACPI laptop modules ( ) done

Starting acpid done

<notice>startproc: execve (/usr/sbin/powersaved) [ /usr/sbin/powersaved -d -f /var/run/acpid.socket -v 3 ], [ HOME=/ PATH=/bin:/sbin:/usr/bin:/usr/sbin SHELL=/bin/sh RUNLEVEL=5 PREVLEVEL=N DAEMON=/usr/sbin/powersaved ]

I have the same problem on my Ubuntu. 7,04

Looking around on the web I found this suggestion on an OpenSuse forum.

He says that DSDT could help us.

Quote:

Howto Fix Your Buggy DSDT., Yes you most probably have one!

http://www.suseforums.net/index.php?...=13893&hl=dsdt

I am a totally new user of Ubuntu so I can't test OpenSuse but maybe Suse have a similar way of fixing this DSDT?
How much does OpenSuse and Suse and Ubuntu differ? if it works for OpenSuse then maybe it works for us too?

In the fedora community one user wrote this:

Quote:

the problem occurs when I activate the desktop effects. I have been reading a lot of posts about desktop effects and shutting down problems and it appears that there is no solution. Do you know how to fix this?? I will keep my desktop effects off until I find a solution because it is really annoying not being able to shut down correctly.

http://forums.fedoraforum.org/forum/...61&postcount=7

As a newbie I have no idea what he refers to as "desktops effects".

how do I know if I have such in Ubuntu?

My problem has nothing to do with desktop effects at least. If I boot directly into runlevel 3 (shell only), I still have the same problem with shutdown.

I'll have a look at DSDT...

Sorry, as you see all users do their best to help each other and what we really need is that the programmers of the Kernel if the problem are there could find a way to make it known.

That was why I asked. Are there any distro that doesn't have this problem?