Please, notify this bug has been resolved and the bug description is not
adequate - the root couse is not hardware dependent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326567
Title:
[Asus
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326567
Looking at the description of above macros at ./include/drm/drmP.h the
logging is active only when drm.debug kernel option is set. Indeed I
found this option in my /etc/default/grub file:
GRUB_CMDLINE_LINUX_DEFAULT=plymouth:debug splash quiet drm.debug=0xe
It seems the option is not default in
There is also another place with produces the second type of message
(drm:drm_mode_addfb) - in the file:
linux-source-3.13.0/drivers/gpu/drm/drm_crtc.c:
DRM_DEBUG_KMS([FB:%d]\n, fb-base.id);
Commenting this and the line in prevoius post makes the kernel log to be
quiet.
--
You received this
Does this need to be pushed upstream? Who is the people ultimately
responsible for that code, the kernel hackers or is this outside that
project?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326567
Thanks Christopher but I think my problem is pretty the same as in this
bug report. Looking at the source code provided with Ubuntu 14.04
distribution it seems the reason is just some debug logging switched on
in the kernel file:
linux-source-3.13.0/drivers/gpu/drm/radeon/radeon_display.c
There
I have similiar problem but with different motherboard - K8T Neo2-F and
Radeon 9550.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326567
Title:
[Asus M4A88T-M] problem with drm:drm_mode_addfb and
Radoslaw, thank you for your comment. So your hardware and problem may be
tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into the default Ubuntu kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please read the
