From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Randy Dunlap" <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: BUG: scheduling while atomic, new libata code
Date: Thu, 28 Dec 2006 17:46:49 -0500 [thread overview]
Message-ID: <9e4733910612281446h1def63fbp89996690577cb2f4@mail.gmail.com> (raw)
In-Reply-To: <200612282247.06127.arnd@arndb.de>
On 12/28/06, Arnd Bergmann <arnd@arndb.de> wrote:
> On Thursday 28 December 2006 03:16, Jon Smirl wrote:
> > BUG: scheduling while atomic: hald-addon-stor/0x20000000/5078
> > [<c02b0289>] __sched_text_start+0x5f9/0xb00
> > [<c024a623>] net_rx_action+0xb3/0x180
> > [<c01210f2>] __do_softirq+0x72/0xe0
> > [<c0105205>] do_IRQ+0x45/0x80
>
> This doesn't seem to be related to libata at all. Like your
> first trace, you call schedule from a softirq context, which
> is always atomic.
> The only place where I can imagine this happening is the
> local_irq_enable() in there, which can be defined in different
> ways.
> Are you running with paravirt_ops, CONFIG_TRACE_IRQFLAGS_SUPPORT
> and/or kernel preemption enabled?
Forgot this,
# CONFIG_PARAVIRT is not set
CPU is 2.8Mhz P4, no virtualization capabilities.
>
> Arnd <><
>
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2006-12-28 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 1:47 BUG: scheduling while atomic, new libata code Jon Smirl
2006-12-27 1:55 ` Randy Dunlap
2006-12-27 4:33 ` Jon Smirl
2006-12-28 2:16 ` Jon Smirl
2006-12-28 21:47 ` Arnd Bergmann
2006-12-28 22:43 ` Jon Smirl
2006-12-28 22:46 ` Jon Smirl [this message]
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=9e4733910612281446h1def63fbp89996690577cb2f4@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.