Bug 1102066 - When using kernel 3.14.4 hangs at boot with NVIDIA Corporation G72M [Quadro NVS 110M/GeForce Go 7300]
Summary: When using kernel 3.14.4 hangs at boot with NVIDIA Corporation G72M [Quadro N...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-28 12:39 UTC by antonio montagnani
Modified: 2015-12-02 16:09 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 03:12:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
copy of messages... (1.68 MB, text/plain)
2014-05-28 13:44 UTC, antonio montagnani
no flags Details
xorg from a 14.4 boot (33.55 KB, text/plain)
2014-05-29 16:43 UTC, antonio montagnani
no flags Details
lspci (7.45 KB, text/plain)
2014-12-06 19:58 UTC, rviadil
no flags Details
dmesg with kernel 3.17.4-301 (66.32 KB, text/plain)
2014-12-06 20:01 UTC, rviadil
no flags Details
journalctl with kernel 3.17.4-301 (1.07 MB, text/x-vhdl)
2014-12-06 20:13 UTC, rviadil
no flags Details

Description antonio montagnani 2014-05-28 12:39:03 UTC
Description of problem:
when upgrading kernel to 3.4.14-100 hangs at boot with a black screen

Version-Release number of selected component (if applicable):
3,4.14-100

How reproducible:
always

Steps to Reproduce:
1.install new kernel
2.boot
3.

Actual results:
blank screen

Expected results:
normal boot

Additional info:
it doesn't start also with nomodeset

Comment 1 antonio montagnani 2014-05-28 12:56:08 UTC
enetring in a different session in text mode, and issuing startx nothing happens and I get a blank screen

Comment 2 Josh Boyer 2014-05-28 12:59:44 UTC
Please attach the output of dmesg after boot.

Comment 3 antonio montagnani 2014-05-28 13:44:49 UTC
Created attachment 899984 [details]
copy of messages...

hope it can help

Comment 4 Josh Boyer 2014-05-28 13:51:12 UTC
Can you attach your /var/log/Xorg.0.log from a boot with 3.14.4?

Comment 5 antonio montagnani 2014-05-29 16:43:09 UTC
Created attachment 900438 [details]
xorg from a 14.4 boot

boot from a 14.4 kernel

Comment 6 rviadil 2014-12-06 19:56:56 UTC
Hi,

If I'm not wrong, this issue is still here with Fedora 20 (at least from liveUSB) and 21.

With Fedora 21 Gnome, GDM does not even appear (Fedora logo stays on screen).
With Fedora 20 live with KDE, the desktop appears but is not usable because of heavy image corruption.
Fedora 21 Gnome is usable with nomodeset kernel parameter (1024x768 maximum, basic colors).
With a live Xubuntu 14.04, it works well.

I also have a line like this in my dmesg : "nouveau E[     DRM] GPU lockup - switching to software fbcon"

Do not hesitate to ask if I can help.

Roberto

Comment 7 rviadil 2014-12-06 19:58:55 UTC
Created attachment 965450 [details]
lspci

Comment 8 rviadil 2014-12-06 20:01:03 UTC
Created attachment 965451 [details]
dmesg with kernel 3.17.4-301

Comment 9 rviadil 2014-12-06 20:13:36 UTC
Created attachment 965463 [details]
journalctl with kernel 3.17.4-301

Comment 10 Eugene Kanter 2014-12-08 03:03:54 UTC
I am observing a regression in Fedora 20 new 3.17 series kernel drm/nouveau.
Last working drm/nouveau is in kernel-3.15.6-200.
01:00.0 VGA compatible controller: NVIDIA Corporation G84M [GeForce 8600M GT] (rev a1)
graphical boot is working but X is not.

Comment 11 Eugene Kanter 2014-12-14 16:37:33 UTC
latest kernel-3.17.6-200.fc20.x86_64 is still not working, staying with kernel-3.15.6-200.fc20.x86_64. I missed 3.16.x series, though.

Comment 12 Eugene Kanter 2014-12-14 16:54:47 UTC
does this have anything to do with nvidia problem I am observing in 3.17.x series?
http://www.spinics.net/lists/stable-commits/msg39131.html

Comment 13 rviadil 2014-12-21 16:36:12 UTC
I don't know if this can be usefull, but I tried the "almost stable" Debian Jessie on this same computer and the result is the same (kernel 3.16). I tried many previous kernels and the last working is the 3.12.
You can see the full bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773368

Comment 14 Eugene Kanter 2014-12-23 15:28:17 UTC
kernel-3.15.6-200.fc20.x86_64 stopped working as well.
updated to Fedora 21 - the same "no screens found" in Xorg.0.log

Comment 15 Richard Shaw 2015-01-16 03:34:04 UTC
I'm having the same problem after installing Fedora 21 on an old Dell Latitude D620 with Nvidia Quadro NVS 110M.

I'm getting the same GPU lockup messages.

Comment 16 antonio montagnani 2015-03-06 22:20:20 UTC
I am experiencing this issue also an an old DELL with same video card with Fedora 21 (kernel 3.18.7-200.fc21.i686)

Comment 17 Slobodan Sredojevic 2015-04-15 11:45:46 UTC
I see the same problem using dell latitude d820 trying to use both fedora 21 & fedora 22 alpha, even with updates. Seems this is upstream bug:
https://bugs.freedesktop.org/show_bug.cgi?id=88893

In my case gpu is slightly different:
NVIDIA Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)

Richard in fdo bugzilla said cinnamon works but gnome-shell and unity are affected.

Any news on this guys?

Comment 18 Fabash 2015-06-01 19:31:42 UTC
I had the same issue, ie: kernel hangs during boot since 3.18.x branch, using Nvidia card and nouveau driver.
My last working Kernel is 3.17.8-200.fc20.x86_64 (FC20).

I've upgraded to last Kernel 4.0.4, hoping issue would be fixed but not.
So, I have investigated within Linux source code.

- Download Linux source from git and use branch 'linux-4.0.y'
- Use config file '/boot/config-4.0.4-201.fc21.x86_64' as default config
- Build, install and boot this kernel.

After some experimentations and full debug traces, I've came to disable the DRM (Direct Rendering Manager) configuration in the Graphical drivers section, ie:

# CONFIG_DRM is not set

Now, I'm able to boot and use use my laptop but I can't confirm/infirm what are the disavantages (no optimizations ?) as I don't use much 'graphical' ressources.
I hope that this can help.

Comment 19 Richard Shaw 2015-10-30 16:12:35 UTC
The problem is (at least for me) related to MSI interrupts, kernels > 4.0 have this enabled by default for this GPU but you can get earlier kernels to work by setting

nouveau.config=NvMSI=0

for your kernel

See: https://bugs.freedesktop.org/show_bug.cgi?id=88893#c17

Comment 20 Fabash 2015-11-01 22:21:47 UTC
Thanks a lot Richard for this help.
It works also fine for me now, altough that I got plenty of 'nouveau SCHED_ERROR or DRM erros in the Kernel log.

Comment 21 Fedora End Of Life 2015-11-04 09:59:25 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 22 Fedora End Of Life 2015-12-02 03:12:28 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.


Note You need to log in before you can comment on or make changes to this bug.