Bug 51041

Summary: Kernel panic while downloading files w/ ncftp
Product: [Retired] Red Hat Public Beta Reporter: Clay Cooper <clay_cooper>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: roswellCC: 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 Flags
Output of ksymoops none

Description Clay Cooper 2001-08-06 20:46:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i686; en-US; rv:0.9.1)
Gecko/20010607 Netscape6/6.1b1

Description of problem:
Fairfax beta3 installed on a 6400  updated to 2.4.7-0.3 enterprise kernel,
w/ 5GB ram and 2GB swap, test bios T42, and a perc3qc raid 1 container.

While downloading several 1-10MB files with ncftp, kernel panics.

May not happen everytime.

Output of ksymoops attached.

How reproducible:
Sometimes

Steps to Reproduce:
1. Fairfax beta3 installed on a 6400 updated to 2.4.7-0.3 enterprise
kernel, w/ 5GB ram and 2GB swap, test bios T42, and a perc3qc raid 1 container.
2. Use ncftp to download several 1-10MB files.  (I was using the kernel
update rpms)
3. Look for kernel panic
	

Actual Results:  Kernel panic

Expected Results:  No kernel panic

Additional info:

Comment 1 Clay Cooper 2001-08-06 20:47:21 UTC
Created attachment 26497 [details]
Output of ksymoops

Comment 2 Glen Foster 2001-08-06 22:06:14 UTC
Re-assigning to kernel

Comment 3 Glen Foster 2001-08-06 22:53:08 UTC
We (Red Hat) really need to fix this defect before next release.

Comment 4 Matt Domsch 2001-08-06 23:36:56 UTC
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.

Comment 5 Arjan van de Ven 2001-08-09 09:11:08 UTC
Broadcom has provided an updated driver, which will be in kernels 2.4.7-0.12 and
later.

Comment 6 Clay Cooper 2001-08-10 18:11:41 UTC
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.

Comment 7 Arjan van de Ven 2001-08-13 09:06:38 UTC
>>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.

Comment 8 Bill Nottingham 2001-08-23 21:07:08 UTC
Closing as fixed.