From nobody@FreeBSD.org  Thu Feb 17 07:26:20 2005
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 3224816A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 17 Feb 2005 07:26:20 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1BA2443D5A
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 17 Feb 2005 07:26:20 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j1H7QJbs019915
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 17 Feb 2005 07:26:19 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j1H7QJNv019914;
	Thu, 17 Feb 2005 07:26:19 GMT
	(envelope-from nobody)
Message-Id: <200502170726.j1H7QJNv019914@www.freebsd.org>
Date: Thu, 17 Feb 2005 07:26:19 GMT
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: aMule hardlocks AMD64 system
X-Send-Pr-Version: www-2.3

>Number:         77629
>Category:       amd64
>Synopsis:       aMule hardlocks AMD64 system
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 17 07:30:18 GMT 2005
>Closed-Date:    Fri Nov 25 17:02:49 GMT 2005
>Last-Modified:  Fri Nov 25 17:02:49 GMT 2005
>Originator:     Markus Trippelsdorf
>Release:        5.3-STABLE
>Organization:
>Environment:
FreeBSD bsd.trippelsdorf.de 5.3-STABLE FreeBSD 5.3-STABLE #5: Sat Feb 12 21:34:47 UTC 2005     markus@bsd.trippelsdorf.de:/usr/obj/usr/src/sys/MYKERNEL  amd64
>Description:
running aMule for >1h deterministicly hardlocks my system.
No problem is reported in dmesg and the only way to proceed
is a soft reset.
>How-To-Repeat:
Run ports/net/amule and use the program in it's intended way.

>Fix:
No fix is known. I would be glad to help in debugging the problem,
just let me know what other infos you need.

>Release-Note:
>Audit-Trail:

From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: freebsd-gnats-submit@FreeBSD.org, markus@trippelsdorf.de
Cc:  
Subject: Re: amd64/77629: aMule hardlocks AMD64 system
Date: Tue, 22 Feb 2005 07:15:27 +0100

 After further investigation it turned out that fxp Ethernet driver was
 the cause of my problems. I bought a new NIC (RealTek 8169S chip)
 yesterday and everything is working fine and stable now.
 For the record: I'm using an AMD64 939 motherboard (ASUS A8V) with a
 64bit kernel.
 
State-Changed-From-To: open->closed 
State-Changed-By: arved 
State-Changed-When: Fri Nov 25 16:59:48 GMT 2005 
State-Changed-Why:  
Close, the problem seems to be resolved by using a different hardware. 

If the fxp card is still broken on 6.0 and you think this is a driver  
issue please report with more detailed information about the specific 
hardware revision 

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