From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 28F05C4743C for ; Fri, 4 Jun 2021 17:17:20 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E8C866140F for ; Fri, 4 Jun 2021 17:17:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E8C866140F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 576776F62F; Fri, 4 Jun 2021 17:17:19 +0000 (UTC) Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) by gabe.freedesktop.org (Postfix) with ESMTPS id C8C946F62E; Fri, 4 Jun 2021 17:17:17 +0000 (UTC) Received: by mail-qt1-x82a.google.com with SMTP id t20so7530806qtx.8; Fri, 04 Jun 2021 10:17:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2wmazLLGsfTXVIzn4BhBH78YNgGvUwJNK95soFcTokk=; b=P6RO8fl8Xcr+/vCRve4bc7UGYodwuQwXQ3Ej9FKVnkQvXum3mUeUo0LgDodTKAx3GK BbfW7fn9x+tdc+ocCSMPt/p4oy/s5HRMIK5t5rQcbEB97gbc4iEujNx1wljYSkdPgaNU sdIfB9PIE/RVFQyM8tCGNcm9TSGZenGt95r95VIHv21JZ7gf/QmyzGfY/JoSxhSeraLl z65h/yY3vk3EI0Oktak5PmlAFA9Lp32H09XLFDTNDn//1O7oLzupq92sMIlcmG0F0nP5 tBKRJ3Jv6cfTAL1vwm3C5W4Z8SYoUJ1J9rKEsDFZNG1GhZNBY29EOqPUCRwBM5VYnPry zNHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2wmazLLGsfTXVIzn4BhBH78YNgGvUwJNK95soFcTokk=; b=uAzNxrAK/RDhGZ7qfEQc+EwynOf14Nt0dsEhZb+2dzcheIsElOf7A7rsPF7nRyIWgu Ghd5B7AE1uTc5BzixTVGovn623Bd1dYAM9pQbR33+1mfpPGdtP6ODNu1I92eWgSYq6hI 2pH/61krbVsFCaPnjIyW+Y7DoeItEovktsYc82wLOBlCE1AqPaRqlRaXXWuce1r4DjuT nD5yJo9FkuJtEZR+JOGBSA4Nn7fM6rZyeFdRUZHzm6ax+gMC0bwUyF7nEV3sTPqSE5DD nH/NHfoNN0XTvXODhpE6xtcnp3hpXiawbEPu5EjS8uYGx0MHWnLRBPBfzqZe7anjOmCM 2yFg== X-Gm-Message-State: AOAM531e+lD4z5s2O5YZvpmouH08T3hjbbIWUi1JIQm1+j/wreXuEsZW aRfAWxCJl0LwgvLUs3j5tyLYUKNG092oEDNdAryUilgVBUGjZQ== X-Google-Smtp-Source: ABdhPJypISXuGLvy+Ro2vdW7Zln9YQRKJ0fongdc3pDkW4RuBIbnthdWqifs4c2eOyh98Haxq0fOjOumvnbljm7AHUQ= X-Received: by 2002:ac8:6f06:: with SMTP id g6mr5698528qtv.87.1622827036922; Fri, 04 Jun 2021 10:17:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Vasily Khoruzhick Date: Fri, 4 Jun 2021 10:16:50 -0700 Message-ID: Subject: Re: [Lima] LIMA kernel bug - help! To: Linus Walleij Content-Type: text/plain; charset="UTF-8" X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Stephan Gerhold , Qiang Yu , "open list:DRM PANEL DRIVERS" , lima@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Thu, Jun 3, 2021 at 11:51 PM Linus Walleij wrote: > > Hi Qiang, Hey Linus, > I am using Lima on the ST-Ericsson U8500 SoC. It is one > of the very earliest versions of MALI 400 MP. It mostly works > on the mobile phones I have using PostmarkeOS and > the Phosh UI (Wayland with MESA), but now I have an issue with > one single specimen. > > I have this bug in my dmesg and after this the graphics > start to act weird: > > [ 48.662336] lima a0300000.gpu: mmu page fault at 0x2020400 from bus > id 0 of type read on ppmmu0 > [ 48.662464] lima a0300000.gpu: fail to save task state from phoc > pid 1581: error task list is full > [ 48.662481] lima a0300000.gpu: pp task error 0 int_state=0 status=1 > [ 48.662494] lima a0300000.gpu: mmu resume It's not a kernel bug, GPU MMU just catched invalid memory access by fragment shader. It's likely a mesa bug. What mesa version do you use? > In interrupts: > > 75: 5 0 GIC-0 147 Level gp > 76: 0 0 GIC-0 146 Level gpmmu > 77: 3 0 GIC-0 145 Level pp0 > 78: 1 0 GIC-0 144 Level ppmmu0 > > My UI definitely want to render some more stuff so it gets > stuck here. It's stuck because context is marked as tainted and all the jobs that are submitted from this context afterwards are essentially no-op. > Any hints on how to troubleshoot this? Please make sure that you still can reproduce the bug with mesa from git main (ex-master), if it's still reproducible please open an issue at https://gitlab.freedesktop.org/mesa/mesa/issues Please also try to capture an apitrace of the failing app. See "Bug Reporting" on [1]. [1] https://docs.mesa3d.org/drivers/lima.html > Yours, > Linus Walleij > _______________________________________________ > lima mailing list > lima@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/lima