Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Unassigned | ||
Utopic |
Fix Released
|
Medium
|
Unassigned | ||
Vivid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
When I first came across this issue I thought it was the same as bug #1316035 (https:/
I originally encountered this issue due to having a bunch of Dell servers that I was testing with kernel 3.13 on 12.04. The text console is so slow that it is unusable when using vi or doing an operation similar to dpkg -l |grep xorg. Comparing the exact same system with kernel 3.2 or 3.11 loaded and running lsmod, vesafb is listed and performance is excellent. It is not listed on the 3.13 system. The same issue exists on 14.04 with the 3.13 or 3.16 kernel.
Attempting to do modprobe vesa or modprobe vesafb returns modprobe: FATAL: Module vesa not found and modprobe: FATAL: Module vesafb not found respectively.
Attempting to use uvesafb on this hardware results in a black screen. Attempting to use vga16fb results in good performance, but I am locked to 640x480. I tried to use fbset to force higher resolutions, but it either results in a distorted display or tells me there is not enough memory.
I need a 1280x1024 console with performance equal to 12.04 with kernels 3.2-3.11. The server I'm using for testing is a Dell R320.
This appears to be regression as I can duplicate it by simply doing a fresh install of 12.04.1 and not having the issue, while doing a fresh install of 12.04.5, 14.04.1, or 14.04.2 results in a very slow console.
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Mar 20 13:17 seq
crw-rw---- 1 root audio 116, 33 Mar 20 13:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2015-03-20 (0 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Dell Inc. PowerEdge R320
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.127.11
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-46-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: root
_MarkForUpload: True
dmi.bios.date: 09/23/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.0.21
dmi.board.name: 0R5KP9
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: PowerEdge R320
dmi.sys.vendor: Dell Inc.
Related branches
CVE References
affects: | xorg-server (Ubuntu) → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: bios-outdated-2.3.3 |
Changed in linux (Ubuntu): | |
status: | Incomplete → Opinion |
status: | Opinion → Incomplete |
tags: | added: needs-bisect |
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
tags: | added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.0-rc5 |
tags: | added: latest-bios-2.3.3 |
Changed in linux (Ubuntu Vivid): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Utopic): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Trusty): | |
status: | Confirmed → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1434581
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.