On Saturday, 31 of May 2008, Johannes Berg wrote: > On Sat, 2008-05-31 at 00:49 +0200, Rafael J. Wysocki wrote: > > On Saturday, 31 of May 2008, Johannes Berg wrote: > > > > > > > It hangs for me either at read_unlock_irqrestore() in b43_op_tx() or somewhere > > > > in ieee80211_tx() (at various places). > > > > > > Huh. Why is it even getting into the tx path? And even then, why does it > > > hang at an unlock? > > > > Well, I saw that during hibernation, so it probably happened after creating the > > image, when devices were being resumed for image saving. > > Yeah, like I said earlier to somebody. Still doesn't make much sense > here. I'll play with it next week, or you could try to put into > suspend() a call to ieee80211_stop_queues() and in resume > ieee80211_wake_queues(), maybe that fixes it? I probably won't have time > over the weekend to look more into it, sorry. No big deal. :-) It's always been breaking for me like this ... Thanks, Rafael -- 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