Comment 4 for bug 1097396

Hi Tony,

Do you happen to know the last kernel version that did not cause this panic? You should be able to identify in by reviewing the grub menu or reviewing /var/log/dpkg.log*

If you can identify the last good and first bad kernel, I can perform a kernel bisect to identify the commit that caused the regression.

Another good test would be to see if this still happens in the latest development kernel, so we know if it exists in Raring. If you have a chance, can you test v3.8-rc2? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc2-raring/

Note that you will need to install both the linux-image and linux-image-extra .deb packages.