aMule Forum

English => Multiplatform => Mac OSX => Topic started by: iManc on August 24, 2005, 12:16:10 PM

Title: aMule 2.0.3 and last CVS kernel panic
Post by: iManc on August 24, 2005, 12:16:10 PM
Hi,
I'm an aMule Mac User since one week and after I've installed the latest Security Update, my iBook has frequently kernel Panic. I've reinstalled the OS X 10.4.2 without the security update and, for now, it's all OK.

A my friend with OS X 10.3.9, also, has the same problem.

Anyone of you has this strange behaviour or can resolve it.
Thaks.
Title: Re: aMule 2.0.3 and last CVS kernel panic
Post by: lfroen on August 24, 2005, 02:08:29 PM
amule is user mode application like many out there. Kernel panic is result of bug in kernel. Plain and simple. No application can be hold responsible for trashing kernel. I guess you can forward this question to Apple.
Title: Re: aMule 2.0.3 and last CVS kernel panic
Post by: lionel77 on August 24, 2005, 06:06:36 PM
So your friend running 10.3.9 has the same problem? Then I highly doubt that amule has anything to with it (thousands of users are running amule under those conditions without problems).

What your friend might want to try:
Boot the computer with apple+s held down to boot into single user mode. There do a "fsck -fy" to check and repair the bootdisk. Then "reboot".
Once the computer is back in regular OS X use Disk Utility to repair permissions.

Hope this helps :)
Title: Re: aMule 2.0.3 and last CVS kernel panic
Post by: iManc on August 24, 2005, 06:11:05 PM
Thanks,
I'll try this solution.  :baby:

But, why does the mac crash only when aMule is opened and connected?

I'll keep you informed. Goodbye!
Title: Re: aMule 2.0.3 and last CVS kernel panic
Post by: ken on August 26, 2005, 08:51:32 AM
Back when I was using Panther, I occasionally had my Mac lock up when using BitTorrent, which I believe had to do with the fact that BitTorrent opened many connections simultaneously and quickly.  Now, lfroen is correct that this is a kernel bug that is Apple's fault.  However, to work around it, make sure to use reasonable limits for "Max. Connections" and "Max. new connections / 5 sec.".  I'm using 500 and 20, respectively, without problems.