On Tue, Jan 10, 2012 at 01:46:05PM +1000, Ben Skeggs wrote:
> On Fri, 2012-01-06 at 16:00 -0500, Jerome Glisse wrote:
> > On Fri, Jan 06, 2012 at 02:52:49PM -0500, Konrad Rzeszutek Wilk wrote:
> > > > Still having difficulty to reproduce can you reproduce with the attached
> > > > printk debuging p
On Tue, Jan 10, 2012 at 01:46:05PM +1000, Ben Skeggs wrote:
> On Fri, 2012-01-06 at 16:00 -0500, Jerome Glisse wrote:
> > On Fri, Jan 06, 2012 at 02:52:49PM -0500, Konrad Rzeszutek Wilk wrote:
> > > > Still having difficulty to reproduce can you reproduce with the attached
> > > > printk debuging p
On Fri, 2012-01-06 at 16:00 -0500, Jerome Glisse wrote:
> On Fri, Jan 06, 2012 at 02:52:49PM -0500, Konrad Rzeszutek Wilk wrote:
> > > Still having difficulty to reproduce can you reproduce with the attached
> > > printk debuging patch and provide the log (only few printk preceding the
> > > oops o
On Tue, Jan 10, 2012 at 01:46:05PM +1000, Ben Skeggs wrote:
> On Fri, 2012-01-06 at 16:00 -0500, Jerome Glisse wrote:
> > On Fri, Jan 06, 2012 at 02:52:49PM -0500, Konrad Rzeszutek Wilk wrote:
> > > > Still having difficulty to reproduce can you reproduce with the attached
> > > > printk debuging p
On Tue, Jan 10, 2012 at 01:46:05PM +1000, Ben Skeggs wrote:
> On Fri, 2012-01-06 at 16:00 -0500, Jerome Glisse wrote:
> > On Fri, Jan 06, 2012 at 02:52:49PM -0500, Konrad Rzeszutek Wilk wrote:
> > > > Still having difficulty to reproduce can you reproduce with the attached
> > > > printk debuging p
On Fri, 2012-01-06 at 16:00 -0500, Jerome Glisse wrote:
> On Fri, Jan 06, 2012 at 02:52:49PM -0500, Konrad Rzeszutek Wilk wrote:
> > > Still having difficulty to reproduce can you reproduce with the attached
> > > printk debuging patch and provide the log (only few printk preceding the
> > > oops o
On Fri, Jan 06, 2012 at 02:52:49PM -0500, Konrad Rzeszutek Wilk wrote:
> > Still having difficulty to reproduce can you reproduce with the attached
> > printk debuging patch and provide the log (only few printk preceding the
> > oops or segfault are interesting).
>
> http://darnok.org/vga/move_not
> Still having difficulty to reproduce can you reproduce with the attached
> printk debuging patch and provide the log (only few printk preceding the
> oops or segfault are interesting).
http://darnok.org/vga/move_notify-v212.log
>
> Cheers,
> Jerome
> >From 862e2cc6d35d85404ed24d24c5a5c49c5ef4
On Fri, Jan 06, 2012 at 11:53:35AM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Jan 06, 2012 at 11:51:03AM -0500, Jerome Glisse wrote:
> > On Fri, Jan 6, 2012 at 9:57 AM, Konrad Rzeszutek Wilk
> > wrote:
> > > On Thu, Jan 05, 2012 at 09:14:10PM -0500, Konrad Rzeszutek Wilk wrote:
> > >> On Fri, J
On Fri, Jan 06, 2012 at 02:52:49PM -0500, Konrad Rzeszutek Wilk wrote:
> > Still having difficulty to reproduce can you reproduce with the attached
> > printk debuging patch and provide the log (only few printk preceding the
> > oops or segfault are interesting).
>
> http://darnok.org/vga/move_not
> Still having difficulty to reproduce can you reproduce with the attached
> printk debuging patch and provide the log (only few printk preceding the
> oops or segfault are interesting).
http://darnok.org/vga/move_notify-v212.log
>
> Cheers,
> Jerome
> >From 862e2cc6d35d85404ed24d24c5a5c49c5ef4
On Fri, Jan 06, 2012 at 11:51:03AM -0500, Jerome Glisse wrote:
> On Fri, Jan 6, 2012 at 9:57 AM, Konrad Rzeszutek Wilk
> wrote:
> > On Thu, Jan 05, 2012 at 09:14:10PM -0500, Konrad Rzeszutek Wilk wrote:
> >> On Fri, Jan 06, 2012 at 07:53:13AM +1000, Ben Skeggs wrote:
> >> > On Thu, 2012-01-05 at 1
On Fri, Jan 6, 2012 at 9:57 AM, Konrad Rzeszutek Wilk
wrote:
> On Thu, Jan 05, 2012 at 09:14:10PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Fri, Jan 06, 2012 at 07:53:13AM +1000, Ben Skeggs wrote:
>> > On Thu, 2012-01-05 at 13:31 -0500, j.glisse at gmail.com wrote:
>> > > From: Jerome Glisse
>> >
On Fri, Jan 06, 2012 at 11:53:35AM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Jan 06, 2012 at 11:51:03AM -0500, Jerome Glisse wrote:
> > On Fri, Jan 6, 2012 at 9:57 AM, Konrad Rzeszutek Wilk
> > wrote:
> > > On Thu, Jan 05, 2012 at 09:14:10PM -0500, Konrad Rzeszutek Wilk wrote:
> > >> On Fri, J
On Thu, Jan 05, 2012 at 09:14:10PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Jan 06, 2012 at 07:53:13AM +1000, Ben Skeggs wrote:
> > On Thu, 2012-01-05 at 13:31 -0500, j.glisse at gmail.com wrote:
> > > From: Jerome Glisse
> > >
> > > ttm might call the move notify with null new mem placement
On Fri, Jan 06, 2012 at 11:51:03AM -0500, Jerome Glisse wrote:
> On Fri, Jan 6, 2012 at 9:57 AM, Konrad Rzeszutek Wilk
> wrote:
> > On Thu, Jan 05, 2012 at 09:14:10PM -0500, Konrad Rzeszutek Wilk wrote:
> >> On Fri, Jan 06, 2012 at 07:53:13AM +1000, Ben Skeggs wrote:
> >> > On Thu, 2012-01-05 at 1
On Fri, Jan 6, 2012 at 9:57 AM, Konrad Rzeszutek Wilk
wrote:
> On Thu, Jan 05, 2012 at 09:14:10PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Fri, Jan 06, 2012 at 07:53:13AM +1000, Ben Skeggs wrote:
>> > On Thu, 2012-01-05 at 13:31 -0500, j.gli...@gmail.com wrote:
>> > > From: Jerome Glisse
>> > >
On Thu, 2012-01-05 at 13:31 -0500, j.glisse at gmail.com wrote:
> From: Jerome Glisse
>
> ttm might call the move notify with null new mem placement,
> properly handle this case inside nouveau move notify callback.
This has been fixed already in a -next tree I sent to Dave.
Ben.
>
> Signed-off-
On Thu, Jan 05, 2012 at 09:14:10PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Jan 06, 2012 at 07:53:13AM +1000, Ben Skeggs wrote:
> > On Thu, 2012-01-05 at 13:31 -0500, j.gli...@gmail.com wrote:
> > > From: Jerome Glisse
> > >
> > > ttm might call the move notify with null new mem placement,
>
On Thu, Jan 5, 2012 at 4:48 PM, Konrad Rzeszutek Wilk
wrote:
> On Thu, Jan 05, 2012 at 01:31:55PM -0500, j.glisse at gmail.com wrote:
>> From: Jerome Glisse
>>
>> ttm might call the move notify with null new mem placement,
>> properly handle this case inside nouveau move notify callback.
>
> Let
On Thu, Jan 05, 2012 at 01:31:55PM -0500, j.glisse at gmail.com wrote:
> From: Jerome Glisse
>
> ttm might call the move notify with null new mem placement,
> properly handle this case inside nouveau move notify callback.
Let me give this a spin tonight on both PCIe and AGP hardware.
Um, were y
On Thu, Jan 5, 2012 at 4:48 PM, Konrad Rzeszutek Wilk
wrote:
> On Thu, Jan 05, 2012 at 01:31:55PM -0500, j.gli...@gmail.com wrote:
>> From: Jerome Glisse
>>
>> ttm might call the move notify with null new mem placement,
>> properly handle this case inside nouveau move notify callback.
>
> Let me
On Thu, Jan 05, 2012 at 01:31:55PM -0500, j.gli...@gmail.com wrote:
> From: Jerome Glisse
>
> ttm might call the move notify with null new mem placement,
> properly handle this case inside nouveau move notify callback.
Let me give this a spin tonight on both PCIe and AGP hardware.
Um, were you
On Thu, 2012-01-05 at 13:31 -0500, j.gli...@gmail.com wrote:
> From: Jerome Glisse
>
> ttm might call the move notify with null new mem placement,
> properly handle this case inside nouveau move notify callback.
This has been fixed already in a -next tree I sent to Dave.
Ben.
>
> Signed-off-by:
From: Jerome Glisse
ttm might call the move notify with null new mem placement,
properly handle this case inside nouveau move notify callback.
Signed-off-by: Jerome Glisse
---
drivers/gpu/drm/nouveau/nouveau_bo.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/dri
From: Jerome Glisse
ttm might call the move notify with null new mem placement,
properly handle this case inside nouveau move notify callback.
Signed-off-by: Jerome Glisse
---
drivers/gpu/drm/nouveau/nouveau_bo.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/dri
26 matches
Mail list logo