public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: Andreas Lampersperger <andreas.l.jhoss@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Kernel Oops on 3.14.66
Date: Wed, 27 Apr 2016 19:28:30 +0100	[thread overview]
Message-ID: <572104CE.4010201@intel.com> (raw)
In-Reply-To: <CAJu7YgBPJiQ6Y+0K7b5c37TZxZLDqQynzJUK4itQiVa6-bqdYg@mail.gmail.com>

> 2016-04-27 12:03 GMT+02:00 Dave Gordon <david.s.gordon@intel.com>:
>
>> On 27/04/16 10:19, Andreas Lampersperger wrote:
>>
>>> Hello,
>>>
>>> has anyone here a hint for me, what can cause this error.
>>> The error occures highly sporadic on different machines with intel hd
>>> graphics (ivb_gt1).
>>> I did also some kernel coredumps and found out, that the failed
>>> paging request came from drm_i915_gem_request->list.prev or ->list.next.
>>>
>>> Thank you
>>> Andreas
>>
>> Try this patch.
>>
>> .Dave.
>
On 27/04/16 13:20, Andreas Lampersperger wrote:
> Hi Dave,
>
> thank you for the patch, but I'm using longtime kernel 3.14.66 and so the
> patch does not fit.
> Do you have any suggestions for that kernel?
>
> Andreas

I have no idea what the code would look like in that version; do you 
have any way to get the git commit hash or tag of the i915 driver?

But essentially, if you have the kernel sources for that version, you 
could look for a line that allocates a "struct drm_i915_gem_request". It 
might be

     req = kmem_cache_zalloc(dev_priv->requests, GFP_KERNEL);

or in older versions it might be

     request = kzalloc(sizeof(*request), GFP_KERNEL);

or some other variation. It should of course be followed by a test for 
successful allocation, e.g.

     if (request == NULL)
         return -ENOMEM;

If you can find that line (or lines, at one time there were TWO such 
places), then you just have to add

     INIT_LIST_HEAD(&request->list);

after the test-for-NULL, or anywhere inline thereafter. For example:

     request = kzalloc(sizeof(*request), GFP_KERNEL);
     if (request == NULL)
         return -ENOMEM;

     ret = i915_gem_get_seqno(ring->dev, &request->seqno);
     if (ret) {
         kfree(request);
         return ret;
     }

+   INIT_LIST_HEAD(&request->list);
     kref_init(&request->ref);
     request->ring = ring;
     request->uniq = dev_private->request_uniq++;

HTH,
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-04-27 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27  9:19 Kernel Oops on 3.14.66 Andreas Lampersperger
2016-04-27 10:03 ` Dave Gordon
2016-04-27 12:20   ` Andreas Lampersperger
2016-04-27 18:28     ` Dave Gordon [this message]
2016-04-28  8:58       ` Andreas Lampersperger
2016-04-28 11:50         ` Dave Gordon
2016-04-27 10:54 ` ✓ Fi.CI.BAT: success for " Patchwork

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=572104CE.4010201@intel.com \
    --to=david.s.gordon@intel.com \
    --cc=andreas.l.jhoss@gmail.com \
    --cc=intel-gfx@lists.freedesktop.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