Bug 30978
Summary: | [aic7xxx] device takes VERY long time in boot | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Daniel Senie <dts> |
Component: | kernel | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | herrold |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-04-17 21:53:37 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
Daniel Senie
2001-03-07 19:24:05 UTC
This sounds more like a kernel issue than an installer issue. I'll buy that. BTW, I also ran some test installs with RH 6.1 and 6.2, both of which took a while at the insmod of the AIC7xxx, but didn't spew on VC4 in the process. Not sure they took less time, or were just less verbose about it. Could you install the latest kernels from rawhide and see if they have the same behaviour? Because this is happening during an install, I can't easily just load a new kernel and try it. What would work is either: 1. Create a new .iso of disc1 of the wolverine set. I can test for this bug, as well as verifying the fix on the Mylex AcceleRAID 170 issue. 2. Point me at some instructions for recreating the disc1 with these things applied. Note that this means replacing the boot kernel as well as the kernels to be installed. #1 is probably easier. No problem at this end downloading an iso image and burning it for the tests. I had mixed results -- reasonable spinup and install without issue on a NetServer 5/100 LH at home -- and totally failed on a NetServer 5/100 LC at the office with kernel-2.4.2-0.1.23 from the 0309 build ... I will investigate the failure further ... I would need to know more about what error messages the boot kernel spewed about the aic7xxx controllers in order to figure out what's going on. Also, if there is nothing connected, and changing termination didn't make a difference in the output, then it might indicate something suspicious about the termination on the motherboard. This host was also fighting geometry issues -- see: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=31778 I have another SCSI drive to attach and report from ... Termination is non-powered at the end of the unidirectional chain, with termination NOT enabled on the drive ... other end is the connector in the onboard motherboard controller ... This bug is now applicable to RedHat 7.1. The released edition contains the same problem. If there's a AIC7xxx present, be prepared to wait 10 minutes while a scan is done on every non-existant device, and an error message generated on one of the alternate consoles. |