CONFIG_DMA_CMA causes ttm performance problems/hangs

Bug #1362261 reported by Andreas Schultz
56
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned
Trusty
Confirmed
Medium
Unassigned
Utopic
Fix Released
Medium
Unassigned

Bug Description

The x86_64 kernels have CONFIG_DMA_CMA enabled, this causes extrem hangs of at least the RADEON driver

full discussion is here: http://lists.freedesktop.org/archives/dri-devel/2014-August/065842.html

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-10-generic 3.16.0-10.15
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aschultz 2224 F.... pulseaudio
 /dev/snd/controlC1: aschultz 2224 F.... pulseaudio
CurrentDesktop: XFCE
Date: Wed Aug 27 18:57:02 2014
HibernationDevice: RESUME=UUID=702fb398-84d9-4e93-9b4b-980323bf2d53
MachineType: Hewlett-Packard HP EliteBook 8560w
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-10-generic root=UUID=9a10044a-a505-4049-b794-a0ab87709daa ro rootflags=subvol=@ quiet splash init=/lib/systemd/systemd vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-10-generic N/A
 linux-backports-modules-3.16.0-10-generic N/A
 linux-firmware 1.132
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-07-21 (37 days ago)
dmi.bios.date: 07/15/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SVD Ver. F.42
dmi.board.name: 1631
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 01.3D
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8560w
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Andreas Schultz (aschultz) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

The CONFIG_DMA_CMA parameter was enabled in trusty in Ubuntu-3.13.0-24.46 by commit:

a9d615a UBUNTU: Rebase to 2d3c627502f2a9b0a7de06a5a2df2365542a72c9

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
tags: added: kernel-key
Revision history for this message
Andy Whitcroft (apw) wrote :

Confirming this option is enabled for Trusty and Utopic, creating tasks there. Currently, the discussion is still ongoing, but the primary bug seems to be that DMA requests for order 0 pages are being passed into CMA which makes no sense and triggers the issue. We are expecting a patch for that to be pushed upstream shortly.

Revision history for this message
Andy Whitcroft (apw) wrote :

Overall the recommendation seems to be that this should be disabled on x86.

Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu Trusty):
status: New → Confirmed
Changed in linux (Ubuntu Trusty):
importance: Undecided → Medium
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I built a Trusty test kernel with CONFIG_DMA_CMA not set.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1362261/

Can you test this kernel can confirm it fixes the bug? Be sure to install both the linux-image and linux-image-extra .deb packages.

If it does fix the bug, I can submit and SRU request to have CONFIG_DMA_CMA disabled.

Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Utopic):
status: Triaged → Fix Committed
Revision history for this message
Gannet (ken20001) wrote :

Does CONFIG_DMA_CMA parameter enabled in 3.13.0-35 ? Because I have no problem with it unlike 3.16+.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks, Gannet. Can folks affected by this bug report if it does in fact affect Trusty, or only Utopic? If it does affect Trusty, there is a test kernel posted in comment #9.

Changed in linux (Ubuntu Trusty):
status: Confirmed → Incomplete
Revision history for this message
Gannet (ken20001) wrote :

As I wrote it affects me in Trusty with kernel 3.16 and higher. But with 3.13.0-35, also in Trusty, all it seems is ok.

Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :

For me this bug reproducible only with 3.16 and 3.17 kernels. With 3.15 and previous kernels this bug is not reproducible, at least on my hardware (Radeon HD 6620G).

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.16.0-16.22

---------------
linux (3.16.0-16.22) utopic; urgency=low

  [ Andy Whitcroft ]

  * Revert "SAUCE: x86/xen: Fix setup of 64bit kernel pagetables"
  * [Config] tools -- only build common tools when enabled
  * [Config] follow rename of DEB_BUILD_PROFILES

  [ Tim Gardner ]

  * [Debian] set do_*_tools after stage1 or bootstrap is determined
    - LP: #1370211
  * Release Tracking Bug
    - LP: #1370535

  [ Upstream Kernel Changes ]

  * x86/xen: don't copy bogus duplicate entries into kernel page tables
  * blk-merge: fix blk_recount_segments
    - LP: #1359146
  * igb: bring link up when PHY is powered up
    - LP: #1370018
  * igb: remove unnecessary break after goto
    - LP: #1370018
  * igb: remove unnecessary break after return
    - LP: #1370018
  * igb: Add message when malformed packets detected by hw
    - LP: #1370018
  * igb: bump igb version to 5.2.13
    - LP: #1370018
 -- Tim Gardner <email address hidden> Tue, 16 Sep 2014 10:19:04 -0600

Changed in linux (Ubuntu Utopic):
status: Fix Committed → Fix Released
Revision history for this message
Gannet (ken20001) wrote :

Recently checked 3.16.3 on Trusty. No problems. All is ok. Сheers !

Mathew Hodson (mhodson)
Changed in linux (Ubuntu Trusty):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.