All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, jani.nikula@linux.intel.com,
	kernel list <linux-kernel@vger.kernel.org>,
	rodrigo.vivi@intel.com
Subject: Re: 5.13-rc6 on thinkpad X220: graphics hangs with recent mainline
Date: Wed, 18 Aug 2021 08:47:08 +0200	[thread overview]
Message-ID: <20210818064708.GB22282@amd> (raw)
In-Reply-To: <162487567602.6944.6736788493261786550@jlahtine-mobl.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

Hi!
> > I'm getting graphics problems with 5.13-rc:
> > 
> > Debian 10.9, X, chromium and flightgear is in use. Things were more
> > stable than this with previous kernels.
> > 
> > Any ideas?
> 
> The error you are seeing:
> 
> > [185300.784992] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
> > [185300.888694] i915 0000:00:02.0: [drm] fgfs[27370] context reset due to GPU hang
> 
> That just indicates that the rendering took too long. It could be caused
> by a change in how the application renders, userspace driver or i915. So
> a previously on-the-edge-of-timeout operation may have got pushed beyond
> the timeout, or the rendering genuinely got completely stuck.
> 
> If you only updated the kernel, not the application or userspace, could
> you bisect the commit that introduced the behavior and report:
> 
> https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
> 
> We have changes around this area, so would be helpful if you can bisect
> the commit that started the behavior.

So with more recent kernels, problem went away. Is it possible it was
one of those "aborted fence aborts both application and X" problems?

Best regards,
								Pavel
-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, jani.nikula@linux.intel.com,
	kernel list <linux-kernel@vger.kernel.org>,
	rodrigo.vivi@intel.com
Subject: Re: [Intel-gfx] 5.13-rc6 on thinkpad X220: graphics hangs with recent mainline
Date: Wed, 18 Aug 2021 08:47:08 +0200	[thread overview]
Message-ID: <20210818064708.GB22282@amd> (raw)
In-Reply-To: <162487567602.6944.6736788493261786550@jlahtine-mobl.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

Hi!
> > I'm getting graphics problems with 5.13-rc:
> > 
> > Debian 10.9, X, chromium and flightgear is in use. Things were more
> > stable than this with previous kernels.
> > 
> > Any ideas?
> 
> The error you are seeing:
> 
> > [185300.784992] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
> > [185300.888694] i915 0000:00:02.0: [drm] fgfs[27370] context reset due to GPU hang
> 
> That just indicates that the rendering took too long. It could be caused
> by a change in how the application renders, userspace driver or i915. So
> a previously on-the-edge-of-timeout operation may have got pushed beyond
> the timeout, or the rendering genuinely got completely stuck.
> 
> If you only updated the kernel, not the application or userspace, could
> you bisect the commit that introduced the behavior and report:
> 
> https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
> 
> We have changes around this area, so would be helpful if you can bisect
> the commit that started the behavior.

So with more recent kernels, problem went away. Is it possible it was
one of those "aborted fence aborts both application and X" problems?

Best regards,
								Pavel
-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2021-08-18  6:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24  9:53 5.13-rc6 on thinkpad X220: graphics hangs with recent mainline Pavel Machek
2021-06-24  9:53 ` [Intel-gfx] " Pavel Machek
2021-06-28 10:21 ` Joonas Lahtinen
2021-06-28 10:21   ` [Intel-gfx] " Joonas Lahtinen
2021-08-18  6:47   ` Pavel Machek [this message]
2021-08-18  6:47     ` Pavel Machek

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=20210818064708.GB22282@amd \
    --to=pavel@ucw.cz \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@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.