Bug 715175

Summary:	[Intel 5.8 Bug] - ia64 kernel oops then panic with timer tick before it's due
Product:	Red Hat Enterprise Linux 5	Reporter:	Eryu Guan <eguan>
Component:	kernel	Assignee:	Prarit Bhargava <prarit>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.7	CC:	hui.xiao, jane.lv, jarod, jburke, jstancek, jvillalo, jwilleford, luyu
Target Milestone:	rc
Target Release:	5.8
Hardware:	ia64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-24 16:47:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	688932

Description Eryu Guan 2011-06-22 05:29:48 UTC

Description of problem:
I got a ia64 panic when running xfstests in beaker, with lots of messages like
Oops: timer tick before it's due (itc=4135ff3ee8,itm=413602e9bd) 
Oops: timer tick before it's due (itc=4136d218f6,itm=4136d26edf) 
Oops: timer tick before it's due (itc=4137a3c3dd,itm=4137a80e82) 
Oops: timer tick before it's due (itc=4138756f0c,itm=41387793a4) 
Oops: timer tick before it's due (itc=4139471cbb,itm=41394d3347) 

Version-Release number of selected component (if applicable):
kernel-2.6.18-268.el5

How reproducible:
unknown

Steps to Reproduce:
1. Don't know the exact steps, I got this when running xfstests on ext2 fs.
2. 
3.
  
Actual results:
Kernel oops then panic

Expected results:
No panic.

Additional info:
I hit this only once.
Beaker job: https://beaker.engineering.redhat.com/recipes/204831
Beaker log: http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/06/1004/100418/204831//console.log

Comment 4 Jarod Wilson 2011-07-19 15:47:10 UTC

Note: there's not actually a panic. Beaker just *thinks* there was a panic, because it saw the string "oops", which generally is accompanied by a panic, since we have panic-on-oops set by default. This just appears to be a host-specific timer issue, and an unfortunate string collision from the warning message.

Comment 5 Prarit Bhargava 2011-07-19 18:21:31 UTC

This has only been seen on planck.rhts.eng.rdu.redhat.com .

P.

Comment 10 RHEL Program Management 2012-01-09 14:31:23 UTC

This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.8 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.

Comment 13 Jason Willeford 2012-01-24 16:47:20 UTC

Engineering testing has been unable to reproduce this issue after updating the BIOS.  I'm closing this issue as notabug.  If you experience this issue, please open a new bug and record specific reproducing steps.