Re: [bisected] nouveau: "Failed to idle channel x" after resume

2012-07-05 Thread Martin Nyhus
On Mon, 11 Jun 2012 23:18:42 +0200 Martin Nyhus wrote: > after resuming from suspend nouveau starts writing Failed to idle > channel x (where x is 2 or 3) to the log and X appears to stop and > then restart only to stop again. Starting Firefox after resuming > triggers the bugs eve

[bisected] nouveau: "Failed to idle channel x" after resume

2012-07-05 Thread Martin Nyhus
On Mon, 11 Jun 2012 23:18:42 +0200 Martin Nyhus wrote: > after resuming from suspend nouveau starts writing Failed to idle > channel x (where x is 2 or 3) to the log and X appears to stop and > then restart only to stop again. Starting Firefox after resuming > triggers the bugs eve

[bisected] nouveau: "Failed to idle channel x" after resume

2012-06-12 Thread Martin Nyhus
Hi, after resuming from suspend nouveau starts writing Failed to idle channel x (where x is 2 or 3) to the log and X appears to stop and then restart only to stop again. Starting Firefox after resuming triggers the bugs every time, and bisecting leads to 03bd6efa ("drm/nv50/fifo: use hardware chann

[bisected] nouveau: "Failed to idle channel x" after resume

2012-06-11 Thread Martin Nyhus
Hi, after resuming from suspend nouveau starts writing Failed to idle channel x (where x is 2 or 3) to the log and X appears to stop and then restart only to stop again. Starting Firefox after resuming triggers the bugs every time, and bisecting leads to 03bd6efa ("drm/nv50/fifo: use hardware chann

Re: [next] Null pointer dereference in nouveau_vm_map_sg

2012-01-25 Thread Martin Nyhus
On Tue, 24 Jan 2012 17:33:19 -0500 Jerome Glisse wrote: > Can you please both test if attached patch fix it for you ? Thanks. It looks good too me, but it crashes a little later due to vma->node being invalid: Jan 25 00:54:21 callisto kernel: [ 119.038357] [drm] nouveau_vm_unmap vma 880057

[next] Null pointer dereference in nouveau_vm_map_sg

2012-01-25 Thread Martin Nyhus
On Tue, 24 Jan 2012 17:33:19 -0500 Jerome Glisse wrote: > Can you please both test if attached patch fix it for you ? Thanks. It looks good too me, but it crashes a little later due to vma->node being invalid: Jan 25 00:54:21 callisto kernel: [ 119.038357] [drm] nouveau_vm_unmap vma 880057

[next] Null pointer dereference in nouveau_vm_map_sg

2012-01-17 Thread Martin Nyhus
On Monday 16. January 2012 21:30:59 Jerome Glisse wrote: > On Sun, Jan 15, 2012 at 10:31:08PM +0100, Martin Nyhus wrote: > > In some cases mem will be null in nouveau_vm_map_sg, resulting in a crash > > at drivers/gpu/drm/nouveau/nouveau_vm.c:84. It seems to be easy enough to >

Re: [next] Null pointer dereference in nouveau_vm_map_sg

2012-01-16 Thread Martin Nyhus
On Monday 16. January 2012 21:30:59 Jerome Glisse wrote: > On Sun, Jan 15, 2012 at 10:31:08PM +0100, Martin Nyhus wrote: > > In some cases mem will be null in nouveau_vm_map_sg, resulting in a crash > > at drivers/gpu/drm/nouveau/nouveau_vm.c:84. It seems to be easy enough to >

[next] Null pointer dereference in nouveau_vm_map_sg

2012-01-15 Thread Martin Nyhus
In some cases mem will be null in nouveau_vm_map_sg, resulting in a crash at drivers/gpu/drm/nouveau/nouveau_vm.c:84. It seems to be easy enough to reproduce, so I can test patches if needed. Martin [ 216.546584] BUG: unable to handle kernel NULL pointer dereference at 00d

[next] Null pointer dereference in nouveau_vm_map_sg

2012-01-15 Thread Martin Nyhus
In some cases mem will be null in nouveau_vm_map_sg, resulting in a crash at drivers/gpu/drm/nouveau/nouveau_vm.c:84. It seems to be easy enough to reproduce, so I can test patches if needed. Martin [ 216.546584] BUG: unable to handle kernel NULL pointer dereference at 00d