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.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham 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 7B99DC43387 for ; Fri, 11 Jan 2019 21:26:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4B94721783 for ; Fri, 11 Jan 2019 21:26:40 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="P+wRkfbn" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725535AbfAKV0j (ORCPT ); Fri, 11 Jan 2019 16:26:39 -0500 Received: from mail-pg1-f195.google.com ([209.85.215.195]:42792 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725355AbfAKV0j (ORCPT ); Fri, 11 Jan 2019 16:26:39 -0500 Received: by mail-pg1-f195.google.com with SMTP id d72so6813934pga.9 for ; Fri, 11 Jan 2019 13:26:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mime-version :content-disposition:user-agent; bh=M5uDjm/qFpDqrmMaOzoBCnY/VdI8LTeKehhGQHY3pyE=; b=P+wRkfbnbySj5Fb5P1PqQzJeJAHk6ZVj5Q24HkgAo+YVWDG/YL0vONWdnqG+8J8xnn 5TD8diuRpmdcs43gDQlKCyRBHNswKBHm/1Y7PHsbIuJd2n5ZTaH6hwQpluEiKfMEJjVY IUT+yQEYKpNoGIcYGvUiW6x7INd9A2WhMRDNo9INtniKy3pUDtuM73II2vb+zKrQj9vr b5/39ZAOdniHyndsGhAr3e8uOJ5dTbfdTDhxi1m3yeMH+Zb+T2HyYm8gtmGqtDJo/lpt s0R2JpO7NbAiA389WSU36CXv7fT0Cfi7+Rd++BCjdw3UvuGncAo8vEedIdZx9BGF8lDk btzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mime-version:content-disposition:user-agent; bh=M5uDjm/qFpDqrmMaOzoBCnY/VdI8LTeKehhGQHY3pyE=; b=QO/woe2xx7ExxPhQCk4w0v018vTSvSEZ1VISMl/pCWbLy58vENfsqCoDQ22ezzEE9g TrexD5aKIZVYzc6tLWj7XNdgvwaeqyae91sVH85UkAOm751amoswFZN1A2+NclOK4n8Q z2X5BOdFXioxXwo+fFtRfYJHfJ3r5CDJQdlRht2O5FXB+gP0bINBoFXxADGTFhhG2+av MpLB6rlqUy/bDwoSjTKRzqvxI08kk1bUAUMZgkzMdqPtB0nfk4eCLBT11oDbylgq5ipR 5HTrdgNEqOPyWQuAElTbi7z8C3895bm7PJI5L7numxiWXM3D7c7cxoNWNCx0DUVUaXSb B/Ug== X-Gm-Message-State: AJcUukdWiL1I7/h2vzNj9szPjTe9ECazhJVP21R23lqVc5wYm3xpCCqX 5cwLxtIp2b/LMsyObJ+B1R78wxUU X-Google-Smtp-Source: ALg8bN6WjKoCGjmc0tjeK5oGc1STwUnS5rFKxlP+U0bnjvZlE3J7R8pHTPlu4Xx8tZCKOiStBwR27A== X-Received: by 2002:a63:6704:: with SMTP id b4mr14928349pgc.100.1547241997848; Fri, 11 Jan 2019 13:26:37 -0800 (PST) Received: from localhost ([2600:1700:e321:62f0:329c:23ff:fee3:9d7c]) by smtp.gmail.com with ESMTPSA id s130sm152176982pgc.60.2019.01.11.13.26.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Jan 2019 13:26:36 -0800 (PST) Date: Fri, 11 Jan 2019 13:26:35 -0800 From: Guenter Roeck To: stable@vger.kernel.org Cc: "David S. Miller" , Greg Kroah-Hartman , Ben Hutchings Subject: boot stalls when booting sparc32 images on v3.16.y/v3.18.y in qemu Message-ID: <20190111212635.GA6399@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org Hi, I recently updated the sparc32 root file system in my testbed with one generated with buildroot. As a result, sparc32 images no longer boot with v3.16.y and v3.18.y. The system starts to come up, but stalls while starting syslog. However, v3.16 and v3.18 do boot. I bisected v3.18.y and ended up with commit 16c193364b4 ("sparc: Harden signal return frame checks.") as culprit; bisect results below. Reverting this commit fixes the problem for both v3.16.y and v3.18.y. Is it worth spending any time on this, or should I just stop testing sparc32 boot tests with v3.16.y and v3.18.y ? Thanks, Guenter --- # bad: [fa42fea0d8b49ba65b49a999331950d74827a52d] Linux 3.18.131 # good: [b2776bf7149bddd1f4161f14f79520f17fc1d71d] Linux 3.18 git bisect start 'HEAD' 'v3.18' # bad: [6e64ac0957e06a81b22f95f3509cc39b07735d3d] usb: increase ohci watchdog delay to 275 msec git bisect bad 6e64ac0957e06a81b22f95f3509cc39b07735d3d # good: [3e2003cccc9fb5f73a0d251dbb595f4c6e3a08bd] USB: usbfs: allow URBs to be reaped after disconnection git bisect good 3e2003cccc9fb5f73a0d251dbb595f4c6e3a08bd # good: [d6a1481f7411425041271c3084f3c2e399dc6526] ASoC: wm8958: Fix enum ctl accesses in a wrong type git bisect good d6a1481f7411425041271c3084f3c2e399dc6526 # good: [bc4b57be51fa419cd870398624c763b7afb91154] Btrfs: make btrfs_abort_transaction consider existence of new block groups git bisect good bc4b57be51fa419cd870398624c763b7afb91154 # bad: [b4d9416d6388fb450b397484e0ab85a154471723] of: fix memory leak related to safe_name() git bisect bad b4d9416d6388fb450b397484e0ab85a154471723 # good: [35807de76e1c2b7d15eea2f947983fcd043a2db0] clk: rockchip: free memory in error cases when registering clock branches git bisect good 35807de76e1c2b7d15eea2f947983fcd043a2db0 # bad: [cae1c6c281d8728e98f7e7a8950d6e64746b5bbc] netfilter: arp_tables: simplify translate_compat_table args git bisect bad cae1c6c281d8728e98f7e7a8950d6e64746b5bbc # good: [f02212dd4bd88826afccc36146177589eccb699b] tty: vt, return error when con_startup fails git bisect good f02212dd4bd88826afccc36146177589eccb699b # bad: [16c193364b4d6ff58c38c209e1e2b5c6fd674123] sparc: Harden signal return frame checks. git bisect bad 16c193364b4d6ff58c38c209e1e2b5c6fd674123 # good: [09600dd82044bf676e875d3bd9c904193c31c1f0] sfc: on MC reset, clear PIO buffer linkage in TXQs git bisect good 09600dd82044bf676e875d3bd9c904193c31c1f0 # good: [0396a871c4e3fbbaabb4f2632c1d388a04b68c84] sparc64: Fix numa node distance initialization git bisect good 0396a871c4e3fbbaabb4f2632c1d388a04b68c84 # good: [2a3e4b3cbee2c53c53e82b6f593160fb6583b24e] sparc/PCI: Fix for panic while enabling SR-IOV git bisect good 2a3e4b3cbee2c53c53e82b6f593160fb6583b24e # good: [705de0f20b1751f5816952486589543aaaa0bcbe] sparc64: Take ctx_alloc_lock properly in hugetlb_setup(). git bisect good 705de0f20b1751f5816952486589543aaaa0bcbe # first bad commit: [16c193364b4d6ff58c38c209e1e2b5c6fd674123] sparc: Harden signal return frame checks.