Bug 51041
Summary: | Kernel panic while downloading files w/ ncftp | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Clay Cooper <clay_cooper> | ||||
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | roswell | CC: | afom_m, dale_kaisner, danny_trinh, dean_oliver, john_hull, joshua_giles, mark_rusk, matt_domsch, michael_e_brown | ||||
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-08-13 09:06:43 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: | |||||||
Attachments: |
|
Description
Clay Cooper
2001-08-06 20:46:07 UTC
Created attachment 26497 [details]
Output of ksymoops
Re-assigning to kernel We (Red Hat) really need to fix this defect before next release. Looks like the bcm5700 driver has a dereference NULL bug. I'm trying to find out who at Broadcom is the driver maintainer and have them look at it. Broadcom has provided an updated driver, which will be in kernels 2.4.7-0.12 and later. I noticed the mention of the broadcom driver and wanted to point out that the configuration exhibiting this error had the onboard intel nic configured and running on eth0 and the broadcom configured and running on the same subnet at eth1. I'm assuming that eth0 would have been the nic in use when the kernel panic occured. >>EIP; f8a23966 <[bcm5700]MM_IndicateRxPackets+76/1b0> <=====
in the oops trace suggests the broadcom driver was at least involved,
and triggered me to classify this as a broadcom driver failure, especially
as the driver had a known oops bug.
Closing as fixed. |