I/O performance problems with kernel 3.15.x

Bug #1325819 reported by Removed by request
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Unassigned

Bug Description

I'm using Ubuntu 14.10 dev with linux-image-generic 3.15.0.5.6 and after the kernel 3.15.x was installed I noticed some I/O problems after a reboot. I'm noticing that now on every boot my hard disk will stop multiple times for a short time and logging out from the console does sometimes hang a few seconds.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.15.0-5-generic.
ApportVersion: 2.14.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: root 2613 F...m plugin-containe
 /dev/snd/controlC0: root 2613 F.... plugin-containe
 /dev/snd/timer: root 2613 f.... plugin-containe
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,18497662,00100101'
   Controls : 36
   Simple ctrls : 18
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19'
   Mixer name : 'Nvidia GPU 42 HDMI/DP'
   Components : 'HDA:10de0042,14583555,00100100'
   Controls : 21
   Simple ctrls : 3
CurrentDmesg:
 Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file or directory
 dmesg: write failed: Broken pipe
DistroRelease: Ubuntu 14.10
EcryptfsInUse: Yes
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-5-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq
ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
RfKill: Error: [Errno 2] No such file or directory
Tags: utopic
Uname: Linux 3.15.0-5-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.asset.tag: BC5FF4739C55
dmi.board.name: 960GM/U3S3 FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Removed by request (removed3425744) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected utopic
description: updated
Revision history for this message
Removed by request (removed3425744) wrote : AplayDevices.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : ArecordDevices.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : Card1.Amixer.values.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : Card1.Codecs.codec.0.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : HookError_source_linux.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : Lspci.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : PciMultimedia.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : ProcModules.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : UdevDb.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : UdevLog.txt

apport information

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1325819

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.

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

Are you able to reproduce the bug easily? If so, we can test some upstream kernels[0] to try and find the last good kernel and first bad kernel. If we can find those two, I can perform a kernel bisect to identify the specific commit that introduced the regression.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
tags: added: performing-bisect
Revision history for this message
Removed by request (removed3425744) wrote :

I have now tested some different versions to find the first problematic version. On the last test I have booted multiple times with kernel 3.13.11.2-trusty and all was working fine. But on booting multiple times with kernel 3.14-rc1-trusty I have always noticed this I/O issue.

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

I started a kernel bisect between v3.13 final and v3.14-rc1. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
365c483f190fea03971b3eca8d68406f425777b5

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

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

Revision history for this message
Removed by request (removed3425744) wrote :

365c483f190fea03971b3eca8d68406f425777b5 works fine but there is something other very interesting: This kernel has an extreme performance boost in booting time on my system. It boots now about 2-3 seconds faster (~10-15%) compared to the working kernels. Normally I have noticed within the last months that the kernel booting time in generic got slower. What is the difference of this compiled kernel compared to the others in the official repository and http://kernel.ubuntu.com/~kernel-ppa/mainline/ ?

penalvch (penalvch)
tags: added: latest-bios-1.40
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Utopic is now updates to the 3.16 kernel. Before we continue the bisect, can you apply the latest Utopic updates and confirm if this bug still exists or not?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Removed by request (removed3425744) wrote :

I haven't noticed the last time any issues. Also on testing this with the kernel 3.16.0.9.10 the booting time is stable and nothing hangs anymore. But the issue that the booting time in generic is slower than some kernels before does still exist. But I have opened another report for this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359754

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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