[kernel-unable-to-test-upstream] Crashes randomly in Chrome and Firefox

[Patrick Bertsch]

Crashes and sends me back to the login screen

gnome-session[15580]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012

Updated arround 21:01 hours my Laptop and at arround 21:35:49 it started chrashing. SYSLOG is attached !

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-58-generic 3.2.0-58.88
ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
Uname: Linux 3.2.0-58-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: patrick 4980 F.... pulseaudio
 /dev/snd/controlC0: patrick 4980 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf7310000 irq 48'
   Mixer name : 'VIA VT1802'
   Components : 'HDA:11068446,10431487,00100000'
   Controls : 32
   Simple ctrls : 19
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xf7080000 irq 17'
   Mixer name : 'Nvidia GPU 16 HDMI/DP'
   Components : 'HDA:10de0016,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
Date: Tue Jan 28 23:13:47 2014
HibernationDevice: RESUME=UUID=347af211-349c-47f7-97a0-7f5793aef990
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: ASUSTeK COMPUTER INC. G75VW
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-58-generic root=UUID=c4068681-1c18-4d6f-ab5e-74ddc22e8d87 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-58-generic N/A
 linux-backports-modules-3.2.0-58-generic N/A
 linux-firmware 1.79.9
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VW.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.210:bd06/15/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Patrick Bertsch (patrickbertsch-pb)]

Attached the Syslog from today /var/log/syslog

because it all started arround 21:35:49

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue occur in a previous version of Ubuntu, or is this a new issue?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 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.13-trusty/

[Patrick Bertsch (patrickbertsch-pb)]

Will try installing the latest Upstream Kernel . I will let you know how it went !

Thanks for your rapid response !

[Patrick Bertsch (patrickbertsch-pb)]

I did not have the chance to install the new upstream Kernel
BUT i remembered that there was also an Kernel-Update to 3.2.058 so
I went back to 3.2.057 I now everything is working fine !!!!!!

I rather use the 3.2.057 because its my developing machine and I can't affort
losing it for one day.

Thanks.