From mboxrd@z Thu Jan 1 00:00:00 1970 From: Embedded Engineer Subject: Re: Unstable Kernel behavior on an ARM based board Date: Tue, 5 Mar 2019 20:44:52 +0500 Message-ID: References: <20190305112226.rhbl3dwopmip45ja@shell.armlinux.org.uk> <20190305115730.GE26369@ulmo> <20190305132350.pzfmz4yvh6ujgotn@shell.armlinux.org.uk> <20190305142351.ktciqkj5kycdwilr@shell.armlinux.org.uk> <20190305145853.qsmcaop4ths2jgrl@shell.armlinux.org.uk> <20190305153111.frvgnoba646uf5ar@shell.armlinux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190305153111.frvgnoba646uf5ar@shell.armlinux.org.uk> 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: Russell King - ARM Linux admin Cc: Andrew Lunn , Vladimir Murzin , Jon Hunter , Thierry Reding , linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-Id: linux-tegra@vger.kernel.org On Tue, Mar 5, 2019 at 8:31 PM Russell King - ARM Linux admin wrote: > > Right now, I don't have anything further to add beyond what I've > already suggested as causes - this is *definitely* memory corruption > either by something else writing to memory, by the CPU writes not > properly being stored in RAM or the CPU not being able to reliably > read data back from RAM. Thanks alot for your help, I will try updating u-boot to newer version so that we can eliminate the chance that u-boot has left something on in undesired state. 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 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 B7985C43381 for ; Tue, 5 Mar 2019 15:45:28 +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 8064F20684 for ; Tue, 5 Mar 2019 15:45:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="P9kJv7tT"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="U5EsjNFg" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8064F20684 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=SiRmgXsJnW9AK3jlT2Knbg6jKc/FiPHiXvNJVKLhuc8=; b=P9kJv7tTaW6ECh uSdwHLqMVfp37w78JQnpbSfWoqZzZ1jqGZsvfKgXxJQAMHPR4AMbwuSotsK+fYnK9NiuUGVCjVZ+h 1kXcDKYIXXLeuA8VU9HpCFqgSlO6vRZGYbp+/9+X/2bOK7aKv/TEQUaaTfO/adPR26TFWjKhv9CeP Rm4IAM2rxNgQTvCWLPtvyFR7LszdvpPpM29ZtzTYLiIriWHtgOc4ScIgsxDroAkS3uJlvkJoDfKm0 A8F/pNXuXjHtRR6YTg8Vna2ZvFHB3EeuDNrZ5ZKY/iv+kcN95IUCGGVonf/lJIfmirx9FvEQjPWYY gq8ea/Ott1dBmXKlWfMw==; 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 1h1CFw-0004IA-LG; Tue, 05 Mar 2019 15:45:24 +0000 Received: from mail-io1-xd34.google.com ([2607:f8b0:4864:20::d34]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1h1CFu-0004Ht-9j for linux-arm-kernel@lists.infradead.org; Tue, 05 Mar 2019 15:45:23 +0000 Received: by mail-io1-xd34.google.com with SMTP id x4so7420495ion.2 for ; Tue, 05 Mar 2019 07:45:22 -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=qW8P1Vs9b3qv2JXMNYtu1x+LgDP8uUHv/QahgeTnfDo=; b=U5EsjNFguT5ZE6ivffvqgpvfnvcXNvPHeLSzIG6zhcsSq8dBoshdzi78LgJ8pCgeRY 1/VZJltEF4TvHi5Whxxr11UlOfAlXPuLR6C/Cz829ysdwmS5G5gcPvxcuL4HN/VHvUoc CTGWXZoIlgIzIeACCfYiMkKvQ7B+DEmDM8PwBz7Zb15I2lVWK8d0q4Ssf/h22bRcQMxj RPhGfMdwbPE+Q9Rg0wjmPhho5zAOW/OnvTiHtsoRYJs9qWG3ROZaHv5aTstPJi8UP8Ak 6pBzgBRmkxFiRC0+kAxDnAWx58HlIoiPM7IFV6MgRcYyTi1giJsFKUdHxL0D9L7a129n h2HA== 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=qW8P1Vs9b3qv2JXMNYtu1x+LgDP8uUHv/QahgeTnfDo=; b=HvNjyJ/smYbKrMwrGDfDWBXJdmsNh1aDBa3Pk5rkXz3i6AMBGgS2VGOE28CYwQGkOD ORxr22YX6FtfXgE7Wcip6R704in5F4d0lbOSROw2LqqtMv4ig9AP16fZRR+Uxq04tVUs dvCo/R0wEATiJWBhirmGRv1CN0EePHIUwXIKVTe9E9DQBc2YC2y/7TBdQzQZHl28C9Fr VEJ+EP3VRYeWdVOpUxhjwApmeHKYD17GUtjc0Lq2H93JADPxMr8Vz83gqba9m8CywUPU OPOCzWNAUTPEtZ3/LJWqqxGXn0nrO26B/Qpys9JHcb3I0drMdjJbGvnCQ9XZy90BqbuK a6KA== X-Gm-Message-State: APjAAAW5ZT9UB6Y7ZWe/7jVZLjAsSW1iOYdcjsE6z1ktWNoiYbm5Qiu3 YjJJRPZe+p0aO0Hih3mtdG5AGJXdTTyEvo9kZ4g= X-Google-Smtp-Source: APXvYqzECY45zu0UyF1z/rYDAzeogjb/tkBxB5CCSD7nPlrzTaabkk7Y3Is0Z+cZL7l8U064vMhS5Hz0aT7OGP/Dy2U= X-Received: by 2002:a5e:9611:: with SMTP id a17mr407236ioq.2.1551800721303; Tue, 05 Mar 2019 07:45:21 -0800 (PST) MIME-Version: 1.0 References: <20190305112226.rhbl3dwopmip45ja@shell.armlinux.org.uk> <20190305115730.GE26369@ulmo> <20190305132350.pzfmz4yvh6ujgotn@shell.armlinux.org.uk> <20190305142351.ktciqkj5kycdwilr@shell.armlinux.org.uk> <20190305145853.qsmcaop4ths2jgrl@shell.armlinux.org.uk> <20190305153111.frvgnoba646uf5ar@shell.armlinux.org.uk> In-Reply-To: <20190305153111.frvgnoba646uf5ar@shell.armlinux.org.uk> From: Embedded Engineer Date: Tue, 5 Mar 2019 20:44:52 +0500 Message-ID: Subject: Re: Unstable Kernel behavior on an ARM based board To: Russell King - ARM Linux admin X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190305_074522_342373_9DA94440 X-CRM114-Status: UNSURE ( 8.74 ) X-CRM114-Notice: Please train this message. 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: Andrew Lunn , Vladimir Murzin , Jon Hunter , Thierry Reding , linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org 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 On Tue, Mar 5, 2019 at 8:31 PM Russell King - ARM Linux admin wrote: > > Right now, I don't have anything further to add beyond what I've > already suggested as causes - this is *definitely* memory corruption > either by something else writing to memory, by the CPU writes not > properly being stored in RAM or the CPU not being able to reliably > read data back from RAM. Thanks alot for your help, I will try updating u-boot to newer version so that we can eliminate the chance that u-boot has left something on in undesired state. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel