public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: freeze when mounting fs
Date: Fri, 18 Feb 2005 17:36:37 +0100	[thread overview]
Message-ID: <20050218163636.GD5926@synertronixx3> (raw)
In-Reply-To: <1108742958.24721.295.camel@tglx.tec.linutronix.de>

Am 2005-02-18 17:09 +0100 schrieb Thomas Gleixner:
> On Fri, 2005-02-18 at 16:48 +0100, Konstantin Kletschke wrote:
> 
> > CONFIG_JFFS2_FS_DEBUG=2
> 
> Please use level 1
> 
> > And when mounting functional rootfs it speaks a lot, but:
> 
> What happens when you mount the non-functional one ? Can you please

Nothing.

> provide logs via serial console. klogd does not work for logging of that
> stuff.

Even with level 3 _nothing_ happens.

> > Rootfs is at http://ludenkalle.de/mtd/52
> 
> The image is clean. There is no problem to see.
> 
> It would be interesting to have a binary image after you programmed it
> to FLASH. cat /dev/mtdX >flash.img

I will try what I can do or reproduce it later, I am sure my device
table triggered a bug or some sort of that:

I removed 3 lines mungling up some access permissions of subdirectories
under /home and now the image gets mounted.
I am fighting with svn ATM to get the actual change...

Konsti

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

  reply	other threads:[~2005-02-18 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18 15:42 freeze when mounting fs Konstantin Kletschke
2005-02-18 15:48 ` Artem B. Bityuckiy
2005-02-18 16:01   ` Konstantin Kletschke
2005-02-18 16:12     ` Thomas Gleixner
2005-02-18 16:15     ` Artem B. Bityuckiy
2005-02-18 15:48 ` Konstantin Kletschke
2005-02-18 16:09   ` Thomas Gleixner
2005-02-18 16:36     ` Konstantin Kletschke [this message]
2005-02-21  8:21 ` Konstantin Kletschke

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=20050218163636.GD5926@synertronixx3 \
    --to=lists@ku-gbr.de \
    --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