From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: sleeping function called from illegal context at mm/slab.c:1723
Date: Tue, 25 Mar 2003 15:01:19 +0100 [thread overview]
Message-ID: <200303251501.22938.schlicht@uni-mannheim.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
Every second I get following Debug message with kernel 2.5.66:
Debug: sleeping function called from illegal context at mm/slab.c:1723
Call Trace:
[<c0124ba2>] __might_sleep+0x52/0x60
[<c014f4bd>] kmalloc+0x5d/0x16c
[<c027ab6c>] accel_cursor+0xcc/0x2c0
[<c0121fb8>] try_to_wake_up+0x23c/0x3b4
[<c027af20>] fb_vbl_handler+0x74/0x8c
[<c012281f>] scheduler_tick+0x37b/0x384
[<c01290ca>] profile_hook+0x1e/0x39
[<c011c7be>] smp_local_timer_interrupt+0xe/0xa0
[<c027980f>] cursor_timer_handler+0xf/0x28
[<c0130ea6>] run_timer_softirq+0x1ca/0x2cc
[<c0279800>] cursor_timer_handler+0x0/0x28
[<c012c942>] do_softirq+0x52/0xac
[<c010d468>] do_IRQ+0x2cc/0x2e4
[<c010b958>] common_interrupt+0x18/0x20
This message was not present with 2.5.65. I am using the VESA VGA frame buffer
as following part of the boot.msg shows:
<6>vesafb: framebuffer at 0xe0000000, mapped to 0xd0800000, size 65536k
<6>vesafb: mode is 1024x768x16, linelength=2048, pages=0
<6>vesafb: protected mode interface info at c000:c2c0
<6>vesafb: scrolling: redraw
<6>vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
<6>fb0: VESA VGA frame buffer device
My .config file is attached.
Thomas Schlichter
[-- Attachment #2: config-2.5.66.gz --]
[-- Type: application/x-gzip, Size: 11604 bytes --]
next reply other threads:[~2003-03-25 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 14:01 Thomas Schlichter [this message]
2003-03-25 12:05 ` dan carpenter
2003-03-26 5:36 ` James Simmons
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=200303251501.22938.schlicht@uni-mannheim.de \
--to=schlicht@uni-mannheim.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®