Bug 160285

I confirm this, I have a Tyan motherboard too, this appeared with 2.6.11 kernel
series, it use 2.6.10 and every kernel before that works fine.

Can you do a test ?
Boot your system with kernel option  acpi=off  and  quiet removed.
With my system the kernel freezes at booting with no indication (not even a
kernel panic), as this :
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=115424

Please report the behaviour you can observe

I do not have any freeze as you have shown.  The kernel boots up normally into 
FC3 with acpi=off.  The only difference in behaviour for me was that a 
shutdown -h now shows "Power down." (which makes sense because it no longer 
knows how to shut down via ACPI).

"shutdown -h now" also fails (reboots instead of halts) with kernel-2.6.11-
1.35_FC3 on same system config as initial report.

An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

The problem is still present with kernel-2.6.12-1.1372_FC3 - I will try 
upgrading to FC4 and see this makes any difference.

I saw this bug with a system a while back...  It doesn't affect every 2882
system for sure.  How much RAM do you have?  Is it over 4G?

Exactly 4GB RAM (PC3200 ECC)

We have it happening on about 20% of our S2882's.  Didn't happen with RHEL3/2.4
kernel.  Any fix yet?

The problem is still present on my same system - now with FC4 and kernel 
2.6.13-1.1526_FC4 - also with 4GB RAM.

The amount of RAM doesn't make a difference for me actually.

I am running with BIOS 2882-D v3.03 - am contemplating trying the latest v3.04 
BIOS from http://www.tyan.com/support/html/b_s2882d.html (although it does not 
mention anything any ACPI changes that might be relevant in its changelog)

I have upgraded my Tyan S2882-D motherboard BIOS to v3.04 and also kernel to 
2.6.13-1.1532_FC4 - halt is still non-operationa (doesn't power down)

2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.

I have tried kernel 2.6.14-1.1637_FC4 on my Tyan S2882-D (Thunder K8SD Pro) 
and the behaviour is the same - it reboots instead of halts/power down.

I have updated to 2.6.14-1.1644 on my Tyan S2882-D with BIOS v3.04 and no 
change to issue.  I upgraded to BIOS v3.05 and there is no change to the issue.

Please clarify.
Does the reset on shutdown happen in both cases?:
1. ACPI enabled
2. "acpi=off"

Test scenario on 22 Jan 2006

Kernel: 2.6.14-1.656_FC4
Tyan S2882-D BIOS v3.05
Kernel params Default
BIOS ACPI Aware O/S Yes
BIOS ACPI 2.0 Support Yes
BIOS AMD PowerNow Disabled
Plug & Play O/S Yes

------------------------------
Test 1:
Additional kernel param: acpi=off

shutdown -h now 
does not reboot.  Console shows:

Halting system...
Power down.
and the system does not power down.

------------------------------
Test 2:
Plug & Play O/S No
shutdown -h now reboots system.

------------------------------
Test 3:
Plug & Play O/S No
BIOS AMD PowerNow Enabled
shutdown -h now reboots system.

does the 2.6.15 kernel in updates-testing do any better ?

Test 4:
Kernel 2.6.15-1.1824_FC4.x86_64
Plug & Play O/S No
BIOS AMD PowerNow Enabled
shutdown -h now reboots system

This is a mass-update to all currently open kernel bugs.

A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

Thank you.

Test 5:

Outcome: Bug still exists

Kernel 2.6.15-1.1830_FC4.x86_64
Tyan S2882-D BIOS v3.05
Kernel params Default
BIOS ACPI Aware O/S Yes
BIOS ACPI 2.0 Support Yes
Plug & Play O/S No
BIOS AMD PowerNow Enabled
'shutdown -h now' results in system reboot (instead of halting it)

This one really is puzzling, as I'm unable to reproduce it on my 2882.
Other than stabbing in the dark and hoping that some random upstream change
makes it work again, I'm totally out of ideas on this one.

I assume it's still affecting you with the 2.6.17 kernel ?

[This comment added as part of a mass-update to all open FC4 kernel bugs]

FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel.  As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
to FC5.

Please retest with Fedora Core 5.

Thank you.

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Problem still exists in FC6 X86-64

Upgraded to FC6 (2.6.18-1.2798.fc6)
Also upgraded Motherboard BIOS to 2882D BIOS to v3.09 to see if that had any effect.

Kernel 2.6.15-1.1830_FC4.x86_64
Tyan S2882-D BIOS v3.09
Kernel params Default
BIOS ACPI Aware O/S Yes
BIOS ACPI 2.0 Support Yes
Plug & Play O/S No
BIOS AMD PowerNow Enabled

'shutdown -h now' results in system reboot (instead of halting it)

Please try kernel 2.6.20-1.2944.fc6

Problem still exists in FC6 X86-64 with 2.6.20-1.2948.fc6

Upgraded to kernel 2.6.20-1.2948.fc6
no other changes

'shutdown -h now' results in system reboot (instead of halting it)

Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Problem still exists in Fc8 X86-64 with 2.6.24.4-64.fc8
ie
'shutdown -h now' results in system reboot (instead of halting it)

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Still present in FC9 X86-64 with 2.6.25.11-97.fc9.x86_64

This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.