From: "Henrik Rydberg" <rydberg@euromail.se>
To: Ben Skeggs <skeggsb@gmail.com>
Cc: Ben Skeggs <bskeggs@redhat.com>,
nouveau@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf
Date: Mon, 9 Jul 2012 15:13:25 +0200 [thread overview]
Message-ID: <20120709131325.GA22653@polaris.bitmath.org> (raw)
In-Reply-To: <20120705083410.GA395@polaris.bitmath.org>
On Thu, Jul 05, 2012 at 10:34:10AM +0200, Henrik Rydberg wrote:
> On Thu, Jul 05, 2012 at 08:54:46AM +0200, Henrik Rydberg wrote:
> > > Thanks for tracking down the source of this corruption. I don't have
> > > any such hardware, so until someone can figure it out, I think we
> > > should apply this patch.
> >
> > In that case, I would have to massage the patch a bit first; it
> > creates a problem with suspend/resume. Might be something with
> > nva3_pm.c, who knows. I am really stabbing in the dark here. :-)
>
> It seems the suspend/resume problem is unrelated (bad systemd update),
> so I am fine with applying this as is. Obviously not the best
> solution, and if I have time I will continue to look for problems in
> the nva3 copy code, but for now,
>
> Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
I have not encountered the problem in a long while, and I do not have
the patch applied. It is entirely possible that this was fixed by
something else. Unless you have already applied the patch, I would
suggest holding on to it to see if the problem reappears.
Sorry for the churn.
Thanks,
Henrik
next prev parent reply other threads:[~2012-07-09 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 6:31 [REGRESSION] nouveau: Memory corruption using nva3 engine for 0xaf Henrik Rydberg
2012-07-05 6:40 ` Ben Skeggs
2012-07-05 6:54 ` Henrik Rydberg
2012-07-05 8:34 ` Henrik Rydberg
2012-07-09 13:13 ` Henrik Rydberg [this message]
2012-07-09 18:27 ` Henrik Rydberg
2013-06-04 20:48 ` [REGRESSION] nouveau: Resume hung after protecting against client races (MBA3,1) Henrik Rydberg
2013-06-04 21:16 ` Ilia Mirkin
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=20120709131325.GA22653@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=skeggsb@gmail.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;
as well as URLs for NNTP newsgroup(s).