Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: stable@vger.kernel.org,
	Geoff Crompton <geoffc@trinity.unimelb.edu.au>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Matthew Garrett <mjg@redhat.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Ben Widawsky <ben@bwidawsk.net>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [3.4.y, 3.5.y] drm/i915: Use the correct size of the GTT for placing the per-process entries
Date: Fri, 12 Apr 2013 17:13:45 +0100	[thread overview]
Message-ID: <20130412161345.GA16426@hercules> (raw)
In-Reply-To: <20130412073153.GM5710@elie.Belkin>

On Fri, Apr 12, 2013 at 12:31:53AM -0700, Jonathan Nieder wrote:
> Hi Greg,
> 
> Please consider
> 
>  9a0f938bde74 drm/i915: Use the correct size of the GTT for placing
>               the per-process entries, 2012-08-24
> 
> for application to the 3.4.y tree.

Thanks, I'll queue this for 3.5 kernel as well.

Cheers,
--
Luis

> 
> Without this patch, Geoff Crompton's iMac hits a BUG during bootup.
> The problem is reproducible on
> 
>  * Debian's 3.2.y-based kernel with drm backported from 3.4.37
>  * a Debian kernel close to 3.4.4
>  * a Debian kernel close to 3.5.5
>  * vanilla 3.4.4
> 
> He is not able to reproduce the problem on
> 
>  * Debian's older 3.2.y-based kernels without the 3.4.y drm backport
>  * a Debian kernel close to 3.6.4; various newer kernels
>  * vanilla 3.4.4 + this patch
> 
> The patch was applied upstream during the 3.6-rc4 cycle, so newer
> kernels don't need it.
> 
> http://bugs.debian.org/703468 has details, including a screenshot of
> the boot failure ("unable to handling kernel paging request at
> ffffc9000b7ff000" in i915_gem_init_ppgtt).
> 
> Thoughts welcome, as always.
> 
> Regards,
> Jonathan
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-04-12 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <515B5A00.30603@trinity.unimelb.edu.au>
     [not found] ` <20130402223058.GA30308@google.com>
     [not found]   ` <516261D8.50307@trinity.unimelb.edu.au>
     [not found]     ` <20130408062805.GB20159@elie.Belkin>
     [not found]       ` <5163C00F.8020701@trinity.unimelb.edu.au>
     [not found]         ` <20130410063225.GA13832@elie.Belkin>
     [not found]           ` <516609E3.5060207@trinity.unimelb.edu.au>
     [not found]             ` <516742C2.8040107@trinity.unimelb.edu.au>
     [not found]               ` <20130411234036.GQ27070@google.com>
     [not found]                 ` <5167B2EF.5050404@trinity.unimelb.edu.au>
2013-04-12  7:31                   ` [3.4.y, 3.5.y] drm/i915: Use the correct size of the GTT for placing the per-process entries Jonathan Nieder
2013-04-12 16:13                     ` Luis Henriques [this message]
2013-04-12 20:00                     ` Greg KH

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=20130412161345.GA16426@hercules \
    --to=luis.henriques@canonical.com \
    --cc=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geoffc@trinity.unimelb.edu.au \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jrnieder@gmail.com \
    --cc=mjg@redhat.com \
    --cc=stable@vger.kernel.org \
    /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