Comment 5 for bug 1132129

Hi,

This week, a new kernel was available for quantal : 3.5.0-25-generic, and used.
After 1 day 2:59 uptime and usual activity, another oops occurred.

To help figure out a possible culprit, here is a summary of recent activity.
* using for days a heavily loaded firefox (total of 27 windows and 91 tabs, session restored after reboot to change kernel)
* opening a 16000x16000 JPEG, namely http://www.eso.org/public/archives/images/large/eso1309a.jpg
* plugging Galaxy Nexus smartphone on USB
* observing USB mouse suddenly not working, but mouse laser light still on
* unplugging-replugging USB mouse. Mouse laser light now off.
* observing system freeze for about 5 seconds (probably music, too)
* observing switch to text mode and oops text (like described in original bug report)
* switching VTs using Ctrl-Alt-Fn to regain X session access
* observing firefox taking 100% of one cpu core and memory 3.2GB (varying, 2.9GB after a while, still 100% cpu)
* not observing signifiant system slowdown or led showing disk thrashing
* machine has 6GB physical RAM + 6GB swap, using 4.7GB RAM and virtually no swap (58MB)
* observing rhythmbox has stopped playing when oops occurred. Pausing/playing changes the "play/pause" status in rhythmbox window, but time indicator does not move and no sound produced.
* opening another firefox window to write this very report
* while I type, rhythmbox resumed playing (after about a minute without touching it)

On previous bugs occurrences, firefox also was heavily loaded a Galaxy Nexus plugged recently on USB.
Firefox was also loaded all the week, though probably a bit less, and phone is plugged/unplugged more than daily.

Attached dmesg from command line because /var/log/dmesg does not contain oops text.

Considering to try latest kernel soon.

Hope this helps. Thank you for your attention.