Hide Forgot
Description of problem: Kernel backtraces after syscall from userspace (which seems to cause future calls to backtrace, e.g., umount). Version-Release number of selected component (if applicable): kernel-3.1.6-1.fc16.x86_64 How reproducible: Don't know Steps to Reproduce: 1. Leave rtorrent idling 2. 3. Additional info: Here are the traces themselves (sorry the pictures aren't great): http://imgur.com/a/9SHRF
Nevermind, got one-too-many kernel crashes lately and decided to run memtest86+. Sure enough, one of the sticks was bad. Sorry to waste your time.