Hi Tejun, >> On my Dell XPS 13 9343 (x86_64), the following warning was logged right >> after a resume from suspend-to-mem (not on *every* resume, though, so it >> might be hard to reproduce). The kernel is v4.12.0-rc6+ as of 94a6df251dd0, >> and I don't really use bluetooth, though the drivers are loaded: >> >> PM: Finishing wakeup. >> OOM killer enabled. >> Restarting tasks ... done. >> Bluetooth: hci0: read Intel version: 370710018002030d00 >> Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq >> Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated >> ... <more, unrelated messages> >> workqueue: WQ_MEM_RECLAIM hci0:hci_power_off is flushing !WQ_MEM_RECLAIM events:btusb_work > > So, WQ_MEM_RECLAIM has to be transitive; otherwise, it doesn't mean > anything. I have a hard time believing that bluetooth actually needs > WQ_MEM_RECLAIM unless people mount nfs through a bluetooth tethered > phone. Would it be possible to remove WQ_MEM_RECLAIM from these > workqueues? frankly I do not remember. We used what was recommended to use. I know that the only requirement in one case is that it is a truly single workqueue. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
