From: Artem Bityutskiy <dedekind1@gmail.com>
To: Nigel Hathaway <nigel.hathaway@node-h.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS kernel oops
Date: Fri, 09 Mar 2012 09:56:01 +0200 [thread overview]
Message-ID: <1331279761.22872.24.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <000201ccf2d8$3cb7adb0$b6270910$@node-h.com>
On Fri, 2012-02-24 at 09:39 +0000, Nigel Hathaway wrote:
> Code: 7c420400 1040000c 00000000 <c0820010> 14400005 00000000 00600821
> e0810010 102000b0
> Disabling lock debugging due to kernel taint
>
> The kernel version is 3.6.31.12 with real-time extensions (patches) compiled
> with "mips-linux-gnu-gcc (Sourcery G++ Lite 4.4-303) 4.4.1"
>
> We have seen this posted before here:
>
> http://lists.infradead.org/pipermail/linux-mtd/2011-December/038852.html
>
> For us, UBIFS is not read-only. Any ideas what could be causing this and/or
> whether such an issue has been fixed in later kernels?
May be someone corrupting memory, dunno :-( I guess this needs some
hardcore debugging...
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2012-03-09 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 9:39 UBIFS kernel oops Nigel Hathaway
2012-03-09 7:56 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-24 15:58 Brian Foster
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=1331279761.22872.24.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nigel.hathaway@node-h.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