CONFIG_DMA_CMA causes performance problems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
After upgrade to utopic, regular freezes for some seconds to some minutes appeared. Linux freezes with up-to-date linux-image from repository (version 3.16.0-11.16). It doesn't matter, whether I use radeon or vesa driver.
Discussion about the bug in either X or kernel happened on
http://
WORKAROUND: Using custom kernel compiled from provided source of 3.16.0-11.16 with CONFIG_DMA_CMA=n solves the problem.
---
ApportVersion: 2.14.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
DistroRelease: Ubuntu 14.10
MachineType: Hewlett-Packard HP ProBook 4510s
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
Tags: utopic utopic
Uname: Linux 3.16.1 x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: Upgraded to utopic on 2014-08-23 (6 days ago)
UserGroups: audio dialout firebird games libvirtd lp sudo users wireshark
WifiSyslog:
_MarkForUpload: True
dmi.bios.date: 12/02/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PZI Ver. F.18
dmi.board.name: 3074
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 24.0F
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP ProBook 4510s
dmi.product.
dmi.sys.vendor: Hewlett-Packard
tags: | added: bios-outdated-f.20 |
description: | updated |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1363384
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.