drm-4.7-final tagged - CFT for drm-next was Re: drm-4.7-rc1 tagged

Matthew Macy mmacy at nextbsd.org
Sun Aug 14 22:54:19 UTC 2016




 ---- On Sun, 14 Aug 2016 05:43:42 -0700 Felix Hanley <felix at userspace.com.au> wrote ---- 
 > Hi, 
 >  
 > I have been running on drm-next-4.6 for a while and have been getting 
 > panics when using Chromium about once or twice a day (sorry, too busy to 
 > debug). I then updated to 762b75d which made X load to black screen and 
 > forced me to reboot. 3a8ce37 fixed that and has been great, no issues 
 > with Chromium (so far). 
 >  
 > I then tried drm-next and have seen the same issues, X loading to black 
 > screen and forcing me to reboot, though does not mean it is related. 
 >  
 > I apologize for the vague debugging but have just not had the time. I 
 > will see what I can do this week. 
 >  
 > For what its worth this is on a Broadwell 5500 system: 
 >  
 > vgapci0 at pci0:0:2:0:     class=0x030000 card=0x802d103c chip=0x16168086 rev=0x09 hdr=0x00 
 >     vendor     = 'Intel Corporation' 
 >     device     = 'HD Graphics 5500' 
 >     class      = display 
 >     subclass   = VGA 


It would help if you'd take the steps suggested on the project's github wiki to get a core. Thanks.


 > -felix 
 >  
 > On Sat, Aug 13, 2016 at 07:57:56PM -0700, Matthew Macy wrote: 
 > > I have merged up through v4.7 and fixed a number of issues.  I've also added kevent support to drm and merged in evdev, so all the kernel dependencies for Wayland are enabled by default in GENERIC. I've tagged the last commit as drm-v4.7-final as following that I will start merging v4.8-rc1 changes. 
 > >  
 > > With the final change Wayland now works on post-Haswell hardware: 
 > > https://twitter.com/Yohanesu75Tweet/status/764640489429540864 
 > >  
 > > Unfortunately I still see corruption when playing multiple videos on chrome (chrome has hardware accelerated video playback). FF (not offloaded) does not show corruption, but requires the use of a compositor to avoid tearing to keep frame updates in sync with screen refresh. 
 > >  
 > > The scope of my personal testing is limited so please report any regressions with respect to drm-next-4.6. 
 > >  
 > >  
 > >  ---- On Fri, 12 Aug 2016 00:21:02 -0700 Matthew Macy <mmacy at nextbsd.org> wrote ----  
 > >  >   
 > >  > A few days ago I branched drm-next-4.6 in to drm-next and synced it with Torvalds' tree as of the v4.6 tag. I then integrated the ~800 commits to drm / i915 / radeon / amdgpu , testing periodically along the way and updating the linuxkpi as needed. I've just tagged the drm-next branch with drm-4.7-rc1 to indicate that it is in sync with 4.7-rc1 upstream.   
 > >  >   
 > >  > If any of you are feeling adventurous I would appreciate it if you would try it and report any regressions with respect to drm-next-4.6. I'm aware that there are a number of issues with drm-next-4.6 so I'm only really interested in _new_ issues.   
 > >  >   
 > >  > If you're feeling really adventurous - run the piglit test suite from the ports' xserver-next branch and do a root cause analysis on test failures.    
 > >  >   
 > >  > As always the repo is at:  
 > >  > https://github.com/FreeBSDDesktop/freebsd-base-graphics  
 > >  >   
 > >  > Look through the existing open issues before filing a report and check the wiki first to address any problems.  
 > >  >   
 > >  > Cheers.  
 > >  >   
 > >  > -M  
 > >  >   
 > >  > _______________________________________________  
 > >  > freebsd-current at freebsd.org mailing list  
 > >  > https://lists.freebsd.org/mailman/listinfo/freebsd-current  
 > >  > To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"  
 > >  >  
 > >  
 > > _______________________________________________ 
 > > freebsd-x11 at freebsd.org mailing list 
 > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 
 > > To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org" 
 > _______________________________________________ 
 > freebsd-x11 at freebsd.org mailing list 
 > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 
 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org" 
 > 



More information about the freebsd-x11 mailing list