Bug 74799
| Summary: | |||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Ed <edward> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | alan, bobirvin, mgsmith, scronk, wbmayberry |
| 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: | 2006-02-21 18:49:42 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
Ed
2002-10-01 19:39:32 UTC
Narrowed this down to the /etc/init.d/network script. It's locking up on this line: action $"Bringing up loopback interface: " ./ifup ifcfg-lo It does not get past this line. Did a clean install on the same machine (not an upgrade of 7.3). Same problem
occurred. This is a complete show-stopper.
I narrowed the hang down to this section in /sbin/ifup:
if ! ip link set ${REALDEVICE UP} ; then
echo $"Failed to bring up ${DEVICE}."
exit 1
fi
Also, if I totally disable the network during init, the init crashes loading pcmcia.
I have the same problem with a HP Pavilion ZE1230 (mobile Athlon XP 1500). If I do the interactive startup, and skip the "start service network",(and PCMCIA, but that's another one), then the system starts up ok, but I cannot access the LAN. It worked fine with Redhat 7.3, but freezes with 8.0 at this point. Also, when frozen, a CTRL/ALT/DEL will wake it up and cause it to restart, but it does that same thing. same behavior with a Sony Vaio PCG-GR370 pentium 3m 1.13GHz fresh install.
Worked great with RH 7.2 and 7.3.
note that at least in my case, once booted through interactive boot (no pcmcia
or network), manually insmodding pcmcia modules (yenta_socket etc...) will
hang. ifconfig will also hang.
-Tried after removing pcmcia cards and found no change in behavior.
try to disable kudzu service I am installing RedHat 8.0 on a Sony Vaio PCG-GRX570 and I see exactly the same problem. I am completely dead in the water. mphelps As stated by omlex, if you skip the kudzu service this problem does not occur. Being relatively new to Linux, how do I skip kudzu service? Do I just do it through interactive startup? Also,how do I install new hardware? Do I just run kudzu manually? Thanks, Will Install RH 8.0 and boot 'I'nteractive. do NOT activate Kudzu. The system will start just fine. Then disable kudzu with chkconfig or ntsysv. Worked for me anyways. Do you have an alias for iee1394-controller in your /etc/modules.conf? What happens if you change the alias to 'off'? Here's my module.conf (no ieee1394 entry that I can see): # more modules.conf alias parport_lowlevel parport_pc alias eth0 eepro100 alias sound-slot-0 i810_audio post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || : pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 | | : alias usb-controller usb-uhci *** Bug 75028 has been marked as a duplicate of this bug. *** *** Bug 77729 has been marked as a duplicate of this bug. *** *** Bug 80426 has been marked as a duplicate of this bug. *** i also have a sony grx550 laptop and have the same problems with 8.0. i have tried to disable kudzu but have problems with glide point mouse..very erratic response..but disabling kudzu does allow me to boot into 8.0..but with the mouse wierd response..this problem is still a show stopper for me. i have since downgraded to 7.3. A solution was posted to Google Groups by crywolf. This at least allows you to get past the boot. The rest will have to wait for a Red Hat Patch. Boot and use the I option (interactive boot), Do not run kudzu. Then you can turn off kudzu as per below. ------------------------------------------------------------------- "looks like kudzu has a problem with certain hardware. go into runlevel 1 and turn kudzu off /sbin/chkconfig --level 345 kudzu off and you should be up and running" I found another way around this bug as I would rather not have kudzu disabled. Pulling the ieee1394 directory from /lib/modules/2.4.18-my-ver allowed kudzu to run and did not hang the init. note:: I did not see firewire or ieee1394 mentioned in /etc/modules.conf so I did not try to go about this in a clean fashion. So for myself and anyone else who is not dependant on firewire peripherals this might be a good way to get around this issue. This is a kernel bug in that loading the firewire modules appears to greatly destabilize the system. hi using Ed's suggestion in comment#9, I went into chkconfig and turned off Kudzu (after booting interactively and not starting Kudzu)typing the following: chkconfig -level 345 kudzu off My VAIO GRX550 laptop boots fine with RH 8.0 (kernel 2.14.18) Is this definitely a bug in kudzu and, if so, will it get fixed? This has been at NEW status since October! Is anyone actively looking into this problem? I have since removed RH 8.0 from my laptop, there are several temp fixes for this problem listed in this ticket...but they are temporary. This is very poor customer service..you released an operating system that does not install unless finagle with the boot process..even windows installs without this much headache. At the very least this status should not be NEW! Unstatisfied, Steve Cronk Not only has it been looked at it may also work fine with the newer errata kernels. Does it ? *** This bug has been marked as a duplicate of 72587 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |