On Sat, Feb 03, 2018 at 05:41:34PM +0000, Andy Simpkins wrote: > >Many thanks for your help and suggestions, this is now sounding like >a driver issue. We'll re-assign this to the appropriate linux-image >package I'm using and CC the kernel folks too. > >Dear kernel folks - sorry, looks like this is your bug (and clearly upstream!).
Quickly responding here again - we've just tried the latest kernel from experimental (4.15.0-rc8) and this still shows the same problem. -- Steve McIntyre, Cambridge, UK. st...@einval.com Who needs computer imagery when you've got Brian Blessed?