From: Ralf Baechle <ralf@oss.sgi.com>
To: Krishna Kondaka <krishna@Sanera.net>
Cc: linux-mips@oss.sgi.com
Subject: Re: kernel BUG at slab.c:1073!
Date: Wed, 24 Jul 2002 20:58:43 +0200 [thread overview]
Message-ID: <20020724205843.A22500@dea.linux-mips.net> (raw)
In-Reply-To: <200207241834.g6OIYDi28110@icarus.sanera.net>; from krishna@Sanera.net on Wed, Jul 24, 2002 at 11:34:13AM -0700
On Wed, Jul 24, 2002 at 11:34:13AM -0700, Krishna Kondaka wrote:
> slab.c : line 1072-1073 is
>
> if (in_interrupt() && (flags & SLAB_LEVEL_MASK) != SLAB_ATOMIC)
> BUG();
>
> The driver being loaded is a small proprietary driver. The init routine of
> the driver is doing kmalloc() with GFP_KERNEL as the second argument. I know
> that I can fix my driver to use GFP_ATOMIC if running in interrupt context.
>
> My question is why is the "insmod" command running in interrupt context?
Simple answer: it isn't, normally. You should try to figure out who was
calling kmalloc or the slab allocator; knowing the function will probably
already solve the miracle. All the addresses in the call trace that are
in the range from 0xc0000000 and above are potencially modules addresses,
so they're worth some closer examination.
Aside, I urgently recommend an upgrade to a newer kernel. 2.4.9 is lacking
more than half a year worth of bug fixes. That can ruin your whole day ...
Ralf
next prev parent reply other threads:[~2002-07-24 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 18:34 kernel BUG at slab.c:1073! Krishna Kondaka
2002-07-24 18:45 ` Jun Sun
2002-07-24 18:58 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-24 19:08 Krishna Kondaka
2002-07-24 19:14 ` Ralf Baechle
2002-07-24 19:15 ` Jun Sun
2002-07-25 12:06 ` Steven Seeger
2002-07-25 12:06 ` Steven Seeger
2002-07-25 13:53 ` Ralf Baechle
2002-07-24 19:16 Krishna Kondaka
2002-07-24 19:23 Krishna Kondaka
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=20020724205843.A22500@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=krishna@Sanera.net \
--cc=linux-mips@oss.sgi.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