Xorg crash during login using additional TV at HDMI

Bug #1461656 reported by Anselm
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

login does loop.
Hardware changes, which is responsible:
add TV with HDMI

repeating error messages in dmesg:
[ 7.073512] nouveau [ PGRAPH][0000:01:00.0] using external firmware
[ 7.073527] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2
[ 7.073531] nouveau 0000:01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2
[ 7.073532] nouveau E[ PGRAPH][0000:01:00.0] failed to load fuc409c
[ 16.105932] nouveau [ PGRAPH][0000:01:00.0] using external firmware
[ 16.105941] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2
[ 16.105945] nouveau 0000:01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2
[ 16.105946] nouveau E[ PGRAPH][0000:01:00.0] failed to load fuc409c
[ 17.026449] sound hdaudioC1D0: HDMI: invalid ELD data byte 76
[ 17.103147] nouveau [ PGRAPH][0000:01:00.0] using external firmware
[ 17.103156] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2
[ 17.103160] nouveau 0000:01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2
[ 17.103162] nouveau E[ PGRAPH][0000:01:00.0] failed to load fuc409c
[ 18.003879] sound hdaudioC1D0: HDMI: invalid ELD data byte 74
[ 18.084568] nouveau [ PGRAPH][0000:01:00.0] using external firmware
[ 18.084583] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2
[ 18.084590] nouveau 0000:01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2
[ 18.084591] nouveau E[ PGRAPH][0000:01:00.0] failed to load fuc409c
[ 19.005339] sound hdaudioC1D0: HDMI: invalid ELD data byte 76
[ 19.098829] nouveau [ PGRAPH][0000:01:00.0] using external firmware
[ 19.098838] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv117_fuc409c failed with error -2

hardware (using lshw:)

 *-display
                description: VGA compatible controller
                product: GM107 [GeForce GTX 750 Ti]
                vendor: NVIDIA Corporation
                physical id: 0
                bus info: pci@0000:01:00.0
                version: a2
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
                configuration: driver=nouveau latency=0
                resources: irq:30 memory:f6000000-f6ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:f7000000-f707ffff
           *-multimedia
                description: Audio device
                product: NVIDIA Corporation
                vendor: NVIDIA Corporation
                physical id: 0.1
                bus info: pci@0000:01:00.1
                version: a1
                width: 32 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list
                configuration: driver=snd_hda_intel latency=0
                resources: irq:17 memory:f7080000-f7083fff

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
.tmp.unity.support.test.1:

ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jun 3 20:33:35 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:362d]
InstallationDate: Installed on 2015-05-09 (24 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: MSI MS-7821
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=59d2c31b-6829-45f8-b5c6-be29de9db5c0 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-G45 GAMING (MS-7821)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd07/21/2014:svnMSI:pnMS-7821:pvr1.0:rvnMSI:rnZ87-G45GAMING(MS-7821):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7821
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Wed Jun 3 20:00:03 2015
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input USB OPTICAL MOUSE MOUSE, id 8
 input USB USB Keykoard KEYBOARD, id 9
 input USB USB Keykoard KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: nouveau

Revision history for this message
Anselm (anselm2004) wrote :
penalvch (penalvch)
tags: added: latest-bios-1.9
Revision history for this message
penalvch (penalvch) wrote :

Anselm, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.

If that fails, one may open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xorg (Ubuntu):
status: New → Invalid
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.