From: Cal Page <pagcal@runbox.com>
To: ubifs <linux-mtd@lists.infradead.org>
Subject: ubifs: another scheduling while atomic back trace
Date: Wed, 17 Dec 2008 12:10:14 -0500 [thread overview]
Message-ID: <49493276.703@runbox.com> (raw)
Here's a second backtrace. When the ubifs partition fills up, I get
'scheduling while atomic' from schedule().
Any ideas?
Cal Page
Backtrace:
[<c0e1e580>] (schedule+0x0/0x6dc) from [<c0e1ff68>] (__mutex_lock_slowpath+0x84/0xe4)
[<c0e1fee4>] (__mutex_lock_slowpath+0x0/0xe4) from [<c0e1fd48>] (mutex_lock+0x20/0x28)
r6 = C4C1D574 r5 = 00000000 r4 = C529A000
[<c0e1fd28>] (mutex_lock+0x0/0x28) from [<c0c46460>] (make_reservation+0x78/0x6d0)
[<c0c463e8>] (make_reservation+0x0/0x6d0) from [<c0c474f0>] (ubifs_jnl_write_data+0x1e4/0x334
[<c0c4730c>] (ubifs_jnl_write_data+0x0/0x334) from [<c0c498c4>] (do_writepage+0xbc/0x204)
[<c0c49808>] (do_writepage+0x0/0x204) from [<c0c4aaa0>] (ubifs_writepage+0x240/0x278)
[<c0c4a860>] (ubifs_writepage+0x0/0x278) from [<c0bb6ce8>] (generic_writepages+0x1e8/0x388)
[<c0bb6b00>] (generic_writepages+0x0/0x388) from [<c0bb6ed0>] (do_writepages+0x48/0x60)
[<c0bb6e88>] (do_writepages+0x0/0x60) from [<c0bf2e20>] (__writeback_single_inode+0x1b8/0x384)
r4 = 00000004
[<c0bf2c68>] (__writeback_single_inode+0x0/0x384) from [<c0bf32a0>] (sync_sb_inodes+0x1d8/0x2c8)
[<c0bf30c8>] (sync_sb_inodes+0x0/0x2c8) from [<c0bf35a4>] (generic_sync_sb_inodes+0x10/0x14)
[<c0bf3594>] (generic_sync_sb_inodes+0x0/0x14) from [<c0c65534>] (ubifs_budget_space+0x98c/0xe98)
[<c0c64ba8>] (ubifs_budget_space+0x0/0xe98) from [<c0c4a578>] (ubifs_prepare_write+0x18c/0x1a4)
[<c0c4a3ec>] (ubifs_prepare_write+0x0/0x1a4) from [<c0bb22f4>] (generic_file_buffered_write+0x2a0/0x694)
[<c0bb2058>] (generic_file_buffered_write+0x4/0x694) from [<c0bb2c24>] (__generic_file_aio_write_nolock+0x53c/0x5bc)
[<c0bb26e8>] (__generic_file_aio_write_nolock+0x0/0x5bc) from [<c0bb2d20>] (generic_file_aio_write+0x7c/0xf0)
[<c0bb2ca8>] (generic_file_aio_write+0x4/0xf0) from [<c0c49220>] (ubifs_aio_write+0x1b4/0x244)
[<c0c49070>] (ubifs_aio_write+0x4/0x244) from [<c0bd2718>] (do_sync_write+0xc0/0x114)
[<c0bd2658>] (do_sync_write+0x0/0x114) from [<c0bd30d8>] (vfs_write+0xb8/0x194)
r6 = C529BF80 r5 = BED58AF8 r4 = C5450B40
[<c0bd3020>] (vfs_write+0x0/0x194) from [<c0bd37f0>] (sys_write+0x4c/0x80)
r7 = 00000004 r6 = 00000000 r5 = 0012C000 r4 = C5450B40
[<c0bd37a4>] (sys_write+0x0/0x80) from [<c0b6fde0>] (ret_fast_syscall+0x0/0x2c)
r6 = 4001D660 r5 = BED58AF8 r4 = 00002000
Code: e59f0650 ebf5b474 ebf55526 e3a03000 (e5833000)
<6>prphw_disable Disable PRP CH 2
Kernel panic - not syncing: Aiee, killing interrupt handler!
next reply other threads:[~2008-12-17 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 17:10 Cal Page [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-18 13:34 ubifs: another scheduling while atomic back trace Cal Page
2008-12-18 13:53 ` Artem Bityutskiy
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=49493276.703@runbox.com \
--to=pagcal@runbox.com \
--cc=linux-mtd@lists.infradead.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.