Bug 10677
Summary: | SCSI module won't accept documented options | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Peter Hunter <peter.hunter> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
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: | 2000-04-22 07:08:46 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
Peter Hunter
2000-04-09 09:18:12 UTC
Those options still work fine in the aic7xxx module, I would suspect that your kernel upgrade did not include making a new initrd image and as a result the panic is coming from the fact that the aic7xxx module is never getting loaded with the new kernel. No. That's not what happened. I know because I mounted the initrd file (which had been made automatically by the installer when it upgraded from 6.1). When I did so, if I ran the insmod listed in there, my SCSI cards would not be detected: the insmod didn't give an error, I don't think, but it didn't detect the cards. When I did the insmod without the module options, all was well (though of course I don't get tagged command queueing.) I need to know the exact error messages when trying to load the aic7xxx driver with options to be of any more help. I'm not sure how you mounted the initrd and loaded the driver if the machine panics when the module doesn't load properly. In any case, I need to know the particular commands used, the kernel in use, the module you are trying to load, and the exact messages from both the insmod command and the kernel after the load was attempted (which you can get by using the dmesg command). |