Nouveau - Jun 2017 - [Bug 101665] New: lspci blocks forever with a GP107M

https://bugs.freedesktop.org/show_bug.cgi?id=101665

            Bug ID: 101665
           Summary: lspci blocks forever with a GP107M
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: kenneth at whitecape.org
        QA Contact: xorg-team at lists.x.org

Hello,

I have a Dell XPS 15 9560 with a GTX 1050 Mobile (GP107M) and an Intel Kabylake
CPU.  Using Kernel 4.11.3 on the Arch installer image, whenever I run
'lspci',
it blocks indefinitely and never prints any output.

After running lspci, dmesg contains:

[   54.819264] nouveau 0000:01:00.0: Refused to change power state, currently
in D3
[   54.879968] nouveau 0000:01:00.0: Refused to change power state, currently
in D3
[   54.879973] nouveau 0000:01:00.0: Refused to change power state, currently
in D3
[   54.879974] nouveau 0000:01:00.0: DRM: resuming object tree...

Eventually the scheduler gets cranky about the hung process and starts spewing
[  245.385522] INFO: task lspci:576 blocked for more than 120 seconds.
and a backtrace every 2 minutes.

Blacklisting nouveau makes lspci work.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20170630/a8b203d6/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> ---
I believe including a full dmesg (from boot) would be helpful to show what may
be going wrong.

Note that running with nouveau.runpm=0 will prevent the suspend from happening.
However that will, of course, cause the GPU to remain on. [I believe it will
remain on without nouveau loading as well, but with this new PCIe PM stuff,
I'm
not sure anymore.]

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20170630/6010e8d8/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

Peter Wu <peter at lekensteyn.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |peter at lekensteyn.nl

--- Comment #2 from Peter Wu <peter at lekensteyn.nl> ---
With the "new PCIe PM stuff", if nouveau is not loaded and something
else
enabled automatic runtime PM (via powertop, via TLP or manually by writing
"auto" to /sys/bus/pci/devices/.../power/control) for the Nvidia PCI
devices,
then indeed the problematic ACPI methods could be triggered.

Kenneth, can you upload your acpidump?
sudo pacman -S acpidump && sudo acpidump > acpidump.txt

Most likely you are affected by
https://bugzilla.kernel.org/show_bug.cgi?id=156341

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20170704/8a90b665/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #3 from Karol Herbst <karolherbst at gmail.com> ---
this is because lspci reads the config file, which then triggers a full GPU
wake up, which is a silly thing to do in the first place.

What we need is something like this in the kernel:
https://github.com/karolherbst/linux/commit/cb918e4c926990dfcfce92e1ecd905e0896de605
and then make use of those in userspace, so that we don't need to read
config
every time anymore.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20170710/6fd53c8a/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

Rhys Kidd <rhyskidd at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.freedesktop.or
                   |                            |g/show_bug.cgi?id=100228
                 CC|                            |rhyskidd at gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20170720/06dc2396/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

Etienne URBAH <eurbah at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eurbah at free.fr

--- Comment #4 from Etienne URBAH <eurbah at free.fr> ---
I am trying to use 'nouveau' with GP107M [GeForce GTX 1050 Ti Mobile].

With Linux Kernel 4.13.0-16 from Ubuntu 17.10 Artful, 'lspci'
systematically
makes immediately 1 CPU freeze.

Therefore, I am testing Linux kernels from
http://kernel.ubuntu.com/~kernel-ppa/mainline

With Linux kernel 4.14.0-rc7, this issue does NOT show up :

$ lspci -nn -v -s 1:0
01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti
Mobile] [10de:1c8c] (rev a1)
        Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX
1050 Ti Mobile] [1462:11c8]
        Flags: bus master, fast devsel, latency 0, IRQ 134
        Memory at de000000 (32-bit, non-prefetchable) [size=16M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Memory at d0000000 (64-bit, prefetchable) [size=32M]
        I/O ports at e000 [size=128]
        Expansion ROM at df000000 [disabled] [size=512K]
        Capabilities: <access denied>
        Kernel driver in use: nouveau
        Kernel modules: nvidiafb, nouveau

With Linux kernel 4.14.0-rc8, 'lspci' systematically makes immediately
the
whole computer freeze.

With Linux kernel 4.14.0 (released yesterday), 'lspci' systematically
fails to
answer, and makes the whole computer freeze after some time.

So, there is probably a regression.

I have also reported this issue at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729736

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20171113/931cd415/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #5 from Etienne URBAH <eurbah at free.fr> ---
With following Linux kernels, 'lspci' systematically fails to answer,
and makes
the whole machine immediately freeze :
- 4.13.0-17 from Ubuntu 17.10 (Artful)
- 4.14.1 from http://kernel.ubuntu.com/~kernel-ppa/mainline

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20171121/36efd2a9/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #6 from Etienne URBAH <eurbah at free.fr> ---
With Linux kernel 4.15.0-041500rc1 from
http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically
fails to
answer, and makes the whole machine freeze after some time.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20171127/ea0aa1ea/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #7 from Etienne URBAH <eurbah at free.fr> ---
With Linux kernel 4.15.0-041500rc2 from
http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically
fails to
answer, and makes the whole machine freeze after some time.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20171204/152e9950/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #8 from Etienne URBAH <eurbah at free.fr> ---
With Linux kernel 4.15.0-041500rc3 from
http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically
fails to
answer, and makes the whole machine freeze after some time.

Besides, inside 'kern.log', I have detected following messages :
nouveau 0000:01:00.0: DRM: BIT table 'A' not found
nouveau 0000:01:00.0: DRM: BIT table 'L' not found
nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20171211/1e4a707f/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #9 from Pierre Moreau <pierre.morrow at free.fr> ---
@Étienne Could you please provide the information that was asked in comment #1
and comment #2 of this bug report? Adding `nouveau.runpm=0` to the kernel
command line should avoid the freeze but will prevent the NVIDIA card from
being suspended.
Looking at the bug report mentioned in comment #2, could you try booting with
`acpi_osi=! acpi_osi="Windows 2009"` and/or `acpi_rev_override=5` on
the kernel
command line (without `nouveau.runpm=0`)?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20171212/6eb44a61/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #10 from Etienne URBAH <eurbah at free.fr> ---
Created attachment 136105
  --> https://bugs.freedesktop.org/attachment.cgi?id=136105&action=edit
lspci for GP107M [GeForce GTX 1050 Ti Mobile]

Lot of thanks to Pierre Moreau for his suggestions of options in the kernel
command line :

-  Adding just 'nouveau.runpm=0' prevents the whole machine to freeze,
but
'nouveau' FAILS to manage an external display with resolution 3840 x
2160 at
60Hz through DisplayPort.

-  Adding just 'acpi_rev_override=5' does NOT prevent the whole machine
to
freeze.

-  Adding just 'acpi_osi=! acpi_osi="Windows 2009"' permits
'lspci' to succeed,
and 'nouveau' to successfully manage an external display with resolution
3840 x
2160 at 60Hz through DisplayPort.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20171212/5829c40f/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

Rhys Kidd <rhyskidd at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.freedesktop.or
                   |                            |g/show_bug.cgi?id=104621

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20180114/8a26221a/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #11 from Etienne URBAH <eurbah at free.fr> ---
With Linux kernel 4.16.0-041600rc5 from
http://kernel.ubuntu.com/~kernel-ppa/mainline, 'lspci' systematically
fails to
answer, and makes the whole machine freeze after some time.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20180317/0a7a79bc/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #12 from Etienne URBAH <eurbah at free.fr> ---
With Linux kernel 4.17.0-041700rc1 from
http://kernel.ubuntu.com/~kernel-ppa/mainline, graphical login fails, and the
machine is frozen.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20180418/22cff27e/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #13 from Etienne URBAH <eurbah at free.fr> ---
With Linux kernel 4.17.0-041700rc1 from
http://kernel.ubuntu.com/~kernel-ppa/mainline, I confirm that systematically :

-  Inside a Linux console, 'lspci' fails to answer, and makes the whole
machine
immediately freeze.

-  Graphical login fails, and makes the whole machine immediately freeze.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20180418/065d2401/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #14 from Loris Z. <the.lz.himself at gmail.com> ---
I'm experiencing the same issue on an XPS 9560 with Ubuntu 18.04 (same
symptoms, same dmesg output).
Any new information required?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20180514/9e7e3e42/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #15 from Etienne URBAH <eurbah at free.fr> ---
With Linux kernel 4.18.0-041800rc1 from
http://kernel.ubuntu.com/~kernel-ppa/mainline :

I tried to open a Linux console with Ctrl Alt F2, but did NOT succeed.

Systematically, graphical login fails, and makes the whole machine immediately
freeze.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20180619/52577997/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

Andrey Melentyev <andrey+freedesktop at psyduck.se> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrey+freedesktop at psyduck.
                   |                            |se

--- Comment #16 from Andrey Melentyev <andrey+freedesktop at psyduck.se>
---
Created attachment 143031
  --> https://bugs.freedesktop.org/attachment.cgi?id=143031&action=edit
dmesg from thinkpad x1 extreme / GTX 1050 Ti on kernel 4.20 with hybrid
graphics

I may be blind but I haven't seen anyone attaching full dmesg output, sorry
if
I missed it.

The laptop in question is Thinkpad X1 Extreme with NVIDIA Corporation GP107M
[GeForce GTX 1050 Ti Mobile] (rev a1). It has a BIOS setting to switch between
"Hybrid" and "Discrete only" graphics. 

This dmesg output is from a boot with "Hybrid" graphics, where running
'lspci'
hangs and causes the system fans to spin. X server hangs on start too (using
modesetting DDX)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190109/c43d9d87/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

--- Comment #17 from Andrey Melentyev <andrey+freedesktop at psyduck.se>
---
Created attachment 143032
  --> https://bugs.freedesktop.org/attachment.cgi?id=143032&action=edit
dmesg from thinkpad x1 extreme / GTX 1050 Ti on kernel 4.20 with discrete only
graphics

Not sure if that helps with the diagnostics, but on the same Thinkpad X1
Extreme laptop with "Discrete only" BIOS setting, lspci works fine, X
starts
and works, but there's a timeout logged by nouveau.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190109/b90b1933/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=101665

Martin Peres <martin.peres at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |MOVED
             Status|NEW                         |RESOLVED

--- Comment #18 from Martin Peres <martin.peres at free.fr> ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/358.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20191204/6a49a723/attachment.html>