Comment 256 for bug 263555

All,

If you read the entire thread pointed to in #7 you would have read Intel response to this. The thread has to do with VMWare and not Linux. VMWare is based on a very old kernel that has some poor kernel locking issues. We pointed this out to them and asked the question is any of the people responding had actually seen this problem on Linux. This is where thing went awry a bit. All (_all_) of the reports that we have so far have had this gfx panic just before this problem comes up. The current belief is that the gfx panic is scribbling all over our NVM space somehow. We are not sure how this is happening. Since we can't repro the problem without this panic happing first this is very hard for us to look at. If the gfx panic does not happen there have been no problems reported. I do not know the status of a fix for the gfx panic. We are working on repro cases but because the problem relies on a panic to another driver this is very hard for us to work on. Work will continue.