Description of problem:
I install FC5T3 on my smp box. It can't detect pci device when It was first boot
during instllation, so login prompt appear after a lot of error.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
boot up with many error
It can boot without error if noapic kernel option is used.
Created attachment 125019 [details]
Created attachment 125020 [details]
dmesg when noapic is used
M/B: RIOWORKS TDVIA (VT8633T, VT8233C)
CPU: PIII 1.4Ghz x 2
title Fedora Core (2.6.15-1.1955_FC5smp)
kernel /boot/vmlinuz-2.6.15-1.1955_FC5smp ro root=LABEL=/1 rhgb quiet
00:00.0 Host bridge: VIA Technologies, Inc. VT8653 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:08.0 RAID bus controller: Promise Technology, Inc. PDC20267
(FastTrak100/Ultra100) (rev 02)
00:09.0 SCSI storage controller: Adaptec AHA-2940U2/U2W
00:0a.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
00:0b.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233C PCI to ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
00:11.4 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
01:00.0 VGA compatible controller: nVidia Corporation NV15 [GeForce2 GTS/Pro]
Created attachment 126023 [details]
/proc/interrupts with no append kernel option
Created attachment 126024 [details]
dmesg with appending pci=noacpi option
2.6.15-1.2041_FC5smp works fine, if pci=noacpi is used.
Created attachment 126025 [details]
/proc/interrupts with appending pci=noacpi option
FC6T1 still have this bug.
You do have the latest BIOS installed on yor machine?
Yes. I'm using latest BIOS version 1.42.
http://www.rioworks.co.jp/bios/tdvia.html ( sorry for Japanese language )
I think this is made in October 15, 2002. Because I can see such date in boot
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.
doesn't work for me.
to change status.
kernel-188.8.131.52-10.fc7 works for me.