*** Bug 331701 has been marked as a duplicate of this bug. ***

This is happening to me as well. I have a x86 machine and I tried disabling the firewall, but had no luck.

Is this on a multi-processor machine?

Can you attach the output of 'hwinfo'?

Created attachment 177079 [details]
HWINFO

This is an old pc and not a multi-processor machine & hwinfo is attached.

Can you try the next kernel-of-the-day which will come out tomorrow?  There is a fix for something like this and I think it might solve your issue.

Sure why not.

So, There is a new kernel coming out? Is it going to be in the updater?

No, not yet, this is in the "kernel-of-the-day" as found on our ftp site at:
http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/

I have seen the same bug on a Compaq Pressario v6000.

What a bummer the kernel update didn't do anything now what

I have not tried it, But there is another kernel security update today. I will try it. Wish me luck!

Sadly, The update did not work.

For now, I'm going to go back to 10.0.

So, what was actually there in the kernel update if the problem still exists

Ok back to Ubuntu 6.06 

Hm, for some reason the KOTD isn't being updated with the latest changes.

You should see something in the changelog talking about upgrading to the 2.6.22.10-rc1 kernel, if not, then the fix is not in the updated kernel, and nothing should have changed.

Let me go download the rpm and check it out.

As for moving back to ubuntu, that's fine, you will run into the same problem when they upgrade their kernel to a newer one :)

Ok, sorry, the kernel-of-the-day does not have this bugfix in it, so it would not make any difference.  Let me figure out how to get an update out there...

Thanks for your help! Can you let me know when there is an update? Because, I will move back to 10.3.

Ok, please try the updated kernel at http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/i386/ now, it should have the shutdown fix in it and let me know if it solves the problem or not for you.

What file should we download?

I tried it and it did not work. I downloaded kernel-debug-2.6.22.10-20071011115904.i586.rpm off the site and installed it using yast. I know it installed properly. It also appeared in the GRUB Menu and booted up fine, But it has not fixed the shutdown problem.

I reverted back to suse 10.1, But what is the status of the shutdown hang?

The Description of the last three visible lines is identical to the case in bug <https://bugzilla.novell.com/show_bug.cgi?id=274042>.
I had the same phenomenon, when I used acpi=off boot parameter.
As I understand, the system doesn't power off w/o acpi, so these lines are the last messages that may appear, there may be no firewall issue at all...

Should we wait till there is a new kernel version out?

Created attachment 181744 [details]
Hardware Info, Toshiba P35-S629

The same problem occurs on the Toshiba Satellite P35. However, the Toshiba hangs of reboot (before the initial shutdown completes) but will shutdown. So this is the same symptoms applied to reboot instead of sd.

(In reply to comment #26 from david rankin)
> Created an attachment (id=181744) [details]
> Hardware Info, Toshiba P35-S629
> 
> The same problem occurs on the Toshiba Satellite P35. However, the Toshiba
> hangs of reboot (before the initial shutdown completes) but will shutdown. So
> this is the same symptoms applied to reboot instead of sd.
> 

NOTE: my e-mail is now drankinatty@suddenlinkmail.com. The cox account is inactive and I can't find where to change it on bugzilla.novell.com.

I just installed the 10.3 boxed version yesterday and have this same bug, will not shutdown. Intel P3, 866MHZ Micron Millemia. AIM BIOS. I know BIOS is older than cutoff date of 2001. I had the same problem with 10.2 and it was fixed by booting with ACPI=Force, ACM=0 or something like that. Cannot find where I wrote it down. If you think the new RPM mentioned above will work, I can try it.

It looks like there is a few more updates on the ftp server. I will try those. I'm currently at 10.1, But when I get a second I will go back to 10.3. Wish me Luck!

I have the same problem after updating the kernel yesterday...
After "The System will be halted immediately" nothing happens.

Same problem after kernel update - I will check next weekend...

Are you sure it is the kernel? Because, I'm currently at 10.1 and I think I'm running the latest version of the kernel. I will try and find out if I'am. If I'm not I will go to the ftp site and install the latest kernel in 10.1. Than we will go from there.

I have the same problem on a dell inspiron 1501 with a 64 amd turion chip. No shutdown after update possible. i downgraded the kernel. Interesting: no problems on my older pc. it's i686 machine with a amd athlon xp 2.4

Strange! If someone from Novell can tell us the status on this bug that would be great!

We are very slowly still working on this, sorry...

Don't worry about it. I'm still on 10.1 and it is fine for now. But, When do you think this will be fixed?

It is impossible to determine given that we still don't know why this is happening...

If you need anymore info from me, Like log files. I will try my best to give them to you. If I install a kernel version from a year ago, Will it work?

nothing changed after a new installation. my dell inspiron will only shutdown manually. i tried bootloader option apci=force, senseless. my old i686 machine works perfectly. sorry novell, but this is disappointing - the new kernel patch was marked as a security update.......:-(

Ah, I think this is a SMP issue, can someone please try booting with the "nosmp" or "maxcpus=0" command line added to the kernel and let me know if that changes anything or not on the shutdown?

hi greg, i gave it a try, but it changed nothing on my dell inspiron. i had a response on the console like: "ata1: failed some devices" or something like that und booting was much much slower than normal. 

Peter, is your machine a multi-processor box or single processor machine?  I think this should only fix the single processor ones...

@Greg: my laptop (dell inspiron 1501) is a multi-processor machine. and i tried booting with "nosmp" and later with "maxcpus=0" on a fresh openSUSE 10.3 installation. but shutdown keeps on hanging......

I believe this is a timing issue.
I performed a few boot-shutdown cycles and sometimes the system is turned off, sometimes not.
I can't discern a real pattern.

Is this a similar problem to the one solved in Bug 332845?

model name      : Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz

As already mentioned in comment 44 I suspect a timing issue.
Now - notwithstanding that I'm not really knowing what I'm doing - I inserted following lines into
/etc/init.d/halt.local
#####
echo -n Letting the system settle.
for i in `seq 10`; do
    echo -n "  ."
    sleep 1
done
echo
#####

I tried a system halt more than 5 times and the system always powered off.
So this might be a work around...

It could be a work around. I just switched to Fedora 8 and it is running the kernel from opensuse 10.3. No problems.

Peter, thanks for testing.

And yes, it is a timing issue, one I suspect dealing with the hotplug cpu sleep stuff, I'm still trying to track it down...

OK, I'm that we now what it is. We are making progress.

some folks on suseforums.net had success with changing boot.grub menue. i will try booting with acpi=force, perhaps this will help.

See also: 
http://www.suseforums.net/index.php?showtopic=33291&hl=shutdown+hang

....okay, okay.....it doesn't work. no change in behaviour.

That is a bummer. I installed Ubuntu 7.10 yesterday and it is shutting down fine. I think we should rule out a Kernel Bug.

What was the kernel version in Ubuntu 7.10?

If people upgrade to the FACTORY kernel version (2.6.24-rc2), does this problem go away for them?

I'm not sure what the kernel version is in Ubuntu 7.10, But I will check and get back to you. I still have not had time to do the updates in 7.10, So the shutdown may hang after the updates.

Ubuntu 7.10 is running kernel version 2.6.22-14-generic

@ Greg: i upgraded to kernel version ftp://ftp.suse.com/pub/projects/kernel/kotd/SL103_BRANCH/i386/kernel-default-2.6.22.13-SL103_BRANCH_20071120141840.i586.rpm

but no success, my dell inspiron keeps on hanging when shutdown. i suppose this is no kernel bug.....??

No, can you try the KOTD from HEAD instead?  It should be 2.6.24-rc2 based (don't know if it moved to -rc3 yet or not...)

I think it´s rc3 meanwhile. Yes, i will try it this afternoon and let you know what happened.....

*** Bug 343225 has been marked as a duplicate of this bug. ***

Hi,

I installed yesterday Suse 10.3 with all the updates.  When I do a shut down, Suse seems to close but it doesn't stop the power supply.  Before the install of Suse 10.3 I had Windows XP on the same computer without getting a shut down bug.  Of course the hardware was the same for XP and Suse 10.3.

Here is the last lines I have when I shut down Suse 10.3:


...
Unmounting file systems
securityfs unmounted
/dev/sdc3 unmounted
devpts unmounted
debugfs unmounted
/dev/sdc1 unmounted
Stopping udevd:

The system will be halted immediately
Master Resource Control: runlevel 0 has been
Skipped services in runlevel 0:
_



That is it!  The power supply stills running.

Yes, we realize this is an issue and are working to figure it out...

That is happening to me to. But, The problem is not the power supply. I think it could be the motherboard not halting the system or a command that is not being completed. When I shut it off and listen closely to the system it sounds like it has shut everything off except for the power supply, but the screen is still on meaning there is more than that.

...perhaps this is the solution. i tried installing the kotd you recommended greg. but after that the booting of opensuse stopped just when the system tries to initialize the powersupply daemon. i tried booting suse again and again but booting stopped every time when powersupply daemon comes into it......

@greg: 
it seems that this bug is happening also with ubuntu users. Searching i found this bug report:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/119308

looks very similiar to what we are experiencing. At the end of this bug report there is a workaround mentioned. i don´t know if this is also a possible solution for opensuse-users.

I'm currently running Ubuntu 7.10 and have no problems. If anyone could try modifying the lines in a text editor and let us know how it goes.

I found the following yesterday on my SUSE 10.3 system. If I chg the boot command line to acpi=force and apm=off my system will shut off.

System P3 Intel, 768 MB, 866MHZ Note the boot says the BIOS is older than 2001 and acpi is not present. 

My P4, ASUS 3,2MHZ 4GB with SUSE 10.2 shutdown Ok, No Mod. It seems I had this problem when 10.2 was on the P# system but it was fixed by adding the above command to a config file. I cannot remember which one. 

If you would like me to test the above mods, let me know what to modify and I will.

Thanks for testing it. How did you change the boot command line? Did you do it at the Grub Menu? If you can test the mods above that would be great!

Yes I changed it at the grub menu this time. On 10.2 I changed one of the config files but forgot which one. i thought I wrote it down but did not. If Ikdepim-users@kde.org remember it may have been under YaSt --> System --> /etc/sysconfig editor. But I don't find it there now on 10.2, so I must have modified one of the etc files.

Which mod are you refering to above? By the way my 10.3 kernel is 2.6.22.12-0.1-default

Referring to #61, thats what my system sounds like also without the command at grub boot.

*** Bug 341956 has been marked as a duplicate of this bug. ***

Can people try adding "acpi=off api=on" to their grub kernel command line when booting to see if that helps here?

no good news greg. i added acpi=off and api=on to grub kernel command line. i was shutting down first with gnome gui and second with shutdown -h now. but without success. Terminal tolds:

"The system will be halted immediately
Master Resource Control: runlevel 0 has been reached
Skipped services in runlevel 0: SuSEfirewall2_setup
Stty_ standard input: unable to perform all requested operations"

I hope there are any information you need.....

..one more hint:

when i shutdown my laptop i get this message:

"Running /etc/init.d/halt.local
gdm [2768]: WARNING: Failed to connect to socket /var/run/dbus/system_bus_socket"

I just did some testing on my older system. P3 Intel Tanzer board, 866mhz Award Bios. SUSE 10.3 (2.6.22.12-0.1-default) No actual acpi in BIOS. Tried several combinations:

Nothing in Grub command line:        Hangs as described above
acpi=force                           Hangs as described above
acpi=force apm=off:                  Shutsdown
acpi=force api=off:                  Shutsdown
acpi=force api=on:                   Shutsdown
acpi=force api=on apm=off            Shutsdown
All above were with factory DVD in Drive

Removing factory DVD made no difference in above results.

@ Russ: I tested your combinations on my dell inspiron 1501, 1.6 Ghz AMD Turion, 1024 MB RAM, openSUSE 10.3 (2.6.22.12-0.1-default) with these results:

acpi=force apm=off:                  no shutdown
acpi=force api=off:                  no shutdown
acpi=force api=on:                   no shutdown
acpi=force api=on apm=off            no shutdown

The last commands (acpi=force api=on  and   acpi=force api=on apm=off) brought once again this message:

"Running /etc/init.d/halt.local
gdm [2768]: WARNING: Failed to connect to socket
/var/run/dbus/system_bus_socket"

Did anybody else try the delay "work around" as described in comment 45?
Did they succeed?

I'm also experiencing this problem with a Core 2 Duo 6600, but not on every shutdown (exactly as described in comment #44). However, the last lines on the screen look like this:

Unmounting file systems
rpc_pipefs umounted
securityfs umounted
/dev/sda1 umounted
devpts umounted
debugfs umounted
/dev/sda3 umounted                                        done
Stopping udevd:                                           done
                                                          done
The system will be halted immediately.

I don't have the lines with runlevel 0 or the firewall. Moreover, it's strange that I've only 3 "done"s at the positions as above, but that might be normal.

@Peter: i will try the workaround described in comment #44 and will tell you my results.

I just tried the workaround described in #44. It did not work! I even changed the Sleep to 15. went back to one of the ones in #72 that worked. It may be BIOS related since it works on some System and not others. My system is a Micron Millinea. My system was purchased in 1999. No BIOS updates. Boot says BIOS older than 2001 for acpi stuff. Looking in actual BIOS there are no options for acpi.

The message with the #44 work around is Master Resource Control: runlevel 0 has been reached
Skipped services in runlevel 0   SuSEfirewall2_setup.

I tried also the workaround described in comment #44. But: no success at all. no shutdown on my dell inspiron. is there anybody who could give some advice what to do? wait for a knew kernel or what?

....one additional comment from me:
i tried installing the x86-64bit version of opensuse 10.3 on my laptop - the first time. the result was: i could shutdown my dell inspiron twice without problems. could it be that it's necessary to install the 64bit-version on a multiprocessor machine? i thought it's not......
meanwhile shutdown hangs once again - even with 64bit-installation......

*** Bug 345200 has been marked as a duplicate of this bug. ***

*** Bug 344581 has been marked as a duplicate of this bug. ***

*** Bug 344952 has been marked as a duplicate of this bug. ***

Created attachment 185591 [details]
This patch resolved the problem in the RT Kernel, by backing out hunk from 2.6.22.10

Will this patch come as an update?

(In reply to comment #83 from Sven Dietrich)
> Created an attachment (id=185591) [details]
> This patch resolved the problem in the RT Kernel, by backing out hunk from
> 2.6.22.10
> 

Hm, that kind of makes sense.

Can anyone build their own kernel and try this change out?  It will be a day or so before I can get a test kernel out for this due to travel issues...

*** Bug 345511 has been marked as a duplicate of this bug. ***

*** Bug 341117 has been marked as a duplicate of this bug. ***

Sven, your change might work for the people who are suddenly seeing a regression, as it just reverts a .10 patch that was added to try to _fix_ this issue :(

For the others, this problem has always been there, and I thought that the patch would help fix it.  I'll back it out upstream, which should fix it for one class of people, but for the original group, no such luck...

*** Bug 345682 has been marked as a duplicate of this bug. ***

My dell inpiron 1501 fails to shutdown as well, with kernel 2.6.22.12
so I am running 2.6.22.9-0.4 now, since id like to shutdown :D does this appear to be the same bug? or is this problem solved in 2.6.22.13 (id really not like to mess with ati driver if at all possible :D)

As I wrote in my duplicated bug report (Sorry I didn't found this bug report), on my system this bug occurs after a kernel update.

After kernel update 2.6.22.12-0.1 the system don't power off. With earlier kernel, power off works. Later kernel updates also don't power off. I use the 64 Bit version of openSUSE 10.3. with an AMD 64 Bit dual core on an Asus Mainboard M2N 1349.

Exactly the same behaviour on my HP Compaq 6715s (AMD Turion 64 X2 mobile, openSuse 10.3, 32 bit): kernels starting from 2.6.22.12-0.1 (including the latest 2.6.22.13-0.3) fails to shutdown thus I am running 2.6.22.9-0.4 for now. (Sorry for duplicated report 341117).

I tried opensuse 11.0 Alpha0 and seeing the same problem. That is also running a different kernel version.

(In reply to comment #88 from Greg Kroah-Hartman)
> Sven, your change might work for the people who are suddenly seeing a
> regression, as it just reverts a .10 patch that was added to try to _fix_ this
> issue :(
> 

I found this as regression after updating SLE-RT to .10, via bisect, so it definitely tripped up RT. Usually when things like this show up in RT, and sporadically in other Kernels, a race is to blame.

> For the others, this problem has always been there, and I thought that the
> patch would help fix it.  I'll back it out upstream, which should fix it for
> one class of people, but for the original group, no such luck...
> 

I actually need to be near the machines to test this (to see if it powers down).
I added Ken Johnson, who now has the 8-way Intel where I first saw the issue (although it also affected an AMD box, iirc). Maybe Ken can install a current 10.3 RPM on the Intel and see if it powers down.

*** Bug 347277 has been marked as a duplicate of this bug. ***

The next kernel-of-the-day, based on 2.6.22.15 should fix the machines that regressed from the older 2.6.22.10 patch that was added.

Now to work on the older problem of machines that do not work for either "fix"...

I have installed this kernel
kernel-debug-2.6.22.15-SL103_BRANCH_20071216004958.x86_64
the problem is fixed

Will there be an official update via YOU?

It's Fixed? It there a 32 Bit patch?

Yes I also need a 32 bit patch. My kernel is linux-bt1m 2.6.18.8-0.7-bigsmp. Will there be a kernel update from You?

*** Bug 349076 has been marked as a duplicate of this bug. ***

okay, i have installed kotd 2.6.22.15-SL103_BRANCH_20071217210116-default i686
the problem is fixed so far with my dell inspiron 1501

Peter, Do you remember what the link was on 2.6.22.15-SL103_BRANCH_20071217210116-default i686?

Julian, the link is
ftp://ftp.suse.com/pub/projects/kernel/kotd/SL103_BRANCH/i386/

Good luck!

*** Bug 351321 has been marked as a duplicate of this bug. ***

*** Bug 351511 has been marked as a duplicate of this bug. ***

Solucionado.

Kernel 2.6.24-rc7-gd0c4c9d4-15-default

http://download.opensuse.org/repositories/Kernel:/Vanilla/openSUSE_10.2/i586/

perdon.

el nuevo kernel lo baje de:

http://download.opensuse.org/repositories/Kernel:/Vanilla/openSUSE_10.3/i586/

Gracias.

did the vanilla download fix this? My kernel is 2.6.22.13-0.3-default, is there an update for it?

Thanks

I have not had a second the try the patches. I will reply back when I do.

Sadly I had no luck. It is really weird it is working for Peter. But, my system is getting older so that probably has something to do with it. Hopefully, it will be resolved by the time opensuse 11.0 beta 1 is released.

(In reply to comment #110 from Julian Medina)
> Sadly I had no luck. It is really weird it is working for Peter. But, my system
> is getting older so that probably has something to do with it. Hopefully, it
> will be resolved by the time opensuse 11.0 beta 1 is released.
> 

Julian, meanwhile i changed kernel to ftp://ftp.suse.com/pub/projects/kernel/kotd/SL103_BRANCH/i386/kernel-default-2.6.22.16-SL103_BRANCH_20080123142852.i586.rpm

hopefully this will work for you, it worked for me.
cheers

*** Bug 357265 has been marked as a duplicate of this bug. ***

getting very sick of this bug... can someone pls tell me when it will be fixed or a way to prevent opensuse updater (KDE) from notifying me and having a reg triangle. 

Duplicate bug reporter:-

I can confirm that kernel update available via YOU 10.3
2.6.22.16-0.1
has CORRECTED power down/system hang on
Processor (CPU): AMD Athlon(tm) 64 X2 Dual Core Processor 4800+
Speed: 2,511.39 MHz
Cores: 2
With Motherboard ASUS M2N-MX SE 
Attn Bernd Lachner - This may be of interest to you ;-)
Attn Andrew Sorensen - Open Yast>Online update - Note errors - Possibly an issue I experienced a bug reported on errors in resolving dependencies in X64_86 systems ????? ;-)
One day suspend to RAM may actually work for us all - apologies different bug.

*** Bug 339311 has been marked as a duplicate of this bug. ***

(In reply to comment #114 from Scott Couston)
> Duplicate bug reporter:-
> 

Unfortunately, the kernel update 2.6.22.16-0.1 did not fix the problem on my Compaq Presario V4000 w Centrino 1.7 GHz CPU. The interesting thing is that the problem occurs ONLY when I attempt to reboot/shut down the computer when no user is logged in (directly via SuSE splash screen). As long as I am logged on via KDE GUI as any user, the computer restarts/shuts down just fine.

I upgraded my kernel to 2.6.22.16-0.2 and because I was curious, I tried to reboot the computer from the splash screen via KDE GUI. To my surprise the computer rebooted fine. Then I logged on as a certain user, logged off again (ended GUI session) and attempted to reboot the computer via the splash screen once more. Guess what! The computer froze. I suspect it has something to do with a wireless network card. The computer rebooted okay when the wireless ethernet connection was inactive. As soon as I activated the connection to an access point when I was logged on, the computer was unable to reboot again via the splash screen.

(In reply to comment #117 from Jan Zitnansky)

Well, I was obviously wrong about the radio. The OS often gets hanging though the computer is not connected to any network.

I got the same problem

My laptop ran fine with 10.2
at the update to 10.3 it did not turn off

DELL Inspiron 1501 AMD Thurion dual core 64bits

Greetings

I still haven't had a second to test the new kernel out. I may test the alpha version of 11.0 and see if that doesn't fix the problem.

(In reply to comment #120 from Julian Medina)
> I still haven't had a second to test the new kernel out. I may test the alpha
> version of 11.0 and see if that doesn't fix the problem.
> 

I still see the issue on a(In reply to comment #119 from Alex Rodriguez)
> I got the same problem
> 
> My laptop ran fine with 10.2
> at the update to 10.3 it did not turn off
> 
> DELL Inspiron 1501 AMD Thurion dual core 64bits
> 
> Greetings
> 

I still see the issue on a Dell 7500 Inspiron that I inherited end of 07.
No time to bisect things at this point - sorry.

with 2.6.22.17-0.1-default, the issue is still present for a Dell Dimension 4100

(In reply to comment #122 from David Rankin)
> with 2.6.22.17-0.1-default, the issue is still present for a Dell Dimension
> 4100
> 
Does it have ANY ACPI functionality? 

Hi all. I'm too having the same problem on my notebook. An Intel Core Duo T2250 1,73GHz.

Tried installing kotd 2.6.25 and had the same problem. Computer doesn't shutdown, hanging on the last message: The system will be halted immediately.

Tried different configuration at grub menu with acpi=off, apm=off, acpi=on apm=off and none of those worked.

Tried the timing workaround with no luck as well.

Is there any info that I could provide to help out?

it didnt happen here when i compiled my own 2.6.24 kernel. so its something suse did to the kernel, i went back to the 2.6.22.9-0.4-default i686 kernel offical from suse to get away from the bug, since ati does no good with my custom kernel (i have to use old driver) I really hope you are working on this bug, its super anoying...

(In reply to comment #123 from Sven Dietrich)
> (In reply to comment #122 from David Rankin)
> > with 2.6.22.17-0.1-default, the issue is still present for a Dell Dimension
> > 4100
> > 
> Does it have ANY ACPI functionality? 
> 

Yes, but what ever minimal ACPI came with the P3-800 system. Windows will suspend and resume, but that's about it.  I've looked at the specs: http://support.dell.com/support/edocs/systems/dzuul/specs.htm and they don't tell you much. This computer had no problems with 10.0. However, since loading 10.3, it has never shut down without hanging.

I have a new problem. Old systems were 10.3 with no acpi or apm. would shutdown with acpi=force, apm=off. 10.2 system shutdown with no changes it has acpi. Upgraded to lastest 10.3 with patch disk for sis problem. It now refuses to shutdown even with acpi=off apm=off in menu.lst. Tryed other combinations with no success. Its an ASUS p4p800-de motherboard.

how much longer till this is fixed? its super annoying... if you cant fix it, why not just make a way to ignore the kernel updates in opensuse updater or something, or make a repo with a working kernel in it, that overrides the offical one...

hey, no more shutdown hang after i rebuilt and updated kernel to latest offical, now lets hope it will stay that way.

Andrew could you post the version url of the kernel you used and also any special things for recompling the kernel as I've never done that.
Thanks

2.6.22.17-0.1-default, installed from zypper, I previously didn't install this kernel because of ATi and since there was nothing about it being fixed in log and such, but it works :)

I have not had a second to try opensuse 11.0 Alpha2 yet. Does anybody know if it has been fixed?

(In reply to comment #131 from Andrew Sorensen)
> 2.6.22.17-0.1-default, installed from zypper, I previously didn't install this
> kernel because of ATi and since there was nothing about it being fixed in log
> and such, but it works :)
> 

Thats the kernel I have except mine is: 2.6.22.17-0.1-bigsmp. It does not work on my ASUS motherboard. I have another system with 10.3 and no acpi or apm in bios. I think it works there. I was setting acpi=force and apm=off in menu.lst and I don't know if I took it out. I will check. the above big version came from the download.opensuse.org/update/10.3. I did use the KSIO patch to get 10.3 installed because off hang at the SIS controller.

Guess this is not fixed for everyone. I can tell you on same machine 11.0alpha2 works fine.

(In reply to comment #132 from Julian Medina)
> I have not had a second to try opensuse 11.0 Alpha2 yet. Does anybody know if
> it has been fixed?
> 
I have 11.0 alpha installed on my system and it shuts down fine with no changes by me. ASUS P4 motherboard.

For all the old P3 boards: try to use acpi=force.
Are there any boards newer than 5 years showing this, then please reopen and explain what kind of HW you have.
Filing a critical bug with prio 1 against these old HW pieces is ridiculous (external users really should not be able to touch the prio flag...).

Closing won't fix for 10.3. Please try 11.0. If it works with acpi=force, this is needed. No, it is not possible to detect automatically whether your old BIOS works better with or without acpi.

I'm running an ASUS p4s800DE motherboard. Its on the board of 5 years. I have 11.0 Beta 3 installed and I do not have to set acpi or apm off to shutdown. So I guess when the orfficall release come I will switch to that for production. I also have a old p200 866MHZ whic has acpi=off and apm=off since neither is available in the BIOS. It shutsdown. The ASUS does not shutdown with either or both shut off. It hangs with strange sounds from the speakers. I then push the power off and it shuts down. SO I can live for another month or so with it.

Thanks for your responses.

Best, only describe the affected machine. This is a very BIOS/machine specific (99% of all machines shut down nicely).
If the machine is too old and already gets blacklisted to automatically boot with acpi=off (dmesg |grep -i acpi), then try acpi=force
Otherwise (if acpi is used) try acpi=off.

The bug reporter has relatively new machine a P4. There you should not try the acpi=off/force switch. Best you first check whether you run the latest BIOS, as said this is very BIOS dependent.

The sad part is that I have been trying to fight this bug since October. I have sort of given up. But for some reason still working on it.