kerneloops eating up cpu
jackson byers
byersjab at gmail.com
Sun Nov 29 23:54:25 UTC 2009
After googling I found this to be a common problem
when some error message is flooding /var/log/messages.
Apparently it is ok to killall kerneloops;
I did,
and this does of course stop it from eating cpu.
But it doesn't solve the basic problem, what is flooding the messages file?
In my case it is huge number of lines:
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_reset] *ERROR*
mga_dma_reset called without lock held, held 0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_flush] *ERROR*
mga_dma_flush called without lock held, held 0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_reset] *ERROR*
mga_dma_reset called without lock held, held 0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_flush] *ERROR*
mga_dma_flush called without lock held, held 0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_reset] *ERROR*
mga_dma_reset called without lock held, held 0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_flush] *ERROR*
mga_dma_flush called without lock held, held 0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_reset] *ERROR*
mga_dma_reset called without lock held, held 0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_flush] *ERROR*
mga_dma_flush called without lock held, held 0 owner f4041ae0
f4041ae0
Any advice on this?
Might it be tied to my somewhat frequent X-freezes?
As it stands now I will still continue to get the large messages file
requiring me to truncate the file, every day or so
Jack
More information about the fedora-list
mailing list