Bug 77629

Summary:	aMule hardlocks AMD64 system
Product:	Base System	Reporter:	Markus Trippelsdorf <markus>
Component:	amd64	Assignee:	freebsd-amd64 (Nobody) <amd64>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	5.3-STABLE
Hardware:	Any
OS:	Any

Description Markus Trippelsdorf 2005-02-17 07:30:18 UTC

running aMule for >1h deterministicly hardlocks my system.
No problem is reported in dmesg and the only way to proceed
is a soft reset.

Fix: 

No fix is known. I would be glad to help in debugging the problem,
just let me know what other infos you need.
How-To-Repeat: Run ports/net/amule and use the program in it's intended way.

Comment 1 Markus Trippelsdorf 2005-02-22 06:15:27 UTC

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.

Comment 2 Tilman Keskinoz freebsd_committer

2005-11-25 16:59:48 UTC

State Changed
From-To: open->closed

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