Bug 52055
| Summary: | Installer hangs when attempting to boot in rescue mode | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | William M. Quarles <walrus> |
| Component: | installer | Assignee: | Brent Fox <bfox> |
| Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.1 | ||
| 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: | 2002-01-15 20:45: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
William M. Quarles
2001-08-19 22:08:03 UTC
*** Bug 52056 has been marked as a duplicate of this bug. *** try booting with "linux ide=nodma" at the boot: prompt Yes, it does work, but ou problem was with RESCUE MODE. Our problem was most specifically **NOT** WITH GRAPHICAL INSTALLATION MODE. So when the system hangs while loading anaconda, can you press <Alt><F4> and see if there are any interesting error messages? I have removed some of the out put, because it doesn't all seem relevant. Here is what seemed most alarming. <Beginning> ... ... <6>PCI: Found IRQ 11 for device 00:11.0 <6>PCI: The same IRQ used for device 00:07.2 ... ... <same two lines as above appear again> ... ... <7>ISO 9660 Extensions:RRIP_1991A <4>Unable to identify CD-ROM format. <6>raid0 personality registered as nr2 <6>raid1 personality registered as nr3 <6>raid5: measuring checksumming speed <4> 8regs : 825.600 MB/sec <4> 32regs : 461.200 MB/sec <4> pII_mmx : 1128.000 MB/sec <4> p5_mmx : 1170.800 MB/sec <4>raid5: using function: p5_mmx (1170.800 MB/sec) <4>raid5 personality registered as nr4 <Ending> I know that there are two elements to the PCI bus that share the same IRQ as standard operation but I don't know enough about it to see whether or not that is a problem. I don't know why this message comes up twice. The CD-ROM format error obviously seems like a problem. We also don't have any RAID devices installed, just EIDE. Please boot adding 'nomount' to the command line when going into rescue mode. Let us know if that helps. Also, the output on VC3 would be helpful at the time it hangs. I was not able to find a single line that contained "vc3" in the messages using Alt+F4 when I tried booting linux rescue again normally. The nomount option worked, insofar as it gave me a shell prompt, but doing Alt+F4 displayed the same mesages. I also experienced some problems with apache and an experimental kernel module after doing this and rebooting, but I suspect that was caused by changes made by others to the system that I will have to track down and fix. The output on VC3 can be found by pressing Alt+F3. Any output from here when it hangs would be usfeul in tracking down the problem. Here is everything that was viewable on the monitor after pressing Alt+F4: -------------- * looking for video cards requiring agpart module * found video card controller unknown * in startPcmcia() * pcmcia probe returned: |PCI bridge probe: not found. Intel PCIC probe: not found. Databook TCIC-2 probe: not found. | * no pcic controller found * probing buses * finished bus probing * found suggestion of agpart * found suggestion of 3c59x * found 3c59x device * found suggestion of usb-uhci * found devices justProbe is 0 * going to insmod 3c59x.o (path is NULL) * trying to mount device hdc * loopfd is 9 * getting ready to spawn shell now * probing buses * finished bus probing * found suggestion of 3c59x * found 3c59x device * found suggestion of usb-uhci * found devices justProbe is 0 * going to insmod raid0.o (path is NULL) * going to insmod raid0.o (path is NULL) * going to insmod raid1.o (path is NULL) * going to insmod xor.o (path is NULL) * going to insmod raid5.o (path is NULL) * going to insmod fat.o (path is NULL) * going to insmod msdos.o (path is NULL) * going to insmod vfat.o (path is NULL) * going to insmod ext3.o (path is NULL) * looking for USB mouse... * 127 keymaps are available * loaded 9 keymap tables -------------- Any repetitions, as in the preivous submission I made, are real and are not a tpyographical error on my part. I don't see anything besides the IRQ messages from VC4 that seem concerning. To find out what devices are sharing that IRQ, can you boot into the system normally and attach the output of 'lspci' and 'cat /proc/interrupts'? Any more info here? Well, I've been rather busy lately, as it seems you have been since it has taken you a while to respond to my last posting. Mostly dealing with problems of Windows NT and its habit of randomly obtaining worms on a frequent basis late this summer and fall. Give me another week or two and I will post the 'lspci' and 'cat /proc/interrupts' ouputs. Ok. Good luck with that NT thing. ;) Any progress? Well, our Linux box has had huge filsystem errors that are corrected yet keep
coming back, but I have managed to get this much info for you:
[root@mach quarles]# /sbin/lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
00:0e.0 Communication controller: National Instruments PCI-GPIB (rev 01)
00:0f.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)
00:11.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24)
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP 1X/2X
(rev 5c)
[root@mach quarles]# cat /proc/interrupts
CPU0
0: 43115 XT-PIC timer
1: 694 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 13353 XT-PIC Crystal audio controller
8: 1 XT-PIC rtc
10: 0 XT-PIC gpib
11: 13752 XT-PIC usb-uhci, eth0
12: 22669 XT-PIC PS/2 Mouse
14: 11733 XT-PIC ide0
15: 12695 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
[root@mach quarles]#
So I guess our USB controller and our ehternet card are sharing the same IRQ. I
honestly would have never guessed that, since we didn't change anything on the
system that might do that.
I'll change it to NOTABUG and figure out how to solve this problem.
I just thought of something: USB support wasn't available before 7.0, right? We upgraded from 6.2 to 7.1. The rescue mode DID work before the 7.1 upgrade, but DID NOT work afterward. It seems that maybe this is a problem with the upgrade process, that it sets the USB controller to a default IRQ rather than finding an open one. Go ahead and close this again if you disagree. Sorry, I keep having thoughts. Last time today, I swear. I tried disabling the ehternet adaptor in the BIOS (since it is integrated), and trying to boot of the CD-ROM in rescue mode again. It still hung, and VC4 did not show any IRQ conflicts. This issue seems resolved - you were able to get into rescue mode with the 'nomount' option, right? Closing due to inactivity. Please reopen if you have more information. |