Re: [bisected] Re: drm, qxl: post 5.11 merge warning+explosion

2020-12-18 Thread Christian König
Since -rc1 is not out yet I've just pushed it to drm-misc-next-fixes. Thanks, Christian. Am 17.12.20 um 19:50 schrieb David Airlie: Yes this looks correct, please add my rb and get into a fixes queue somewhere. Dave. On Fri, Dec 18, 2020 at 2:39 AM Christian König wrote: Am 17.12.20 um

Re: [bisected] Re: drm, qxl: post 5.11 merge warning+explosion

2020-12-17 Thread David Airlie
Yes this looks correct, please add my rb and get into a fixes queue somewhere. Dave. On Fri, Dec 18, 2020 at 2:39 AM Christian König wrote: > > Am 17.12.20 um 17:26 schrieb Mike Galbraith: > > On Thu, 2020-12-17 at 17:24 +0100, Christian König wrote: > >> Hi Mike, > >> > >> what exactly is the

Re: [bisected] Re: drm, qxl: post 5.11 merge warning+explosion

2020-12-17 Thread Mike Galbraith
On Thu, 2020-12-17 at 17:38 +0100, Christian König wrote: > > Mike can you test the attached patch? Yup, one-liner made it all better. That was quick like bunny. -Mike

Re: [bisected] Re: drm, qxl: post 5.11 merge warning+explosion

2020-12-17 Thread Christian König
Am 17.12.20 um 17:26 schrieb Mike Galbraith: On Thu, 2020-12-17 at 17:24 +0100, Christian König wrote: Hi Mike, what exactly is the warning from qxl you are seeing? [1.815561] WARNING: CPU: 7 PID: 355 at drivers/gpu/drm/ttm/ttm_pool.c:365 ttm_pool_alloc+0x41b/0x540 [ttm] Yeah, that is

Re: [bisected] Re: drm, qxl: post 5.11 merge warning+explosion

2020-12-17 Thread Mike Galbraith
On Thu, 2020-12-17 at 17:24 +0100, Christian König wrote: > Hi Mike, > > what exactly is the warning from qxl you are seeing? [1.815561] WARNING: CPU: 7 PID: 355 at drivers/gpu/drm/ttm/ttm_pool.c:365 ttm_pool_alloc+0x41b/0x540 [ttm] [1.815561] Modules linked in: ext4(E) crc16(E)

Re: [bisected] Re: drm, qxl: post 5.11 merge warning+explosion

2020-12-17 Thread Christian König
Hi Mike, what exactly is the warning from qxl you are seeing? Thanks, Christian. Am 17.12.20 um 17:21 schrieb Mike Galbraith: ee5d2a8e549e90325fcc31825269f89647cd6fac is the first bad commit commit ee5d2a8e549e90325fcc31825269f89647cd6fac Author: Christian König Date: Sat Oct 24 13:10:28

[bisected] Re: drm, qxl: post 5.11 merge warning+explosion

2020-12-17 Thread Mike Galbraith
ee5d2a8e549e90325fcc31825269f89647cd6fac is the first bad commit commit ee5d2a8e549e90325fcc31825269f89647cd6fac Author: Christian König Date: Sat Oct 24 13:10:28 2020 +0200 drm/ttm: wire up the new pool as default one v2 Provide the necessary parameters by all drivers and use the new

Re: drm, qxl: post 5.11 merge warning+explosion

2020-12-16 Thread Mike Galbraith
On Wed, 2020-12-16 at 03:41 +0100, Mike Galbraith wrote: > Little kvm works fine with nomodeset, so will be busy for a while > bisecting two other problems that popped up here this cycle. (hohum) > > [1.815561] WARNING: CPU: 7 PID: 355 at drivers/gpu/drm/ttm/ttm_pool.c:365 >

drm, qxl: post 5.11 merge warning+explosion

2020-12-15 Thread Mike Galbraith
Little kvm works fine with nomodeset, so will be busy for a while bisecting two other problems that popped up here this cycle. (hohum) [1.815561] WARNING: CPU: 7 PID: 355 at drivers/gpu/drm/ttm/ttm_pool.c:365 ttm_pool_alloc+0x41b/0x540 [ttm] [1.815561] Modules linked in: ext4(E) crc16(E)