Comment 4 for bug 1643719

Hello Joseph,

This issue seems to happen randomly. Between the time I posted this bug and now, I decided to mount /var/log on a separate partition, to allow me to use my system the next time this error occurs and to be able to better report bugs. I have not yet experienced the bug but it will probably happen again randomly.

I will try upgrading my kernel to the upstream version you linked, and I'll let you guys know the next time this happens.

However, before I do that, I want to ask, on that page it says "First, if one is using select proprietary or out-of-tree modules (ex. vitualbox, nvidia, fglrx, bcmwl, etc.)...", does this mean I would have to use the nouveau drivers instead of Nvidia's proprietary drivers if I wanted to test this against the upstream kernel? As a gamer, I wouldn't be willing to do that until it happens again, the nouveau drivers are not very good. Also, I have several other proprietary applications on my system, such as Dropbox, and TeamViewer, and Google Chrome.

Note, also, that I'm not really asking for the fix to be preventing this error, because I'm sure that there is some other problem with my system causing such an error, but I'm instead asking for a "speed limit" for these error messages, to prevent systems from becoming unusable due to gigantic log files, which would be bad should anyone else have this same issue.