Bug 117171

Summary:	kernel 2.6.3 (and 2.6.2) kernel panik with ipsec (interrupt not syncing)
Product:	[Fedora] Fedora	Reporter:	Jost Diederichs <jost>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED RAWHIDE	QA Contact:	Brian Brock <bbrock>
Severity:	high	Docs Contact:
Priority:	high
Version:	rawhide	CC:	ckjohnson, jost
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:	2004-03-09 14:36:26 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:
Bug Depends On:
Bug Blocks:	114961

Description Jost Diederichs 2004-03-01 04:26:56 UTC

Description of problem:
Heavy traffic through ipsec tunnel (100 or more kb/sec) will cause
kernel panic after about 5 to 10 seconds. 

Version-Release number of selected component (if applicable):
so far I have tested almost all fedora development kernels from
version 2.6.3-1.90 up to version 2.6.3-1.116

How reproducible:
Happens every time. Either heavy traffic through the tunnel or a
combination of some traffic through the tunnel and heavy traffic to
the internet. 
I have tested this now on two different machines ( one AMD K6-2 and
one Intel PIII on Intel motherboard) with the same results. 
I have also used both, the freeswan userland tools and the racoon
tools to setup the tunnel, in both cases using the kernel's built in
ipsec functionality. 

The kernel debug output is long and scrolls off my screen. I will
obtain a null modem cable and try to capture it to an external console. 

Here is what I managed to capture from what is visible on the console: 
EIP is at des_small_fips_decrypt
[...]
 Kernel panik: Fatal exception in interrupt
In interrupt handler - not syncing

Comment 1 Christopher Johnson 2004-03-06 15:34:12 UTC

Is bug 116494 a duplicate of this?

Comment 2 Jost Diederichs 2004-03-07 04:33:04 UTC

It probably is, sorry about that. 

In addition, this bug appears to be fixed in kernel-2.6.3-2.1.238. I
haven't been able to reproduce it.