From: Matthew Wilcox <willy@infradead.org>
To: Uwe Sauter <uwe.sauter.de@gmail.com>
Cc: almaz.alexandrovich@paragon-software.com, ntfs3@lists.linux.dev,
linux-fsdevel@vger.kernel.org
Subject: Re: Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
Date: Fri, 19 Nov 2021 13:13:06 +0000 [thread overview]
Message-ID: <YZei4gn1zgIc32Ii@casper.infradead.org> (raw)
In-Reply-To: <aea2a926-8ce6-fcb0-cd60-03202c30cca1@gmail.com>
On Fri, Nov 19, 2021 at 08:48:11AM +0100, Uwe Sauter wrote:
> [ 1132.645038] BUG: unable to handle page fault for address: 0000000000400000
> [ 1132.645045] #PF: supervisor instruction fetch in kernel mode
> [ 1132.645047] #PF: error_code(0x0010) - not-present page
> [ 1132.645050] PGD 0 P4D 0
> [ 1132.645053] Oops: 0010 [#1] PREEMPT SMP PTI
> [ 1132.645057] CPU: 7 PID: 429941 Comm: rsync Tainted: P OE
> 5.15.2-arch1-1 #1 e3bfbeb633edc604ba956e06f24d5659e31c294f
> [ 1132.645061] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C226 WS, BIOS P3.40 06/25/2018
> [ 1132.645063] RIP: 0010:0x400000
Your computer was trying to execute instructions at 0x400000. This
smells very much like a single bit flip; ie there was a function
pointer which should have been NULL, but actually had one bit flip
and so the CPU jumped to somewhere that doesn't have any memory
backing it.
Can you run memtest86, or whatever the current flavour of memory testing
software is?
next prev parent reply other threads:[~2021-11-19 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 7:48 Bug using new ntfs3 file system driver (5.15.2 on Arch Linux) Uwe Sauter
2021-11-19 13:13 ` Matthew Wilcox [this message]
2021-11-19 14:19 ` Uwe Sauter
-- strict thread matches above, loose matches on Subject: below --
2021-11-27 14:13 Mohan R
2021-11-27 14:50 ` Matthew Wilcox
2021-12-28 21:00 ` August Wikerfors
2021-12-29 1:13 ` Matthew Wilcox
2022-01-03 15:20 ` Jan Kara
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=YZei4gn1zgIc32Ii@casper.infradead.org \
--to=willy@infradead.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=uwe.sauter.de@gmail.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).