From: Tobias Klausmann <tobias.johannes.klausmann-AqjdNwhu20eELgA04lAiVw@public.gmane.org>
To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Dave Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
nouveau
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 3.12rc1-pre Nouveau? oops
Date: Mon, 09 Sep 2013 00:01:53 +0200 [thread overview]
Message-ID: <522CF3D1.2020303@mni.thm.de> (raw)
In-Reply-To: <CAPM=9tyCOdzC1NYy7jt+zh3WOuzubaO3b8vwFVast9ec=BWOkA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 08.09.2013 23:33, Dave Airlie wrote:
>>> Looks like you have Optimus (intel + nvidia), and the backtrace has
>>> runtime pm in it, which is something new Dave added for 3.12, adding
>>> him in explicitly. The simplest explanation is that disp->init is
>>> NULL. And it seems like there are no outputs from the earlier nouveau
>>> init prints. I guess that the call to nouveau_display_resume from
>>> nouveau_pmops_runtime_resume should be guarded by a if
>>> (dev->mode_config.num_crtc) like it is everywhere else.
>>>
>>> -ilia
>> Your guess was right, this (hopefully attached patch) fixes it for me!
> Does it look like this one?
>
> Dave.
No, mine was quick and dirty, reverted it and took yours. But i'm a
little bit confused that this is a suspend/resume problem, i booted the
kernel for the first time while seeing the oops. But anyway i tested it
and it works.
Tobias
WARNING: multiple messages have this Message-ID (diff)
From: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>
To: Dave Airlie <airlied@gmail.com>
Cc: Ilia Mirkin <imirkin@alum.mit.edu>,
Dave Airlie <airlied@linux.ie>,
nouveau <nouveau@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Nouveau] 3.12rc1-pre Nouveau? oops
Date: Mon, 09 Sep 2013 00:01:53 +0200 [thread overview]
Message-ID: <522CF3D1.2020303@mni.thm.de> (raw)
In-Reply-To: <CAPM=9tyCOdzC1NYy7jt+zh3WOuzubaO3b8vwFVast9ec=BWOkA@mail.gmail.com>
On 08.09.2013 23:33, Dave Airlie wrote:
>>> Looks like you have Optimus (intel + nvidia), and the backtrace has
>>> runtime pm in it, which is something new Dave added for 3.12, adding
>>> him in explicitly. The simplest explanation is that disp->init is
>>> NULL. And it seems like there are no outputs from the earlier nouveau
>>> init prints. I guess that the call to nouveau_display_resume from
>>> nouveau_pmops_runtime_resume should be guarded by a if
>>> (dev->mode_config.num_crtc) like it is everywhere else.
>>>
>>> -ilia
>> Your guess was right, this (hopefully attached patch) fixes it for me!
> Does it look like this one?
>
> Dave.
No, mine was quick and dirty, reverted it and took yours. But i'm a
little bit confused that this is a suspend/resume problem, i booted the
kernel for the first time while seeing the oops. But anyway i tested it
and it works.
Tobias
next prev parent reply other threads:[~2013-09-08 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 16:53 3.12rc1-pre Nouveau? oops Tobias Klausmann
2013-09-08 16:53 ` Tobias Klausmann
2013-09-08 19:39 ` Ilia Mirkin
2013-09-08 21:21 ` Tobias Klausmann
2013-09-08 21:21 ` [PATCH] Bail in nouveau_display_resume() if there are no output available! Tobias Klausmann
[not found] ` <1378675264-3005-1-git-send-email-tobias.johannes.klausmann-AqjdNwhu20eELgA04lAiVw@public.gmane.org>
2013-09-08 21:33 ` 3.12rc1-pre Nouveau? oops Dave Airlie
2013-09-08 21:33 ` [Nouveau] " Dave Airlie
[not found] ` <CAPM=9tyCOdzC1NYy7jt+zh3WOuzubaO3b8vwFVast9ec=BWOkA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-08 22:01 ` Tobias Klausmann [this message]
2013-09-08 22:01 ` Tobias Klausmann
[not found] ` <522CF3D1.2020303-AqjdNwhu20eELgA04lAiVw@public.gmane.org>
2013-09-08 22:14 ` Ramkumar Ramachandra
2013-09-08 22:29 ` Dave Airlie
2013-09-08 22:29 ` [Nouveau] " Dave Airlie
2013-09-08 23:02 ` Tobias Klausmann
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=522CF3D1.2020303@mni.thm.de \
--to=tobias.johannes.klausmann-aqjdnwhu20eelga04laivw@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=airlied-cv59FeDIM0c@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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.