From nobody@FreeBSD.org  Wed Jul 28 15:00:43 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4A5E916A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 28 Jul 2004 15:00:43 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 42A6043D66
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 28 Jul 2004 15:00:43 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i6SF0hjS089258
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 28 Jul 2004 15:00:43 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i6SF0hPr089257;
	Wed, 28 Jul 2004 15:00:43 GMT
	(envelope-from nobody)
Message-Id: <200407281500.i6SF0hPr089257@www.freebsd.org>
Date: Wed, 28 Jul 2004 15:00:43 GMT
From: Morgoth <morgothdbma@o2.pl>
To: freebsd-gnats-submit@FreeBSD.org
Subject: just quite unstable (panic when burncd fails, or when checking ufs1/ufs2, heavy load panics)
X-Send-Pr-Version: www-2.3

>Number:         69713
>Category:       amd64
>Synopsis:       just quite unstable (panic when burncd fails, or when checking ufs1/ufs2, heavy load panics)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-amd64
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 28 15:10:21 GMT 2004
>Closed-Date:    Sun Aug 22 09:44:38 GMT 2004
>Last-Modified:  Sun Aug 22 09:44:38 GMT 2004
>Originator:     Morgoth
>Release:        5.2.1
>Organization:
none
>Environment:
FreeBSD 5.2.1 amd64 morgoth@/usr/src/sys/conf/STARLIGHT
>Description:
sometimes 5.2.1amd64 is quite unstable, failed burncd can cause kpanic. Checking UFS1/UFS2 partition also causes kpanics sometimes. I have UDMA5 mode set by default when kernel starts.
>How-To-Repeat:
try to interrupt burncd (small probabilty). Just try to intensive use system (heavy load) for few hours...
>Fix:
   Very careful checking code for 32-->64bit porting problems??/
hmm.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: tjr 
State-Changed-When: Sun Aug 22 09:43:18 GMT 2004 
State-Changed-Why:  
Please try the upcoming 5.3-BETA releases and submit detailed problem reports 
if you can reproduce these problems. 

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