From: Artem Bityutskiy <dedekind@infradead.org>
To: Cal Page <pagcal@runbox.com>
Cc: ubifs <linux-mtd@lists.infradead.org>
Subject: Re: ubifs: BUG: scheduling while atomic - when runs out of space
Date: Wed, 17 Dec 2008 15:20:07 +0200 [thread overview]
Message-ID: <1229520007.17960.34.camel@sauron> (raw)
In-Reply-To: <4948FC5F.10907@runbox.com>
On Wed, 2008-12-17 at 08:19 -0500, Cal Page wrote:
> When I run a ubifs partition out of space, I get
>
> BUG: scheduling while atomic: tar/0xffffffff/3324
>
> repeated until I stop trying to write the partition.
>
> What's wrong? Who went atomic in ubi/ubifs? If I wait a minute, disk
> usage drops from 100% to 75%, no doubt due to garbage collection.
Please, provide more information. You probably have stack dump at least?
Did you look at dmesg output?
What is your platform/kernel/flash/UBI volume size?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2008-12-17 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 13:19 ubifs: BUG: scheduling while atomic - when runs out of space Cal Page
2008-12-17 13:20 ` Artem Bityutskiy [this message]
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=1229520007.17960.34.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pagcal@runbox.com \
/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