Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1686006
| From | Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 |
| Date | 2017-07-12 21:50 +0200 |
| Message-ID | <u2vO1-41S-9@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <u2853-5KF-3@gated-at.bofh.it> <u2mB3-6AZ-1@gated-at.bofh.it> <u2o0a-7C7-13@gated-at.bofh.it> <u2o9P-7G6-21@gated-at.bofh.it> <u2tCy-2IA-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 7/12/17 7:19 PM, Mike Galbraith wrote: > On Wed, 2017-07-12 at 07:37 -0400, Ilia Mirkin wrote: >> On Wed, Jul 12, 2017 at 7:25 AM, Mike Galbraith <efault@gmx.de> wrote: >>> On Wed, 2017-07-12 at 11:55 +0200, Mike Galbraith wrote: >>>> On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote: >>>>> Some display stuff did change for 4.13 for GM20x+ boards. If it's not >>>>> too much trouble, a bisect would be pretty useful. >>>> Bisection seemingly went fine, but the result is odd. >>>> >>>> e98c58e55f68f8785aebfab1f8c9a03d8de0afe1 is the first bad commit >>> But it really really is bad. Looking at gitk fork in the road leading >>> to it... >>> >>> 52d9d38c183b drm/sti:fix spelling mistake: "compoment" -> "component" - good >>> e4e818cc2d7c drm: make drm_panel.h self-contained - good >>> 9cf8f5802f39 drm: add missing declaration to drm_blend.h - good >>> >>> Before the git highway splits, all is well. The lane with commits >>> works fine at both ends, but e98c58e55f68 is busted. Merge arfifact? >> Hmmm... that tree does not appear to have gotten a v4.12 backmerge at >> any point. The last backmerge from Linus as far as I can tell was >> v4.11-rc7. Could be an interaction with some out-of-tree change. > FWIW, checking out the fingered commit then.. > > git log --oneline 52d9d38c183b..e98c58e55f68|grep nouveau and reverting > the lot helped not at all. > > Checking out 6b7781b42dc9 and reverting the fingered commit did. Given > the nouveau bits reverted are mostly the vblank changes, CC to Daniel, > maybe he'll know why both GTX 980 and GeForce 8600 GT get all upset. > > Either I'm damn lucky, both of my nvidia equipped boxen going boom 100% > repeatably, or there are a lot of folks out there who haven't yet tried > suspend with our latest/greatest kernel. I suspect the later. > > -Mike > I should have had a look at my inbox, would have save me a log of work bisecting. Yet i come to the same conclusion: # first bad commit: [e98c58e55f68f8785aebfab1f8c9a03d8de0afe1] Merge tag 'drm-misc-next-2017-05-16' of git://anongit.freedesktop.org/git/drm-misc into drm-next I suspect it is some vblank change as it shows up in every trace i have seen while bisecting, but that is just a wild guess... Greetings, Tobias
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Ilia Mirkin <imirkin@alum.mit.edu> - 2017-07-11 20:00 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-11 20:10 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Ilia Mirkin <imirkin@alum.mit.edu> - 2017-07-11 20:30 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-11 21:00 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-12 09:50 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-12 12:00 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-12 13:30 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Ilia Mirkin <imirkin@alum.mit.edu> - 2017-07-12 13:40 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-12 19:30 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de> - 2017-07-12 21:50 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-14 15:40 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-14 15:50 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de> - 2017-07-14 17:10 +0200
Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Ilia Mirkin <imirkin@alum.mit.edu> - 2017-07-14 17:20 +0200
Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Karol Herbst <karolherbst@gmail.com> - 2017-07-14 17:20 +0200
Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-14 17:20 +0200
Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de> - 2017-07-14 17:20 +0200
Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Ilia Mirkin <imirkin@alum.mit.edu> - 2017-07-14 17:30 +0200
Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Peter Zijlstra <peterz@infradead.org> - 2017-07-14 18:00 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-14 17:20 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Peter Zijlstra <peterz@infradead.org> - 2017-07-14 18:00 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-14 18:00 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Peter Zijlstra <peterz@infradead.org> - 2017-07-14 18:20 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-14 18:40 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Josh Poimboeuf <jpoimboe@redhat.com> - 2017-07-14 21:50 +0200
Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith <efault@gmx.de> - 2017-07-15 04:50 +0200
Re: suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Jessica Yu <jeyu@kernel.org> - 2017-07-17 19:30 +0200
csiph-web