Bug 1403638

Summary: frist boot black screen
Product: [Fedora] Fedora Reporter: Ron dencer <rd2164>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 25CC: ajax, cz172638, dennis, gansalmon, ichavero, itamar, jdisnard, jonathan, kernel-maint, kevin, labbott, madhu.chinakonda, mboddu, mchehab, rd2164, xgl-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:43:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
log none

Description Ron dencer 2016-12-12 02:51:31 UTC
Descr Logs begin at Thu 2016-12-08 11:15:08 PST, end at Sun 2016-12-11 18:12:40 PST. --
Dec 11 13:39:44 localhost.localdomain spice-vdagent[1942]: Cannot access vdagent virtio channel /dev/virtio-ports/c
Dec 11 13:39:44 localhost.localdomain cinnamon-session[1735]: GLib-GObject-CRITICAL: t+0.09832s: Custom constructor
Dec 11 13:39:44 localhost.localdomain cinnamon-session[1735]: GLib-GObject-CRITICAL: t+0.09828s: object CsmAutostar
Dec 11 13:39:26 localhost.localdomain spice-vdagent[1600]: Cannot access vdagent virtio channel /dev/virtio-ports/c
Dec 11 13:39:15 localhost.localdomain cupsd[1157]: [cups-deviced] PID 1268 (gutenprint52+usb) stopped with status 1
Dec 11 13:39:15 localhost.localdomain python3[1260]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 13:39:15 localhost.localdomain hp[1261]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dec 11 13:39:09 localhost.localdomain avahi-daemon[1061]: chroot.c: open() failed: No such file or directory
Dec 11 13:39:03 localhost.localdomain kernel: kvm: disabled by bios
Dec 11 13:38:57 localhost rpcbind[358]: cannot save any registration
Dec 11 13:38:57 localhost rpcbind[358]: cannot open file = /tmp/portmap.xdr for writing
Dec 11 13:38:57 localhost rpcbind[358]: cannot save any registration
Dec 11 13:38:57 localhost rpcbind[358]: cannot open file = /tmp/rpcbind.xdr for writing
Dec 11 13:38:56 localhost iscsid[340]: can't open iscsid.safe_logout configuration file /etc/iscsi/iscsid.conf
Dec 11 13:38:56 localhost iscsid[340]: can't open InitiatorAlias configuration file /etc/iscsi/initiatorname.iscsi
Dec 11 13:38:56 localhost iscsid[340]: Warning: InitiatorName file /etc/iscsi/initiatorname.iscsi does not exist or
Dec 11 13:38:56 localhost iscsid[340]: can't open InitiatorName configuration file /etc/iscsi/initiatorname.iscsi
Dec 11 13:38:55 localhost iscsid[340]: iSCSI daemon with pid=341 started!
-- Reboot --
Dec 11 13:31:13 localhost.localdomain kernel: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to train DP, ab
Dec 11 13:31:13 localhost.localdomain kernel: [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many f
Dec 11 13:31:13 localhost.localdomain kernel: [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many f
lines 1-23


iption of problem:


Version-Release number of selected component (if applicable):

fedora 25
How reproducible: i  ran jornal


Steps to Reproduce:
1.
2.
3.

Actual results:frist boot


Expected results:  none , black screen


Additional info:down load went well on re boot black screen, went recue it bring up 25 ok

Comment 1 Kevin Fenzi 2016-12-12 04:57:43 UTC
It looks like this is related to the intel video kernel modules... 

moving over to the kernel for further debugging.

Comment 2 Peter Robinson 2016-12-20 07:07:38 UTC
Looks more kernel (intel_dp_start_link_train is display port), but could be mesa as all new intel HW uses glamor not xorg-x11-drv-intel.

Ron: you need to include hardware details (make of laptop/desktop, whether it's attached to an external screen, if so how it's attached etc). 

Looks related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1265606 
https://bugs.archlinux.org/task/46462
https://bugzilla.kernel.org/show_bug.cgi?id=74931

Comment 3 Ron dencer 2016-12-20 20:46:57 UTC
Created attachment 1234065 [details]
log

log, montor asus

Comment 4 Ron dencer 2016-12-20 20:48:47 UTC
if need more give me command to run get what you want thxs

Comment 5 Fedora End Of Life 2017-11-16 18:41:17 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2017-12-12 10:43:50 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.