Red Hat Bugzilla – Bug 180013
PC does't boot without "acpi=noirq" option on I/O-4 chipset.
Last modified: 2015-01-04 17:25:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.7.12) Gecko/20050930 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
Description of problem:
I have begun to use a PC with a Motherboard named NFPIK8AA-8EKRS.
The Board has two on-board SATA controllers,
one is called Nforce4 Professional 2200(CK8-04)
other is called Nforce4 professional 2050(I/O-4).
And each controller has four SATA ports.
Thus this board has total 8 SATA ports.
I find when a SATA Disk which FC4 is installed
is connected to a SATA ports controlled by I/O-4,
the disk is not boot without the option of "acpi=noirq".
When the Disk is connected to CK8-04,
Boot process works fine.
PC's configuration is:
CPU: Opteron 140EE
Memory: 512MB x 2 (ECC-Reg. DDR400)
If further information is needed,
I will post it as much as possible.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Power off the PC
2. Connect the SATA disk to ports controlled by I/O-4.
3. Power on the PC
[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
Please retest with Fedora Core 5.
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.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen