All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: John Maguire <jmaguire2013@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: Kernel crash on 4.19.77-1-lts (Arch Linux / ThinkPad T470p)
Date: Fri, 11 Oct 2019 13:12:43 +0300	[thread overview]
Message-ID: <20191011101243.GI1208@intel.com> (raw)
In-Reply-To: <CAEk+mvvz1SJQD0Yo8s0oB8=jN4yh2ZbURmZ8Ln1VKxcfBE96DQ@mail.gmail.com>

On Thu, Oct 10, 2019 at 01:15:09PM -0400, John Maguire wrote:
> Hi there,
> 
> I wasn't sure which mailing list to use so I BCC'd
> intel-gfx@lists.freedesktop.org and dri-devel@lists.freedesktop.org

Just use Cc. We want all replies to go to the list(s) as well.

> 
> I'm using a Lenovo Thinkpad T470p and running the 4.19.77-1-lts kernel on
> Arch Linux. Recently, I've started getting freezes each day. Audio can
> still be heard, but video output stops. I was able to retrieve a call trace
> from journald.
> 
> I've attached the output of "sudo lspci -vvv" as well as the message from
> journald (null pointer dereference).

Oct 10 12:53:30 scorpion kernel: RIP: 0010:dma_fence_signal_locked+0x30/0xe0                                            

Looks like it could be
https://bugs.freedesktop.org/show_bug.cgi?id=111381

in which case you just need to upgrade to 4.19.78 and it should be
fixed.

-- 
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-10-11 10:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 17:15 Kernel crash on 4.19.77-1-lts (Arch Linux / ThinkPad T470p) John Maguire
2019-10-11 10:12 ` Ville Syrjälä [this message]
2019-10-11 15:33   ` John Maguire
2019-11-05 22:20     ` John Maguire

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=20191011101243.GI1208@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jmaguire2013@gmail.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.