Comment 5 for bug 1080789

Revision history for this message
Sean Feole (sfeole) wrote :

Moving bug back to a New status since it's not currently assigned to anyone.

Per comment #4 if this is a Tegra3 potential bug then it will have to be brought to NVidia's attention.