Bug 59415
Summary: | Kernel Panic Kernel 2.4.9-13 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | mike.radomski |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
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: | 2003-06-08 01:13:08 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
mike.radomski
2002-02-07 14:56:41 UTC
Hmmm this oops seems half mutilated (yes I know syslog sometimes does that, grrr) It seems to be either the qlogic driver or the e100 driver you are using. I know both have some serious issues (and for the qlogic driver we've added a newer, fixed version in the 2.4.9-21 kernel we released). Please try using eepro100 instead of e100! Does this still happen with eepro100 and qla2200 (from 2.4.9-21) ? The problem has not re-occurred since I changed the NIC module from e100 to eepro100. I did not change the qla2x00 driver as it was from qLogic, nor did I upgrade the kernel. Since it appears that it was the NIC module, I am going to upgrade to the latest kernel. Thanks for your help. |