Author Topic: SOLVED - Shutdown won't (Read 2456 times)

AS · « **Reply #30 on:** July 05, 2011, 05:38:40 AM »

Try to reboot your machine, at grub screen press F3, select default and then add the parameters acpi=force apm=off,
later start the shutdown and let us know if it work.

if still not working, please post your /var/log/dmesg

Maurice · « **Reply #31 on:** July 05, 2011, 06:07:30 AM »

Quote from: as on July 05, 2011, 05:38:40 AM

Try to reboot your machine, at grub screen press F3, select default and then add the parameters acpi=force apm=off,
later start the shutdown and let us know if it work.

if still not working, please post your /var/log/dmesg

I did this and selected default but all I got was a line of parameters with no seeming method of adding to it or altering it. No way to force acpi and apm was not there.

The dmesg was really huge - perhaps over 500 lines.. Do you want it all?

AS · « **Reply #32 on:** July 05, 2011, 06:13:19 AM »

Quote from: Maurice on July 05, 2011, 06:07:30 AM

Quote from: as on July 05, 2011, 05:38:40 AM
Try to reboot your machine, at grub screen press F3, select default and then add the parameters acpi=force apm=off,
later start the shutdown and let us know if it work.

if still not working, please post your /var/log/dmesg

I did this and selected default but all I got was a line of parameters with no seeming method of adding to it or altering it. No way to force acpi and apm was not there.

strange, once the parameters are visible you should be able to move across the line using right-arrow and left-arrow and of course to add one or more parameters.

Quote

The dmesg was really huge - perhaps over 500 lines.. Do you want it all?

let start with something less: type the following commands:
dmesg | grep -i acpi

Maurice · « **Reply #33 on:** July 05, 2011, 06:21:02 AM »

Quote from: as on July 05, 2011, 06:13:19 AM

let start with something less: type the following commands:
dmesg | grep -i acpi

Code: [Select]

[mihi@localhost ~]$ dmesg | grep -i acpi
 BIOS-e820: 00000000ce76f000 - 00000000ce830000 (ACPI NVS)
 BIOS-e820: 00000000cfb8d000 - 00000000cfbe5000 (ACPI NVS)
 BIOS-e820: 00000000cfbea000 - 00000000cfbf3000 (ACPI data)
 BIOS-e820: 00000000cfbf4000 - 00000000cfbff000 (ACPI data)
ACPI: RSDP 000fe020 00014 (v00 INTEL )
ACPI: RSDT cfbfd038 0005C (v01 INTEL  DG33FB   00000197      01000013)
ACPI: FACP cfbfc000 00074 (v01 INTEL  DG33FB   00000197 MSFT 01000013)
ACPI: DSDT cfbf8000 03DAD (v01 INTEL  DG33FB   00000197 MSFT 01000013)
ACPI: FACS cfb98000 00040
ACPI: APIC cfbf7000 00078 (v01 INTEL  DG33FB   00000197 MSFT 01000013)
ACPI: WDDT cfbf6000 00040 (v01 INTEL  DG33FB   00000197 MSFT 01000013)
ACPI: MCFG cfbf5000 0003C (v01 INTEL  DG33FB   00000197 MSFT 01000013)
ACPI: ASF! cfbf4000 000A6 (v32 INTEL  DG33FB   00000197 MSFT 01000013)
ACPI: SSDT cfbf2000 00204 (v01 INTEL     CpuPm 00000197 MSFT 01000013)
ACPI: SSDT cfbf1000 001F9 (v01 INTEL   Cpu0Ist 00000197 MSFT 01000013)
ACPI: SSDT cfbf0000 001F9 (v01 INTEL   Cpu1Ist 00000197 MSFT 01000013)
ACPI: SSDT cfbef000 001F9 (v01 INTEL   Cpu2Ist 00000197 MSFT 01000013)
ACPI: SSDT cfbee000 001F9 (v01 INTEL   Cpu3Ist 00000197 MSFT 01000013)
ACPI: SSDT cfbed000 000DD (v01 INTEL   Cpu0Cst 00000197 MSFT 01000013)
ACPI: SSDT cfbec000 000DD (v01 INTEL   Cpu1Cst 00000197 MSFT 01000013)
ACPI: SSDT cfbeb000 000DD (v01 INTEL   Cpu2Cst 00000197 MSFT 01000013)
ACPI: SSDT cfbea000 000DD (v01 INTEL   Cpu3Cst 00000197 MSFT 01000013)
ACPI: Local APIC address 0xfee00000
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: Checking initramfs for custom DSDT
ACPI: Core revision 20110112
ACPI: bus type pci registered
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: No dock devices found.
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
 pci0000:00: Requesting ACPI _OSC control (0x1d)
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 *11 12)
PCI: Using ACPI for IRQ routing
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active)
pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:07: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:09: Plug and Play ACPI device, IDs PNP0003 (active)
pnp: PnP ACPI: found 10 devices
ACPI: ACPI bus type pnp unregistered
Switching to clocksource acpi_pm
pata_acpi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pata_acpi 0000:03:00.0: setting latency timer to 64
pata_acpi 0000:03:00.0: PCI INT A disabled
ACPI: acpi_idle registered with cpuidle
ACPI: Sleep Button [SLPB]
ACPI: Power Button [PWRF]
[mihi@localhost ~]$

AS · « **Reply #34 on:** July 05, 2011, 06:31:18 AM »

Your ACPI subsystem is clearly enabled and doesn't show anything wrong... try to check your BIOS settings ...

what's your motherboard brand/model ?
Also, I see from your grub/menu.lst you have 2 kernel installed, are both kernels affected from the shutdown issue ?

Maurice · « **Reply #35 on:** July 05, 2011, 06:43:31 AM »

Quote from: as on July 05, 2011, 06:31:18 AM

Your ACPI subsystem is clearly enabled and doesn't show anything wrong... try to check your BIOS settings ...

what's your motherboard brand/model ?
Also, I see from your grub/menu.lst you have 2 kernel installed, are both kernels affected from the shutdown issue ?

Afraid I'll have to leave replying to this till tomorrow AS. My wife's going on an overseas trip early in the morning so I'll have to help her out with the final packing. It's probably getting to the early hours in your part of the world too.

Incidentally I just tried shutting down after closing my net connection but it still failed to power off.

Maurice · « **Reply #36 on:** July 05, 2011, 10:27:04 PM »

Quote from: as on July 05, 2011, 06:31:18 AM

Your ACPI subsystem is clearly enabled and doesn't show anything wrong... try to check your BIOS settings ...

what's your motherboard brand/model ?
Also, I see from your grub/menu.lst you have 2 kernel installed, are both kernels affected from the shutdown issue ?

Well - despite a scare with a late taxi, the wife's away.

Not sure what to look for in the bios settings and not sure what my motherboard brand and model are either.

Short of opening up the box I don't know where to find them.

I logged in to the older (33) kernel version three times and each time it Shutdown immediately. But the loops were still there. So - this might be a workaround, but not a satisfactory one.

Archie · « **Reply #37 on:** July 05, 2011, 10:39:01 PM »

Good to have a little scare every now and then. I hope your wife has a safe and pleasant flight.

Well, from what we know so far. Shutdown is good with 2.6.33.5 (?) ... isn't that supposed to be a 7?? ... but not with 2.6.38.8.

I also noticed that your older kernel is a BFS and your newer is PAE. Is this because of your 4Gb RAM?

Maurice, do you think you could install 2.6.38.8 BFS and see how that kernel performs on shutdown?? And You might also try reinstalling the PAE ... maybe the modules didn't build correctly.

But wait for as' diagnostic because he is the master-in-disguise, and I am just a padawan.

Maurice · « **Reply #38 on:** July 06, 2011, 01:46:12 AM »

Quote from: Archie on July 05, 2011, 10:39:01 PM

Good to have a little scare every now and then. I hope your wife has a safe and pleasant flight.

Well, from what we know so far. Shutdown is good with 2.6.33.5 (?) ... isn't that supposed to be a 7?? ... but not with 2.6.38.8.

I also noticed that your older kernel is a BFS and your newer is PAE. Is this because of your 4Gb RAM?

Maurice, do you think you could install 2.6.38.8 BFS and see how that kernel performs on shutdown?? And You might also try reinstalling the PAE ... maybe the modules didn't build correctly.

But wait for as' diagnostic because he is the master-in-disguise, and I am just a padawan.

Yes I used the PAE kernel on advice from a previous thread, to make use of the ram

I have just reinstalled the BSF.PAE and then installed the plain BSF as you suggested. I had a bit of trouble as my pass repo was playing up so I had to go to heanet.

However there was improvement with either, in fact it wouldn't even start with the BFS kernel. The verbose showed that it was starting the modules painfully slowly so it might have started if I'd waited..

Archie · « **Reply #39 on:** July 06, 2011, 01:53:16 AM »

Quote from: Maurice on July 06, 2011, 01:46:12 AM

Quote from: Archie on July 05, 2011, 10:39:01 PM
Good to have a little scare every now and then. I hope your wife has a safe and pleasant flight.

Well, from what we know so far. Shutdown is good with 2.6.33.5 (?) ... isn't that supposed to be a 7?? ... but not with 2.6.38.8.

I also noticed that your older kernel is a BFS and your newer is PAE. Is this because of your 4Gb RAM?

Maurice, do you think you could install 2.6.38.8 BFS and see how that kernel performs on shutdown?? And You might also try reinstalling the PAE ... maybe the modules didn't build correctly.

But wait for as' diagnostic because he is the master-in-disguise, and I am just a padawan.

Yes I used the PAE kernel on advice from a previous thread, to make use of the ram

I have just reinstalled the BSF.PAE and then installed the plain BSF as you suggested. I had a bit of trouble as my pass repo was playing up so I had to go to heanet.

However there was improvement with either, in fact it wouldn't even start with the BFS kernel. The verbose showed that it was starting the modules painfully slowly so it might have started if I'd waited..

I'm sure you're aware that in installing/reinstalling new kernels, the modules have to be rebuilt again ... which usually takes any time between 3 to ten minutes. And after the mods had been built, they will be OK.

AS · « **Reply #40 on:** July 06, 2011, 04:03:44 AM »

At this point I'm unsure about the whole issue, re-read the whole thread:

- kernel-2.6.33.5.bfs is working as expected
- kernel-2.6.38.8.pae-bfs doesn't shutdown correctly

other users look live having some/similar shutdown issue using 2.6.38.8 kernel, but a custom 2.6.36.x works:
http://www.pclinuxos.com/forum/index.php/topic,92384.0.html

this bug from fedora look to me very similar to your issue:
https://bugzilla.redhat.com/show_bug.cgi?id=712060

all the above point the finger to some change in 2.6.38.8 kernel, while previous kernels (< 2.6.37.x) look like to not be affected.

Debugging this issue can be very difficult an time consuming, I would suggest to install kernel 2.6.33.7.pae.bfs,
until someone will find the underlying issue and possibly the solution.

(a note about the "loop" dependency you notice at shutdown: some service depends from other services, which in turn may depend
from the first, these messages only note about this "dependency loop" but are otherwise harmful, do not worry about that).

AS

Maurice · « **Reply #41 on:** July 06, 2011, 04:48:10 AM »

Quote from: as on July 06, 2011, 04:03:44 AM

At this point I'm unsure about the whole issue, re-read the whole thread:

- kernel-2.6.33.5.bfs is working as expected
- kernel-2.6.38.8.pae-bfs doesn't shutdown correctly

other users look live having some/similar shutdown issue using 2.6.38.8 kernel, but a custom 2.6.36.x works:
http://www.pclinuxos.com/forum/index.php/topic,92384.0.html

this bug from fedora look to me very similar to your issue:
https://bugzilla.redhat.com/show_bug.cgi?id=712060

all the above point the finger to some change in 2.6.38.8 kernel, while previous kernels (< 2.6.37.x) look like to not be affected.

Debugging this issue can be very difficult an time consuming, I would suggest to install kernel 2.6.33.7.pae.bfs,
until someone will find the underlying issue and possibly the solution.

(a note about the "loop" dependency you notice at shutdown: some service depends from other services, which in turn may depend
from the first, these messages only note about this "dependency loop" but are otherwise harmful, do not worry about that).

AS

That did it AS.

I installed kernel 2.6.33.7-pclos6.pae (There was no 2.6.33.7-pclos6.bsf.pae). checked it three times and it shut down perfectly each time - reasonably fast too.

Archie
I'm sure you're aware that in installing/reinstalling new kernels, the modules have to be rebuilt again ... which usually takes any time between 3 to ten minutes. And after the mods had been built, they will be OK.

Kindly put Archie. I'd forgotten that.

This is a relief - thanks for all the help guys - it was very much appreciated. Now to mark it SOLVED.

PCLinuxOS-Forums

News:

Author Topic: SOLVED - Shutdown won't (Read 2456 times)

AS

Re: Shutdown won't

Maurice

Re: Shutdown won't

AS

Re: Shutdown won't

Maurice

Re: Shutdown won't

AS

Re: Shutdown won't

Maurice

Re: Shutdown won't

Maurice

Re: Shutdown won't

Archie

Re: Shutdown won't

Maurice

Re: Shutdown won't

Archie

Re: Shutdown won't

AS

Re: Shutdown won't

Maurice

Re: Shutdown won't