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=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 5129AC3F2CE for ; Sat, 29 Feb 2020 09:57: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 0E03620661 for ; Sat, 29 Feb 2020 09:57: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="AzoKyBSW"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=armlinux.org.uk header.i=@armlinux.org.uk header.b="fsy+dcC6" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0E03620661 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=fVch6jJq2lYjc1JIcnZ7GRNK+nRzQyMDH++yFNdcdpU=; b=AzoKyBSWDGV4l2 EMjl639HlOlLvV/oAQIu89tyfd053lrm/x9PLQErjmAziqreLhmnPiFOXAjPndVxg0DP7Ap7FCdkE 34Fr57Wv7rSk2hnLPbYEf4GdsvXipr3w0el7TfUMxO+AJOAsaLBNSrwsA3vN6x+QmbsOhuT5qSz0H fsDwWUnQx0hPUbXvQHllGAfME534QzsikrIZrG7cs7OCdakaL4tuI8DWCMmSS5aXCPTLIjD3Kd+eK K/ccmGfvClURR8y5obbOtaH9h0Fb/akcqxY7Asn5UFT7lcMTCR9T/2b69DhDyVzcXbZyCGGefhZmp HTsnFkEfux5C+1m4rGSg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1j7yrU-0001Y5-Gr; Sat, 29 Feb 2020 09:56:44 +0000 Received: from [2001:4d48:ad52:3201:214:fdff:fe10:1be6] (helo=pandora.armlinux.org.uk) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1j7yrP-0001Wk-6G for linux-arm-kernel@lists.infradead.org; Sat, 29 Feb 2020 09:56:41 +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-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding: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=LAjJNSR/XcdsDm90VwMAHSUY7bpYfoUCar8rZ8PpWp8=; b=fsy+dcC6pABNqsXjDt94Rnrsl FEN3b5zZS1IMaDMYRN4MXviaoDbUvdTjG1fza6StniMkGtFw71zPtK1VGOlP4yfTPWKk1TIlfhyRG RpxZ0ShQuhVapiGV0q/lv8bV2FvRj6qd+dFFB1oKpB1kOjB81HurWaIxIHKwRShtzSwUolgVUXDx4 EE4l4/7ELOxxYLLKr52/9UeWvYF7KRbpfHO4md/UBVB5sTRkkvbJ6+6kixaeC1A8Bw4fhRfkhGAgb S2Q44pl5zuSiIkWj5FZAJAyUwwnpuzTCmgycTils3Sdjcjvc+yoIMua7IpPUdGoxKp72Iiy25SO8u 1Nem8qmIA==; Received: from shell.armlinux.org.uk ([2001:4d48:ad52:3201:5054:ff:fe00:4ec]:46796) by pandora.armlinux.org.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1j7yqr-0000nL-NH; Sat, 29 Feb 2020 09:56:06 +0000 Received: from linux by shell.armlinux.org.uk with local (Exim 4.92) (envelope-from ) id 1j7yqc-0002s4-P3; Sat, 29 Feb 2020 09:55:50 +0000 Date: Sat, 29 Feb 2020 09:55:50 +0000 From: Russell King - ARM Linux admin To: Olof Johansson , Jon Nettleton Subject: Re: [PATCHv9 00/12] PCI: Recode Mobiveil driver and add PCIe Gen4 driver for NXP Layerscape SoCs Message-ID: <20200229095550.GX25745@shell.armlinux.org.uk> References: <20191120034451.30102-1-Zhiqiang.Hou@nxp.com> <20200110153347.GA29372@e121166-lin.cambridge.arm.com> <20200210152257.GD25745@shell.armlinux.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200210152257.GD25745@shell.armlinux.org.uk> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200229_015639_386297_7DA8A4FA X-CRM114-Status: GOOD ( 22.44 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "mark.rutland@arm.com" , Lorenzo Pieralisi , "arnd@arndb.de" , "m.karthikeyan@mobiveil.co.in" , "linux-pci@vger.kernel.org" , "Z.q. Hou" , "l.subrahmanya@mobiveil.co.in" , "will.deacon@arm.com" , "linux-kernel@vger.kernel.org" , Leo Li , "M.h. Lian" , Xiaowei Bao , "catalin.marinas@arm.com" , "bhelgaas@google.com" , "andrew.murray@arm.com" , "shawnguo@kernel.org" , Mingkai Hu , "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 Mon, Feb 10, 2020 at 03:22:57PM +0000, Russell King - ARM Linux admin wrote: > On Mon, Feb 10, 2020 at 04:12:30PM +0100, Olof Johansson wrote: > > On Thu, Feb 6, 2020 at 11:57 AM Z.q. Hou wrote: > > > > > > Hi Olof, > > > > > > Thanks a lot for your comments! > > > And sorry for my delay respond! > > > > Actually, they apply with only minor conflicts on top of current -next. > > > > Bjorn, any chance we can get you to pick these up pretty soon? They > > enable full use of a promising ARM developer system, the SolidRun > > HoneyComb, and would be quite valuable for me and others to be able to > > use with mainline or -next without any additional patches applied -- > > which this patchset achieves. > > > > I know there are pending revisions based on feedback. I'll leave it up > > to you and others to determine if that can be done with incremental > > patches on top, or if it should be fixed before the initial patchset > > is applied. But all in all, it's holding up adaption by me and surely > > others of a very interesting platform -- I'm looking to replace my > > aging MacchiatoBin with one of these and would need PCIe/NVMe to work > > before I do. > > If you're going to be using NVMe, make sure you use a power-fail safe > version; I've already had one instance where ext4 failed to mount > because of a corrupted journal using an XPG SX8200 after the Honeycomb > Serror'd, and then I powered it down after a few hours before later > booting it back up. > > EXT4-fs (nvme0n1p2): INFO: recovery required on readonly filesystem > EXT4-fs (nvme0n1p2): write access will be enabled during recovery > JBD2: journal transaction 80849 on nvme0n1p2-8 is corrupt. > EXT4-fs (nvme0n1p2): error loading journal ... and last night, I just got more ext4fs errors on the NVMe, without any unclean power cycles: [73729.556544] EXT4-fs error (device nvme0n1p2): ext4_lookup:1700: inode #917524: comm rm: iget: checksum invalid [73729.565354] Aborting journal on device nvme0n1p2-8. [73729.568995] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [73729.569077] EXT4-fs error (device nvme0n1p2): ext4_journal_check_start:61: Detected aborted journal [73729.573741] EXT4-fs error (device nvme0n1p2): ext4_lookup:1700: inode #917524: comm rm: iget: checksum invalid [73729.593330] EXT4-fs error (device nvme0n1p2): ext4_lookup:1700: inode #917524: comm mv: iget: checksum invalid The affected file is /var/backups/dpkg.status.6.gz It was cleanly shut down and powered off on the 22nd February, booted yesterday morning followed by another reboot a few minutes later. What worries me is the fact that corruption has happened - and if that happens to a file rather than an inode, it will likely go unnoticed for a considerably longer time. I think I'm getting to the point of deciding NVMe or the LX2160A to be just too unreliable for serious use. I hadn't noticed any issues when using the rootfs on the eMMC, so it suggests either the NVMe is unreliable, or there's a problem with PCIe on this platform (which we kind of know about with Jon's GPU rendering issues.) -- 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