Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 55742

Summary: spinlock code stuck
Product: [Retired] Red Hat Linux Reporter: Isaiah Weiner <iweiner>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED CURRENTRELEASE QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: medium    
Version: 7.1   
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-07 20:31: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 Isaiah Weiner 2001-11-05 22:11:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
Using kernel-2.4.2-2 and the Cisco-modified 2.4.2-7 (ALSA stuff added, can 
get a list) an 'rpm -ba' of the kernel over NFS (options are 
rw,v3,rsize=32768,wsize=32768,hard,udp,lock) makes the machine 
unresponsive to network traffic (ping included).  SysRq data tracked it 
down to being a BKL spinlock issue.  arjan, do you remember this IRC 
conversation?  You told me to test the 2.4.2-2 stock and the 2.4.9-6 
errata.  The errata doesn't break, but the stock does.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. over nfs with the options i used, mounting from a netapp f700 filer
2. rpm -ba the kernel
3. at the console, use sysrq to get eip
	

Additional info:

Comment 1 Arjan van de Ven 2001-11-06 09:29:57 UTC
ALSA or ARLA ?
Either way, "fixed in errata" sounds like good advice....

Comment 2 Arjan van de Ven 2001-11-06 11:27:19 UTC
Also, which network driver is this ?

Comment 3 Isaiah Weiner 2001-11-06 18:04:03 UTC
ALSA, and eepro100.  "Fixed in errata" is unfortunately not where we (Red Hat) 
drop it.  Again, because of Rational's lack of support beyond 2.4.2 currently, 
Cisco cannot migrate to the errata.  This is a good opportunity for them to use 
developer hours, too.  I'd like to facilitate the creation of a patch for them 
to go on 2.4.2.  I can provide the kernel SRPM they're currently using and 
collaborate to gather any further diagnostic data.

I will escalate it through the proper channels if you like.