This on happens on my intel g45 machine (not on my 965 laptop which also uses the intel driver). I'm currently seeing this bug on pre-release ubuntu jaunty which got an early 2.6.28 rc kernel and intel 2.5.1 however, I also saw the same bug when I was running intrepid ibex (which had a 2.6.27 based kernel with intel 2.4.1). Basically what happens is that /bin/dd, /sbin/klogd, /sbin/syslogd constantly take up 30-100% of a single core on my machine. This happens because some strange error is being fired constatly from the intel xorg driver. My dmesg has an endless flood of errors like this: [ 1862.521238] [drm:drm_ioctl] pid=5442, cmd=0xc0086444, nr=0x44, dev 0xe200, auth=1 [ 1862.521240] [drm:i915_emit_irq] [ 1862.521243] [drm:drm_ioctl] pid=5442, cmd=0x40046445, nr=0x45, dev 0xe200, auth=1 [ 1862.521245] [drm:i915_wait_irq] irq_nr=654659 breadcrumb=654659 [ 1862.521309] [drm:drm_ioctl] pid=5442, cmd=0x40206443, nr=0x43, dev 0xe200, auth=1 [ 1862.521311] [drm:i915_batchbuffer] i915 batchbuffer, start ffaa000 used 40 cliprects 0 [ 1862.521314] [drm:drm_ioctl] pid=5442, cmd=0xc0086444, nr=0x44, dev 0xe200, auth=1 [ 1862.521316] [drm:i915_emit_irq] [ 1862.521321] [drm:drm_ioctl] pid=5442, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1 [ 1862.521323] [drm:drm_lock] 1 (pid 5442) requests lock (0x00000002), flags = 0x00000000 [ 1862.521325] [drm:drm_lock] 1 has lock [ 1862.521328] [drm:drm_ioctl] pid=5442, cmd=0x40046445, nr=0x45, dev 0xe200, auth=1 [ 1862.521330] [drm:i915_wait_irq] irq_nr=654661 breadcrumb=654661 [ 1862.521338] [drm:drm_ioctl] pid=5442, cmd=0x40046445, nr=0x45, dev 0xe200, auth=1 [ 1862.521340] [drm:i915_wait_irq] irq_nr=654658 breadcrumb=654661 [ 1862.521342] [drm:drm_ioctl] pid=5442, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1 [ 1862.521344] [drm:drm_lock] 2 (pid 5442) requests lock (0x00000001), flags = 0x00000000 [ 1862.521346] [drm:drm_lock] 2 has lock [ 1862.521350] [drm:drm_ioctl] pid=5442, cmd=0xc0086444, nr=0x44, dev 0xe200, auth=1 [ 1862.521352] [drm:i915_emit_irq] [ 1862.521354] [drm:drm_ioctl] pid=5442, cmd=0x40046445, nr=0x45, dev 0xe200, auth=1 [ 1862.521356] [drm:i915_wait_irq] irq_nr=654662 breadcrumb=654662 [ 1862.521418] [drm:drm_ioctl] pid=5442, cmd=0x40206443, nr=0x43, dev 0xe200, auth=1 [ 1862.521420] [drm:i915_batchbuffer] i915 batchbuffer, start ffaa000 used 40 cliprects 0 [ 1862.521424] [drm:drm_ioctl] pid=5442, cmd=0xc0086444, nr=0x44, dev 0xe200, auth=1 [ 1862.521426] [drm:i915_emit_irq] [ 1862.521430] [drm:drm_ioctl] pid=5442, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1 [ 1862.521432] [drm:drm_lock] 1 (pid 5442) requests lock (0x00000002), flags = 0x00000000 [ 1862.521434] [drm:drm_lock] 1 has lock [ 1862.521440] [drm:drm_ioctl] pid=5442, cmd=0x6458, nr=0x58, dev 0xe200, auth=1 [ 1862.538391] [drm:drm_ioctl] pid=5442, cmd=0x6458, nr=0x58, dev 0xe200, auth=1 [ 1862.538407] [drm:drm_ioctl] pid=5442, cmd=0x6458, nr=0x58, dev 0xe200, auth=1 [ 1862.586385] [drm:drm_ioctl] pid=5442, cmd=0x6458, nr=0x58, dev 0xe200, auth=1 [ 1862.586401] [drm:drm_ioctl] pid=5442, cmd=0x6458, nr=0x58, dev 0xe200, auth=1 [ 1862.586718] [drm:drm_ioctl] pid=5442, cmd=0x6458, nr=0x58, dev 0xe200, auth=1
This happens on a desktop machine with a Gigabyte GA-EG45M-DS2H (G45-chipset, Socket-775) motherboard that has a GMA X4500HD (G45) on it. Xorg log etc is attached to the corresponding ubuntu bug report here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/305983 Direct link to xorg_log is here: http://launchpadlibrarian.net/20281088/XorgLog.txt
You've enabled debug in the drm module, probably by the module parameter. Don't do that.
You we're right Eric, sorry for wasting your time.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.