From: Paul P Komkoff Jr <i@stingr.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: lots of scheduling-while-atomic in 2.5.44-mm6
Date: Tue, 29 Oct 2002 21:35:09 +0300 [thread overview]
Message-ID: <20021029183509.GA29935@stingr.net> (raw)
bad: scheduling while atomic!
Call Trace:
[<c011e8cb>] do_schedule+0x40b/0x410
[<c014c17b>] kswapd+0x12b/0x15e
[<c0121780>] autoremove_wake_function+0x0/0x50
[<c011e906>] preempt_schedule+0x36/0x50
[<c0121780>] autoremove_wake_function+0x0/0x50
[<c014c050>] kswapd+0x0/0x15e
[<c01056fd>] kernel_thread_helper+0x5/0x18
and this
Debug: sleeping function called from illegal context at mm/slab.c:1304
Call Trace:
[<c0147b34>] kmem_flagcheck+0x64/0x70
[<c0148457>] kmalloc+0x67/0xc0
[<c01b579c>] __jbd_kmalloc+0x2c/0x80
[<c01acb1b>] new_handle+0x2b/0x70
[<c01ace18>] journal_try_start+0xb8/0x100
[<c01a074c>] ext3_writepage_trans_blocks+0x1c/0x90
[<c019e69e>] ext3_writepage+0x2ce/0x360
[<c0182d27>] mpage_writepages+0x2f7/0x441
[<c019e3d0>] ext3_writepage+0x0/0x360
[<c0158ba6>] do_writepages+0x36/0x40
[<c0158b4f>] generic_vm_writeback+0x3f/0x60
[<c014adec>] shrink_list+0x3ec/0x650
[<c014a133>] __pagevec_release+0x23/0x40
[<c014a6ac>] __pagevec_lru_add_active+0x18c/0x1a0
[<c014b270>] shrink_cache+0x220/0x4a0
[<c0238617>] vsnprintf+0x207/0x460
[<c014bfc2>] balance_pgdat+0xc2/0x150
[<c014c1a7>] kswapd+0x157/0x15e
[<c0121780>] autoremove_wake_function+0x0/0x50
[<c011e906>] preempt_schedule+0x36/0x50
[<c0121780>] autoremove_wake_function+0x0/0x50
[<c014c050>] kswapd+0x0/0x15e
[<c01056fd>] kernel_thread_helper+0x5/0x18
feeling that it eating my fs while emitting these :)
--
Paul P 'Stingray' Komkoff 'Greatest' Jr /// (icq)23200764 /// (http)stingr.net
When you're invisible, the only one really watching you is you (my keychain)
reply other threads:[~2002-10-29 18:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021029183509.GA29935@stingr.net \
--to=i@stingr.net \
--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