linux-kernel - Re: [Nouveau] REGRESSION: Kernel PANIC 8777c5c11764d8336d8270f96778158c34c92108 - drm/nouveau/dp: probe dpcd to determine connectedness

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACAvsv6nyu4cw6Yc1r5L8XNbS_Dyrka7o1JH=2Kc6URUWVcxjA@mail.gmail.com>
Date:	Tue, 17 Jun 2014 15:39:19 +1000
From:	Ben Skeggs <skeggsb@...il.com>
To:	Ben Skeggs <skeggsb@...il.com>, Ben Skeggs <bskeggs@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	nouveau <nouveau@...ts.freedesktop.org>
Subject: Re: [Nouveau] REGRESSION: Kernel PANIC 8777c5c11764d8336d8270f96778158c34c92108
 - drm/nouveau/dp: probe dpcd to determine connectedness

On Tue, Jun 17, 2014 at 3:33 PM, Thomas Glanzmann <thomas@...nzmann.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/