Bug 1070845

Summary: [abrt] WARNING: CPU: 1 PID: 0 at drivers/usb/host/xhci-ring.c:1583 handle_cmd_completion+0xdfe/0xe10()
Product: [Fedora] Fedora Reporter: nioroso_x3
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/553c2e4268f650649dd77f2ec1be0b4fc4101333
Whiteboard: abrt_hash:08808ac16cfbdf85d88f7f4af4d1cc64783746ca
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-23 17:26:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg none

Description nioroso_x3 2014-02-27 15:13:45 UTC 
Description of problem:
To use the VIA USB 3.0 controller, iommu=pt or iommu=soft has to be enabled. There were no errors until kernel 3.14.

Additional info:
reporter:       libreport-2.1.12
WARNING: CPU: 1 PID: 0 at drivers/usb/host/xhci-ring.c:1583 handle_cmd_completion+0xdfe/0xe10()
Modules linked in: radeon(+) r8169 firewire_ohci mii firewire_core i2c_algo_bit crc_itu_t drm_kms_helper ttm drm i2c_core
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.14.0-0.rc4.git0.1.fc21.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD3, BIOS F2 07/15/2013
 0000000000000000 5c9298cded198736 ffff88023ec43d30 ffffffff816ed0d5
 0000000000000000 ffff88023ec43d68 ffffffff8108a06d ffff880230f80470
 0000000000000000 ffff880230f80020 0000000230f80020 ffff8800b91d0000
Call Trace:
 <IRQ>  [<ffffffff816ed0d5>] dump_stack+0x45/0x56
 [<ffffffff8108a06d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8108a19a>] warn_slowpath_null+0x1a/0x20
 [<ffffffff8151fc0e>] handle_cmd_completion+0xdfe/0xe10
 [<ffffffff8101ced9>] ? sched_clock+0x9/0x10
 [<ffffffff810c2725>] ? sched_clock_cpu+0x85/0xc0
BIOS-e820: [mem 0x00000000be981000-0x00000000be98afff] ACPI data
 [<ffffffff810b71cc>] ? update_rq_clock.part.83+0x1c/0x170
 [<ffffffff8101ce75>] ? native_sched_clock+0x35/0x90
 [<ffffffff815202fb>] xhci_irq+0x37b/0x1bb0
 [<ffffffff81098c38>] ? update_process_times+0x68/0x70
 [<ffffffff81521b41>] xhci_msi_irq+0x11/0x20
 [<ffffffff810e559e>] handle_irq_event_percpu+0x3e/0x1d0
 [<ffffffff810e5767>] handle_irq_event+0x37/0x60
 [<ffffffff810e833f>] handle_edge_irq+0x6f/0x120
 [<ffffffff810169df>] handle_irq+0xbf/0x150
 [<ffffffff816f843a>] ? atomic_notifier_call_chain+0x1a/0x20
 [<ffffffff816ff70f>] do_IRQ+0x4f/0xf0
 [<ffffffff816f45ed>] common_interrupt+0x6d/0x6d
 <EOI>  [<ffffffff8158b05f>] ? cpuidle_enter_state+0x4f/0xc0
 [<ffffffff8158b058>] ? cpuidle_enter_state+0x48/0xc0
 [<ffffffff8158b189>] cpuidle_idle_call+0xb9/0x1f0
 [<ffffffff8101e80e>] arch_cpu_idle+0xe/0x30
 [<ffffffff810e4aa5>] cpu_startup_entry+0xf5/0x2a0
 [<ffffffff81044f3b>] start_secondary+0x23b/0x300

Potential duplicate: bug 1066554
Comment 1 nioroso_x3 2014-02-27 15:13:55 UTC 
Created attachment 868579 [details]
File: dmesg
Comment 2 Jaroslav Reznik 2015-03-03 15:32:05 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 3 Justin M. Forbes 2015-10-20 19:46:10 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is 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 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  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 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.
Comment 4 Fedora Kernel Team 2015-11-23 17:26:36 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 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.