Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 169339 - hang while loading network modules.
hang while loading network modules.
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-09-27 03:21 EDT by Tim Mayberry
Modified: 2015-01-04 17:22 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-04 16:18:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
output of lspci -v command (7.12 KB, text/plain)
2005-09-27 03:23 EDT, Tim Mayberry
no flags Details

  None (edit)
Description Tim Mayberry 2005-09-27 03:21:32 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.0.6-1.2.fc4 Firefox/1.0.6

Description of problem:
Installation of FC4 x86_64 and Rawhide(260905) x86_64 via NFS are successful, so the network interface does work but when the machine is restarted for the first time and the lines

Starting udev:                        [ OK ]
Intializing hardware....storage network

are displayed, at which point it hangs and will not progress any further.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install FC4 or Rawhide
2. reboot

Actual Results:  On first boot the system wouldn't progress past initializing the network harware.

Expected Results:  The network hardware should be initialized so the installation can be completed.

Additional info:
Comment 1 Tim Mayberry 2005-09-27 03:23:15 EDT
Created attachment 119291 [details]
output of lspci -v command
Comment 2 Dave Jones 2005-10-06 02:56:57 EDT
hrmph, we've yet to do a release where some broken module hasn't caused this.

usually I ask the reporter to modify /etc/rc.d/rc.sysinit so that the
load_module() function has a 

echo $1

just before the modprobe line.

sometimes this shows us the bogus module, sometimes it makes the problem hide.
Lets hope your case is the former..
Comment 3 Tim Mayberry 2005-10-17 01:47:38 EDT
I installed a more recent build of Rawhide and this problem no longer occurs.

Note You need to log in before you can comment on or make changes to this bug.