On 16 May 2011 18:25, John W. Linville <linville@xxxxxxxxxxxxx> wrote: > On Fri, May 13, 2011 at 09:34:49PM +0100, James Hogan wrote: >> Hi, >> >> On 2.6.39-rc7 I've seen a panic due to "BUG: scheduling while atomic" >> with the backtrace below (not much detail as it was written in a text >> message while it was displayed on the screen!). All worked fine in >> 2.6.38. >> >> This was soon after resuming from suspend (enough time to unlock the >> screen, but not much else). I think it was the same bug I saw in rc2 but >> didn't have time to track down. I can probably get it to happen again if >> more detail is needed. It doesn't happen every suspend (I think it had >> survived a couple of suspend/resume cycles at this point). >> >> I could bisect if necessary, but hopefully the backtrace will be enough >> to see what's going on? > > A bisect might be very helpful -- time is short for 2.6.39 already. Hmm, it won't reproduce. I'll have to try and bisect this evening, as it was in my home network that it hit the BUG before. Cheers James > > John > -- > John W. Linville Someday the world will need a hero, and you > linville@xxxxxxxxxxxxx might be all we have. Be ready. > -- James Hogan -- 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
