All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: [REGRESSION] nouveau: 30 second boot hang after commit 2b700825e
Date: Tue, 1 Mar 2016 01:45:29 -0600	[thread overview]
Message-ID: <20160301074529.GA1870@zzz> (raw)

Hello,

I am encountering a 30 second hang during boot, in the Xorg process just before
the display manager comes up.  I have bisected the problem to the following
commit:

	commit 2b700825e7a7702fb862edba1262c98040dc1bf6
	Author: Ben Skeggs <bskeggs@redhat.com>
	Date:   Thu Aug 20 14:54:22 2015 +1000

	    drm/nouveau/mc: move device irq handling to platform-specific code

The hang only occurs with CONFIG_DEBUG_SHIRQ=y, which is why I didn't notice it
sooner (I don't usually compile my kernels with that option).

Based on the log output with drm_debug=0x3f, the hang is occurring in
nouveau_gem_ioctl_cpu_prep(), where there is a 30 second timeout.

This is on an "Optimus" laptop which has both an Intel and an Nvidia card.  I
understand that the Nvidia card is being disabled automatically, and only the
Intel one is used; but the nouveau driver obviously still does a few things
either way.  The Nvidia hardware is: NVIDIA Corporation GK107GLM [Quadro K1100M]
(rev a1).

I don't have the expertise to fully assess the suspect commit.  Any thoughts as
to the root cause of this problem?  Is there any other information I can
provide?

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

             reply	other threads:[~2016-03-01  7:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01  7:45 Eric Biggers [this message]
2016-03-02  3:22 ` [REGRESSION] nouveau: 30 second boot hang after commit 2b700825e Alexandre Courbot
     [not found]   ` <CAAVeFuLMwZ4Bq4mx5St3shcCwzN67ZPHdhBB1_WCahFwH1zXCA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-02  3:48     ` Eric Biggers
2016-03-09  4:24     ` Eric Biggers

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=20160301074529.GA1870@zzz \
    --to=ebiggers3-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.