From: Pavel Machek <pavel@ucw.cz>
To: Harald Dunkel <harald.dunkel@aixigo.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 4.20.1: BUG: unable to handle kernel paging request at 0000100000000008
Date: Thu, 7 Mar 2019 00:10:27 +0100 [thread overview]
Message-ID: <20190306231027.GF7915@amd> (raw)
In-Reply-To: <4b1cdcac-e6ec-09ca-558a-1ff391f13e52@aixigo.de>
[-- Attachment #1: Type: text/plain, Size: 5288 bytes --]
On Tue 2019-01-22 11:15:39, Harald Dunkel wrote:
> Is this the wrong list to report this problem? I haven't found a
> "mem" mailing list on vger.
Right list, ugly looking problem. How reproducible is it?
You may want to look at MAINTAINERS file, cc x86 and memory management
people...?
Pavel
> Regards
> Harri
> -------------------------------------------------------------------------
> On 1/14/19 2:01 PM, Harald Dunkel wrote:
> >Hi folks,
> >
> >my server stumbled over this last night:
> >
> >Jan 13 19:03:15 sylvester kernel: [272280.820190] BUG: unable to handle kernel paging request at 0000100000000008
> >Jan 13 19:03:15 sylvester kernel: [272280.820198] PGD 0 P4D 0
> >Jan 13 19:03:15 sylvester kernel: [272280.820203] Oops: 0000 [#1] PREEMPT SMP PTI
> >Jan 13 19:03:15 sylvester kernel: [272280.820207] CPU: 3 PID: 46 Comm: kswapd0 Not tainted 4.20.1-raw #1
> >Jan 13 19:03:15 sylvester kernel: [272280.820211] Hardware name: /DH67CF, BIOS BLH6710H.86A.0125.2011.0705.1517 07/05/2011
> >Jan 13 19:03:15 sylvester kernel: [272280.820219] RIP: 0010:find_get_entries+0xed/0x240
> >Jan 13 19:03:15 sylvester kernel: [272280.820223] Code: 4e 4e 00 48 89 c2 48 85 d2 0f 84 91 00 00 00 48 81 fa 02 04 00 00 0f 84 a3 00 00 00 48 81 fa 06 04 00 00 74 ca f6
> >Jan 13 19:03:15 sylvester kernel: [272280.820230] RSP: 0018:ffffc90000fdb9c8 EFLAGS: 00010246
> >Jan 13 19:03:15 sylvester kernel: [272280.820234] RAX: 0000100000000000 RBX: 000000000000000f RCX: 0000000000000000
> >Jan 13 19:03:15 sylvester kernel: [272280.820238] RDX: 0000100000000000 RSI: 0000000000000680 RDI: ffffffffffffffc0
> >Jan 13 19:03:15 sylvester kernel: [272280.820242] RBP: 0000000000000002 R08: ffff8880a98b7d80 R09: 0000000000000000
> >Jan 13 19:03:15 sylvester kernel: [272280.820246] R10: 000000000000004b R11: ffffc90000fdb9c8 R12: ffffffffffffffff
> >Jan 13 19:03:15 sylvester kernel: [272280.820250] R13: ffffc90000fdbae0 R14: ffffc90000fdba60 R15: 0000000000000000
> >Jan 13 19:03:15 sylvester kernel: [272280.820255] FS: 0000000000000000(0000) GS:ffff888217980000(0000) knlGS:0000000000000000
> >Jan 13 19:03:15 sylvester kernel: [272280.820259] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >Jan 13 19:03:15 sylvester kernel: [272280.820263] CR2: 0000100000000008 CR3: 000000000200a003 CR4: 00000000000606e0
> >Jan 13 19:03:15 sylvester kernel: [272280.820268] Call Trace:
> >Jan 13 19:03:15 sylvester kernel: [272280.820276] pagevec_lookup_entries+0x15/0x20
> >Jan 13 19:03:15 sylvester kernel: [272280.820280] truncate_inode_pages_range+0xc5/0x810
> >Jan 13 19:03:15 sylvester kernel: [272280.820289] ? ___cache_free+0x2c/0x2f0
> >Jan 13 19:03:15 sylvester kernel: [272280.820296] ? jbd2_journal_release_jbd_inode+0x105/0x130 [jbd2]
> >Jan 13 19:03:15 sylvester kernel: [272280.820301] ? iput+0x1e9/0x210
> >Jan 13 19:03:15 sylvester kernel: [272280.820305] ? __inode_wait_for_writeback+0x7a/0xe0
> >Jan 13 19:03:15 sylvester kernel: [272280.820319] ext4_evict_inode+0x52/0x5d0 [ext4]
> >Jan 13 19:03:15 sylvester kernel: [272280.820325] evict+0xbf/0x190
> >Jan 13 19:03:15 sylvester kernel: [272280.820328] dispose_list+0x30/0x40
> >Jan 13 19:03:15 sylvester kernel: [272280.820332] prune_icache_sb+0x4d/0x70
> >Jan 13 19:03:15 sylvester kernel: [272280.820337] super_cache_scan+0x121/0x1a0
> >Jan 13 19:03:15 sylvester kernel: [272280.820342] do_shrink_slab+0x136/0x2d0
> >Jan 13 19:03:15 sylvester kernel: [272280.820346] shrink_slab+0x22a/0x290
> >Jan 13 19:03:15 sylvester kernel: [272280.820351] ? __mod_node_page_state+0x64/0xa0
> >Jan 13 19:03:15 sylvester kernel: [272280.820354] shrink_node+0xe1/0x450
> >Jan 13 19:03:15 sylvester kernel: [272280.820358] kswapd+0x3f9/0x740
> >Jan 13 19:03:15 sylvester kernel: [272280.820362] ? mem_cgroup_shrink_node+0x1b0/0x1b0
> >Jan 13 19:03:15 sylvester kernel: [272280.820367] kthread+0x111/0x130
> >Jan 13 19:03:15 sylvester kernel: [272280.820371] ? kthread_create_worker_on_cpu+0x60/0x60
> >Jan 13 19:03:15 sylvester kernel: [272280.820376] ret_from_fork+0x35/0x40
> >Jan 13 19:03:15 sylvester kernel: [272280.820380] Modules linked in: cpuid fuse btrfs xor zstd_compress raid6_pq zstd_decompress xxhash ufs hfsplus ntfs vfat msdos fat j
> >Jan 13 19:03:15 sylvester kernel: [272280.820423] scsi_mod mfd_core usbcore e1000e
> >Jan 13 19:03:15 sylvester kernel: [272280.820452] CR2: 0000100000000008
> >Jan 13 19:03:15 sylvester kernel: [272280.820456] ---[ end trace b383b200f5d976a9 ]---
> >Jan 13 19:03:15 sylvester kernel: [272280.820461] RIP: 0010:find_get_entries+0xed/0x240
> >Jan 13 19:03:15 sylvester kernel: [272280.820465] Code: 4e 4e 00 48 89 c2 48 85 d2 0f 84 91 00 00 00 48 81 fa 02 04 00 00 0f 84 a3 00 00 00 48 81 fa 06 04 00 00 74 ca f6
> >Jan 13 19:03:15 sylvester kernel: [272280.820472] RSP: 0018:ffffc90000fdb9c8 EFLAGS: 00010246
> >
> >
> >I have opened https://bugzilla.kernel.org/show_bug.cgi?id=202257, providing
> >kernel.log and config file.
> >
> >Is there anything else I could do to help tracking down this problem?
> >
> >
> >Regards
> >Harri
> >
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-03-06 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 13:01 4.20.1: BUG: unable to handle kernel paging request at 0000100000000008 Harald Dunkel
2019-01-22 10:15 ` Harald Dunkel
2019-03-06 23:10 ` Pavel Machek [this message]
2019-03-07 8:51 ` Harald Dunkel
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=20190306231027.GF7915@amd \
--to=pavel@ucw.cz \
--cc=harald.dunkel@aixigo.de \
--cc=linux-kernel@vger.kernel.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: 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