From: Andrew Morton <akpm@digeo.com>
To: Kent Yoder <key@austin.ibm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.46: sleeping function called from illegal context at mm/slab.c:1305
Date: Wed, 06 Nov 2002 11:30:20 -0800 [thread overview]
Message-ID: <3DC96DCC.A7094AEC@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211061308510.14931-100000@ennui.austin.ibm.com
Kent Yoder wrote:
>
> Seen on boot from 2.5.46-bk pulled earlier today. This is a UP pentium 3
> w/ 256 MB RAM. For some reason this sounds like a duplicate but I didn't see
> anything...
>
> Kent
>
> slab: reap timer started for cpu 0
> Starting kswapd
> aio_setup: sizeof(struct page) = 40
> [cfea2020] eventpoll: driver installed.
> Debug: sleeping function called from illegal context at mm/slab.c:1305
> Call Trace:
> [<c0143367>] kmem_flagcheck+0x67/0x70
> [<c0143d47>] kmalloc+0x67/0xc0
> [<c01461bf>] set_shrinker+0x1f/0xa0
> [<c0188a10>] mb_cache_create+0x1f0/0x2d0
> [<c0188640>] mb_cache_shrink_fn+0x0/0x1e0
> [<c0160299>] do_kern_mount+0xa9/0xe0
> [<c01050c3>] init+0x83/0x1b0
> [<c0105040>] init+0x0/0x1b0
> [<c010730d>] kernel_thread_helper+0x5/0x18
Yup, thanks. Andreas has prepared a patch which fixes this up.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@digeo.com>
To: Kent Yoder <key@austin.ibm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.46: sleeping function called from illegal context at mm/slab.c:1305
Date: Wed, 06 Nov 2002 11:30:20 -0800 [thread overview]
Message-ID: <3DC96DCC.A7094AEC@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211061308510.14931-100000@ennui.austin.ibm.com
Kent Yoder wrote:
>
> Seen on boot from 2.5.46-bk pulled earlier today. This is a UP pentium 3
> w/ 256 MB RAM. For some reason this sounds like a duplicate but I didn't see
> anything...
>
> Kent
>
> slab: reap timer started for cpu 0
> Starting kswapd
> aio_setup: sizeof(struct page) = 40
> [cfea2020] eventpoll: driver installed.
> Debug: sleeping function called from illegal context at mm/slab.c:1305
> Call Trace:
> [<c0143367>] kmem_flagcheck+0x67/0x70
> [<c0143d47>] kmalloc+0x67/0xc0
> [<c01461bf>] set_shrinker+0x1f/0xa0
> [<c0188a10>] mb_cache_create+0x1f0/0x2d0
> [<c0188640>] mb_cache_shrink_fn+0x0/0x1e0
> [<c0160299>] do_kern_mount+0xa9/0xe0
> [<c01050c3>] init+0x83/0x1b0
> [<c0105040>] init+0x0/0x1b0
> [<c010730d>] kernel_thread_helper+0x5/0x18
Yup, thanks. Andreas has prepared a patch which fixes this up.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-11-06 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 19:19 2.5.46: sleeping function called from illegal context at mm/slab.c:1305 Kent Yoder
2002-11-06 19:19 ` Kent Yoder
2002-11-06 19:30 ` Andrew Morton [this message]
2002-11-06 19:30 ` Andrew Morton
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=3DC96DCC.A7094AEC@digeo.com \
--to=akpm@digeo.com \
--cc=key@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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.