system unresponsive during disk access

Bug #1415377 reported by alepac
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The system become unresponsive during disk access. I'm using Ubuntu 14.04 on a ThinkPad lenovo E540.

The steps I use to reproduce this bug is:
 - install `stress` package
 - stress the disk (# stress -d 2 --timeout 20s)
 - during the stress test the system hangs while accessing disk from another process (even ls hangs waiting the stress timeout)

The problem persist with the upstream kernel 3.19.0-031900rc6-generic

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-44-generic 3.13.0-44.73
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alepac 2907 F.... pulseaudio
 /dev/snd/controlC1: alepac 2907 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Jan 28 09:52:50 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=18d574ae-5963-4128-ac7d-93e85043999e
InstallationDate: Installed on 2014-08-25 (155 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: LENOVO 20C6003QIX
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=abc61567-9159-409e-becf-f1db0b9bfd8d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-44-generic N/A
 linux-backports-modules-3.13.0-44-generic N/A
 linux-firmware 1.127.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 Jan 28 08:44:21 alepac-lenovo kernel: [ 847.480724] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
 Jan 28 09:53:06 alepac-lenovo kernel: [ 4975.967152] nouveau E[ PIBUS][0000:01:00.0] GPC0: 0x4188ac 0x00000001 (0x1e70822e)
dmi.bios.date: 07/31/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ET92WW (2.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C6003QIX
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrJ9ET92WW(2.12):bd07/31/2014:svnLENOVO:pn20C6003QIX:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6003QIX:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C6003QIX
dmi.product.version: ThinkPad Edge E540
dmi.sys.vendor: LENOVO

Revision history for this message
alepac (alessandro-pacifici) 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
alepac (alessandro-pacifici) wrote :

The bug seems related to AHCI.

I found a WORKAROUND disabling AHCI from BIOS.

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

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 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] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc6-vivid/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key
tags: added: kernel-bug-exists-upstream
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.