From stask@tiger.thukraine.com  Wed Aug 16 00:15:00 2000
Return-Path: <stask@tiger.thukraine.com>
Received: from tiger.thukraine.com (uline15.crimea.com [212.3.116.47])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4FAB937BF1C; Wed, 16 Aug 2000 00:09:06 -0700 (PDT)
	(envelope-from stask@tiger.thukraine.com)
Received: (from stask@localhost)
	by tiger.thukraine.com (8.9.3/8.9.3) id KAA00535;
	Wed, 16 Aug 2000 10:14:22 +0300
Message-Id: <200008160714.KAA00535@tiger.thukraine.com>
Date: Wed, 16 Aug 2000 10:14:22 +0300
From: Stas Kisel <stask@tiger.thukraine.com>
To: stask@tiger.thukraine.com, wpaul@FreeBSD.ORG
Cc: freebsd-gnats-submit@FreeBSD.ORG, jblaine@linus.mitre.org,
	sheldonh@uunet.co.za
Subject: Re: arpintr

>Number:         20639
>Category:       kern
>Synopsis:       Re: arpintr
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Aug 16 00:20:01 PDT 2000
>Closed-Date:    Mon Sep 25 12:07:42 PDT 2000
>Last-Modified:  Tue Nov 27 18:33:12 PST 2001
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 > From wpaul@FreeBSD.ORG  Tue Aug 15 20:07:26 2000
 > Subject: Re: arpintr
 > Cc: freebsd-gnats-submit@FreeBSD.ORG, jblaine@linus.mitre.org,
 >         sheldonh@uunet.co.za
 > From: wpaul@FreeBSD.ORG (Bill Paul)
 >
 > > 
 > > Hi.
 > > 
 > > I've moved to 4.1-RELEASE 3 days ago. Since that, machine did not rebooted,
 > > but it did hang up 2 times (and these 2 times were in 3 minutes one after
 > > another). Looked like very high LA. I had not reniced shell or top handy,
 > > so may be it was some userland tool ( I have some on machine ), but I didn't
 > > seen that since I've installed machine, and my last change in software was
 > > 2 weeks ago.
 > > 
 > > I'm afraid that this bug has turned from easy-trackable page fault panic
 > > to hangup after I've moved to 4.1. What can I do to provide you with
 > > stacktrace under these circumstances?
 >
 > You are making the unwarranted assumption that the problem you're seeing
 > now is related to the problem you were seeing before. Your reasoning is:
 > "Well, something is still wrong, therefore it must be caused by the same
 > thing as the previous problem." This reasoning is faulty. It is not the
 > same bug.
 
 May be it is not, of course.
 
 > If you want to try to debug this, compile your kernel with options DDB
 > and try to break into the kernel debugger next time it wedges.
 
 May I ask you what should I check? In fact, I'll have a very limited time
 for online debugging.
 Is it possible do dump all necessary data, reboot machine, and debug
 later? A sort of make panic so I'll have core?
 
 \bye
 Stas
 
 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: peter 
State-Changed-When: Mon Sep 25 12:07:42 PDT 2000 
State-Changed-Why:  
Not a PR 


Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: peter 
Responsible-Changed-When: Mon Sep 25 12:07:42 PDT 2000 
Responsible-Changed-Why:  
Not a PR 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20639 
>Unformatted:
