From: Ben Widawsky <ben@bwidawsk.net>
To: Keith Packard <keithp@keithp.com>
Cc: dri-devel@lists.freedesktop.org, Lasso <a_villacis@palosanto.com>,
=?ISO-8859-1?Q?Alex_Villac=ED=ADs_?=@freedesktop.org
Subject: Re: Memory corruption starting in i915 code, in 3.2-rc5
Date: Fri, 16 Dec 2011 14:04:23 -0800 [thread overview]
Message-ID: <4EEBC067.2050006@bwidawsk.net> (raw)
In-Reply-To: <86ty50pbi2.fsf@sumi.keithp.com>
On 12/16/2011 11:22 AM, Keith Packard wrote:
> On Tue, 13 Dec 2011 19:26:50 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Tue, Dec 13, 2011 at 10:14:46AM -0800, Keith Packard wrote:
>>> On Tue, 13 Dec 2011 10:14:15 -0500, Alex Villacís Lasso <a_villacis@palosanto.com> wrote:
>>>
>>>> By using a bootable USB stick, I could check the logs, which
>>>> showed many segfaults at /lib64/ld-2.14.90.so .
>>>
>>> Ouch!
>>>
>>> Please let me know if you find anything further; I'd like to get a
>>> revert sent upstream in the next day or so.
>>
>> I think the revert is trtd. But if you revert it, please also
>> revert/disable the ilk vt-d workaound or apply one of Ben's patches,
>> because that one _does_ blow up, too.
>
> Only if VT-d is enabled though, and that patch is now old enough that
> reverting it may cause additional problems.
>
> Ben's patches still appear to have problems -- they don't appear to
> resolve the infinite recursion issue for unknown reasons.
>
> I'm going to revert the patch which causes the reported regression, then
> wait for Eric to finish up his request queue cleanups and revisit this
> problem after that.
If this is referring to Dave Airlie's comment that it blows up, I think
he took that back as a bad backport on his part (maybe he can confirm).
Aside from that, I never saw anyone report my patch as bad... or good.
Ben
next prev parent reply other threads:[~2011-12-16 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 18:36 Memory corruption starting in i915 code, in 3.2-rc5 Alex Villacís Lasso
2011-12-11 20:46 ` Keith Packard
2011-12-11 21:29 ` Alex Villacís Lasso
2011-12-12 14:51 ` Alex Villacís Lasso
2011-12-12 16:41 ` Keith Packard
2011-12-13 15:14 ` Alex Villacís Lasso
2011-12-13 18:14 ` Keith Packard
2011-12-13 18:26 ` Daniel Vetter
2011-12-16 19:22 ` Keith Packard
2011-12-16 22:04 ` Ben Widawsky [this message]
2011-12-13 18:36 ` Daniel Vetter
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=4EEBC067.2050006@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc==?ISO-8859-1?Q?Alex_Villac=ED=ADs_?=@freedesktop.org \
--cc=a_villacis@palosanto.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.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