From: Richard Weinberger <richard@nod.at>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] reproducable ubifs reboot assert and corruption
Date: Wed, 29 Jan 2014 16:56:04 +0100 [thread overview]
Message-ID: <52E92494.1090407@nod.at> (raw)
In-Reply-To: <20140129154622.GB7278@gmail.com>
Am 29.01.2014 16:46, schrieb Andrew Ruder:
> On Wed, Jan 29, 2014 at 08:30:45AM +0100, Richard Weinberger wrote:
>> BTW: Can you please share your .config?
>
> No problem. FYI, this is for a board that is still in development so
> not all my changes have been submitted for inclusion yet. I would be
> happy to share the changes now if necessary but I've attached the --stat
> to show that as far as mtd/ubifs goes, i'm basically running a stock
> v3.12:
Does the issue also happen if you disable preemption?
i.e. CONFIG_PREEMPT_NONE=y
Maybe it is really a race...
Thanks,
//richard
WARNING: multiple messages have this Message-ID (diff)
From: richard@nod.at (Richard Weinberger)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] reproducable ubifs reboot assert and corruption
Date: Wed, 29 Jan 2014 16:56:04 +0100 [thread overview]
Message-ID: <52E92494.1090407@nod.at> (raw)
In-Reply-To: <20140129154622.GB7278@gmail.com>
Am 29.01.2014 16:46, schrieb Andrew Ruder:
> On Wed, Jan 29, 2014 at 08:30:45AM +0100, Richard Weinberger wrote:
>> BTW: Can you please share your .config?
>
> No problem. FYI, this is for a board that is still in development so
> not all my changes have been submitted for inclusion yet. I would be
> happy to share the changes now if necessary but I've attached the --stat
> to show that as far as mtd/ubifs goes, i'm basically running a stock
> v3.12:
Does the issue also happen if you disable preemption?
i.e. CONFIG_PREEMPT_NONE=y
Maybe it is really a race...
Thanks,
//richard
next prev parent reply other threads:[~2014-01-29 15:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 5:15 [BUG] reproducable ubifs reboot assert and corruption Andrew Ruder
2014-01-24 13:31 ` Andrew Ruder
2014-01-24 13:31 ` Andrew Ruder
2014-01-24 13:31 ` Andrew Ruder
2014-01-25 15:02 ` Richard Weinberger
2014-01-27 16:39 ` Andrew Ruder
2014-01-27 16:39 ` Andrew Ruder
2014-01-27 16:39 ` Andrew Ruder
2014-01-29 5:32 ` Andrew Ruder
2014-01-29 5:32 ` Andrew Ruder
2014-01-29 7:17 ` Richard Weinberger
2014-01-29 7:17 ` Richard Weinberger
2014-01-29 15:39 ` Andrew Ruder
2014-01-29 15:39 ` Andrew Ruder
2014-01-29 15:39 ` Andrew Ruder
2014-01-29 7:30 ` Richard Weinberger
2014-01-29 7:30 ` Richard Weinberger
2014-01-29 9:12 ` Andrea Adami
2014-01-29 15:46 ` Andrew Ruder
2014-01-29 15:46 ` Andrew Ruder
2014-01-29 15:46 ` Andrew Ruder
2014-01-29 15:56 ` Richard Weinberger [this message]
2014-01-29 15:56 ` Richard Weinberger
2014-01-29 19:13 ` Andrew Ruder
2014-01-29 19:13 ` Andrew Ruder
2014-01-29 19:56 ` Richard Weinberger
2014-01-29 19:56 ` Richard Weinberger
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=52E92494.1090407@nod.at \
--to=richard@nod.at \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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.