From: Tim Sander <tim01@iss.tu-darmstadt.de>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiformat & linux 3.0.14-rt
Date: Mon, 16 Jan 2012 13:59:48 +0100 [thread overview]
Message-ID: <201201161359.49629.tim01@iss.tu-darmstadt.de> (raw)
In-Reply-To: <1326712798.14299.53.camel@sauron.fi.intel.com>
Hi Artem
Am Montag, 16. Januar 2012 schrieb Artem Bityutskiy:
> On Mon, 2012-01-16 at 11:43 +0100, Tim Sander wrote:
> > > http://git.infradead.org/ubifs-2.6.git/commit/1f5d78dc4823a85f112aaa2d0
> > > f176 24f8c2a6c52
> > > http://git.infradead.org/ubifs-2.6.git/commit/d34315da9146253351146140e
> > > a4b 277193ee5e5f
> >
> > Do you think it is worthwhile checking the ubifs 3.0 backport with the
> > above two cherry-picked?
>
> I've pushed them to the ubifs-v3.0 back-port tree as well. But I think
> they are useless - sorry, I was confused.
Ok i was wondering that logging was causing this cind of behavoir...
> Also, if you say this happens when you run ubiformat - this is something
> about your flash driver. Do you use NOR or NAND? Can you detect which
> interrupt takes too much time? If the theory is that this is your flash
> driver interrupt - can you verify it by injecting some instrumentation
> to the interrupt handler?
This is a arm i.mx35 (pcm43) platform using the nor and nand driver. The
mxc_nand driver is loaded later which seems to be around the same time this
message:
"sched: RT throttling activated" comes up and the ubi on the nand gets
attached. I will see what if i can dig s.t. up with the instrumentation and
will report back.
Best regards
Tim
next prev parent reply other threads:[~2012-01-16 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 9:06 ubiformat & linux 3.0.14-rt Tim Sander
2012-01-13 15:34 ` Artem Bityutskiy
2012-01-16 10:43 ` Tim Sander
2012-01-16 11:19 ` Artem Bityutskiy
2012-01-16 12:59 ` Tim Sander [this message]
2012-01-16 13:04 ` Artem Bityutskiy
2012-01-16 14:59 ` Tim Sander
2012-01-18 14:17 ` Artem Bityutskiy
2012-01-18 14:38 ` Tim Sander
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=201201161359.49629.tim01@iss.tu-darmstadt.de \
--to=tim01@iss.tu-darmstadt.de \
--cc=dedekind1@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox