Bug 204921

Summary:	Kernel 2.4.17: Enabling ACPI in BIOS of Via 686B mainboard causes /proc/bus/pci/devices to be empty.
Product:	[Fedora] Fedora	Reporter:	Bruce Bigby <bbigby64>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Brian Brock <bbrock>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	5	CC:	jonstanley, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:	MassClosed
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-20 04:39:44 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:

Description Bruce Bigby 2006-09-01 12:31:44 UTC

Description of problem:

Somewhere during the 2.4.17 kernel frame of time, enabling ACPI in a VIA BIOS
started to prevent the kernel from intializing the /proc/bus/pci/devices file. 
This has the effect of preventing networking and video from starting, because
the devices appear to be missing.  The symptom is that the kernel reports that
eth0 appears to not be present so it delays initialization.  Also, X won't start.

Version-Release number of selected component (if applicable): 2.4.17_1.2174, and
other releases in the 2.4.17 series.


How reproducible:
Every time that I enable ACPI in the BIOS.

Steps to Reproduce:
1. Enable ACPI in the BIOS of a VIA 686B mainboard -- Tyan Tiger 230(T)
2. Reboot the computer.
3.
  
Actual results:
/proc/bus/pci/devices is empty so the kernel reports that eth0 doesn't appear to
be present so it will delay initialization. Also, X won't launch.

Expected results:
/proc/bus/pci/devices contains a proper list of device information, and the
kernel successfully boots up; networking, X, and everything else is working.

Additional info: None

Comment 1 David Lawrence 2006-09-05 15:58:16 UTC

Changing to proper owner, kernel-maint.

Comment 2 Dave Jones 2006-10-16 18:23:10 UTC

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.

Comment 3 Jon Stanley 2008-01-20 04:39:44 UTC

(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
this bug.