public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Frank R Callaghan <f.callaghan@ieee.org>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: Please Help, problem mounting jffs2
Date: Fri, 13 Jun 2003 18:54:00 -0400	[thread overview]
Message-ID: <200306131854.00636.f.callaghan@ieee.org> (raw)
In-Reply-To: <200306140052.38541.tglx@linutronix.de>

On Friday 13 June 2003 18:52, you wrote:
> On Friday 13 June 2003 21:18, David Woodhouse wrote:
> > On Fri, 2003-06-13 at 19:47, Frank R Callaghan wrote:
> > > OK, this sounds bad !  Where can I go from here ?
> >
> > Well, you can start by just commenting out the whole of both the
> > jffs2_{start,stop}_garbage_collect_thread() functions since the thread
> > is an optimisation anyway. But basically you need to find out why
> > kernel_thread() isn't working.
> >
> > It's not a uclibc bug -- it's a kernel bug, and not one in the standard
> > kernel either -- I'm inclined to suspect RTAI at this stage, although
> > you blatantly have other kernel threads running so it's not a simple and
> > obvious breakage.
>
> Maybe it's a RTAI problem. But I have JFFS2 / RTAI running on a couple of
> boards.
>
> Have you tried this with a vanilla kernel without RTAI ? If not, can you do
> that ?
>
> If RTAI is the guilty one, then consider the following:
> kernel_thread () is a syscall. RTAI captures syscalls. Maybe the syscall is
> lost anywhere in RTAI.

I have two userland processes communicating via shared mem to an rtai_module
also using two rtf's.

what I have found is after loading rtai & starting the programs - attempting 
to mount the jffs2 filesystem stops. When I killed the two processes the mount 
resumed and all works perfectly (killing the proceses forces the unload of the
shared memory & forces the closing of the rtf's)
Starting them backup after mounting sees to work fine !

I guess I can try to isolate it futher by not starting the
 fifo's / shared memory,  unless anyone can suggest a better way to locate
the problem.

TIA,
	Frank.

  reply	other threads:[~2003-06-13 23:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13 14:51 Please Help, problem mounting jffs2 Frank R Callaghan
2003-06-13 15:47 ` Sid Gluckman
2003-06-13 15:53   ` Frank R Callaghan
2003-06-13 16:31     ` David Woodhouse
2003-06-13 16:58       ` Frank R Callaghan
2003-06-13 17:39         ` David Woodhouse
2003-06-13 18:11           ` Frank R Callaghan
2003-06-13 18:28             ` David Woodhouse
2003-06-13 18:47               ` Frank R Callaghan
2003-06-13 19:18                 ` David Woodhouse
2003-06-13 22:52                   ` Thomas Gleixner
2003-06-13 22:54                     ` Frank R Callaghan [this message]
2003-06-16 16:06                       ` Frank R Callaghan
2003-06-16 16:25                         ` David Woodhouse
2003-06-16 18:21                           ` Frank R Callaghan
2003-06-16 20:21                             ` Thomas Gleixner

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=200306131854.00636.f.callaghan@ieee.org \
    --to=f.callaghan@ieee.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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