From mboxrd@z Thu Jan 1 00:00:00 1970 From: Embedded Engineer Subject: Re: Unstable Kernel behavior on an ARM based board Date: Mon, 4 Mar 2019 20:51:24 +0500 Message-ID: References: <20190302113651.zerdonykcvv5ex3e@shell.armlinux.org.uk> <20190302115729.zbowssfwf4j7jf22@shell.armlinux.org.uk> <20190302123907.qoe46qs6qmx7qnjs@shell.armlinux.org.uk> <453072a9-52e2-7591-750f-624ca27e0bbf@gmx.net> <20190304142546.GB24676@ulmo> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190304142546.GB24676@ulmo> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Thierry Reding Cc: linux-tegra@vger.kernel.org, Vladimir Murzin , linux-arm-kernel@lists.infradead.org, Jon Hunter List-Id: linux-tegra@vger.kernel.org Thanks a lot Thierry for considering this thread. On Mon, Mar 4, 2019 at 7:25 PM Thierry Reding wrote: > > Or it could indicate that something is > wrong when loading files from the root filesystem. When I used the downstream kernel and L4T filesystem, there was no problem regarding filesystem mounting. > All of the memory related configuration is part of a file called the > BCT. I think if you could provide that it would be very useful to have. Please find the link to our BCT: https://drive.google.com/open?id=1Az4nDIImCm14cnDSfHeBPlQYlYijGMrS > Also, it looks like you're using the Jetson TK1 device tree to boot, so > can I assume you haven't modified it at all? Yes, I modified the downstream kernel's dtb by generating new pinmux using Nvidia's dts generation tool but for upstream kernel I haven't modified any dts. > Other bits of information that would be good to know are how you are > generating the BCT and your boot images, what exactly you do to flash > the board and which release of L4T you use. We run Shmoo memory characterization tool and get cfg file from that. Then we convert that cfg to BCT (using mkbct command I guess). We were never able to flash the board using nvflash/flash.sh utility. So 1. We build and flash u-boot & BCT using tegra-uboot-flasher. 2. We build kernel using make separately using sources available on Nvidia download center. 3. We use apply_binaries.sh to copy tegra related files to sample file system downloaded from Nvidia download center. 4. We mount the emmc/SD-card using u-boot's ums command on our Linux host, and copy the whole filesystem, kernel and DTB to it. We are using R21.7 > Perhaps also try to run a recent linux-next just to exclude any issues > that may have been part of the 4.8.0-rc7 that you tested. Ok I will build kernel using linux-next and update here. Thanks again. 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.7 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED 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 973A3C43381 for ; Mon, 4 Mar 2019 15:52:02 +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 683A3206B8 for ; Mon, 4 Mar 2019 15:52:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="PFt7X4f3"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="J82pUS3N" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 683A3206B8 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-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:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=uYaxGoEp6tMb+131whuYPFvMAXZfQCUgk/Npp/gt1y4=; b=PFt7X4f3VEwWXk Cp/5kJBA1PaC8ter21Brf+HSMgpaqagvDBzqqT5eNpkl5sFRegoN6tWttydvD0QdcAGyBxe8DYRR9 PRFkt9ted2QsKhpnqkEoFP3+VJWpsn4u2Y17Lpa1Vpy08gFhqP1vgReWDmeyLFpxmBc4zTrjiXFuz AbG8JAF85zdX8BaZrJHSKY87IoGNpfnA7NMAWohOoQCsAJO6Y2ieniSfZsD/145VSQICNCDBi9dh1 w08bQ3xC3Ft3zQvlM3pA0rNPAnkYkj0Wh1YSRFxTiRVIjq++nqanMpr0fxjJW5mSlkyQtVvLckztC 1GeTfgm/HgWglNSzjduA==; 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 1h0psl-0008Nr-Er; Mon, 04 Mar 2019 15:51:59 +0000 Received: from mail-io1-xd2f.google.com ([2607:f8b0:4864:20::d2f]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1h0psh-0008N6-T3 for linux-arm-kernel@lists.infradead.org; Mon, 04 Mar 2019 15:51:57 +0000 Received: by mail-io1-xd2f.google.com with SMTP id p18so4313533ioh.5 for ; Mon, 04 Mar 2019 07:51:55 -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=fYpKHBHQxmJzH0EoAtIFg8PYb2Tq77RY7vPj6f2FTGM=; b=J82pUS3NI+i8XGmDAnFVRwVzgud57RwrvL0q3fKRCpECSAn4M8OtPiLBEjzVJRbv8z M2xfHqdW4a8Fbvf1jmRfurY2tCnCKqpuO0PcYac4i25uBbbw4F8J9YtHdBX3T8W8uCA9 BTtMG6ArGa03apGu0Ve51ivXF6Cb6QeChHE6XZn5V0mabUwtEjfwIrccmc4uhfQJN/bk WtnXegSo+d0W6SNt8VfzhifUa7x2Zu+Z0+vO8SeYdICV/EJNHNiGYVqHyDrcFZu/BHbp vpsLFQQy5cTV4LC+zNExLRZ6N5vvAq0qFUbP81MCYurD+kgycb8BOFvVdXgpVmaTyTtz JaWg== 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=fYpKHBHQxmJzH0EoAtIFg8PYb2Tq77RY7vPj6f2FTGM=; b=DWD49ncOFpb6N3eSR6U/SSl4hhDB/GWzpLN30ODCPKX0iUPnqZ7yaVi4DUFWmuSLDu N9SpMsTlzHxDVFfS8g5tHZevMJapVRqOsMQ6jmAzd7c9FLw7tmOHwgVQPShMugTlcS87 +mu3mv+fdxwHnXxnOTS4Y10k7+Q3rwGDSClzIazsuuFpopnZ2BLIwecwb38DTkGEPT1l 700XfJrkgn1SmLDZoacfRYwgITSiwzhAJ6tBNq3s8z0lBoE645I5/WSsM6ctOHkj9uJV 4YRFCbyLTZODZTgd2AitQUGZV+yN/y3oslMYQAptQKht3z7V36bM25q9WvbJB2fd/e5T I/JQ== X-Gm-Message-State: APjAAAU77pfkdCtkubFxrRQ9+EyGr3CHr4gVRLc41PO2cE4EH2CEdF4j sNHX442IZTiXtXIPpi5E2NhwHftlCzdycTC6uqdyzV7iddY= X-Google-Smtp-Source: APXvYqzXkJOO9vPG5HcZmja6ohRsayH2BCWYqv7zApAV60E4cfX/g3TqHx7ZAE3Daiopf3bY45HNhovFsscoQV8dUV4= X-Received: by 2002:a5e:9611:: with SMTP id a17mr9732286ioq.2.1551714714671; Mon, 04 Mar 2019 07:51:54 -0800 (PST) MIME-Version: 1.0 References: <20190302113651.zerdonykcvv5ex3e@shell.armlinux.org.uk> <20190302115729.zbowssfwf4j7jf22@shell.armlinux.org.uk> <20190302123907.qoe46qs6qmx7qnjs@shell.armlinux.org.uk> <453072a9-52e2-7591-750f-624ca27e0bbf@gmx.net> <20190304142546.GB24676@ulmo> In-Reply-To: <20190304142546.GB24676@ulmo> From: Embedded Engineer Date: Mon, 4 Mar 2019 20:51:24 +0500 Message-ID: Subject: Re: Unstable Kernel behavior on an ARM based board To: Thierry Reding X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190304_075155_935654_CA2FEF34 X-CRM114-Status: GOOD ( 14.57 ) 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: linux-tegra@vger.kernel.org, Vladimir Murzin , linux-arm-kernel@lists.infradead.org, Jon Hunter Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Thanks a lot Thierry for considering this thread. On Mon, Mar 4, 2019 at 7:25 PM Thierry Reding wrote: > > Or it could indicate that something is > wrong when loading files from the root filesystem. When I used the downstream kernel and L4T filesystem, there was no problem regarding filesystem mounting. > All of the memory related configuration is part of a file called the > BCT. I think if you could provide that it would be very useful to have. Please find the link to our BCT: https://drive.google.com/open?id=1Az4nDIImCm14cnDSfHeBPlQYlYijGMrS > Also, it looks like you're using the Jetson TK1 device tree to boot, so > can I assume you haven't modified it at all? Yes, I modified the downstream kernel's dtb by generating new pinmux using Nvidia's dts generation tool but for upstream kernel I haven't modified any dts. > Other bits of information that would be good to know are how you are > generating the BCT and your boot images, what exactly you do to flash > the board and which release of L4T you use. We run Shmoo memory characterization tool and get cfg file from that. Then we convert that cfg to BCT (using mkbct command I guess). We were never able to flash the board using nvflash/flash.sh utility. So 1. We build and flash u-boot & BCT using tegra-uboot-flasher. 2. We build kernel using make separately using sources available on Nvidia download center. 3. We use apply_binaries.sh to copy tegra related files to sample file system downloaded from Nvidia download center. 4. We mount the emmc/SD-card using u-boot's ums command on our Linux host, and copy the whole filesystem, kernel and DTB to it. We are using R21.7 > Perhaps also try to run a recent linux-next just to exclude any issues > that may have been part of the 4.8.0-rc7 that you tested. Ok I will build kernel using linux-next and update here. Thanks again. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel