From stask@tiger.thukraine.com  Tue Aug 22 11:36:36 2000
Return-Path: <stask@tiger.thukraine.com>
Received: from columbus.cris.net (columbus.cris.net [212.110.128.65])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0B1B437B423; Tue, 22 Aug 2000 11:36:20 -0700 (PDT)
Received: from tiger.thukraine.com (nat.thukraine.com [212.110.132.221] (may be forged))
	by columbus.cris.net (8.9.3/8.9.3) with ESMTP id VAA41155;
	Tue, 22 Aug 2000 21:02:34 +0300 (EEST)
Received: (from stask@localhost)
	by tiger.thukraine.com (8.9.3/8.9.3) id TAA30766;
	Tue, 22 Aug 2000 19:20:19 +0300
Message-Id: <200008221620.TAA30766@tiger.thukraine.com>
Date: Tue, 22 Aug 2000 19:20:19 +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:         20786
>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:   Tue Aug 22 11:40:01 PDT 2000
>Closed-Date:    Mon Sep 25 12:12:37 PDT 2000
>Last-Modified:  Mon Sep 25 12:13:11 PDT 2000
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 > From wpaul@FreeBSD.ORG  Tue Aug 15 20:07:26 2000
 
 > 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.
 >
 > 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.
 
 I could not reproduce it. Probably it is good idea to close PR. Maybe
 someone has something against it - but I don't. I could not reproduce
 the problem during last week. If one will account this problem again,
 it is good idea to try to upgrade to 4.1 or later.
 
 Thank you.
 
 \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:12:37 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:12:37 PDT 2000 
Responsible-Changed-Why:  
Not a PR 

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