Bug 65179

Summary:	Kernel crash from Assertion failure in __journal_file_buffer()
Product:	[Retired] Red Hat Linux	Reporter:	Geoff Dolman <geoff.dolman>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2
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:	2002-05-20 20:40:57 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 Geoff Dolman 2002-05-19 14:21:09 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020509

Description of problem:
While running ssh in gnome the machine hung up and I got this message on the
console:

May 19 14:33:27  kernel: Assertion failure in __journal_file_buffer() at
transaction.c:1960: "jh->b_transaction == transaction || jh->b_transaction == 0"
 
The X then completely froze up and it would not respawn with ctrl-alt-backspace.
I also couldn't get a login on a virtual console. I pressed control-alt-delete
to try to reboot and got a message again and again that apm couldn't enter
state: busy.
Eventually I switched the power off.

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


How reproducible:
Couldn't Reproduce


Additional info:

Comment 1 Stephen Tweedie 2002-05-20 20:40:48 UTC

Did you manage to capture any more of the oops message?

This particular error has been seen in the past, but pretty much every single
case has been tracked down to faulty hardware.  I'd suggest memtest86 as a first
diagnostic.

Without the rest of the oops, it's not really possible for me to eliminate
software as a fault.  There have been a few small bug fixes since 2.4.9-31, but
none that I can think of that match this particular footprint.  I'd really need
more information to go any further with this one.