Bug 1381473

Summary:	WARNING: CPU: 0 PID: 4 at drivers/dma/ioat/dca.c:342 ioat_dca_init+0x18a/0x1a0 [ioatdma]
Product:	[Fedora] Fedora	Reporter:	Jan Hutař <jhutar>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	24	CC:	gansalmon, ichavero, itamar, jbieren, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone:	---	Flags:	jforbes: needinfo?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-28 17:12:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jan Hutař 2016-10-04 08:44:26 UTC

Description of problem:
[   55.728776] ------------[ cut here ]------------
[   55.728792] WARNING: CPU: 0 PID: 4 at drivers/dma/ioat/dca.c:342 ioat_dca_init+0x18a/0x1a0 [ioatdma]
[   55.728793] ioatdma 0000:00:04.0: APICID_TAG_MAP set incorrectly by BIOS, disabling DCA
[   55.728822] Modules linked in: mei_me(+) intel_uncore(+) ioatdma(+) mei intel_rapl_perf lpc_ich i2c_i801 dca ipmi_si(+) tpm_tis ipmi_msghandler tpm fjes nfsd auth_rpcgss nfs_acl lockd grace sunrpc xfs libcrc32c mgag200 i2c_algo_bit drm_kms_helper ttm crc32c_intel megaraid_sas isci drm libsas scsi_transport_sas wmi
[   55.728827] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.7.4-200.fc24.x86_64 #1
[   55.728828] Hardware name: SGI.COM UV20 ........../SVRBD-ROW_T, BIOS SE5C600.86B.01.07.0001.111620121607 11/16/2012
[   55.728836] Workqueue: events work_for_cpu_fn
[   55.728840]  0000000000000286 000000008e76dc28 ffff88081bea7c20 ffffffff853d994f
[   55.728843]  ffff88081bea7c70 0000000000000000 ffff88081bea7c60 ffffffff8509faab
[   55.728845]  00000156c09b58c1 ffff88181b2ab000 ffff88081a505ac0 ffff8808177a6f00
[   55.728846] Call Trace:
[   55.728854]  [<ffffffff853d994f>] dump_stack+0x63/0x84
[   55.728858]  [<ffffffff8509faab>] __warn+0xcb/0xf0
[   55.728861]  [<ffffffff8509fba7>] warn_slowpath_fmt_taint+0x57/0x70
[   55.728867]  [<ffffffffc09b42ba>] ioat_dca_init+0x18a/0x1a0 [ioatdma]
[   55.728872]  [<ffffffffc09b0295>] ioat_pci_probe+0xa35/0xf10 [ioatdma]
[   55.728876]  [<ffffffff8542ba55>] local_pci_probe+0x45/0xa0
[   55.728879]  [<ffffffff850b5d94>] work_for_cpu_fn+0x14/0x20
[   55.728881]  [<ffffffff850b9364>] process_one_work+0x184/0x440
[   55.728883]  [<ffffffff850b97e5>] worker_thread+0x1c5/0x480
[   55.728885]  [<ffffffff850b9620>] ? process_one_work+0x440/0x440
[   55.728888]  [<ffffffff850bf548>] kthread+0xd8/0xf0
[   55.728892]  [<ffffffff857eba7f>] ret_from_fork+0x1f/0x40
[   55.728895]  [<ffffffff850bf470>] ? kthread_worker_fn+0x180/0x180
[   55.728897] ---[ end trace 759821a89f0b909b ]---


Version-Release number of selected component (if applicable):
Fedora 24 GA


How reproducible:
sometimes


Steps to Reproduce:
1. Install and boot


Actual results:
dmesg complains about:
WARNING: CPU: 0 PID: 4 at drivers/dma/ioat/dca.c:342 ioat_dca_init+0x18a/0x1a0 [ioatdma]


Expected results:
No warning

Comment 2 John Bieren 2017-01-26 08:51:50 UTC

I am still seeing this bug on Fedora-Rawhide-20170125.n.0 Server x86_64 with kernel-4.10.0-0.rc5.git2.1.fc26

Any update on this?

Comment 4 Justin M. Forbes 2017-04-11 14:53:15 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 5 Justin M. Forbes 2017-04-28 17:12:27 UTC

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.