From: Ben Skeggs <skeggsb@gmail.com>
To: Ben Skeggs <skeggsb@gmail.com>, Ben Skeggs <bskeggs@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
nouveau <nouveau@lists.freedesktop.org>
Subject: Re: [Nouveau] REGRESSION: Kernel PANIC 8777c5c11764d8336d8270f96778158c34c92108 - drm/nouveau/dp: probe dpcd to determine connectedness
Date: Tue, 17 Jun 2014 15:39:19 +1000 [thread overview]
Message-ID: <CACAvsv6nyu4cw6Yc1r5L8XNbS_Dyrka7o1JH=2Kc6URUWVcxjA@mail.gmail.com> (raw)
In-Reply-To: <20140617053332.GA9117@glanzmann.de>
On Tue, Jun 17, 2014 at 3:33 PM, Thomas Glanzmann <thomas@glanzmann.de> wrote:
> Hello Ben,
>
>> Are you able to double-check that bisect? I'm not at all sure how
>> that particular commit could trigger the issue you're seeing. Some of
>> the others, certainly. It might be worth trying a couple of times
>> before marking something as "good", in case there's a timing aspect to
>> the problem.
>
> please CC me, otherwise I might not see your message. The bug is very
> clear, I boot my machine, the screen turns black as soon as the X server
> is booted and the system does not ping anymore. I rebooted several times
> before the bisect and the bug always hit me. For my taste the offending
> commit is to large. So maybe I can split it in multiple smaller commits
> and than debug it. However I'm currently out of the office, so maybe
> tomorrow. If you do any progress on this, please CC me in order to avoid
> duplicate effort.
8777c5c11764d8336d8270f96778158c34c92108 (which is mentioned as the
first bad commit above...) is a tiny commit, so I have no idea what
you mean by "too large for your taste".
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.
Thanks,
Ben.
>
> Cheers,
> Thomas
next prev parent reply other threads:[~2014-06-17 5:39 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 [this message]
2014-06-17 5:40 ` Ben Skeggs
2014-06-17 5:46 ` Thomas Glanzmann
2014-06-17 6:12 ` Andreas Tscharner
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='CACAvsv6nyu4cw6Yc1r5L8XNbS_Dyrka7o1JH=2Kc6URUWVcxjA@mail.gmail.com' \
--to=skeggsb@gmail.com \
--cc=bskeggs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).