All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Thomas Richter" <thorfdbg@t-online.de>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: Intel-gfx related suspend-to-ram issues on IBM R31
Date: Wed, 27 Sep 2017 17:16:46 +0300	[thread overview]
Message-ID: <87y3p06xbl.fsf@intel.com> (raw)
In-Reply-To: <e769432a-3662-2d50-00aa-30c78ff552a3@t-online.de>

On Sat, 23 Sep 2017, Thomas Richter <thorfdbg@t-online.de> wrote:
> Hi Ville,
>
> Thanks for the pointers. However, which branch of mesa does this
>> 
>> drm-tip + https://patchwork.freedesktop.org/patch/176870/ 
>
> patch apply to? I assume it is the intel-drm-nightly? Tried that, 
> without success. While the 4.9.xx reaches at least S1, this one gets 
> stuck earlier, with or without the patch.

drm-tip branch of [1].

BR,
Jani.

[1] https://cgit.freedesktop.org/drm/drm-tip


>
>> works rather
>> well on my 830 machine (Fujitu-Siemens Lifebook S6010). Without that
>> things gets stuck on account of vblank interrupts getting disabled at
>> random times. Xonotic has been pretty good at reproducing that bug for
>> me. Apart from that S3 works, S4 works, never tried S1 and probably
>> never will since I have S3 ;)
>
> Well, you forget that the IBM R31 "made by Acer" has a quite buggy bios 
> compared to the Fujitsu. Unfortunately, my S6010 died about two years 
> ago, a very nice machine for its age, actually. The R31 never woke up 
> from S3, the Fujitsu did from the 4.1.38 kernel. The same kernel worked 
> only for S1, though Win XP seems to manage it on the same hardware.
>
>
>> There are some bugs in Mesa though. One at least (a missing workaround)
>> can cause the GPU to die. I think the current upstream Mesa doesn't hit
>> it very reliably because it inlines the vertex data into the batch.
>> I've been working on making it use vertex buffers instead, and I think
>> that made me hit it more reliably. I have a pile of patches for Mesa
>> that I need to clean up at some point. In the meantime here's the diff
>> for that one fix (probably won't apply as is since I have it sitting
>> on top a pile of other stuff atm):
>
> Sorry, again the same question: I checked the head branch, but there the 
> functions look quite different. I tried to tweak it in, there seems to 
> be the same sort of misalingment issue, but it's really not the same 
> structure. With the modifications below "fiddled in", I do not see much 
> of of a difference.
>
> Thanks and greetings,
>
> Thomas
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-09-27 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 18:36 Intel-gfx related suspend-to-ram issues on IBM R31 Thomas Richter
2017-09-22 15:42 ` Ville Syrjälä
2017-09-22 22:24   ` Thomas Richter
2017-09-27 14:16     ` Jani Nikula [this message]

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=87y3p06xbl.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=thorfdbg@t-online.de \
    --cc=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.