Bug 29088
Summary: | qla2x00 module will not unload | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michael E Brown <michael_e_brown> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | afom_m, john_hull, mark_rusk, matt_domsch |
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-03-06 22:28:44 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
Michael E Brown
2001-02-23 16:50:29 UTC
the line from 'lsmod' is as follows: module size used by qla2x00 0 0 (deleted) Is there an oops in dmesg ? if so, please type dmesg | ksymoops There is no oops or anything in 'dmesg'. There is nothing in /var/log/messages. After this, you cannot reload the qla2x00 driver at all... 'modprobe qla2x00' will return immediately, but does not change the state of the system. We (Red Hat) should really try to resolve this before next release. *** Bug 29732 has been marked as a duplicate of this bug. *** Still present in RC2. kernel 2.4.2-0.1.19 I believe we have a patch in the pipeline. Please test 2.4.2-0.1.22 or later, and re-open this report if the bug is not fixed. |