All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank R Callaghan <f.callaghan@ieee.org>
To: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: Please Help, problem mounting jffs2
Date: Fri, 13 Jun 2003 14:47:45 -0400	[thread overview]
Message-ID: <200306131447.45138.f.callaghan@ieee.org> (raw)
In-Reply-To: <1055528889.3632.180.camel@passion.cambridge.redhat.com>

On Friday 13 June 2003 02:28 pm, David Woodhouse wrote:
> On Fri, 2003-06-13 at 19:11, Frank R Callaghan wrote:
> > On Friday 13 June 2003 01:39 pm, David Woodhouse wrote:
> > > Looks like it's waiting for the garbage collect thread. What happened
> > > to it? Can you put a printk into the very beginning of
> > > 'jffs2_garbage_collect_thread()' in background.c, and another printk
> > > after the daemonize() call.
> >
> > Like this:
> >
> > static int jffs2_garbage_collect_thread(void *_c)
> > {
> >         struct jffs2_sb_info *c = _c;
> >
> >         D1(printk(KERN_DEBUG "****jffs2_garbage_collect_thread
> > start...\n"));
> >
> > -----------------
> > No extra output !!!
> > -----------------
>
> Just like that... in which case for some reason kernel_thread() is not
> working. What architecture is it?
>

i486 ELAN(SC520)

> > > Also hit SysRq-T and see exactly where the mount process is waiting --
> > > I suspect it's in jffs2_start_garbage_collect_thread().
> >
> > I'm running this on an embedded system and the console is via minicom
> > (ttyS1), SysRq-T doesn't seem to work !
>
> Hmmm. It may require that there's something in userspace trying to read
> from the port. There are also hacks around to enable sysrq by echoing
> letters to a /proc file. Doesn't really matter -- it's fairly obvious
> it's never actually making it into the kernel thread.

OK, this sounds bad !  Where can I go from here ?
I really need this flash working for the product to be viable !
Is this a kernel bug ? uclibc ? RTAI ?
Is there anyway to hack the code to get it working ?

Help !!!

  reply	other threads:[~2003-06-13 18:59 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 [this message]
2003-06-13 19:18                 ` David Woodhouse
2003-06-13 22:52                   ` Thomas Gleixner
2003-06-13 22:54                     ` Frank R Callaghan
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=200306131447.45138.f.callaghan@ieee.org \
    --to=f.callaghan@ieee.org \
    --cc=dwmw2@infradead.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.