From: James Morse <james.morse@arm.com> To: Qu Wenruo <quwenruo.btrfs@gmx.com> Cc: Matthew Wilcox <willy@infradead.org>, Linux FS Devel <linux-fsdevel@vger.kernel.org>, Ext4 <linux-ext4@vger.kernel.org>, linux-arm-kernel@lists.infradead.org Subject: Re: [aarch64] Kernel crash on v5.1-rc5, __arch_copy_from_user+0x1bc/0x240 Date: Wed, 24 Apr 2019 14:50:06 +0100 [thread overview] Message-ID: <98fad1eb-b033-3c31-9100-bad672b4cfe0@arm.com> (raw) In-Reply-To: <09135f7a-874e-5ea0-164a-306ca3db2799@gmx.com> Hi Qu, On 22/04/2019 02:14, Qu Wenruo wrote: > On 2019/4/21 下午9:28, Matthew Wilcox wrote: >> On Sun, Apr 21, 2019 at 05:12:50PM +0800, Qu Wenruo wrote: >>> On 2019/4/21 下午4:20, Qu Wenruo wrote: >>>> Just hit one crash on v5.1-rc5 kernel, on ext4 filesystem. >>> >>> Well, also hit the same one in v5.0.8 kernel. >>> >>> Exact the same backtrace. >>> >>> Really not sure which part is to blame, ARM or ext4? >> >> You probably have faulty hardware: > I tried memtester, and kernel also crashed. > > Maybe it's really faulty memory or I'm using wrong memory speed. As another option: there may be no memory at this physical address. If your board only has 1G of memory, but the bootloader/DT is reporting 2G, you could see SError like this (assuming this is the first access to that page). SError can be a fatal interrupt from the hardware, its also how the CPU tells us about 'asynchronous external abort'. In this case it could be an attempt to access a physical address where nothing exists. Thanks, James
WARNING: multiple messages have this Message-ID (diff)
From: James Morse <james.morse@arm.com> To: Qu Wenruo <quwenruo.btrfs@gmx.com> Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>, Ext4 <linux-ext4@vger.kernel.org>, linux-arm-kernel@lists.infradead.org, Matthew Wilcox <willy@infradead.org> Subject: Re: [aarch64] Kernel crash on v5.1-rc5, __arch_copy_from_user+0x1bc/0x240 Date: Wed, 24 Apr 2019 14:50:06 +0100 [thread overview] Message-ID: <98fad1eb-b033-3c31-9100-bad672b4cfe0@arm.com> (raw) In-Reply-To: <09135f7a-874e-5ea0-164a-306ca3db2799@gmx.com> Hi Qu, On 22/04/2019 02:14, Qu Wenruo wrote: > On 2019/4/21 下午9:28, Matthew Wilcox wrote: >> On Sun, Apr 21, 2019 at 05:12:50PM +0800, Qu Wenruo wrote: >>> On 2019/4/21 下午4:20, Qu Wenruo wrote: >>>> Just hit one crash on v5.1-rc5 kernel, on ext4 filesystem. >>> >>> Well, also hit the same one in v5.0.8 kernel. >>> >>> Exact the same backtrace. >>> >>> Really not sure which part is to blame, ARM or ext4? >> >> You probably have faulty hardware: > I tried memtester, and kernel also crashed. > > Maybe it's really faulty memory or I'm using wrong memory speed. As another option: there may be no memory at this physical address. If your board only has 1G of memory, but the bootloader/DT is reporting 2G, you could see SError like this (assuming this is the first access to that page). SError can be a fatal interrupt from the hardware, its also how the CPU tells us about 'asynchronous external abort'. In this case it could be an attempt to access a physical address where nothing exists. Thanks, James _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-24 13:50 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-21 8:20 [aarch64] Kernel crash on v5.1-rc5, __arch_copy_from_user+0x1bc/0x240 Qu Wenruo 2019-04-21 8:20 ` Qu Wenruo 2019-04-21 9:12 ` Qu Wenruo 2019-04-21 9:12 ` Qu Wenruo 2019-04-21 13:28 ` Matthew Wilcox 2019-04-21 13:28 ` Matthew Wilcox 2019-04-22 1:14 ` Qu Wenruo 2019-04-22 1:14 ` Qu Wenruo 2019-04-24 13:50 ` James Morse [this message] 2019-04-24 13:50 ` James Morse 2019-04-24 13:54 ` Qu Wenruo 2019-04-24 13:54 ` Qu Wenruo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=98fad1eb-b033-3c31-9100-bad672b4cfe0@arm.com \ --to=james.morse@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=quwenruo.btrfs@gmx.com \ --cc=willy@infradead.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.