Bug 55977
| Summary: | [qlogic] Installation hangs with add-in adapters. | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Stephen Elia <stephen.c.elia> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.3 | CC: | clay_cooper, eric.g.hudnell, john_hull, matt_domsch |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | ia64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-12-10 17:21:57 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
Stephen Elia
2001-11-09 18:57:54 UTC
As another datapoint, I was able to reproduce this failure as well. Failure occurred when loading the drivers for the adapters in the system. However, if I turned off the slot that contained the AMI 1600 (or removed it), the installation proceeded as expected. Tested: 1 - Adapted 29160 and 39160 2 - Qlogic QLA2200 3 - Qlogic QLA2200 4 - AMI Megaraid 493 5 - Intel Dual EEPro 100 6 - Intel Dual EEPro 100 7 - Intel Pro 1000 (copper) 8 - Intel Pro 10000 (fiber) 9 - empty 10 - Intel EEPro 100 Results: - in all boots but one, machine failed to get out of BIOS. Normally hangs at 'initializing timer' - once, booted succesfully to EFI shell. Then, elilo hung, presumably attempting to get EDD3.0 information from the various storage controllers. So, we can not reproduce this here, because we can not reproduce the HW configuration here. Can you simplify the test case? Does it really require *all* these adapters installed to fail? Additional testing revealed that the adapters in slots 1, 2 and 3 cause the failure as well. PCI-1 Adaptec 29160 Host Adapter PCI-2 QLogic QLA2200-66 Fiber Chanel Host Adapter PCI-3 QLogic QLA2200-66 Fiber Chanel Host Adapter In fact, the machine continues to hang at 'Initializing timer', even after all cards have been removed. Hence, the machine completely useless after the cards are inserted in this manner. We have reproduced this on a second machine, and are supsending investigation of this bug for the safety of our ia64 hardware. Bill wedged our PowerEdge 7150 doing this. :-( The kernel hangs, no VC switching happens. This is not the installer process hanging. Correct, this hang occurs before X starts. I have been able to reliably reproduce this w/o hitting the hang at 'Initializing timer...' observed at RH. I have been working with a subset of the adapters Stephen posted. My findings thus point to the driver for the Qlogic 2200/FC Adapter. Here are my results of several tests: For all tests: Slot1: Adaptec 29160 Slot2: Qlogic 2200/FC Slot3: Qlogic 2200/FC Slot4: AMI 1600 I also have a pro/1000 and an extra pro/100 in the system in further slots, but they do not appear to be causing the problems... TEST1: Slots 1-4 populated -- on load of 12160 driver, "KERNEL PANIC: Invalid or not present host" TEST2: Slots 1-4 populated -- screen blanked on load of Qlogic 2200 driver TEST3: Slots 1-2 populated -- on load of 12160 driver, "KERNEL PANIC: Invalid or not present host" TEST4: Same as TEST2 TEST5: Slots 2-3 only populated -- screen blank when loading the Qlogic 2200 driver TEST6: No Qlogics 2200s in system - slots 2 & 3 left empty, 29160 and AMI1600 still in system -- SUCCESS! Installer started as expected. Only a little bit of probing showed the kernel panic originated from the scsi sub-system - specifically scsi.c in the 1.) scsi_do_req 2.) scsi_init_cmd_from_req and 3.) scsi_do_cmd routines. Based on these results, culprit appears to be the Qlogic 2200 driver. Also, have you tried clearing the CMOS on the hun system? sounds like a kernel qla2x00 driver issue. The next tree AFTER the qa1129 tree will load the qla2200 driver insteaed of the qla2x00 driver for ISP2200 cards. We would like to know if that fixes the problem when that occurs. Unless we hear otherwise, I'm going to assume that qa1207.0 fixed this bug. We have fixed a lot of qla2200 bugs that could have caused this, and we are not reproducing hangs like this here now. qa1207 has fixed the installation issues we have encountered. Closing *** Bug 54736 has been marked as a duplicate of this bug. *** |