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=-2.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 10659C5519F for ; Wed, 18 Nov 2020 22:25:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 95D35246DC for ; Wed, 18 Nov 2020 22:25:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="lHVpf+Ii" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726500AbgKRWZi (ORCPT ); Wed, 18 Nov 2020 17:25:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56610 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725822AbgKRWZi (ORCPT ); Wed, 18 Nov 2020 17:25:38 -0500 Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0DD80C0613D4 for ; Wed, 18 Nov 2020 14:25:38 -0800 (PST) Received: by mail-ed1-x52b.google.com with SMTP id t9so3712946edq.8 for ; Wed, 18 Nov 2020 14:25:37 -0800 (PST) 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=WhgF/IA0ylKv3857epiQSft8PVt9PvfZJmPTqKtYUWk=; b=lHVpf+IiHwYzA5b2OP4M6pDap5B/AtrWq259lzuNt/iFOBJckQFbHahg2TbM7C3fUk jt8tAZRAlM4e8jW12z22NXCGWzGcrwj+UxW7c730jXr9p/3+EoLaB+Td9qGgUSld9KvA 4QvZnmpycwpZhkePUWXdnlRI8zI9+0/sVZrWPti9U4JARlXj0FZqPeDN+SpTVmdIhVm+ I+GR2gcZYaLcHFVPKysWhJ5cDdaxY2aXrDZqtX3Xq/x3QplSUYwLxbydVXO8Pf2+OTZw rWKO8B6ZBGrj/rRD2eJdbz3jGsFP9VInz//nuvEW0Q3NZaO+hABVkaPXCfV6awF/Gvy+ Agbw== 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=WhgF/IA0ylKv3857epiQSft8PVt9PvfZJmPTqKtYUWk=; b=bhPQvxoJI+jE7+cOLs2aSyltN0Bzro9yAagweY7+RPxPS7Fy1gUZYcKCnvRvrIH3E9 qk+uzegyKUcFy3aD0c5q+22umuaQtfHtTFRiHqRoL5pwPeDN4s5Maa4uBOniZ3ozO3Mx uvzuKBWWZi4eh4n2nr/alNlaUoUAOTmxVRtWpqOFDXxKK5ckw9FAX+aCn2TW4GodZs3Y ilgH+j2O7T+I15q9N6FOtjILdnofmnEtb5UWEkeg8GmtehB1OahMK7Z0forHsJCrDpor wOFb+FNhBv2gih5P8mYfSv7ZyjKfDun/GSPS8YpHX7gc16v1jo+Iv6vUiyUiaFAtXqQP o1sg== X-Gm-Message-State: AOAM532S2NVZ07xvlkogfbTBjl/dnmmS1wCTGZQq6pZgbUgo68uYSOoy QZ2zuidJjVNh+TMf+vK/93RbVu2RxqiOVwD/rGw= X-Google-Smtp-Source: ABdhPJzOwvJ+BSFzbS/tue9emcVc7TGxC//Fwu5s5V11amStH73YCO5SCGLGsDa69pJbMqqzH8QEG07gTGWiefYj9FQ= X-Received: by 2002:a50:d516:: with SMTP id u22mr7772043edi.127.1605738336474; Wed, 18 Nov 2020 14:25:36 -0800 (PST) MIME-Version: 1.0 References: <692820a49ded436591b5fe3a18c68a5e@AcuMS.aculab.com> <0a10da3d-085f-c7a7-0053-dc1e9ea871ed@suse.de> In-Reply-To: From: Dave Airlie Date: Thu, 19 Nov 2020 08:25:24 +1000 Message-ID: Subject: Re: Linux 5.10-rc4 To: Daniel Vetter Cc: David Laight , Linux Kernel Mailing List , dri-devel , "Huang, Ray" , Thomas Zimmermann , Dave Airlie , Linus Torvalds , =?UTF-8?Q?Christian_K=C3=B6nig?= Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 19 Nov 2020 at 08:15, Daniel Vetter wrote: > > On Wed, Nov 18, 2020 at 11:01 PM David Laight wrote: > > > > From: Thomas Zimmermann > > > Sent: 18 November 2020 19:37 > > > > > > Hi > > > > > > Am 18.11.20 um 19:10 schrieb Linus Torvalds: > > > > On Wed, Nov 18, 2020 at 4:12 AM David Laight wrote: > > > >> > > > >> I've got the 'splat' below during boot. > > > >> This is an 8-core C2758 Atom cpu using the on-board/cpu graphics. > > > >> User space is Ubuntu 20.04. > > > >> > > > >> Additionally the X display has all the colours and alignment slightly > > > >> messed up. > > > >> 5.9.0 was ok. > > > >> I'm just guessing the two issues are related. > > > > > > > > Sounds likely. But it would be lovely if you could bisect when > > > > exactly the problem(s) started to both verify that, and just to > > > > pinpoint the exact change.. > > > > I don't quite understand what 'git bisect' did. > > I was bisecting between v5.9 and v5.10-rc1 but it suddenly started > > generating v5.9.0-rc5+ kernels. > > We queue up patches for -rc1 way before the previous kernel is > released, so this is normal. > > > The identified commit was 13a8f46d803 drm/ttm: move ghost object created. > > (retyped - hope it is right). > > But the diff to that last 'good' commit is massive. > > Yeah that's also normal for non-linear history. If you want to > double-check, re-test the parent of that commit (which is 2ee476f77ffe > ("drm/ttm: add a simple assign mem to bo wrapper")), which should > work, and then the bad commit. > > Also is this the first bad commit for both the splat and the screen > corruption issues? > > > So I don't know if that is anywhere near right. > > Thomas guessed it could be a ttm change, you hit one, and it looks > like it could be the culprit. Now I guess it's up to Dave. Also adding > Christian, in case he has an idea. I'd be mildly surprised if it's that commit, since it just refactors what looks to me to be two identical code pieces into one instance (within the scope of me screwing that up, but reading it I can't see it). I'll dig into this today. Dave.