On 11/16/2010 06:19 AM, Tejun Heo wrote:
Hello,
On 11/15/2010 10:16 PM, Ben Greear wrote:
Here's the full trace of sysrq-t output:
Hmmm... for some reason, the dump is not complete. Only two kworkers
are printed out.
Can you please do the followings?
1. Try to capture the full dump. Usually serial console works best.
This was from serial console, and I grabbed everything it printed
to the screen. I'll look in /var/log/messages in case there is more
there.
If you have a system with an ath5k nic, I should be able to show you
how to reproduce it, if you're interested.
2. Does adding WQ_MEM_RECLAIM to alloc_ordered_workqueue() call in
ieee80211_register_hw() make any difference?
3. What if you replace it with the following?
alloc_workqueue(wiphy_name(local->hw.wiphy), WQ_NON_REENTRANT, 0)
I can try these things..hopefully today.
Can you explain briefly how this is supposed to work? I'm certain that some
workers can be blocked attempting to get rtnl. When we call flush_work(),
how is a worker chosen/created to flush that work?
Thanks,
Ben
Thanks.
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
