Bug 171950
Summary: | Can't reboot on IBM xSeries 236. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | TAIRA Hajime <htaira> |
Component: | kernel | Assignee: | Dave Anderson <anderson> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | davej, jbaron, s.ivanov |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHSA-2006-0132 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-03-07 20:34:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 168429 |
Description
TAIRA Hajime
2005-10-28 01:49:17 UTC
You first need to try several differnet "reboot=" boot command line options. /* reboot=b[ios] | t[riple] | k[bd] [, [w]arm | [c]old] | [a]cpi bios Use the CPU reboot vector for warm reset warm Don't set the cold reboot flag cold Set the cold reboot flag triple Force a triple fault (init) kbd Use the keyboard controller. cold reset (default) acpi Use the ACPI reset mechanism defined in the FADT */ The main options of interest are the 'b', 't', 'k' and 'a' options. If you do not enter the reboot= option on the boot command line, then the system will default to 'k'. However if your system has a certain ACPI revision, you would see this boot-time message: System reset via FADT Reset Register is supported ...and the default would be changed during boot to 'a'. So, again, without using the reboot= option, the default is either 'k' or 'a', depending upon your ACPI version. However, you can override both defaults by using the reboot= command line option. So, in order to ensure that all possible reboot options are tested, you need to try this boot command line options: reboot=b reboot=t reboot=a reboot=k The 'w' and 'c' options tell the BIOS whether it should be a cold or warm reboot; 'c' is the default. I don't believe it would help to use the 'w' flag in conjunction with the above flags, but I really don't know. So, if none of the 4 options above help, then you should also try: reboot=b,w reboot=t,w reboot=a,w reboot=k,w I believe that some of this reboot code has changed, so please do your testing using the latest RHEL4 kernel. One other thing to test, to rule out any SMP-related issues. 1. boot the EM64T kernel with the command line option "maxcpus=0", which will disable SMP activation. 2. then reboot to see if the system still hangs. We don't have any of these systems available here, so there's little else I can suggest. Thank you for reply. But I do not have this server now. I passed the torch to IBM Japan. *** This bug has been marked as a duplicate of 166888 *** An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0132.html Hello, Just for information: this promlem reprodusable on IBMs x336 & x346 (both EM64T) with RHEL 4 WS Update 3 x86_64 |