Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1676018
| From | Marcel Holtmann <marcel@holtmann.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: 4.12.0-rc6+: WQ_MEM_RECLAIM hci0:hci_power_off is flushing !WQ_MEM_RECLAIM events:btusb_work |
| Date | 2017-06-27 19:30 +0200 |
| Message-ID | <tX2tk-3Gw-7@gated-at.bofh.it> (permalink) |
| References | <tWksi-8vA-15@gated-at.bofh.it> <tX0Bc-2nz-39@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
4.12.0-rc6+: WQ_MEM_RECLAIM hci0:hci_power_off is flushing !WQ_MEM_RECLAIM events:btusb_work Dominik Brodowski <linux@dominikbrodowski.net> - 2017-06-25 20:30 +0200
Re: 4.12.0-rc6+: WQ_MEM_RECLAIM hci0:hci_power_off is flushing !WQ_MEM_RECLAIM events:btusb_work Tejun Heo <tj@kernel.org> - 2017-06-27 17:30 +0200
Re: 4.12.0-rc6+: WQ_MEM_RECLAIM hci0:hci_power_off is flushing !WQ_MEM_RECLAIM events:btusb_work Marcel Holtmann <marcel@holtmann.org> - 2017-06-27 19:30 +0200
Re: 4.12.0-rc6+: WQ_MEM_RECLAIM hci0:hci_power_off is flushing !WQ_MEM_RECLAIM events:btusb_work Tejun Heo <tj@kernel.org> - 2017-06-27 19:50 +0200
Re: 4.12.0-rc6+: WQ_MEM_RECLAIM hci0:hci_power_off is flushing !WQ_MEM_RECLAIM events:btusb_work Dominik Brodowski <linux@dominikbrodowski.net> - 2017-06-28 15:00 +0200
[PATCH] bluetooth: remove WQ_MEM_RECLAIM from hci workqueues Tejun Heo <tj@kernel.org> - 2017-06-28 20:50 +0200
Re: [PATCH] bluetooth: remove WQ_MEM_RECLAIM from hci workqueues Marcel Holtmann <marcel@holtmann.org> - 2017-06-29 14:40 +0200
csiph-web