From: Lucas Stach <dev@lynxeye.de> To: Thorsten Leemhuis <regressions@leemhuis.info>, George Spelvin <linux@sciencehorizons.net> Cc: airlied@redhat.com, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org Subject: Re: Reported regressions for 4.7 as of Sunday, 2016-06-19 Date: Sun, 26 Jun 2016 17:36:13 +0200 [thread overview] Message-ID: <1466955373.3076.1.camel@lynxeye.de> (raw) In-Reply-To: <a2053cba-8044-0239-6091-7f47f278af1f@leemhuis.info> Am Sonntag, den 26.06.2016, 14:52 +0200 schrieb Thorsten Leemhuis: > On 24.06.2016 16:19, George Spelvin wrote: > > > > Here's a regression you might add. > Thx, added. > Probably the same bug as https://bugzilla.kernel.org/show_bug.cgi?id=119861 and already fixed in the last -rc. Regards, Lucas > > > > I only reported it to dri-devel, > > since it's DRI-specific, but since there's been thunderous silence > > for a few weeks, I'm trying to be a squeakier wheel. > Added the nouveau developers to CC, maybe it's a bug in the drm > driver > that triggers this problem; and airlied is "Internet challenged" > right > now and Daniel on holidays, so it might be good to get more people > into > the loop anyway. > > > > > Given that I bisected it to a single, small, revertable commit, I'd > > hoped it would be easy to deal with. > > > > [BISECTED: 0955c1250e] 4.7-rc1 oops at > > drm_connector_cleanup+0x5c/0x1d0 > > > > E-mail report at > > https://marc.info/?l=dri-devel&m=146577898611849 > > > > Bugzilla report at > > https://bugs.freedesktop.org/show_bug.cgi?id=96532 > FWIW the important detail: Reverting > https://git.kernel.org/linus/0955c1250e (drm/crtc: take references to > connectors used in a modeset. (v2)) fixes this. > > Sincerely, your regression tracker for Linux 4.7 (http://bit.ly/28JRm > Jo) > Thorsten > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Lucas Stach <dev@lynxeye.de> To: Thorsten Leemhuis <regressions@leemhuis.info>, George Spelvin <linux@sciencehorizons.net> Cc: airlied@redhat.com, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org Subject: Re: Reported regressions for 4.7 as of Sunday, 2016-06-19 Date: Sun, 26 Jun 2016 17:36:13 +0200 [thread overview] Message-ID: <1466955373.3076.1.camel@lynxeye.de> (raw) In-Reply-To: <a2053cba-8044-0239-6091-7f47f278af1f@leemhuis.info> Am Sonntag, den 26.06.2016, 14:52 +0200 schrieb Thorsten Leemhuis: > On 24.06.2016 16:19, George Spelvin wrote: > > > > Here's a regression you might add. > Thx, added. > Probably the same bug as https://bugzilla.kernel.org/show_bug.cgi?id=119861 and already fixed in the last -rc. Regards, Lucas > > > > I only reported it to dri-devel, > > since it's DRI-specific, but since there's been thunderous silence > > for a few weeks, I'm trying to be a squeakier wheel. > Added the nouveau developers to CC, maybe it's a bug in the drm > driver > that triggers this problem; and airlied is "Internet challenged" > right > now and Daniel on holidays, so it might be good to get more people > into > the loop anyway. > > > > > Given that I bisected it to a single, small, revertable commit, I'd > > hoped it would be easy to deal with. > > > > [BISECTED: 0955c1250e] 4.7-rc1 oops at > > drm_connector_cleanup+0x5c/0x1d0 > > > > E-mail report at > > https://marc.info/?l=dri-devel&m=146577898611849 > > > > Bugzilla report at > > https://bugs.freedesktop.org/show_bug.cgi?id=96532 > FWIW the important detail: Reverting > https://git.kernel.org/linus/0955c1250e (drm/crtc: take references to > connectors used in a modeset. (v2)) fixes this. > > Sincerely, your regression tracker for Linux 4.7 (http://bit.ly/28JRm > Jo) > Thorsten > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-26 15:36 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-24 14:19 Reported regressions for 4.7 as of Sunday, 2016-06-19 George Spelvin 2016-06-26 12:52 ` Thorsten Leemhuis 2016-06-26 15:36 ` Lucas Stach [this message] 2016-06-26 15:36 ` Lucas Stach -- strict thread matches above, loose matches on Subject: below -- 2016-06-19 14:52 Thorsten Leemhuis 2016-06-20 10:21 ` Christoph Hellwig 2016-06-20 10:21 ` Christoph Hellwig 2016-06-21 11:11 ` Josh Boyer 2016-06-21 20:40 ` Linus Torvalds 2016-06-22 0:55 ` Josh Boyer 2016-06-22 1:25 ` Martin K. Petersen 2016-06-22 1:29 ` Quinn Tran 2016-06-22 11:51 ` Johannes Thumshirn 2016-06-22 15:57 ` Quinn Tran 2016-06-23 7:22 ` Johannes Thumshirn 2016-06-23 16:13 ` Quinn Tran 2016-06-23 16:35 ` Linus Torvalds 2016-06-23 20:56 ` Eric W. Biederman 2016-07-05 16:30 ` Josh Boyer 2016-07-05 17:32 ` Linus Torvalds 2016-07-05 18:43 ` Thorsten Leemhuis 2016-07-05 18:43 ` Thorsten Leemhuis 2016-07-05 19:40 ` Martin K. Petersen 2016-06-22 6:36 ` Kalle Valo
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=1466955373.3076.1.camel@lynxeye.de \ --to=dev@lynxeye.de \ --cc=airlied@redhat.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@sciencehorizons.net \ --cc=nouveau@lists.freedesktop.org \ --cc=regressions@leemhuis.info \ /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: linkBe 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.