Summary: | Moving cursor causes kernel: [40048.265024] [drm:drm_atomic_set_fb_for_plane] Set [FB:61] for plane state ffff88002bb02e40 to be entered to syslog thousands of times | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Chris <cpollock> | ||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Severity: | normal | ||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||
Version: | unspecified | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Created attachment 114488 [details]
Output of dmidecode
So why do you have (drm.debug & 0x10) set? In regards to the drm.debug setting in my GRUB_CMDLINE_LINUX_DEFAULT="drm.debug=0x66" I was asked to add that in regards to another bug I was adding information to https://bugs.freedesktop.org/show_bug.cgi?id=75394, comment #12. I'm not sure what you're referring to by the '0x10' setting. I see, I've removed the GRUB_CMDLINE_LINUX_DEFAULT="drm.debug=0x66 in my /etc/default/grub file and this has now quit. I assume then that it was the debug command that was creating it. I apologize then for the noise in creating this bug report. No problem. If this had been spewing w/o the debug flag set, it would have been a serious bug. Glad to see it was just expected debug output. |
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.
Created attachment 114487 [details] Output of lshw First of all I'm still a bit new on doing bug reports so hopefully I've gotten all the information correct. System information, Ubuntu 14.04.2 LTS, kernel 4.0.0-040000rc4-generic #201503152135 SMP Mon Mar 16 01:36:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux. During times that I'm using the system each time the mouse is moved lines such as this will be added to my syslog: Mar 20 08:24:15 localhost kernel: [45661.199471] [drm:drm_atomic_set_fb_for_plane] Set [FB:59] for plane state ffff8800d742fa80 Mar 20 08:24:15 localhost kernel: [45661.207468] [drm:drm_atomic_set_fb_for_plane] Set [FB:59] for plane state ffff8800d742fe40 Mar 20 08:24:15 localhost kernel: [45661.215464] [drm:drm_atomic_set_fb_for_plane] Set [FB:59] for plane state ffff8800d742fa80 Mar 20 08:24:15 localhost kernel: [45661.223477] [drm:drm_atomic_set_fb_for_plane] Set [FB:59] for plane state ffff88002bb02cc0 Mar 20 08:24:15 localhost kernel: [45661.231456] [drm:drm_atomic_set_fb_for_plane] Set [FB:59] for plane state ffff8800d742fe40 During the day this amounts to the thousands of lines such as this. For instance yesterdays syslog was 47Mb in size. Since the system is idle from about 10pm until 6:30am no entries such as this are made.