Johannes Berg <[email protected]> writes: > On Thu, 2009-07-09 at 22:03 +0200, Rafael J. Wysocki wrote: >> On Thursday 09 July 2009, Jan Scholz wrote: >> > Hi, >> > >> > I have just checked this on v2.6.31-rc1 and v2.6.31-rc2-214-g34f2547 >> > (I wanted to test this on v2.6.31-rc2 as well, but there I had other >> > suspend-issues that are fixed in todays v2.6.31-rc2-214-g34f2547) >> > >> > For both v2.6.31-rc1 and v2.6.31-rc2-214-g34f2547 suspend to ram fails >> > with the test procedure described below, but it works fine when I revert >> > commit 5bb644a0fd25a5e083ecbfaa92a211db99aa6ef7 >> > "mac80211: cancel/restart all timers across suspend/resume" >> >> Thanks for the update. >> >> Johannes, do you have any idea what can go wrong here? > > Not really, no. __ieee80211_suspend isn't holding any locks that the > cancel_work_sync() calls could require or so afaict... > > Jan, can you run with console_suspend=0 (or whatever it is now, Rafael > will correct me if I'm wrong) that should work on your platform, and put > a bunch of printk calls into __ieee80211_suspend in net/mac80211/pm.c to > see where in there it's hanging?
Did that, seems like it hangs in drv_remove_interface(local, &conf); Jan -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
