public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: [Intel-gfx] i915: crash with 5.19-rc2
Date: Thu, 23 Jun 2022 11:32:44 +0200	[thread overview]
Message-ID: <cc5f4465-49cf-3a87-e502-4bb21f2e3163@redhat.com> (raw)
In-Reply-To: <YrN/mI4Qlo66qBmg@intel.com>

Dne 22. 06. 22 v 22:46 Rodrigo Vivi napsal(a):
> Hi Zdenek,
>
> On Wed, Jun 22, 2022 at 01:18:42PM +0200, Zdenek Kabelac wrote:
>> Hello
>>
>> While somewhat oldish hw (T61, 4G, C2D) - I've now witnessed new crash with Xorg:
>>
>> (happened while reopening iconified Firefox window  - running 'standard'
>> rawhide -nodebug kernel 5.19.0-0.rc2.21.fc37.x86_64)
> any bisect possible?
>
> if possible, could you please file a bug?
> https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
>
> I know I know, the account requirement :/
> also on main kernel bugzilla is probably better than the email here.


Hi


So far this bisect does not seem doable, since this crash happened after 
several days of  uptime and so far happened just once (and I'm now already on 
-rc3).

If I'll spot any more regular approach to hit this crash, I may try bisecting. 
Meanwhile I just hope, someone will get an idea what has changed recently (I'd 
not seen such crash with 5.18). Although I need to say that I'm witnessing 
some GPU restarts lately causing just some 'temporary hanging' of Xorg 
desktop, but that's not such a big deal.

Zdenek


  reply	other threads:[~2022-06-23  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 11:18 i915: crash with 5.19-rc2 Zdenek Kabelac
2022-06-22 20:46 ` [Intel-gfx] " Rodrigo Vivi
2022-06-23  9:32   ` Zdenek Kabelac [this message]
2022-08-10  9:22 ` Zdenek Kabelac
2022-08-10 15:55   ` Hugh Dickins
2022-08-10 16:09     ` Matthew Wilcox
2022-08-10 21:54       ` Andrew Morton

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=cc5f4465-49cf-3a87-e502-4bb21f2e3163@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox