From: Ben Skeggs <skeggsb@gmail.com>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: Jerome Glisse <jglisse@redhat.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/nouveau: fix ttm move notify callback
Date: Tue, 10 Jan 2012 13:46:05 +1000 [thread overview]
Message-ID: <1326167165.31565.1.camel@nisroch> (raw)
In-Reply-To: <20120106210027.GB2823@homer.localdomain>
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 or segfault are interesting).
> >
> > http://darnok.org/vga/move_notify-v212.log
> >
>
> Looks like nouveau doesn't like move notify being call on driver
> shutdown or when somethings om nv50 is down. Ben i think you will
> be better at finding a fix for that than me.
I'm also not able to reproduce this issue on a NV98 (so, i'd expect
every nv50+ chipset to behave the same) chipset with the current code in
Dave's drm-core-next tree..
Am I missing something?
Ben.
>
> Cheers,
> Jerome
next prev parent reply other threads:[~2012-01-10 3:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 18:31 [PATCH] drm/nouveau: fix ttm move notify callback j.glisse
2012-01-05 21:48 ` Konrad Rzeszutek Wilk
2012-01-05 21:51 ` Jerome Glisse
2012-01-05 21:53 ` Ben Skeggs
[not found] ` <20120106021410.GA3120@phenom.dumpdata.com>
2012-01-06 14:57 ` Konrad Rzeszutek Wilk
2012-01-06 16:51 ` Jerome Glisse
2012-01-06 16:53 ` Konrad Rzeszutek Wilk
2012-01-06 18:22 ` Jerome Glisse
2012-01-06 19:52 ` Konrad Rzeszutek Wilk
2012-01-06 21:00 ` Jerome Glisse
2012-01-10 3:46 ` Ben Skeggs [this message]
2012-01-10 14:34 ` Konrad Rzeszutek Wilk
2012-01-24 15:00 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1326167165.31565.1.camel@nisroch \
--to=skeggsb@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.com \
--cc=jglisse@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox