linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Tscharner <sternenfeuer@gmail.com>
To: Ben Skeggs <skeggsb@gmail.com>, Ben Skeggs <bskeggs@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	nouveau <nouveau@lists.freedesktop.org>,
	damien.wyart@gmail.com
Subject: Re: [Nouveau] REGRESSION: Kernel PANIC 8777c5c11764d8336d8270f96778158c34c92108 - drm/nouveau/dp: probe dpcd to determine connectedness
Date: Tue, 17 Jun 2014 08:12:10 +0200	[thread overview]
Message-ID: <539FDC3A.5080009@gmail.com> (raw)
In-Reply-To: <CACAvsv6nyu4cw6Yc1r5L8XNbS_Dyrka7o1JH=2Kc6URUWVcxjA@mail.gmail.com>

On 17.06.2014 07:39, Ben Skeggs wrote:

[snip]
> In any case, I encountered the oops myself earlier (absolutely nothing
> to do with that commit) and fixed it here.  I've sent it onto Dave for
> the next -fixes merge, so hopefully it'll help your case too.

Has this anything to do with

<CADJQGJe=CmRn0PmofRUFwZEF-Ah=NAnZVpL1uKYTDLd3Oz_OEQ@mail.gmail.com>
"Machine freeze on latest Linus kernel, seems related to nouveau" from 
Damien Wyart

?

TIA and best regards
	Andreas
-- 
Andreas Tscharner                             <sternenfeuer@gmail.com>
----------------------------------------------------------------------
"Intruder on level one. All Aliens please proceed to level one."
                                       -- Call in "Alien: Resurrection"

      parent reply	other threads:[~2014-06-17  6:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13  9:58 REGRESSION: Kernel PANIC 8777c5c11764d8336d8270f96778158c34c92108 - drm/nouveau/dp: probe dpcd to determine connectedness Thomas Glanzmann
2014-06-15 23:22 ` [Nouveau] " Ben Skeggs
2014-06-17  5:33   ` Thomas Glanzmann
2014-06-17  5:39     ` Ben Skeggs
2014-06-17  5:40       ` Ben Skeggs
2014-06-17  5:46         ` Thomas Glanzmann
2014-06-17  6:12       ` Andreas Tscharner [this message]

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=539FDC3A.5080009@gmail.com \
    --to=sternenfeuer@gmail.com \
    --cc=bskeggs@redhat.com \
    --cc=damien.wyart@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=skeggsb@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).