Bug 202339 - [Intel GFX CI] BUG: unable to handle kernel paging request at 0000004000000018
Summary: [Intel GFX CI] BUG: unable to handle kernel paging request at 0000004000000018
Status: RESOLVED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: Platform_x86 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-18 20:34 UTC by Martin Peres
Modified: 2019-04-03 08:12 UTC (History)
0 users

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


Attachments
Boot log (129.03 KB, text/plain)
2019-01-18 20:34 UTC, Martin Peres
Details
Logs during the execution of the tests that triggered the issue (227.32 KB, text/plain)
2019-01-18 20:35 UTC, Martin Peres
Details

Description Martin Peres 2019-01-18 20:34:29 UTC
Created attachment 280591 [details]
Boot log

<1>[  429.563229] BUG: unable to handle kernel paging request at 0000004000000018
<1>[  429.563233] #PF error: [normal kernel read fault]
<6>[  429.563236] PGD 0 P4D 0 
<4>[  429.563239] Oops: 0000 [#1] PREEMPT SMP PTI
<4>[  429.563242] CPU: 0 PID: 159 Comm: kworker/0:3 Tainted: G     U            5.0.0-rc2-CI-CI_DRM_5445+ #1
<4>[  429.563244] Hardware name: Intel Corporation Ice Lake Client Platform/IceLake U DDR4 SODIMM PD RVP TLC, BIOS ICLSFWR1.R00.2402.AD3.1810170014 10/17/2018
<4>[  429.563249] Workqueue: events delayed_fput
<4>[  429.563254] RIP: 0010:debug_check_no_obj_freed+0xcd/0x210
<4>[  429.563257] Code: 00 48 8b 4c 24 20 48 89 44 24 18 48 c7 c0 40 ce 6c 83 48 8b 2c 08 48 85 ed 0f 84 ff 00 00 00 4c 8b 74 24 28 45 31 ed 48 89 ef <48> 8b 47 18 41 83 c5 01 48 8b 2f 49 39 c4 77 37 4c 39 f0 73 32 83
<4>[  429.563259] RSP: 0018:ffffc90000267a58 EFLAGS: 00010046
<4>[  429.563261] RAX: ffffffff836cce40 RBX: 0000000000000000 RCX: 00000000000f6a00
<4>[  429.563263] RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000004000000000
<4>[  429.563264] RBP: 0000004000000000 R08: 000000000c6d722e R09: 0000000000000000
<4>[  429.563266] R10: ffffc900002679d0 R11: ffffffff837c3860 R12: ffff8883b2e74000
<4>[  429.563268] R13: 0000000000000000 R14: ffff8883b2e75000 R15: dead000000000100
<4>[  429.563270] FS:  0000000000000000(0000) GS:ffff8884afe00000(0000) knlGS:0000000000000000
<4>[  429.563272] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[  429.563274] CR2: 0000004000000018 CR3: 0000000005214005 CR4: 0000000000760ef0
<4>[  429.563276] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
<4>[  429.563277] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
<4>[  429.563279] PKRU: 55555554
<4>[  429.563281] Call Trace:
<4>[  429.563287]  free_pcp_prepare+0x77/0x160
<4>[  429.563290]  free_unref_page_list+0x69/0x250
<4>[  429.563296]  release_pages+0x2d3/0x390
<4>[  429.563301]  __pagevec_release+0x1f/0x30
<4>[  429.563304]  shmem_undo_range+0x3ad/0x890
<4>[  429.563313]  shmem_truncate_range+0x11/0x30
<4>[  429.563316]  shmem_evict_inode+0xb8/0x1a0
<4>[  429.563319]  ? dput+0x20/0x2c0
<4>[  429.563322]  evict+0xcb/0x190
<4>[  429.563324]  __dentry_kill+0xca/0x190
<4>[  429.563327]  dentry_kill+0x4b/0x1b0
<4>[  429.563330]  ? dput+0x20/0x2c0
<4>[  429.563332]  dput+0x262/0x2c0
<4>[  429.563335]  __fput+0xf7/0x1f0
<4>[  429.563338]  delayed_fput+0x17/0x30
<4>[  429.563341]  process_one_work+0x245/0x610
<4>[  429.563345]  worker_thread+0x37/0x380
<4>[  429.563348]  ? process_one_work+0x610/0x610
<4>[  429.563351]  kthread+0x119/0x130
<4>[  429.563354]  ? kthread_park+0x80/0x80
<4>[  429.563358]  ret_from_fork+0x3a/0x50
<4>[  429.563362] Modules linked in: vgem snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic x86_pkg_temp_thermal coretemp i915 crct10dif_pclmul crc32_pclmul snd_hda_intel ghash_clmulni_intel snd_hda_codec snd_hwdep snd_hda_core snd_pcm e1000e cdc_ether usbnet mii i2c_i801 prime_numbers
Comment 1 Martin Peres 2019-01-18 20:35:33 UTC
Created attachment 280593 [details]
Logs during the execution of the tests that triggered the issue
Comment 2 Martin Peres 2019-01-18 20:37:26 UTC
All the information about the machine is available here: https://intel-gfx-ci.01.org/hardware/shard-iclb4/
Comment 3 Martin Peres 2019-04-03 08:12:35 UTC
This issue has been seen only once, the kernel has changed a lot, and the machine has been problematic... Closing the bug as insufficient_data.

Sorry for the noise!

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