public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Foster <brian.foster@maxim-ic.com>
To: <linux-mtd@lists.infradead.org>
Cc: nigel.hathaway@node-h.com
Subject: Re: UBIFS kernel oops
Date: Fri, 24 Feb 2012 16:58:52 +0100	[thread overview]
Message-ID: <201202241658.52516.brian.foster@maxim-ic.com> (raw)

nigel.hathaway wrote:
> We are seeing the following:
> 
> Oops[#1]:
>[ ... ]
> PrId  : 59019381 (MIPS 24Kc)

 Nice to see another MIPS user....!  ;-)

>[ ... ]
> The kernel version is 3.6.31.12 with real-time extensions [ ... ]

 This is a *guess*, and quite possibly not a very
 good one (Sorry!).  Do you have commits?:

   cd1510cb5 random: Remove unused inode variable
   a996996dd random: drop weird m_time/a_time manipulation

 We had a devil of a time on our 2.6.30 MIPS system
 with a very(!) *vaguely* similar-ish issue until I
 back-ported those commits.  They may already be in
 your 2.6.31, I'm not sure.

 I also back-ported two other commits, albeit these
 are not known to be related to any problems we had:

   b86a2c56e UBI: do not switch to R/O mode on read errors
   90bf0265e UBI: introduce new constants

 Very probably a Red Herring, Sorry!
cheers,
	-blf-

-- 
Brian Foster
Principal MTS, Software        |  La Ciotat, France
Maxim Integrated Products      |  Web:  http://www.maxim-ic.com/

             reply	other threads:[~2012-02-24 16:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 15:58 Brian Foster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-24  9:39 UBIFS kernel oops Nigel Hathaway
2012-03-09  7:56 ` 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=201202241658.52516.brian.foster@maxim-ic.com \
    --to=brian.foster@maxim-ic.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