Bug 1046483

Summary: nouveau driver fails on Toshiba Qosmio x770
Product: [Fedora] Fedora Reporter: Peter H. Jones <jones.peter.busi>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: airlied, ajax, bskeggs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:49:45 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
dmesg output for kernel-3.12.7-200.fc19.x86_64.debug #1 SMP with nouveau.modeset=2 none

Description Peter H. Jones 2013-12-25 17:52:53 UTC
Description of problem:
http://kojipkgs.fedoraproject.org//work/tasks/2884/6332884/Fedora-Live-Jam-KDE-x86_64-rawhide-20131225.iso fails to compete startup

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-1.0.9-6.fc21.x86_64 in
Fedora-Live-Jam-KDE-x86_64-rawhide-20131225.iso

How reproducible:
Propbably every time, tried only once

Steps to Reproduce:
1. Burn and boot above DVD
2. Use CTRL-ALT-F2 to see message

Actual results:
Boot stops with hard disk icon showing

Expected results:
Complete KDE boot

Additional info:
When system stalls, CTRL-ALT-F2 shows the following message:
[200.14xx] nouveau [PDISP][0000:01.00.0] child 0 mthd 0x0000 data 0x00000000 0x000tt000

When I added nomodeset to the boot line, I again got to the HD icon, and CTRL-ALT-F[2-] showed a blank screen. In no case did I get a getty prompt that would allow me to get more information. I don't know if the above message is an error or not.

Comment 1 Ben Skeggs 2014-01-07 00:03:26 UTC
Yeah, it's an error.  The display engine is angry about something or other.

You might be able to get a better log which will at least give me some basic info on the GPU you have by booting with "nouveau.modeset=2" in your kernel options.

It's worrying that "nomodeset" doesn't work though, nouveau isn't involved at all in this situation, so there might be deeper problems.

Comment 2 Peter H. Jones 2014-01-18 16:09:49 UTC
Created attachment 852051 [details]
dmesg output for kernel-3.12.7-200.fc19.x86_64.debug #1 SMP with nouveau.modeset=2

I have tried what you suggested with working FC19 system. I booted in single, and then typed "exit". The part after the exit command starts with
"[  333.732089] systemd-readahead[490]: Bumped block_nr parameter of 8:0 to 20480. This is a temporary hack and should be removed one day."

When I tried with Fedora-Live-Jam-KDE-x86_64-rawhide-20140117.iso, I got a traceback and the system hung there. I'd need to send a screen photo to retrieve that. I'd rather try a new copy of the spin before doing that.

Comment 3 Peter H. Jones 2014-01-18 16:19:06 UTC
In Comment 2, I meant Fedora-Live-Jam-KDE-x86_64-rawhide-20140116.iso .

Comment 4 Peter H. Jones 2014-01-18 20:10:01 UTC
Perhaps bug 1055105 is related.

Comment 5 Jaroslav Reznik 2015-03-03 15:21:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 6 Fedora End Of Life 2016-07-19 10:49:45 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.