Bug 1491408

Summary: kernel BUG at drivers/gpu/drm/ttm/ttm_bo_util.c:589!
Product: [Fedora] Fedora Reporter: Dominic P Geevarghese <dominicpg>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 27CC: airlied, ajax, bskeggs, elad, eparis, esandeen, gnome-sig, hdegoede, ichavero, itamar, jarodwilson, jforbes, jglisse, jonathan, josef, jwboyer, kernel-maint, labbott, linville, mchehab, mjg59, nhorman, quintela, rstrode, steved
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-18 17:19:57 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:
Embargoed:
Attachments:
Description Flags
journalctl none

Description Dominic P Geevarghese 2017-09-13 17:20:33 UTC
Created attachment 1325545 [details]
journalctl

Description of problem:

Boot progress icon on KVM vm imaged by latest F27 Workstation build; 20170912.n.0, stopped half way during fresh boot and not witnessed any response to keyboard. System booted fine on second attempt and noticed qxl driver trace with $subject

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

F27 branched Workstation Live - 20170912.n.0

How reproducible:

Not sure 

Steps to Reproduce:
1. Installed KVM VM using latest WS Live build.
2. First boot attempt stopped halfway and no response to keyboard

Actual results:

Boot interrupted, neither error message nor response to keyboard witnessed.

Expected results:

smooth boot.

Additional Info:

log file attached


Thanks, 
Dominic Geevarghese
4096R/43EACB09

Comment 1 Dominic P Geevarghese 2017-09-15 08:55:28 UTC
note: issue appears whenever 'rhgb quiet' is there in cmdline.

Comment 2 Dominic P Geevarghese 2017-09-18 17:19:57 UTC

*** This bug has been marked as a duplicate of bug 1462381 ***