Comment 11 for bug 144621

Hey Matt/Tim, are you still seeing this problem?

We haven't seen anything like this in our teams US and China - we're thinking it might have to do with different geographical locations? (U.S vs. Europe, etc.) although we won't know unless we see the debug info.

Can you load the driver with debug=0x41002 and attach the log after the problem happens?

I'll also try the folks at bug#133395 and ask if they can do the same (though the bug is not completely related)