From: James Hogan <james@albanarts.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG: scheduling while atomic 2.6.39-rc7 (iwl3945_irq_tasklet)
Date: Tue, 17 May 2011 09:41:42 +0100 [thread overview]
Message-ID: <BANLkTi=JU2VkyArY4jrt1iE-sdwKp+JaAQ@mail.gmail.com> (raw)
In-Reply-To: <20110516172513.GA2546@tuxdriver.com>
On 16 May 2011 18:25, John W. Linville <linville@tuxdriver.com> 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@tuxdriver.com might be all we have. Be ready.
>
--
James Hogan
next prev parent reply other threads:[~2011-05-17 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 20:34 BUG: scheduling while atomic 2.6.39-rc7 (iwl3945_irq_tasklet) James Hogan
2011-05-16 17:25 ` John W. Linville
2011-05-17 8:41 ` James Hogan [this message]
2011-06-01 14:43 ` Stanislaw Gruszka
2011-06-01 18:02 ` James Hogan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=JU2VkyArY4jrt1iE-sdwKp+JaAQ@mail.gmail.com' \
--to=james@albanarts.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).