aMule Forum
English => en_Bugs => Topic started by: chrisb on May 21, 2009, 12:42:58 AM
-
I run gentoo.
On one system amule locks up the computer, the other runs ok.
I't started when I upgraded to 2.2.4.
I'm not sure what causes but I suspect it has something to do with shared files, I removed a shared directory and it started to work again, however it crashed again when I downloaded more files and left them in the Incomming directory.
Any ideas?
-
How many files are you talking about?
What kind of crash? Log, backtrace?
-
what kind of crash.... the entire system completely locks up
the amule log looks fine
it has been happening while hashing files
i upgraded from 2.2.3 to 2.2.4 where it was working fine
currently im sharing files then i have used in the past
i recently removed the shard file and now it lock up pretty quickly e.g. 30 seconds
-
it locked up because of a corrupt part in a file i was downloading
i cant be exactly sure but the other time it was locking up while hashing an already downloaded file.
-
amule was running and my computer locked up again, while amule wasnt running the computer didnt lock up
-
These may sound like questions that have been asked before but:
have you tested using memtest86+?
Have you tried the option to scan all memory, instead of just testing what the bios reports?
Have you checked your hard drive smartctl reports?
Have you opened your case and checked for bulging/leaking capacitos on the motherboard?
These may sound strange, but many hardware faults will cause mysterious crashes that only manifest when the system load is cranked up and you have to eliminate these as a cause of system lockups before blaming a userspace program.
-
Does it really lock up, or does it only slow down the machine to a state where you are unable to do anything?
-
how can you tell the difference between locking up and slowing down?
the macine responds to nothing at all
-
These may sound like questions that have been asked before but:
have you tested using memtest86+?
Have you tried the option to scan all memory, instead of just testing what the bios reports?
Have you checked your hard drive smartctl reports?
Have you opened your case and checked for bulging/leaking capacitos on the motherboard?
These may sound strange, but many hardware faults will cause mysterious crashes that only manifest when the system load is cranked up and you have to eliminate these as a cause of system lockups before blaming a userspace program.
tried the memory scan, no problems
how do i check then hdd smartctl reports?
hardware looks fine?
NOTE: the first few times it happened it always occured on the same file
when it happened the first time it was after hasing about 30 other files
the second time it occured on the second file
each time when i removed the suspect files it worked flawlessly
this hardly sound like a hardware issue
i also tried emilinating cranking up the system load
now it simply crashes while downloading a few files and not sharing anything else
i've cranked the system by doing the following at once
1. compling
2. md5hasing all files
3. moving files
4. running a benchmark program
-
Does it really lock up, or does it only slow down the machine to a state where you are unable to do anything?
In the first case the machine doesn't respond even though it doesn't seem to do anything.
In the second case the machine doesn't respond, but you can see that the HD led is flashing.
-
this is strange, but I got something like this the other day with 'SVN-r9617'
the upload queue suddenly went down to 0.0 then full system freeze with keyboard lights flashing and X completely locked.
i personally thinks its got to do with just upgrading kernel though..
-
yep i'm also thinking its a kernel bug that amule has somehow exposed
-
btw, I've downgrading from '2.6.29.4' to '2.6.29.3'
I've stress tested this on numerous environments and had no crashes, thus, I think it 'was' a kernel lockup....
I'am on a ArchLinux Rolling Release.
....running r9622 comfortably.
happy muleing. :D
-
it was locking up using 2.6.28.9
i now run it on my laptop 2.6.28-tuxonice-r10 with no, problems
i still have a copy of the faulty file, I wonder what will happen if i share the faulty file via NFS