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.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED, URIBL_SBL,URIBL_SBL_A 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 1680DC04EB9 for ; Tue, 16 Oct 2018 01:00:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B7B3F208E4 for ; Tue, 16 Oct 2018 01:00:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="SwnX+Jxx" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B7B3F208E4 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727037AbeJPIsY (ORCPT ); Tue, 16 Oct 2018 04:48:24 -0400 Received: from mail-qt1-f193.google.com ([209.85.160.193]:38224 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726883AbeJPIsX (ORCPT ); Tue, 16 Oct 2018 04:48:23 -0400 Received: by mail-qt1-f193.google.com with SMTP id l9-v6so23803522qtf.5; Mon, 15 Oct 2018 18:00:36 -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=i15KWysMeu4MH4r+I0X38zhZQetTV9oaA0Pq1P90Bwg=; b=SwnX+JxxzlP9TyWn9C9H2rGdmRQ1J52lNGTpROsb8U4j2Mb5XGJv0XnzTVTZRHGtd+ RZIdaOOx49UQ2S4wZds7q55+BEZjHuNJwD+zeUPpogx2o+hvmpU6sVIars1v13YZL4Id DAA7XpOd2Fd/8Ilf6rIVpA+F2/5Al73hpTBcYyrGsUVJAYQHGoGVKrxwt1yt/rcapqra QNcU/Pd8ptmZWXnwTMrktTPeoay5RLxHKQXwovjVRzW8sRhFS2eCUmayaVmgYOjUCaZd aHOAASXbt6gT/ty0NI+zhvkYbhLRWhgvDk/LN1nlQgfP49L3Q/Xww8kAZxq2cofTvLBM h2uQ== 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=i15KWysMeu4MH4r+I0X38zhZQetTV9oaA0Pq1P90Bwg=; b=QZfS7/Y/DJQBbO1OYi/kH9siMsWjmZrtGo6Upma5srcWe/QfD8knZCyHNSRbNWB0eG Skt9peMNaVoedXr0rgIveATgamLJbbpEI77qTglmF8maFHm/JUnldQCfd75C3t5aqWoI 8UdcW3RBOif8dxalF9d9x6kPqnVHYeoyiSfZJz4VQMZoLnby0pBscOyrQr9pPO/q5h9n pYrHt6CIWnuO1YriN0t8/5DnZxzETJGpjmrfEfcYSDPYJxhja8OUauAjBsKol8LKrR+H h//+MHsAOyLfmI0TN4XkyZS/CLIpzG8WVUV7bjgdLK6QBzhaw7b48UZjfP9vE60Gf+f3 aGXQ== X-Gm-Message-State: ABuFfoheYlsk80490fZ5jmjc4cETPFrrdlSP6nSNof9+KSG6aMVj5ON8 7vYiN/kMj5J3I/jIzhRPYphwAZGta08lLr1Gtw== X-Google-Smtp-Source: ACcGV63He/VXYAWUeDldpxkRKk3Yj/vWLbp8t1TDuXZnwsG0V24hkdJ+bJFvhJlyxVO6IAUBxcOWkUSffw/Tavh17ZQ= X-Received: by 2002:a0c:ade7:: with SMTP id x36mr4142659qvc.218.1539651636139; Mon, 15 Oct 2018 18:00:36 -0700 (PDT) MIME-Version: 1.0 References: <20181015192546.15faf3a1@canb.auug.org.au> <20181015182637.GA16445@roeck-us.net> <20181016071240.3f62816d@canb.auug.org.au> In-Reply-To: From: Rob Herring Date: Mon, 15 Oct 2018 20:00:24 -0500 Message-ID: Subject: Re: linux-next: Tree for Oct 15 To: Stephen Rothwell , David Miller Cc: Guenter Roeck , linux-next , "linux-kernel@vger.kernel.org" , Michael Ellerman , Benjamin Herrenschmidt , linuxppc-dev Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org +davem On Mon, Oct 15, 2018 at 3:35 PM Rob Herring wrote: > > On Mon, Oct 15, 2018 at 3:12 PM Stephen Rothwell wrote: > > > > Hi Guenter, > > > > [Just cc'ing the PPC and devicetree folks] > > > > On Mon, 15 Oct 2018 11:26:37 -0700 Guenter Roeck wrote: > > > > > > On Mon, Oct 15, 2018 at 07:25:46PM +1100, Stephen Rothwell wrote: > > > > > > > > My qemu boots of a powerpc pseries_le_defconfig kernel failed today. > > > > > > Same here. Interestingly, this only affects little endian pseries > > > boots; big endian works fine. I'll try to bisect later. > > > > > > ALl ppc qemu tests (including big endian pseries) also generate a warning. > > > > > > WARNING: CPU: 0 PID: 0 at mm/memblock.c:1301 .memblock_alloc_range_nid+0x20/0x68 > > > Modules linked in: > > > CPU: 0 PID: 0 Comm: swapper Not tainted 4.19.0-rc7-next-20181015 #1 > > > NIP: c000000000f99198 LR: c000000000f99490 CTR: c000000000bb8364 > > > REGS: c000000001217a78 TRAP: 0700 Not tainted (4.19.0-rc7-next-20181015) > > > MSR: 0000000080021000 CR: 24000422 XER: 20000000 > > > IRQMASK: 1 > > > GPR00: c000000000f99490 c000000001217d00 c00000000121a500 00000000000000c0 > > > GPR04: 0000000000000000 0000000000000000 0000000000000000 ffffffffffffffff > > > GPR08: 0000000000000000 00000000000000c0 0000000000000018 00000000000000b7 > > > GPR12: 0000000000000040 c000000000fe7840 0000000000000000 0000000000000000 > > > GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > > > GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > > > GPR24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > > > GPR28: c000000000000304 c000000001262088 00000000000000c0 c000000000fea500 > > > NIP [c000000000f99198] .memblock_alloc_range_nid+0x20/0x68 > > > LR [c000000000f99490] .memblock_alloc_base+0x18/0x48 > > > Call Trace: > > > [c000000001217d00] [c000000002a00000] 0xc000000002a00000 (unreliable) > > > [c000000001217d80] [c000000000f99490] .memblock_alloc_base+0x18/0x48 > > > [c000000001217df0] [c000000000f7a274] .allocate_paca_ptrs+0x3c/0x74 > > > [c000000001217e70] [c000000000f78bf0] .early_init_devtree+0x288/0x320 > > > [c000000001217f10] [c000000000f79b6c] .early_setup+0x80/0x130 > > > [c000000001217f90] [c000000000000528] start_here_multiplatform+0x68/0x80 > > > > > > > > > sparc images crash, starting with next-20181009. Bisect with > > > next-201810112 points to the merge of devicetree/for-next, though > > > devicetree/for-next itself does not have the problem (bisect log > > > attached below). The crash is in devicetree code. > > > > > > Crash logs: > > > https://kerneltests.org/builders/qemu-sparc64-next/builds/981/steps/qemubuildcommand_1/logs/stdio > > > https://kerneltests.org/builders/qemu-sparc-next/builds/975/steps/qemubuildcommand_1/logs/stdio > > The sparc crash appears to be related to changes I made. Looking into it. The problem is a combination of commit 0b9871a3a8cc ("sparc: Convert to using %pOFn instead of device_node.name") and commit 6d0a70a284be ("vsprintf: print OF node name using full_name"). The Sparc functions in prom_*.c can't use %pOFn to ultimately construct full_name as %pOFn is derived from full_name. Reverting the former commit gets QEMU booting again. David, Can you revert commit 0b9871a3a8cc. I'll have to find another approach. Rob