Bug 1158061 - Regression between kernel 3.16.3 and kernel 3.16.4 (system hangs on GDM login screen)
Summary: Regression between kernel 3.16.3 and kernel 3.16.4 (system hangs on GDM login...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 20
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-28 13:10 UTC by Rémi G.
Modified: 2015-06-29 23:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 23:04:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl -b -1 output (24.62 KB, text/plain)
2014-10-28 13:10 UTC, Rémi G.
no flags Details
ouput of "git bisect log" (1.81 KB, text/plain)
2014-10-28 21:45 UTC, Rémi G.
no flags Details
kernel 3.18.0-rc4 logs (310.95 KB, text/x-vhdl)
2014-11-22 21:06 UTC, Rémi G.
no flags Details

Description Rémi G. 2014-10-28 13:10:19 UTC
Created attachment 951403 [details]
journalctl -b -1 output

On Fedora 20, with the Linux kernels 3.16.4 and further, my system hangs on the GDM login screen in a few seconds (usually I click on my name and everything collaps...).

Everything was working fine from kernel 3.14 to kernel 3.16.3.

My laptop is a Dell Vostro 3300 which has Intel/nVidia hybrid graphics (but not optimus I think):

    00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
    01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2)

Below are some of the errors I could gather using the command `journalctl -b -1` (more details in the attachment journalctl.log):

    ...
    BUG: unable to handle kernel NULL pointer dereference
    kernel: nouveau E[     PFB][0000:01:00.0] trapped write at 0x002001a034 on channel 0x0001fb24
    ...
    IP: [<ffffffffa0280985>] nv84_fence_read+0x25/0x30 [nouveau]
    ...
    RIP  [<ffffffffa0280985>] nv84_fence_read+0x25/0x30 [nouveau]

I'll try to bisect the kernel if I remember how to do it and I'll test more upstream kernels from Koji.

Thanks for your help on this matter,

Rémi.

Comment 1 Rémi G. 2014-10-28 21:45:54 UTC
Created attachment 951564 [details]
ouput of "git bisect log"

I did a bisection and I might have found the first bad commit:

    a4c5f39c22082dd53a95e2c63aa3d4ed9805fad4 is the first bad commit
    commit a4c5f39c22082dd53a95e2c63aa3d4ed9805fad4
    Author: Bjorn Helgaas <bhelgaas>
    Date:   Wed Sep 10 13:45:01 2014 -0600
    
    PCI: Add pci_ignore_hotplug() to ignore hotplug events for a device

Hope that helps,

Rémi.

Comment 2 Rémi G. 2014-10-29 19:19:28 UTC
Same issue on kernel 3.17.1 (and hence on Fedora 21).

Comment 3 Rémi G. 2014-11-22 21:06:36 UTC
Created attachment 960288 [details]
kernel 3.18.0-rc4 logs

Problem still exists on kernel 3.18.0-rc4 unfortunately.

Comment 4 Rémi G. 2014-12-20 17:34:23 UTC
A workaround to boot on kernel 3.16.4 and further is to add the boot parameter "nouveau.runpm=0".

It is then possible to install Fedora 21 but the laptop is heating again and the battery life is shrinking...

There are two options to disable the discrete nVidia card:
1) Install Bumblebee/bbswitch (which hasn't worked for me)
2) Install the latest working kernel which can luckily be found on Koji: https://koji.fedoraproject.org/koji/buildinfo?buildID=581187

Comment 5 Fedora End Of Life 2015-05-29 13:10:41 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2015-06-29 23:04:16 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.