Hi, I'm running into some issues while using rtorrent on my raspberrypi.
I have an external, self powered 300gb NTFS drive mounted using ntfs-3g to /mnt/sda1. I am also running rtorrent in a background screen session using the recommended init.d startup script. rtorrent is configured to use ~/rtorrent/watch and ~/rtorrent/session as it's watch and session directories (which are located on the sd card), and /mnt/sda1/rtorrent/downloads as the primary download directory.
After 30 mins or so of downloading a single torrent at ~1MB/s,
the Raspi crashes and I get the message:
Unable to handle kernel paging request at virtual address 8e78b8a2
Internal error: Oops: 805 [#1] PREEMPT
Entering kdb (current0xca4ec520, pid 1313 Oops: (null) due to oops @ 0xc024d3d4
along with a whole bunch of other data on registers etc.
I am using a 4gb class 4 SD card with the paging file extended to fill. It does not matter whether I use the 192/64 or 224/32 memory split, it only buys a little more time before the error occurs. CPU usage stays around 80-100% and free memory jumps around 10-50mb the entire time rtorrent is running. ntfs-3g and rtorrent are using all the cpu and memory.
From the appearance of the OK status led, the SD card is getting accessed in short pulses and fairly frequently, but its not getting "hammered" in any way to suggest heavy swap use. Swap Free stays around 92MB, so the RaspberryPi does not appear to be running out of swap.
I'm running the Raspian (Debian wheezy 2012-07-15) image and have my raspberrypi powered using the apple ipad charger, and the voltages seem to stay at 4.9V stable, so I don't think it's a power issue. either. I'm running stock clocks and the cpu and usb chips are warm but not overly hot to the touch.
At this stage the only thing I can think of is that swap read/write requests are somehow timing out (is this even possible?), but other than that I have no idea. The terminal (local, not ssh) does seem very sluggish at times and input does get delayed a bit. I've googled for similar problems but come up with very little. Are there any log files I could check to try and find out more about why this occurred? Any help would be greatly appreciated.