On Mon, Jan 5, 2009 at 3:55 PM, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote: > Johannes, > > I'm chasing a problem with suspend/resume on rtl8187; however, in my testing, I > found that a simple "modprobe -r/modprobe" sequence fails, even though > unplugging/replugging the stick with or without a "modprobe -r" works just fine. > The last rtl8187 routine that was started was rtl8187_add_interface. From a > debugging message, I see that info->flags = 0x6B6B6B6B - the SLUB debugging > poison value. If I interpret the traceback correctly, a workqueue has been > restarted without being properly initialized. Is this with the current driver unmodified? If by any chance it is with your proposed patch from last week that always called start() or stop() in resume/suspend without some is_up flag, you will definitely get oopses doing that because the register/unregister will be unbalanced. -- Bob Copeland %% www.bobcopeland.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
