[Asus M4A88T-M] problem with drm:drm_mode_addfb and drm:radeon_crtc_page_flip

[[e-mail]]

My kern log is full of literally millions of entries like this:

Jun 1 07:51:05 atkinson-phenomIIx4 kernel: [119346.952590] [drm:drm_mode_addfb], [FB:58]
Jun 1 07:51:05 atkinson-phenomIIx4 kernel: [119346.952610] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = ffff8803de155400, cur_bbo = ffff880407586000
Jun 1 07:51:05 atkinson-phenomIIx4 kernel: [119346.952632] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = ffff8803de155400, cur_bbo = ffff880407586000

I have found places where other have the problem. But none seem to fix the problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-27-generic 3.13.0-27.50
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: oatkinson 3117 F.... pulseaudio
 /dev/snd/controlC1: oatkinson 3117 F.... pulseaudio
 /dev/snd/controlC0: oatkinson 3117 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Jun 4 16:21:04 2014
HibernationDevice: RESUME=UUID=17c46ec6-2541-4e10-9ec2-258d229f3bd8
InstallationDate: Installed on 2011-08-19 (1020 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=3a8918dc-2e21-42ab-8e62-106b9b8f895e ro vesafb.invalid=1 drm.debug=0xe nopat plymouth:debug
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-27-generic N/A
 linux-backports-modules-3.13.0-27-generic N/A
 linux-firmware 1.127.2
RfKill:

SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to trusty on 2014-04-18 (47 days ago)
dmi.bios.date: 12/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2403
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A88T-M
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2403:bd12/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88T-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.2-trusty/

[[e-mail] (olin-atkinsontech)]

Sorry this took so long. I tested with v3.13.11.2-trusty and v3.13.11.3-trusty kernels and they both exhibited the problem.

[Joseph Salisbury (jsalisbury)]

The 3.13.11.5 kernel is also now out. Can you give it a test:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.5-trusty/

[penalvch (penalvch)]

<email address hidden>, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/ and advise to the results?

[Radoslaw (radraw)]

I have similiar problem but with different motherboard - K8T Neo2-F and Radeon 9550.

[penalvch (penalvch)]

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 official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Radoslaw (radraw)]

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 is radeon_crtc_page_flip function that contains:

 DRM_DEBUG_DRIVER("flip-ioctl() cur_fbo = %p, cur_bbo = %p\n",
    work->old_rbo, rbo);

The command is called unconditionally. Solution seems to be simply removing or commenting out above line.

[Radoslaw (radraw)]

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.

[flickerfly (josiah-ritchie)]

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?

[Radoslaw (radraw)]

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 recent Ubuntu release (at least 14.04), becouse restoring content of the file to default makes the line look like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

How the drm.debug option did get to the configuration file I don't know. Maybe this is remainder from prevoius Ubuntu release ant stayed after upgrade ?

Thus there is no need to recompile kernel modules, just remove the drm.debug kernel option from /etc/grub/default and regenerate grub configuration with update-grub.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Radoslaw (radraw)]

Please, notify this bug has been resolved and the bug description is not adequate - the root couse is not hardware dependent.