On 02/19/2016, 11:20 AM, Jiri Slaby wrote:
On 02/18/2016, 06:44 PM, Tejun Heo wrote:
quoted
Hello,
Can you please do the followings?
1. Remove WQ_MEM_RECLAIM from the affected workqueue and see whether
the problem is reproducible. WQ_MEM_RECLAIM on anything bluetooth
doesn't make sense btw. Why is it there?
2. If WQ_MEM_RECLAIM makes the issue go away, see whether the attached
patch works too.
Hello,
1. didn't help, the problem persists. So I haven't applied the patch from 2.
FWIW I dumped more info about the wq:
wq->name='hci0' pwq=ffff8800390d7600 wq->dfl_pwq=ffff8800390d5200
pwq->refcnt=2 pwq->nr_active=0 delayed_works: <nothing>
thanks,
--
js
suse labs