From: Jochen Hein <jochen@jochen.org>
To: linux-kernel@vger.kernel.org
Subject: [2.6.0-test8] might sleep
Date: Mon, 20 Oct 2003 21:53:55 +0200 [thread overview]
Message-ID: <87ekx78z3g.fsf@echidna.jochen.org> (raw)
>From the kernel log:
Oct 20 21:28:54 gswi1164 kernel: PID hash table entries: 512 (order 9:
4096 bytes)
Oct 20 21:28:54 gswi1164 kernel: Detected 232.193 MHz processor.
Oct 20 21:28:54 gswi1164 kernel: Console: colour dummy device 80x25
Oct 20 21:28:54 gswi1164 kernel: in_atomic():1, irqs_disabled():1
Oct 20 21:28:54 gswi1164 kernel: Call Trace:
Oct 20 21:28:54 gswi1164 kernel: [__might_sleep+160/208] __might_sleep+0xa0/0xd0
Oct 20 21:28:54 gswi1164 kernel: [acquire_console_sem+59/96] acquire_console_sem+0x3b/0x60
Oct 20 21:28:54 gswi1164 kernel: [register_console+149/480] register_console+0x95/0x1e0
Oct 20 21:28:54 gswi1164 kernel: [con_init+514/576] con_init+0x202/0x240
Oct 20 21:28:54 gswi1164 kernel: [_stext+0/96] rest_init+0x0/0x60
Oct 20 21:28:54 gswi1164 kernel: [console_init+52/80] console_init+0x34/0x50
Oct 20 21:28:54 gswi1164 kernel: [start_kernel+190/368] start_kernel+0xbe/0x170
Oct 20 21:28:54 gswi1164 kernel: [unknown_bootoption+0/272] unknown_bootoption+0x0/0x110
Oct 20 21:28:54 gswi1164 kernel:
Oct 20 21:28:54 gswi1164 kernel: Memory: 93728k/98112k available (1877k kernel code, 3876k reserved, 713k data, 140k init, 0k highmem)
Oct 20 21:28:55 gswi1164 default.hotplug[142]: invoke /etc/hotplug/usb.agent ()
Oct 20 21:28:55 gswi1164 default.hotplug[143]: invoke /etc/hotplug/usb.agent ()
Oct 20 21:28:55 gswi1164 kernel: in_atomic():1, irqs_disabled():0
Oct 20 21:28:55 gswi1164 kernel: Call Trace:
Oct 20 21:28:55 gswi1164 kernel: [__might_sleep+160/208] __might_sleep+0xa0/0xd0
Oct 20 21:28:55 gswi1164 kernel: [kmem_cache_alloc+474/480] kmem_cache_alloc+0x1da/0x1e0
Oct 20 21:28:55 gswi1164 kernel: [printk+294/384] printk+0x126/0x180
Oct 20 21:28:55 gswi1164 kernel: [kmem_cache_create+362/1696] kmem_cache_create+0x16a/0x6a0
Oct 20 21:28:55 gswi1164 kernel: [mem_init+405/512] mem_init+0x195/0x200
Oct 20 21:28:55 gswi1164 kernel: [_stext+0/96] rest_init+0x0/0x60
Oct 20 21:28:55 gswi1164 kernel: [kmem_cache_init+281/704] kmem_cache_init+0x119/0x2c0
Oct 20 21:28:55 gswi1164 kernel: [start_kernel+206/368] start_kernel+0xce/0x170
Oct 20 21:28:55 gswi1164 kernel: [unknown_bootoption+0/272] unknown_bootoption+0x0/0x110
Oct 20 21:28:55 gswi1164 kernel:
Oct 20 21:28:55 gswi1164 kernel: Calibrating delay loop... 455.68 BogoMIPS
Oct 20 21:28:55 gswi1164 kernel: Security Scaffold v1.0.0 initialized
Jochen
--
#include <~/.signature>: permission denied
next reply other threads:[~2003-10-20 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 19:53 Jochen Hein [this message]
2003-10-20 20:40 ` [2.6.0-test8] might sleep Roland Dreier
-- strict thread matches above, loose matches on Subject: below --
2003-10-20 20:23 Mudama, Eric
2003-10-20 21:22 ` Jochen Hein
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=87ekx78z3g.fsf@echidna.jochen.org \
--to=jochen@jochen.org \
--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 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.