Bug 24871

Summary: Pagefaults occur at random on a 4.2-STABLE machine
Product: Base System Reporter: blovett <blovett>
Component: i386Assignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.2-STABLE   
Hardware: Any   
OS: Any   

Description blovett 2001-02-05 15:40:01 UTC 
	This is taken from my original email to stable@freebsd.org:
	Recently, I have been having random page faults, and the application
	that caused the fault is always random, or none at all, just idle.
	These can occur after 2 days uptime, to 5 hours..  This is on a Toshiba
	Satellite 2505CDS running 4.2-STABLE as of Sunday, January 14, 2001.
	They also occured on this same system running 4.2-STABLE as of about a
	month and a half ago.  I don't remember the exact date I cvsup'd.

	Recently, the CVSup date has been discovered (since I did a complete reinstall from CD-ROM and builtworld to STABLE.  That date would be January 15, 2001.

	You can get a copy of my kernel-debug output at http://www.oneinsane.net/~blovett/kernel.debug.txt .  Due to me not being an "expert" on kernel debugging, I am not sure that I did everything up to par.  But, hopefully this will be adaquate for determining what is up.

Fix: 

None known.
How-To-Repeat: 
	Currently unknown, as they occur at random.
Comment 1 John Polstra freebsd_committer freebsd_triage 2001-06-02 20:22:11 UTC 
State Changed
From-To: open->feedback

I took a look at the code where the trap occurred (ip_input.c 
revision 1.130.2.11 line 492), and also at the revision history 
for this file.  There have been several bug fixes in exactly this 
portion of the code since this revision.  I have a strong suspicion 
that this problem will go away if you upgrade your system to the 
latest -stable, or at least to 4.3-release. 

Please let us know whether this fixes the problem, so that we can 
close the PR if appropriate.
Comment 2 John Polstra freebsd_committer freebsd_triage 2001-06-03 23:26:10 UTC 
State Changed
From-To: feedback->closed

Submitter has a new laptop and is unable to reproduce the problem. 
He suspects there may have been hardware problems in the old laptop.