Bug 84048
Summary: | (NET TULIP) Boot hangs at eth0 initialization | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Nicolas Aspert <nicolas.aspert> |
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | peterm, trevor |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:40:31 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
Nicolas Aspert
2003-02-11 14:43:08 UTC
Jeff: looks like your ballgame.... Lately, since migrating a bunch of working RH7.3 systems to FC1, I've started seeing this same problem. It's now happened on 3 different machines. Mostly they are a mix of tulip, e1000 and 8139too network cards. Note: these systems NEVER had this problem (for years!) under RH7.3. Only after a complete wipe and fresh install of minimal FC3 has this problem started occuring. It hangs bringing up eth0 (the external internet ISP connection) forever and only C-A-D will get a response. If I set eth0 ONBOOT=no, the system will come up fine and then I can run ifup eth0 from a prompt no problem and no hangs! Weird! Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |