Description of problem: Seems like a bug with the lirc kernel module. I use an Apple IR remote to control Kodi through lirc. Additional info: reporter: libreport-2.6.4 WARNING: CPU: 3 PID: 765 at kernel/sched/core.c:7557 __might_sleep+0x75/0x80() do not call blocking ops when !TASK_RUNNING; state=1 set at [<ffffffffa03b2d31>] lirc_dev_fop_read+0x1e1/0x590 [lirc_dev] Modules linked in: ccm rfcomm ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 bnep nf_defrag_ipv6 ip6table_filter nf_conntrack_ipv4 ip6_tables nf_defrag_ipv4 xt_conntrack nf_conntrack iTCO_wdt iTCO_vendor_support snd_hda_codec_hdmi intel_rapl coretemp kvm_intel snd_hda_codec_realtek vfat snd_hda_codec_generic fat kvm irqbypass crct10dif_pclmul crc32_pclmul arc4 iwlmvm mac80211 btusb btrtl btbcm btintel iwlwifi bluetooth cfg80211 i915 i2c_i801 lpc_ich snd_intel_sst_acpi snd_intel_sst_core snd_soc_rt5670 snd_hda_intel snd_soc_sst_mfld_platform i2c_algo_bit mei_txe snd_soc_rl6231 snd_hda_codec drm_kms_helper snd_soc_core mei snd_hda_core drm snd_hwdep dw_dmac_pci shpchp i2c_designware_pci iosf_mbi snd_compress snd_pcm_dmaengine ac97_bus ir_mce_kbd_decoder ir_lirc_codec ir_jvc_decoder lirc_dev ir_sony_decoder ir_xmp_decoder ir_sanyo_decoder ir_sharp_decoder ir_nec_decoder ir_rc5_decoder ir_rc6_decoder snd_seq snd_seq_device rc_rc6_mce snd_pcm ite_cir rc_core video dw_dmac snd_timer dw_dmac_core snd rfkill_gpio soundcore i2c_designware_platform rfkill i2c_designware_core soc_button_array spi_pxa2xx_platform acpi_pad tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc xfs libcrc32c crc32c_intel serio_raw r8169 mii sdhci_pci sdhci_acpi i2c_hid sdhci mmc_core fjes CPU: 3 PID: 765 Comm: lircd Not tainted 4.4.5-300.fc23.x86_64+debug #1 Hardware name: /NUC5PPYB, BIOS PYBSWCEL.86A.0031.2015.0601.1712 06/01/2015 0000000000000286 00000000d9104369 ffff8801742bfc90 ffffffff8142b543 ffff8801742bfcd8 ffffffff81c893ec ffff8801742bfcc8 ffffffff810aef42 ffffffffa03b4428 00000000000002dc 0000000000000000 ffff88007640d380 Call Trace: [<ffffffff8142b543>] dump_stack+0x85/0xc2 [<ffffffff810aef42>] warn_slowpath_common+0x82/0xc0 [<ffffffff810aefdc>] warn_slowpath_fmt+0x5c/0x80 [<ffffffff81885186>] ? _raw_spin_unlock_irqrestore+0x36/0x60 [<ffffffffa03b2d31>] ? lirc_dev_fop_read+0x1e1/0x590 [lirc_dev] [<ffffffffa03b2d31>] ? lirc_dev_fop_read+0x1e1/0x590 [lirc_dev] [<ffffffff810dc475>] __might_sleep+0x75/0x80 [<ffffffff8121bcd3>] __might_fault+0x43/0xa0 [<ffffffffa03b2fe1>] lirc_dev_fop_read+0x491/0x590 [lirc_dev] [<ffffffff8110a38d>] ? trace_hardirqs_on+0xd/0x10 [<ffffffff810e20f0>] ? wake_up_q+0x70/0x70 [<ffffffff81276dc7>] __vfs_read+0x37/0x100 [<ffffffff813a0963>] ? security_file_permission+0xa3/0xc0 [<ffffffff812778d9>] vfs_read+0x89/0x130 [<ffffffff81278658>] SyS_read+0x58/0xd0 [<ffffffff81885b72>] entry_SYSCALL_64_fastpath+0x12/0x76
Created attachment 1142915 [details] File: dmesg
*********** 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 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. 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 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 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.