Bug 111942 - [CI][SHARDS] igt@gem_tiling_max_stride - dmesg-warn - BUG: kernel NULL pointer dereference, address: 0000000000000019
Summary: [CI][SHARDS] igt@gem_tiling_max_stride - dmesg-warn - BUG: kernel NULL point...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-09 17:37 UTC by Lakshmi
Modified: 2019-10-10 05:57 UTC (History)
1 user (show)

See Also:
i915 platform: TGL
i915 features: GEM/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-10-09 17:37:20 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5215/shard-tglb6/igt@gem_tiling_max_stride.html
<1> [282.114574] BUG: kernel NULL pointer dereference, address: 0000000000000019
<1> [282.114578] #PF: supervisor read access in kernel mode
<1> [282.114581] #PF: error_code(0x0000) - not-present page
<6> [282.114585] PGD 0 P4D 0 
<4> [282.114589] Oops: 0000 [#1] PREEMPT SMP NOPTI
<4> [282.114591] CPU: 3 PID: 2296 Comm: kworker/u16:14 Tainted: G     U            5.4.0-rc1-CI-CI_DRM_7020+ #1
<4> [282.114594] Hardware name: Intel Corporation Tiger Lake Client Platform/TigerLake U DDR4 SODIMM RVP, BIOS TGLSFWI1.R00.2321.A08.1909162051 09/16/2019
<4> [282.114600] Workqueue: writeback wb_workfn (flush-259:0)
<4> [282.114606] RIP: 0010:__lock_acquire+0x509/0x15d0
<4> [282.114608] Code: 00 45 31 ff 48 8b 7c 24 40 65 48 33 3c 25 28 00 00 00 44 89 f8 0f 85 dd 0f 00 00 48 83 c4 48 5b 5d 41 5c 41 5d 41 5e 41 5f c3 <48> 81 3f 20 8a 83 82 41 bf 00 00 00 00 45 0f 45 f8 83 fe 01 0f 87
<4> [282.114613] RSP: 0018:ffffc9000061bc68 EFLAGS: 00010002
<4> [282.114628] RAX: 0000000000000000 RBX: 0000000000000019 RCX: 0000000000000000
<4> [282.114629] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000019
<4> [282.114631] RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000001
<4> [282.114633] R10: 0000000000000000 R11: 0000000000000019 R12: 0000000000000000
<4> [282.114635] R13: 0000000000000000 R14: ffff88848d014040 R15: 0000000000000001
<4> [282.114636] FS:  0000000000000000(0000) GS:ffff8884a0580000(0000) knlGS:0000000000000000
<4> [282.114639] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [282.114640] CR2: 0000000000000019 CR3: 0000000005210003 CR4: 0000000000760ee0
<4> [282.114642] PKRU: 55555554
<4> [282.114643] Call Trace:
<4> [282.114646]  ? mark_held_locks+0x49/0x70
<4> [282.114649]  ? trace_hardirqs_on_thunk+0x1a/0x20
<4> [282.114660]  ? lockdep_hardirqs_on+0xe3/0x1c0
<4> [282.114662]  lock_acquire+0xa7/0x1c0
<4> [282.114665]  ? __wake_up_common_lock+0x5c/0xb0
<4> [282.114671]  ? retint_kernel+0x2b/0x2b
<4> [282.114673]  _raw_spin_lock_irqsave+0x33/0x50
<4> [282.114675]  ? __wake_up_common_lock+0x5c/0xb0
<4> [282.114677]  __wake_up_common_lock+0x5c/0xb0
<4> [282.114679]  wb_workfn+0xaa/0x5d0
<4> [282.114683]  ? process_one_work+0x1de/0x620
<4> [282.114685]  process_one_work+0x26a/0x620
<4> [282.114689]  worker_thread+0x37/0x380
<4> [282.114691]  ? process_one_work+0x620/0x620
<4> [282.114694]  kthread+0x119/0x130
<4> [282.114695]  ? kthread_park+0x80/0x80
<4> [282.114697]  ret_from_fork+0x24/0x50
<4> [282.114699] Modules linked in: vgem i915 mei_hdcp x86_pkg_temp_thermal coretemp crct10dif_pclmul ax88179_178a crc32_pclmul usbnet mii ghash_clmulni_intel mei_me mei prime_numbers
<0> [282.114709] Dumping ftrace buffer:
<0> [282.114717] ---------------------------------
<0> [282.114918] CPU:7 [LOST 21215 EVENTS]
Comment 1 CI Bug Log 2019-10-09 17:37:55 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@gem_tiling_max_stride - dmesg-warn - BUG: kernel NULL pointer dereference, address: 0000000000000019
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5215/shard-tglb6/igt@gem_tiling_max_stride.html
Comment 2 Francesco Balestrieri 2019-10-10 05:57:20 UTC
Seen once in 40 runs. Setting to medium for now.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.