Bug 202257 - BUG: unable to handle kernel paging request at 0000100000000008
Summary: BUG: unable to handle kernel paging request at 0000100000000008
Status: RESOLVED WILL_NOT_FIX
Alias: None
Product: Memory Management
Classification: Unclassified
Component: Page Allocator (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Andrew Morton
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-14 04:55 UTC by Harald Dunkel
Modified: 2019-12-01 10:39 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.20.1
Subsystem:
Regression: No
Bisected commit-id:


Attachments
kernel.log of the whole session (459.02 KB, text/plain)
2019-01-14 04:55 UTC, Harald Dunkel
Details
kernel config file (189.98 KB, text/plain)
2019-01-14 04:55 UTC, Harald Dunkel
Details
DMESG. (349.40 KB, text/plain)
2019-01-15 14:55 UTC, Haxk20
Details

Description Harald Dunkel 2019-01-14 04:55:01 UTC
Created attachment 280453 [details]
kernel.log of the whole session

4.20.1 had this problem.

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


Later oom killer was invoked, bringing the host down. 

Logfile is attached.
Comment 1 Harald Dunkel 2019-01-14 04:55:41 UTC
Created attachment 280455 [details]
kernel config file
Comment 2 Haxk20 2019-01-15 14:54:05 UTC
Same issue here with 5.0-rc1 and rc2.
I dont have kernel paging request at that adress but the same error pops out.
BUG: unable to handle kernel paging request at ffffa18f00099000
Then a lot of "corrupted low memory at" messages.
System stays up and running and is usable in TTY but GNOME stays frozen with only mouse cursor moving.
I reported This bug earlier also. Here is bug ID 202247.
This makes the PC unusable for watching any video because it frezes at some point.
Comment 3 Haxk20 2019-01-15 14:55:50 UTC
Created attachment 280495 [details]
DMESG.

Full dmesg of the issue.
Comment 4 Haxk20 2019-01-15 14:59:11 UTC
Also as i see in the log BOTH of our machines run btrfs. And as it seems so far this bug occurs only with BTRFS filesystem.
Comment 5 Harald Dunkel 2019-01-15 16:30:51 UTC
I am not using btrfs, but ext4. 

0000100000000008 looks like some bitmask found at the wrong place, but ffffa18f00099000 appears to be some address-like construct. The stack traces look very different, too, so I am pretty sure these are 2 separate problems.

Haxk20, would you mind to open your own bug report? Thanx
Comment 6 Haxk20 2019-01-16 15:27:50 UTC
(In reply to Harald Dunkel from comment #5)
> I am not using btrfs, but ext4. 
> 
> 0000100000000008 looks like some bitmask found at the wrong place, but
> ffffa18f00099000 appears to be some address-like construct. The stack traces
> look very different, too, so I am pretty sure these are 2 separate problems.
> 
> Haxk20, would you mind to open your own bug report? Thanx

Actually i opened an bug report 2 days before yours and still no response to that issue.
Im sure they are busy but i really hope this gets fixed in later RC builds because i cant work with freezing machine.
Will test linux-next branch to see if it already has a fix because that very possible.
Comment 7 Haxk20 2019-01-17 18:35:37 UTC
OK my issue is fixed in linux-next.
Comment 8 Harald Dunkel 2019-01-18 07:58:24 UTC
Congratulations
Comment 9 Harald Dunkel 2019-04-30 15:17:10 UTC
Would it be possible that anybody looks into this bug report?
Comment 10 Harald Dunkel 2019-12-01 10:39:25 UTC
I'm closing this due to lack of interest

Note You need to log in before you can comment on or make changes to this bug.