Date: Thu, 17 Feb 2005 07:26:19 GMT From: Markus Trippelsdorf <markus@trippelsdorf.de> To: freebsd-gnats-submit@FreeBSD.org Subject: amd64/77629: aMule hardlocks AMD64 system Message-ID: <200502170726.j1H7QJNv019914@www.freebsd.org> Resent-Message-ID: <200502170730.j1H7UJYN096120@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 77629 >Category: amd64 >Synopsis: aMule hardlocks AMD64 system >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 17 07:30:18 GMT 2005 >Closed-Date: >Last-Modified: >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: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502170726.j1H7QJNv019914>