On Tue, Dec 7, 2010 at 12:54 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2010-12-07 at 12:49 -0800, Luis R. Rodriguez wrote: > >> > In what situation? When you just suspend while things are up&running, or >> > if you suspend with interfaces down? >> >> I believe Paul was suspending when the interface is up and running. > > Ok. > >> > It doesn't make sense anyway, so >> > something's going on in the rest of the scan code -- we should be >> > canceling scans properly when going down and when suspending, well >> > before any of this becomes relevant. >> >> The issue might be we race to stop the device prior to canceling a >> scan. Do you see that being possible? > > Not really, since we do scan_cancel() within suspend()... I guess I'd > like to find out why that doesn't do what I think it does. Well lets see, this is only reproducible with the new DBUS APIs, and frankly I am not sure what these things do. Is it possible we have a race between how it brings down an interface for suspend and canceling a scan? Luis -- 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
