Created attachment 1383 [details] the packages I installed this morning This morning I updated cauldron on a laptop for the first time in three days (it was a fresh Mga2a2 install that has been updated since) Since those updates, my /var/log/messages fills with a tsunami of "kernel: [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times" messages The same happens when using older kernels. A list of the packages I installed this morning before this bug occurred, is attached
Created attachment 1384 [details] lspcidrake -v output
Created attachment 1385 [details] Xorg.0.log.old I won't attach /var/log/messages, it is too big and it contains nothing but the line in the summary of this bug being endlessly repeated
Frederik Himpe just said a change in clutter might expose a kernel bug There was some clutter stuff among the updates. cc'ing kernel maintainer :)
CC: (none) => tmb
Created attachment 1394 [details] var/log/messages-20120118 I was wrong. If an update caused this, it was caused by one from 3 days earlier. Scrolling through /var/log/messages, now learns me that * there were already over 20.000 of those identical messages from 08:43:51h till 08:44:46h yesterday (so in only one minute) right after I had booted my system. * these messages weren't there on January 15th (last time laptop was used and updated) or before * It stops every time when uprmi --auto-update is done, but starts again later. (there are more things that make it stop) first attaching the var/log/messages from first boot yesterday till first time "kernel: [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times" message appears after that attaching the list of updates (konsole output) from January 15th.
Attachment 1383 is obsolete: 0 => 1
Created attachment 1395 [details] updates201101152001 Now attaching the urpmi --auto-update output from January 15th
There is a warning in it about update 68 (Default-kde-config) I hadn't seen before. (see attachment 1395 [details]) @ mikala Is there any chance that warning has anything to do with my problem?
CC: (none) => balcaen.john
it's not related at all.
clean Mga2a3 install with updates (/ formatted, /home kept) the problem is still there
(In reply to comment #8) > clean Mga2a3 install with updates (/ formatted, /home kept) > the problem is still there those updates were from the last step when I installed Mga2a3, and before I booted into freshly installed Mga2a3 I just enabled nonfree and tainted media, updated again and rebooted. The problem is gone. (Sorry, can't tell what the last updates were) Closing
Status: NEW => RESOLVEDResolution: (none) => FIXED