mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	Jiri Kosina <jikos@jikos.cz>
Subject: Re: 3.15-rc2: i915 regression: only top 20% of screen works in X
Date: Thu, 24 Apr 2014 15:36:52 +0200	[thread overview]
Message-ID: <20140424133652.GA19610@amd.pavel.ucw.cz> (raw)
In-Reply-To: <CAKMK7uFAgHJ-kYJEcDCvNm3B4ELKC8CFK8iP+-SL7bdT5-VQHA@mail.gmail.com>

On Thu 2014-04-24 08:03:04, Daniel Vetter wrote:
> On Thu, Apr 24, 2014 at 7:50 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > That says that i915.ko failed to initialise the GPU (or rather the GPU
> > wasn't responding) and bailed during module load. The key line here is
> >
> > [drm:init_ring_common] *ERROR* render ring initialization failed ctl
> > 0001f001 head 00002034 tail 00000000 start 0012f000
> >
> > Jiri has been seeing a similar issue creep in during resume, but it is
> > not reliable enough to bisect. Is your boot failure reliable enough to
> > bisect? Also drm-intel-nightly should mitigate this failure and allow
> > i915.ko to continue to load and run X, which would be worth testing to
> > make sure that works as intended.
> 
> Oh right, g4x going beserk :( Apparently something changed in 3.15
> somewhere which made this much more likely, but like Chris said in
> Jiri's case it's too unreliable to reproduce for a bisect. We've had
> this come&go pretty much ever since kms support was merged and never
> tracked it down.

So far I went back to 3.14, and yes, graphics works there.

Back to 3.15, put it to smaller monitor. This time, top 30% of screen
works, and last working scanline is copied to the rest 60% of
screen. [With the exception of mouse cursor, that somehow affects that
magically.]

> The bug is https://bugs.freedesktop.org/show_bug.cgi?id=76554
> 
> Like Chris said please test latest drm-intel-nighlty from
> http://cgit.freedesktop.org/drm-intel to make sure that the recently
> merged mitigation measures work properly. But those won't get your gpu
> back, only the display and it's only for 3.16. We're still hunting a
> proper fix for 3.15.

So you know where the bug is or not?

> And if you can indeed reliably reproduce this a bisect could be really useful.

I'm confused. And yes, it seems reliable. But I'm not sure if I see
same bug you are talking about.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2014-04-24 13:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 20:22 Pavel Machek
2014-04-23 21:09 ` Daniel Vetter
2014-04-23 22:03   ` Pavel Machek
2014-04-23 22:09   ` Pavel Machek
2014-04-24  5:50     ` Chris Wilson
2014-04-24  6:03       ` Daniel Vetter
2014-04-24 13:36         ` Pavel Machek [this message]
2014-04-24 13:56           ` Jiri Kosina
2014-04-24 13:43         ` Pavel Machek
2014-04-24 15:03           ` Chris Wilson
2014-04-24 19:28         ` [partial bisect] " Pavel Machek
2014-04-24 19:40         ` [bisect result] " Pavel Machek
2014-04-24 20:15           ` Chris Wilson
2014-04-24 22:00             ` Pavel Machek
2014-04-24 22:06             ` Pavel Machek
2014-04-24 22:15               ` Jiri Kosina
2014-04-25 11:33               ` Jani Nikula
2014-04-24 20:13         ` [PATCH] fix " Pavel Machek
2014-04-24 10:42       ` 3.15-rc2: " Pavel Machek
2014-04-24 11:39         ` Jiri Kosina

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=20140424133652.GA19610@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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

all inboxes | Powered by JetHome®