From: Daniel Vetter <daniel@ffwll.ch>
To: John Hubbard <jhubbard@nvidia.com>
Cc: lkp <lkp@intel.com>, "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-media@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Kees Cook" <keescook@chromium.org>,
"Dan Williams" <dan.j.williams@intel.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jérôme Glisse" <jglisse@redhat.com>, "Jan Kara" <jack@suse.cz>,
"Arnd Bergmann" <arnd@arndb.de>,
"David Hildenbrand" <david@redhat.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
lkp@lists.01.org
Subject: Re: [resource] 22b17dc667: Kernel panic - not syncing: Fatal exception
Date: Tue, 3 Nov 2020 11:10:35 +0100 [thread overview]
Message-ID: <20201103101035.GY401619@phenom.ffwll.local> (raw)
In-Reply-To: <1ec0dee9-e1bb-9cf1-a8c2-ad1e294c5acf@nvidia.com>
On Mon, Nov 02, 2020 at 10:15:40PM -0800, John Hubbard wrote:
> On 11/2/20 10:06 PM, lkp wrote:
> > Greeting,
> >
> > FYI, we noticed the following commit (built with gcc-9):
> >
> > commit: 22b17dc667d36418ccabb9c668c4b489185fb40a ("[PATCH v5 13/15] resource: Move devmem revoke code to resource framework")
> > url: https://github.com/0day-ci/linux/commits/Daniel-Vetter/follow_pfn-and-other-iomap-races/20201030-181112
> > base: git://linuxtv.org/media_tree.git master
> >
> > in testcase: fsmark
> > version: fsmark-x86_64-3.3-1_20201007
> > with following parameters:
> >
> > iterations: 1x
> > nr_threads: 1t
> > disk: 1BRD_48G
> > fs: f2fs
> > fs2: nfsv4
> > filesize: 4M
> > test_size: 40G
> > sync_method: NoSync
> > cpufreq_governor: performance
> > ucode: 0x5002f01
> >
> > test-description: The fsmark is a file system benchmark to test synchronous write workloads, for example, mail servers workload.
> > test-url: https://sourceforge.net/projects/fsmark/
> >
> >
> > on test machine: 192 threads Intel(R) Xeon(R) Platinum 9242 CPU @ 2.30GHz with 192G memory
> >
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> >
> >
>
> Yep, this is the same crash that I saw. And the .config also has
>
> # CONFIG_IO_STRICT_DEVMEM is not set
>
> so it all makes sense.
New version is on its way, I "just" need to setup ppc cross compiler for
the kvm part and figure out how to test the media side with the sketch
tfiga provided ...
-Daniel
>
>
> > If you fix the issue, kindly add following tag
> > Reported-by: kernel test robot <lkp@intel.com>
> >
> >
> > [ 28.644165] systemd[1]: RTC configured in localtime, applying delta of 0 minutes to system time.
> >
> > [ 28.699473] #PF: supervisor read access in kernel mode
> > [ 28.704611] #PF: error_code(0x0000) - not-present page
> > [ 28.709749] PGD 0 P4D 0
> > [ 28.712291] Oops: 0000 [#1] SMP NOPTI
> > [ 28.715956] CPU: 0 PID: 1 Comm: systemd Not tainted 5.10.0-rc1-00015-g22b17dc667d3 #1
> > [ 28.723793] RIP: 0010:do_dentry_open+0x1c9/0x360
> > [ 28.728410] Code: 84 82 01 00 00 81 ca 00 00 04 00 89 53 44 48 8b 83 f0 00 00 00 81 63 40 3f fc ff ff 48 8d bb 98 00 00 00 c7 43 34 00 00 00 00 <48> 8b 00 48 8b 70 30 e8 2b cb f4 ff f6 43 41 40 74 5a 48 8b 83 f0
> > [ 28.747157] RSP: 0018:ffffc9000006fcc8 EFLAGS: 00010206
> > [ 28.752380] RAX: 0000000000000000 RBX: ffff8881502ad400 RCX: 0000000000000000
> > [ 28.759506] RDX: 00000000000a201d RSI: ffffffff8284d260 RDI: ffff8881502ad498
> > [ 28.766639] RBP: ffff88a485a06490 R08: 0000000000000000 R09: ffffffff8284d260
> > [ 28.773769] R10: ffffc9000006fcc8 R11: 756c6176006d656d R12: 0000000000000000
> > [ 28.780895] R13: ffffffff8133ddc0 R14: ffff8881502ad410 R15: ffff8881502ad400
> > [ 28.788028] FS: 00007ff54afa1940(0000) GS:ffff888c4f600000(0000) knlGS:0000000000000000
> > [ 28.796113] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 28.801858] CR2: 0000000000000000 CR3: 0000000100120003 CR4: 00000000007706f0
> > [ 28.808983] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > [ 28.816114] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> > [ 28.823239] PKRU: 55555554
> > [ 28.825952] Call Trace:
> > [ 28.828412] path_openat+0xaa8/0x10a0
> > [ 28.832073] do_filp_open+0x91/0x100
> > [ 28.835653] ? acpi_os_wait_semaphore+0x48/0x80
> > [ 28.840186] ? __check_object_size+0x136/0x160
> > [ 28.844631] do_sys_openat2+0x20d/0x2e0
> > [ 28.848470] do_sys_open+0x44/0x80
> > [ 28.851878] do_syscall_64+0x33/0x40
> > [ 28.855457] entry_SYSCALL_64_after_hwframe+0x44/0xa9
> > [ 28.860509] RIP: 0033:0x7ff54c1521ae
> > [ 28.864086] Code: 25 00 00 41 00 3d 00 00 41 00 74 48 48 8d 05 59 65 0d 00 8b 00 85 c0 75 69 89 f2 b8 01 01 00 00 48 89 fe bf 9c ff ff ff 0f 05 <48> 3d 00 f0 ff ff 0f 87 a6 00 00 00 48 8b 4c 24 28 64 48 33 0c 25
> > [ 28.882833] RSP: 002b:00007ffd1c9586d0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
> > [ 28.890399] RAX: ffffffffffffffda RBX: 00007ffd1c9587d0 RCX: 00007ff54c1521ae
> > [ 28.897531] RDX: 0000000000080000 RSI: 00007ff54bfa0e5a RDI: 00000000ffffff9c
> > [ 28.904662] RBP: 00007ffd1c9587d8 R08: 000000000000021f R09: 000055f837cf4290
> > [ 28.911796] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000056dd9000
> > [ 28.918927] R13: 00000000ffffffff R14: 00007ffd1c9587d0 R15: 0000000000000002
> > [ 28.926060] Modules linked in: ip_tables
> > [ 28.929986] CR2: 0000000000000000
> > mDebian GNU/Linu
> > [ 28.933416] ---[ end trace 94e4f9aa3df66098 ]---
> > [ 28.939355] RIP: 0010:do_dentry_open+0x1c9/0x360
> > [ 28.943975] Code: 84 82 01 00 00 81 ca 00 00 04 00 89 53 44 48 8b 83 f0 00 00 00 81 63 40 3f fc ff ff 48 8d bb 98 00 00 00 c7 43 34 00 00 00 00 <48> 8b 00 48 8b 70 30 e8 2b cb f4 ff f6 43 41 40 74 5a 48 8b 83 f0
> > [ 28.962721] RSP: 0018:ffffc9000006fcc8 EFLAGS: 00010206
> > [ 28.967948] RAX: 0000000000000000 RBX: ffff8881502ad400 RCX: 0000000000000000
> > [ 28.975079] RDX: 00000000000a201d RSI: ffffffff8284d260 RDI: ffff8881502ad498
> > [ 28.982211] RBP: ffff88a485a06490 R08: 0000000000000000 R09: ffffffff8284d260
> > [ 28.989337] R10: ffffc9000006fcc8 R11: 756c6176006d656d R12: 0000000000000000
> > [ 28.996467] R13: ffffffff8133ddc0 R14: ffff8881502ad410 R15: ffff8881502ad400
> > [ 29.003592] FS: 00007ff54afa1940(0000) GS:ffff888c4f600000(0000) knlGS:0000000000000000
> > [ 29.011668] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 29.017409] CR2: 0000000000000000 CR3: 0000000100120003 CR4: 00000000007706f0
> > [ 29.024539] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > [ 29.031671] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> > [ 29.038804] PKRU: 55555554
> > [ 29.041508] Kernel panic - not syncing: Fatal exception
> > ACPI MEMORY or I/O RESET_REG.
> >
> >
> > To reproduce:
> >
> > git clone https://github.com/intel/lkp-tests.git
> > cd lkp-tests
> > bin/lkp install job.yaml # job file is attached in this email
> > bin/lkp run job.yaml
> >
> >
> >
> > Thanks,
> > oliver.sang@intel.com
> >
>
> thanks,
> --
> John Hubbard
> NVIDIA
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2020-11-03 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201103060649.GA30210@xsang-OptiPlex-9020>
2020-11-03 6:15 ` [resource] 22b17dc667: Kernel panic - not syncing: Fatal exception John Hubbard
2020-11-03 10:10 ` Daniel Vetter [this message]
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=20201103101035.GY401619@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=david@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jgg@ziepe.ca \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=keescook@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=rafael.j.wysocki@intel.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).