From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: jffs2 Oops on 2.6.10-rc1-mm5
Date: Wed, 17 Nov 2004 09:55:56 +0100 [thread overview]
Message-ID: <20041117085555.GA22829@synertronixx3> (raw)
Regarding my aforementioned Oops I put device table and resulting
filesystem to
http://www.ludenkalle.de/arm/device_table_new_major_minor.txt
http://www.ludenkalle.de/arm/root_scb9328
If that is not helpful, how can I start debugging this?
Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next reply other threads:[~2004-11-17 8:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 8:55 Konstantin Kletschke [this message]
2004-11-17 9:04 ` jffs2 Oops on 2.6.10-rc1-mm5 Artem B. Bityuckiy
2004-11-17 9:18 ` Konstantin Kletschke
2004-11-17 9:26 ` Artem B. Bityuckiy
2004-11-17 9:07 ` Artem B. Bityuckiy
2004-11-17 9:21 ` Konstantin Kletschke
2004-11-17 9:22 ` David Woodhouse
2004-11-17 9:30 ` Andrew Morton
2004-11-17 9:24 ` Artem B. Bityuckiy
2004-11-17 9:46 ` Konstantin Kletschke
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 12:44 Konstantin Kletschke
2004-11-16 13:00 ` Artem B. Bityuckiy
2004-11-16 13:16 ` Konstantin Kletschke
2004-11-16 16:42 ` Artem B. Bityuckiy
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=20041117085555.GA22829@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