Red Hat Bugzilla – Bug 186708
FC5 kernel lockups, call trace, network hangups
Last modified: 2008-08-02 19:40:33 EDT
Description of problem: I having massive problems with the default FC5 i686 kernel. I tried to install FC5 using a PXE network install. The network card is detected (tg3 driver) the systems gets an IP address via DHCP. After entering the NFS server name and path to the DVD image my whole network is being blocked after some time, i.e. no other system can communicate with the NFS server anymore. The NFS server is RHES4U3. After switching off the FC5 install client the network becomes usable agin. As network install is impossible I decided to install FC5 locally from the DVD. When I booted the system after the install process I saw a call trace (see screenshot #1) the boot process continued but then hung completely (see screenshot #2). After rebooting the system came up completely but my network was blocked again after some network activity. Version-Release number of selected component (if applicable): How reproducible: Sometimes Steps to Reproduce: 1. have some network activity on a tg3 network card 2. 3. Actual results: Expected results: Additional info:
Created attachment 126724 [details] screenshot of call trace during boot process
Created attachment 126725 [details] screenshot a hanging boot process
Created attachment 126726 [details] /var/log/messages showing kernel call trace
Problem still persists with kernel-2.6.16-1.2080_FC5.
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.
Still the same problems here with the current FC6 kernel. In the meantime I found out that my system is stable when I pass "noapic acpi=off" to the kernel command line.
(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.