Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 101665] New: lspci blocks forever with a GP107M
Date: Fri, 30 Jun 2017 17:13:52 +0000	[thread overview]
Message-ID: <bug-101665-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1487 bytes --]

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-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: kenneth-xkhwgxqQjnbNLxjTenLetw@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.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.

[-- Attachment #1.2: Type: text/html, Size: 2764 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2017-06-30 17:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30 17:13 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-101665-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-06-30 18:08   ` [Bug 101665] lspci blocks forever with a GP107M bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-04 12:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-10 20:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-20 14:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-13 18:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-21 23:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-27 20:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-04 21:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-11 23:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-12  9:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-12 15:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-14 14:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-17  2:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-18 18:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-18 18:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-14 11:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-19 12:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-09  9:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-09  9:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101665-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox