[HP Workstation Z820]: Workstation becomes unresponsive during cpu stress test.

[Jeff Marcom]

Problem:

Machine becomes completely unresponsive while running cpu stress. Mouse, keyboard movement is impossible and I can not switch to another tty. System has to be dc cycled.

Command issued:
stress --cpu 32 --vm 63 --timeout 7200

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"

Kernel: Linux 201206-11248 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-generic 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 2493 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 2493 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xde640000 irq 120'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,103c158b,00100202'
   Controls : 32
   Simple ctrls : 17
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xde080000 irq 44'
   Mixer name : 'Nvidia GPU 11 HDMI/DP'
   Components : 'HDA:10de0011,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
CurrentDmesg:
 [ 166.705148] type=1400 audit(1343138258.598:30): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5" name="/usr/share/gvfs/remote-volume-monitors/" pid=2538 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
 [ 299.886625] [Hardware Error]: Machine check events logged
Date: Tue Jul 24 11:17:12 2012
HibernationDevice: RESUME=UUID=45472ce7-046f-4e95-911a-6c07644c5c8c
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
MachineType: Hewlett-Packard HP Z820 Workstation
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=aab4c67f-7780-4e3f-83fa-b58125e3afd5 ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic N/A
 linux-backports-modules-3.2.0-23-generic N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J63 v01.07
dmi.board.asset.tag: Hewlett-Packard Co
dmi.board.name: 158B
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: Hewlett-Packard Co
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrJ63v01.07:bd05/09/2012:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z820 Workstation
dmi.sys.vendor: Hewlett-Packard

[penalvch (penalvch)]

Jeff Marcom, thank you for reporting this and helping make Ubuntu better. If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

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', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Jeff Marcom (jeffmarcom)]

Re-running cpu stress with 3.5 rc7.

[Jeff Marcom (jeffmarcom)]

This seems to have been fixed with 3.5 rc7:
stress: info: [3165] dispatching hogs: 32 cpu, 0 io, 63 vm, 0 hdd
stress: info: [3165] successful run completed in 7200s

[penalvch (penalvch)]

Marking Triaged as mainline tested and kernel-fixed-upstream-v3.5-rc7-quantal.

[Leann Ogasawara (leannogasawara)]

Based on comment #4 I'll go ahead and note this as fixed for Quantal. If you test with the latest Quantal kernel and find this is not resolved, feel free to re-open the Quantal task. I've gone ahead and left the Precise task open though to reflect that a fix would need to be SRU'd. Thanks.

[Joseph Salisbury (jsalisbury)]

Hi Jeff,

I'd like to perform a reverse bisect to identify the commit that fixes this bug. We can then see if that fix can be submitted to Precise for a SRU.

Can you test the following kernels and report back? We are looking for the first kernel version that doesn't have this bug:

v3.3 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/
v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/
v3.5-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc4-quantal/

Thanks in advance!

[Jeff Marcom (jeffmarcom)]

okay, re-running with v3.3 final now.

[Jeff Marcom (jeffmarcom)]

v3.3 failed. Running with v3.4 now.

[Jeff Marcom (jeffmarcom)]

3.4 failed, running with 3.5rc4 at the moment.

[Joseph Salisbury (jsalisbury)]

Any results from 3.5-rc4?

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release