On Wed, Oct 1, 2008 at 5:10 PM, Elias Oltmanns <eo@xxxxxxxxxxxxxx> wrote: > Toralf Förster <toralf.foerster@xxxxxx> wrote: >> Hello, >> >> the issue (initially reported in August 2008) still remains in the current >> kernel at my ThinkPad T41, a screen shot is attached. The steps to reproduce >> are : >> >> 1. modprobe it >> 2. suspend the system to ram >> 3. wake it up >> 4. rmmod the driver > > Yes, I have run into this problem too. The patch below (applies to > 2.6.27-rc8) fixes the problem, but since I'm not a wireless hacker, > developers might prefer a different approach. Please let me know if I > should change anything. Perhaps I should split this into two separate > patches? Thanks for the patch. I do think a different approach is probably warranted, though. ath5k_init() is supposed to be able to be called from resume. Do you have a better idea of why calib_tim isn't cleaned up properly by ath5k_stop_hw? I'm not near my laptop to test -- does the issue ever happen if you do NOT suspend? -- 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
