Possibly related to frequent freeze-ups during high GPU usage; possibly independent. The error reporter appeared after a forced reboot.

[James]

I have had frequent problems with graphics drivers in general and fglrx in particular. Lately, the system freezes (beyond even the mystic powers of the SysRq) after random lengths of time spent playing any graphics-heavy game (straight video seems to be alright, and sites like google maps). I can't say for sure that this report is related; it appeared after I was forced to do a hard reboot. But it's the first hard evidence the machine has barfed up this week, as I've inexpertly trawled the logs, so this report is a bit of a hail mary.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-core 2:15.200-0ubuntu4.2
Uname: Linux 4.2.0-040200-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
DKMSKernelVersion: 4.2.0-040200-generic
Date: Sat Jan 23 15:08:24 2016
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: fglrx-core, 15.200, 4.2.0-040200-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2715]
InstallationDate: Installed on 2015-05-05 (267 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
PackageVersion: 2:15.200-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-040200-generic root=UUID=6fa2168f-703c-4e45-a79f-1d261233f002 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1.1
 apt 1.0.9.7ubuntu4.2
SourcePackage: fglrx-installer
Title: fglrx-core 2:15.200-0ubuntu1: fglrx-core kernel module failed to build
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2101
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CROSSHAIR V FORMULA-Z
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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.:bvr2101:bd04/17/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVFORMULA-Z:rvrRev1.xx: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.
version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~vivid
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~vivid
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~vivid
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20150926.1ff13a92-0ubuntu0sarvatt~vivid
xserver.bootTime: Wed Jan 27 13:47:54 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3.1
xserver.video_driver: fglrx

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1512527, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.