Comment 4 for bug 863736

This has occurred again and although it is not on the most recent kernel it had a slightly different call stack so I thought I would post the log just in case they help. This is on 3.0.0-13-generic.

The interesting bit is that every stack has a call to schedule near the top. This hints to me that something has changed.

This crash happened while I was both reading and writing somewhat heavily from different processes (a fast filling log file, an MP3 player, and a large image being loaded). That's as close as I know for how to reproduce. It does not happen often so it's really hard to figure out a pattern.