Re: [Intel-gfx] WARNING: CPU: 0 PID: 3634 at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank

2015-07-08 Thread Michal Hocko
On Wed 08-07-15 09:32:18, Daniel Vetter wrote: [...] > Ok that's starting to get nasty. Can you please test what happens when you > boot with drm.vblankoffdelay=0 and whether drm.vblankoffdelay=1000 has an > effect on reproduction rate? No debug output needed. No difference. See the kernel log fro

Re: [Intel-gfx] WARNING: CPU: 0 PID: 3634 at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank

2015-07-08 Thread Daniel Vetter
On Wed, Jul 08, 2015 at 08:40:17AM +0200, Michal Hocko wrote: > I have just tried to boot 4.2-rc1 and cannot seem to reproduce the issue > anymore. > > On Tue 07-07-15 10:43:58, Daniel Vetter wrote: > [...] > > Can you please > > boot with drm.debug=0xf (lots more nois in dmesg with this) and repr

Re: [Intel-gfx] WARNING: CPU: 0 PID: 3634 at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank

2015-07-07 Thread Michal Hocko
I have just tried to boot 4.2-rc1 and cannot seem to reproduce the issue anymore. On Tue 07-07-15 10:43:58, Daniel Vetter wrote: [...] > Can you please > boot with drm.debug=0xf (lots more nois in dmesg with this) and reproduce? > I only need the last few pages before the WARNING backtrace, just t

Re: [Intel-gfx] WARNING: CPU: 0 PID: 3634 at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank

2015-07-07 Thread Daniel Vetter
On Wed, Jul 01, 2015 at 03:23:39PM +0300, Jani Nikula wrote: > > +intel-gfx and Matt > > On Wed, 01 Jul 2015, Michal Hocko wrote: > > On Wed 01-07-15 10:26:39, Daniel Vetter wrote: > >> On Tue, Jun 30, 2015 at 10:13:35PM +0200, Michal Hocko wrote: > >> > On Tue 30-06-15 18:59:29, Daniel Vetter w

Re: [Intel-gfx] WARNING: CPU: 0 PID: 3634 at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank

2015-07-01 Thread Jani Nikula
+intel-gfx and Matt On Wed, 01 Jul 2015, Michal Hocko wrote: > On Wed 01-07-15 10:26:39, Daniel Vetter wrote: >> On Tue, Jun 30, 2015 at 10:13:35PM +0200, Michal Hocko wrote: >> > On Tue 30-06-15 18:59:29, Daniel Vetter wrote: > [...] >> > > Also it might be time to start bisecting this if you c