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.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED, USER_AGENT_NEOMUTT 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 7D526C43381 for ; Sat, 2 Mar 2019 12:39:29 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 39A0120836 for ; Sat, 2 Mar 2019 12:39:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="hKXjcVo/"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=armlinux.org.uk header.i=@armlinux.org.uk header.b="REmrD1Ob" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 39A0120836 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=armlinux.org.uk Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=/qYFQe3WwBNJAHrsEbvJfzbLJYS4jJI1F1l9cYvnd8Q=; b=hKXjcVo/+Ojieu j1SZo27KPthQp5c2XF4VwHfal7tCZ2E8s2mXCP+3wETHdMMC0hwxjtxNO4Gt0GXlkDRrGJMq48I6s TqEP4CzasBf3jQyb0K9v8qYjkbubmRYFLQe0U+dNGw3qZpjaynpUP53oJF1Y/j6XDtb7C8V4jDsU3 czsc5j+RIvNCAJHqRicd7+QAnxeVTFY4iP2LKo/e2EohW+MAOVUq6KnEFzfYmQzNUdIZh9WZ4zb4z MNtpZDekhvex+M8wWJKhngnUq3i8hESs+YsW7kqGIjKxvy3VxkgQXJ482Qn3MqGMMuBZmINEeYWC2 K2+HCIFdZenjzKDLv9ag==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1h03vE-0002WK-7U; Sat, 02 Mar 2019 12:39:20 +0000 Received: from pandora.armlinux.org.uk ([2001:4d48:ad52:3201:214:fdff:fe10:1be6]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1h03v9-0002Vj-It for linux-arm-kernel@lists.infradead.org; Sat, 02 Mar 2019 12:39:17 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=H77Vw2Xj/XEkFwW0E7kHPCMxinkyI4+hdvffp0WZUUc=; b=REmrD1Ob+GsucFJ3V1h9BRdVu ZJPXQkVTyXfQUrypc3u6KFlQqEv71gdnGEI4/yzqCxOcvmxwqGdQ1KcTWlcVQJ76jR8LviwKcK1Qd TD+FXTESbFqEa+iqM0LTplX++wzvXxLjqbcE062zqAYJWcNIAL20tONbnAL3RnJnvmKjShZ164TwW s8E7mN0y25jV1qwUGUOYqk4ZXckhClWNKEAX2U9k+TUCVbdylBM39bS0LdpI95UsxkQFU69fpVjUu OdKMeKAy69NyIwwsdEF6/UOykp3THmAnDVgBreyVp7qmYtN177OpVDoM4fuTQI6LMRZhT0EnVscg9 46fiPaBhg==; Received: from shell.armlinux.org.uk ([2001:4d48:ad52:3201:5054:ff:fe00:4ec]:54908) by pandora.armlinux.org.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1h03v3-000633-JL; Sat, 02 Mar 2019 12:39:09 +0000 Received: from linux by shell.armlinux.org.uk with local (Exim 4.89) (envelope-from ) id 1h03v2-0000eq-01; Sat, 02 Mar 2019 12:39:08 +0000 Date: Sat, 2 Mar 2019 12:39:07 +0000 From: Russell King - ARM Linux admin To: Embedded Engineer Subject: Re: Unstable Kernel behavior on an ARM based board Message-ID: <20190302123907.qoe46qs6qmx7qnjs@shell.armlinux.org.uk> References: <20190302110112.GA13405@1wt.eu> <20190302113651.zerdonykcvv5ex3e@shell.armlinux.org.uk> <20190302115729.zbowssfwf4j7jf22@shell.armlinux.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190302_043915_625767_F0849FBD X-CRM114-Status: GOOD ( 13.53 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Willy Tarreau , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sat, Mar 02, 2019 at 05:20:53PM +0500, Embedded Engineer wrote: > On Sat, Mar 2, 2019 at 4:57 PM Russell King - ARM Linux admin > wrote: > > > > Okay, please try enabling DEBUG_LL, SERIAL_EARLYCON and select the > > correct serial port. Then arrange for u-boot to pass "earlycon" in > > addition to your other kernel arguments (shown in the "append" line > > above.) > = > That's great :). I didn't make any change to kernel config as > DEBUG_LL, SERIAL_EARLYCON were already enabled. Just added 'earlycon' > to kernel arguments and boom, it booted without any crash. However > there were some errors mounting the rootfs. Please find below link to > complete boot logs: > = > https://pastebin.com/7CfN6wLQ I think you're lucky it got that far: tegra-ehci 7d008000.usb: dma_pool_alloc ehci_qtd, f08de000 (corrupted) 00000000: 60 00 00 00 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 =A0`.............= .. 00000010: a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 =A0..............= .. 00000020: 40 02 00 00 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 =A0@.............= .. 00000030: a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 =A0..............= .. 00000040: 60 03 00 00 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 =A0`.............= .. 00000050: a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 a7 =A0..............= .. There is a definite pattern to that corruption - first 32-bit word in every 32-bytes - I suspect the first 32-bit transfer into the cache ends up being corrupted. IMHO, this points to RAM timing or wiring issues. I don't know much about Tegra, but could it be a too-old u-boot (it reports that it's 2014, but apparently extlinux support was only merged in 2017...)? As you've said that these are a new board design, it could also be a design error with the RAM wiring. I suspect at this point you may be better to wait for those who know Tegra to reply - Thierry Reding or Jonathan Hunter. -- = RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps = up According to speedtest.net: 11.9Mbps down 500kbps up _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel