@jamie -- i am unsure why the new kernel would provoke those more than before (or are we saying it didn't work before so you could not provoke it). But looking at the latest kernels this messasge is now officially gone from the kernel under the commit below, the commentary there implies this message is totally benign:
commit a8c051f0c8d2f81c665e820f765aaddf86161640
Author: Jean Delvare <email address hidden>
Date: Fri Oct 8 14:34:49 2010 +0200
drm/radeon/kms: Silent spurious error message
I see the following error message in my kernel log from time to time:
radeon 0000:07:00.0: ffff88007c334000 reserve failed for wait
radeon 0000:07:00.0: ffff88007c334000 reserve failed for wait
After investigation, it turns out that there's nothing to be afraid of
and everything works as intended. So remove the spurious log message.
Signed-off-by: Jean Delvare <email address hidden>
Reviewed-by: Jerome Glisse <email address hidden>
Signed-off-by: Dave Airlie <email address hidden>
@jamie -- i am unsure why the new kernel would provoke those more than before (or are we saying it didn't work before so you could not provoke it). But looking at the latest kernels this messasge is now officially gone from the kernel under the commit below, the commentary there implies this message is totally benign:
commit a8c051f0c8d2f81 c665e820f765aad df86161640
Author: Jean Delvare <email address hidden>
Date: Fri Oct 8 14:34:49 2010 +0200
drm/radeon/kms: Silent spurious error message
I see the following error message in my kernel log from time to time:
radeon 0000:07:00.0: ffff88007c334000 reserve failed for wait
radeon 0000:07:00.0: ffff88007c334000 reserve failed for wait
After investigation, it turns out that there's nothing to be afraid of
and everything works as intended. So remove the spurious log message.
Signed-off-by: Jean Delvare <email address hidden>
Reviewed-by: Jerome Glisse <email address hidden>
Signed-off-by: Dave Airlie <email address hidden>