Ticket #2718 (closed defect: invalid)

Opened 7 months ago

Last modified 7 months ago

Kernel panic - not syncing: Fatal exception in interrupt

Reported by: pope.xtream@gmail.com Owned by: rakshasa
Priority: high Component: rtorrent
Version: HEAD Severity: critical
Keywords: panic, trash, rtorrent Cc:

Description

I am using rTorrent 0.8.6/0.12.6, on a Debian Linux Machine. After download speed increases to about 7-8MB/s, the server-s memory is filling up to 100% and in a matter of seconds i get a kernel panic.

Some details about my system:

$ uname -a Linux ********* 2.6.32-5-686 #1 SMP Mon Oct 3 04:15:24 UTC 2011 i686 GNU/Linux

$ cat /proc/meminfo | grep MemTotal? MemTotal?: 514304 kB

$ cat /proc/cpuinfo | grep "model name" model name : Intel(R) Pentium(R) 4 CPU 1.80GHz

$ cat /etc/issue Debian GNU/Linux 6.0 \n \l

$ cat /etc/rtorrent.conf

min_peers = 20 max_peers = 1000 min_peers_seed = -1 max_peers_seed = 1000 max_uploads = 150 download_rate = 0 upload_rate = 0 directory = ************* session = /var/lock/rtorrent port_range = 32100-32200 port_random = yes check_hash = no use_udp_trackers = yes schedule = ip_tick,0,1800,ip=ip_ext schedule = bind_tick,0,1800,bind=ip_ext encryption = allow_incoming,enable_retry,prefer_plaintext dht = disable peer_exchange = no scgi_port=127.0.0.1:5000 max_memory_usage = 524288000

#hash_read_ahead = 8 #hash_max_tries = 5 #hash_interval = 10 #send_buffer_size = 1048576 #receive_buffer_size = 1048576 #max_open_http = 128

$ ulimit -m 514304

$ cat /proc/sys/net/ipv4/tcp_wmem 4096 16384 2019328

I am starting rtorrent using:

$screen -AmdS torrent rtorrent -b $ip_ext -n -o import=$conf -s $session

where

$ip_ext is my external dynami IPv4 Address $conf is /etc/rtorrent.conf $session is /var/lock/rtorrent

I am attaching the log taken via netconsole.

Attachments

panic.txt Download (11.2 KB) - added by pope.xtream@gmail.com 7 months ago.
Kernel panic Dump

Change History

Changed 7 months ago by pope.xtream@gmail.com

Kernel panic Dump

Changed 7 months ago by rakshasa

  • status changed from new to closed
  • resolution set to invalid

Kernel bugs aren't my problem.

Changed 7 months ago by anonymous

Your max_peers and max_peers_seed is way too high. If you have only 512 MB RAM to use, don't set it to more than 10.

Note: See TracTickets for help on using tickets.