Bug 1141384

Summary: [abrt] WARNING: CPU: 0 PID: 6 at drivers/usb/core/urb.c:339 usb_submit_urb+0x5af/0x5c0()
Product: [Fedora] Fedora Reporter: stephen brede <srbrede>
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: 20CC: fac_franky, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/25c5b8ca15a0c5c2207cde95edadfe3d81e0a3c5
Whiteboard: abrt_hash:2c9d045b07719eef976b6f7d6d784f021e2905d8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-10 15:01:58 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 stephen brede 2014-09-12 21:56:56 UTC 
Description of problem:
I manually hibernated my PC last night and this morning when I powered it up it performed a cold start rahter than return from hibernation.
here have been previous crashes with the same warning but have been identified as being related to kernel tainging by vbox which I use regularly but close before allowing hibernation.

Additional info:
reporter:       libreport-2.2.3
WARNING: CPU: 0 PID: 6 at drivers/usb/core/urb.c:339 usb_submit_urb+0x5af/0x5c0()
URB ffff88012947ca80 submitted while active
Modules linked in: nouveau video mxm_wmi wmi i2c_algo_bit drm_kms_helper ttm drm firewire_ohci ata_generic aic7xxx firewire_core atl1e pata_acpi crc_itu_t scsi_transport_spi pata_marvell i2c_core
CPU: 0 PID: 6 Comm: kworker/u8:0 Not tainted 3.15.10-201.fc20.x86_64 #1
Hardware name: System manufacturer System Product Name/P5Q, BIOS 1501    11/04/2008
Workqueue: events_unbound async_run_entry_fn
 0000000000000000 0000000088192837 ffff880129b57b68 ffffffff816ef848
 ffff880129b57bb0 ffff880129b57ba0 ffffffff8108927d ffff88012947ca80
 0000000000000006 0000000000000030 0000000000000000 0000000000000007
Call Trace:
 [<ffffffff816ef848>] dump_stack+0x45/0x56
 [<ffffffff8108927d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff810892fc>] warn_slowpath_fmt+0x5c/0x80
 [<ffffffff814df60f>] usb_submit_urb+0x5af/0x5c0
 [<ffffffff814d555f>] hub_activate+0x2ff/0x600
 [<ffffffff814ffc15>] ? ehci_bus_resume+0x325/0x730
 [<ffffffff814d5961>] hub_resume+0x31/0x60
 [<ffffffff814e2fb6>] usb_resume_interface.isra.5+0xa6/0x110
 [<ffffffff814e3274>] usb_resume_both+0x74/0x150
 [<ffffffff814e3f7b>] usb_resume+0x1b/0x70
 [<ffffffff814d26e0>] ? usb_dev_restore+0x20/0x20
 [<ffffffff814d26f3>] usb_dev_thaw+0x13/0x20
 [<ffffffff814693b9>] dpm_run_callback+0x49/0xa0
 [<ffffffff814696b6>] device_resume+0xc6/0x1f0
 [<ffffffff814697fd>] async_resume+0x1d/0x50
 [<ffffffff810b25f9>] async_run_entry_fn+0x39/0x120
 [<ffffffff810a4a36>] process_one_work+0x176/0x430
 [<ffffffff810a56cb>] worker_thread+0x11b/0x3a0
 [<ffffffff810a55b0>] ? rescuer_thread+0x3b0/0x3b0
 [<ffffffff810ac468>] kthread+0xd8/0xf0
 [<ffffffff810ac390>] ? insert_kthread_work+0x40/0x40
 [<ffffffff816ff8bc>] ret_from_fork+0x7c/0xb0
 [<ffffffff810ac390>] ? insert_kthread_work+0x40/0x40
Comment 1 stephen brede 2014-09-12 21:57:02 UTC 
Created attachment 937134 [details]
File: dmesg
Comment 2 Justin M. Forbes 2014-11-13 16:02:44 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  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 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.
Comment 3 Justin M. Forbes 2014-12-10 15:01:58 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 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.
Comment 4 stephen brede 2014-12-11 05:15:33 UTC 
As i have been running my machine continuously for the past 6 weeks the hibernation issue has not had a chance to surface. Now the processes requiring continuous running have finished I can report that with the latest updates i have not experienced and hibernation issues over the last week of use (at least 6 hibernations). It has come out of hibernation each time successfully.
VBOX has been updated at the same time to v4.30.
Happy for the bug to be closed as it appears eithet the vbox or kernel updates have fixed the problem.