Created attachment 1193492 [details]
File: dmesg

Description of problem:
right after reboot

Version-Release number of selected component:
kernel-core-4.7.2-200.fc24

Additional info:
reporter:       libreport-2.7.2
cmdline:        BOOT_IMAGE=/vmlinuz-4.7.2-200.fc24.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.luks.uuid=luks-f2300f39-1b39-4d66-9621-567d5ca4e2bf rd.lvm.lv=fedora/swap resume=/dev/mapper/fedora-swap acpi_osi=Linux rhgb quiet LANG=en_US.UTF-8
kernel:         4.7.2-200.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 3 PID: 956 at kernel/workqueue.c:2422 check_flush_dependency+0x122/0x130
workqueue: WQ_MEM_RECLAIM hci0:hci_power_off [bluetooth] is flushing !WQ_MEM_RECLAIM events:btusb_work [btusb]
Modules linked in:
 snd_usb_audio snd_usbmidi_lib snd_rawmidi uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_core btrtl btbcm btintel videodev bluetooth media intel_rapl arc4 x86_pkg_temp_thermal intel_powerclamp coretemp mei_wdt kvm_intel iTCO_wdt iTCO_vendor_support kvm iwlmvm snd_hda_codec_realtek snd_hda_codec_hdmi mac80211 snd_hda_codec_generic snd_hda_intel irqbypass intel_cstate snd_hda_codec intel_uncore intel_rapl_perf snd_hda_core iwlwifi snd_hwdep snd_seq snd_seq_device cfg80211 snd_pcm joydev mei_me intel_pch_thermal mei rtsx_pci_ms thinkpad_acpi memstick snd_timer i2c_i801 shpchp snd lpc_ich wmi soundcore rfkill tpm_crb tpm_tis nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc dm_crypt i915 rtsx_pci_sdmmc mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel
 e1000e i2c_algo_bit drm_kms_helper ghash_clmulni_intel drm serio_raw rtsx_pci ptp pps_core video fjes ecryptfs encrypted_keys trusted tpm
CPU: 3 PID: 956 Comm: kworker/u17:1 Not tainted 4.7.2-200.fc24.x86_64 #1
Hardware name: LENOVO 20CMCTO1WW/20CMCTO1WW, BIOS N10ET44W (1.23 ) 07/13/2016
Workqueue: hci0 hci_power_off [bluetooth]
 0000000000000086 00000000ab235e1d ffff88042d09bb80 ffffffff813d942f
 ffff88042d09bbd0 0000000000000000 ffff88042d09bbc0 ffffffff8109facb
 0000097600000000 ffff88043d48e600 ffff8804380f0000 ffffffffc08c05c0
Call Trace:
 [<ffffffff813d942f>] dump_stack+0x63/0x84
 [<ffffffff8109facb>] __warn+0xcb/0xf0
 [<ffffffffc08c05c0>] ? btusb_diag_complete+0x170/0x170 [btusb]
 [<ffffffff8109fb4f>] warn_slowpath_fmt+0x5f/0x80
 [<ffffffffc07f6c90>] ? hci_dev_do_close+0x500/0x500 [bluetooth]
 [<ffffffff810b6432>] check_flush_dependency+0x122/0x130
 [<ffffffffc08c05c0>] ? btusb_diag_complete+0x170/0x170 [btusb]
 [<ffffffff810b8681>] flush_work+0x81/0x1c0
 [<ffffffff8121fd01>] ? __slab_free+0xa1/0x2a0
 [<ffffffff816b6c37>] ? __alloc_skb+0x87/0x1e0
 [<ffffffff810b901f>] __cancel_work_timer+0x9f/0x1d0
 [<ffffffffc07f6a01>] ? hci_dev_do_close+0x271/0x500 [bluetooth]
 [<ffffffff810b9160>] cancel_work_sync+0x10/0x20
 [<ffffffffc08bcedb>] btusb_close+0x2b/0x100 [btusb]
 [<ffffffffc07f6a27>] hci_dev_do_close+0x297/0x500 [bluetooth]
 [<ffffffffc07f6cb2>] hci_power_off+0x22/0x50 [bluetooth]
 [<ffffffff810b9314>] process_one_work+0x184/0x440
 [<ffffffff810b961e>] worker_thread+0x4e/0x480
 [<ffffffff810b95d0>] ? process_one_work+0x440/0x440
 [<ffffffff810b95d0>] ? process_one_work+0x440/0x440
 [<ffffffff810bf4f8>] kthread+0xd8/0xf0
 [<ffffffff817eba7f>] ret_from_fork+0x1f/0x40
 [<ffffffff810bf420>] ? kthread_worker_fn+0x180/0x180

*********** 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 24 kernel bugs.
 
Fedora 24 has now been rebased to 4.7.4-200.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 25, and are still experiencing this issue, please change the version to Fedora 25.
 
If you experience different issues, please open a new bug report for those.

(In reply to Laura Abbott from comment #3)
> *********** 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 24 kernel bugs.
>  
> Fedora 24 has now been rebased to 4.7.4-200.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 25, and are still experiencing this issue,
> please change the version to Fedora 25.
>  
> If you experience different issues, please open a new bug report for those.

stop with mail automatic treatment . what info is needed ?

*********** 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.

On F25 here, 4.10.9-200.fc25.x86_64 - haven't seen this since 2016-10-31 (on F24 at the time).

*********** 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.