Ubuntu
linux package

System freezes randomly

Bug #1087624 reported by shalinmangar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

System freezes randomly on heavy loads(Google Chrome and Oracle JDK7 running). Possible suspected issues: Nvidia Quadro 600M, SSD(SATA 3) drive access or the new generation of CPU.

The following bug seems to be related/same:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1029504

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-19-generic 3.5.0-19.30
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: shalin 2047 F.... pulseaudio
 /dev/snd/controlC0: shalin 2047 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Fri Dec 7 15:17:45 2012
InstallationDate: Installed on 2012-12-01 (5 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
 usb0 no wireless extensions.

 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-19-generic root=UUID=143c85a5-df44-466b-ab7c-e0d4962a8dee ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-19-generic N/A
 linux-backports-modules-3.5.0-19-generic N/A
 linux-firmware 1.95
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H77M-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd05/11/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

Revision history for this message
shalinmangar (shalinmangar) 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
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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.7-rc8-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
shalinmangar (shalinmangar)
tags: added: kernel-bug-exists-upstream
Revision history for this message
shalinmangar (shalinmangar) wrote :

I installed upstream linux-image and linux-image-extras as specified.

linux-image-3.7.0-030700rc8-generic_3.7.0-030700rc8.201212031649_amd64.deb
linux-image-extra-3.7.0-030700rc8-generic_3.7.0-030700rc8.201212031649_amd64.deb

The bug still exists with the upstream kernel and I've added the appropriate tag.

Running Chrome with five tabs open, Oracle JDK7 (4 instances) and a 720p movie on vlc-player made the system freeze. I was able to reproduce the freeze twice with the same applications.

Interestingly, the chrome "seccomp" violations seen with kernel 3.5 (pasted below) do not happen with 3.7 but the system still freezes. The following is the dmesg output from 3.5:
6332] type=1701 audit(1354947917.650:34): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2055 comm="chrome" reason="seccomp" sig=0 syscall=39 compat=0 ip=0x7f5026c24ed9 code=0x50000
[ 14.138097] type=1701 audit(1354947917.810:35): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2127 comm="chrome" reason="seccomp" sig=0 syscall=4 compat=0 ip=0x7f5026c1b205 code=0x50000
[ 14.138103] type=1701 audit(1354947917.810:36): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2127 comm="chrome" reason="seccomp" sig=0 syscall=4 compat=0 ip=0x7f5026c1b205 code=0x50000
[ 14.138107] type=1701 audit(1354947917.810:37): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2127 comm="chrome" reason="seccomp" sig=0 syscall=4 compat=0 ip=0x7f5026c1b205 code=0x50000
[ 14.138111] type=1701 audit(1354947917.810:38): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2127 comm="chrome" reason="seccomp" sig=0 syscall=4 compat=0 ip=0x7f5026c1b205 code=0x50000
[ 14.138115] type=1701 audit(1354947917.810:39): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2127 comm="chrome" reason="seccomp" sig=0 syscall=4 compat=0 ip=0x7f5026c1b205 code=0x50000
[ 14.272347] type=1701 audit(1354947917.946:40): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2156 comm="chrome" reason="seccomp" sig=0 syscall=4 compat=0 ip=0x7f5026c1b205 code=0x50000
[ 14.272354] type=1701 audit(1354947917.946:41): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2156 comm="chrome" reason="seccomp" sig=0 syscall=4 compat=0 ip=0x7f5026c1b205 code=0x50000
[ 14.272358] type=1701 audit(1354947917.946:42): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2156 comm="chrome" reason="seccomp" sig=0 syscall=4 compat=0 ip=0x7f5026c1b205 code=0x50000
[ 14.272362] type=1701 audit(1354947917.946:43): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=2156 comm="chrome" reason="seccomp" sig=0 syscall=4 compat=0 ip=0x7f5026c1b205 code=0x50000

I checked kernel logs and there are no messages which could indicate any problems.

Please let me know if there's any other detail I can provide to help you with diagnosis.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
shalinmangar (shalinmangar) wrote :

I'm able to reproduce this bug every time. Chrome has no part in this. I can make the system freeze on a gnome desktop by just running all the tests for Apache Lucene/Solr every time.

I installed a different distribution (Sabayon Linux) and the same problem exists.

If there's any information that I can provide to help you debug this problem, please let me know.

Revision history for this message
penalvch (penalvch) wrote :

shalinmangar, as per http://www.gigabyte.us/products/product-page.aspx?pid=4143#bios an update is available for your BIOS (F9). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

tags: added: bios-outdated-f9 needs-upstream-testing regression-potential
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
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.
Subscribing...

Other bug subscribers

Remote bug watches

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