public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thayne Harbaugh <tharbaugh@lnxi.com>
To: philwil@earthlink.net
Cc: Russ.Dill@asu.edu
Cc: linux-mtd@lists.infradead.org
Subject: Re: Jffs2 write Error
Date: 17 Nov 2003 07:35:32 -0700	[thread overview]
Message-ID: <1069079731.14277.71.camel@tubarao> (raw)
In-Reply-To: <3FB6E4AA.27A7AAE1@earthlink.net>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Sat, 2003-11-15 at 19:44, Phil Wilshire wrote:
> I have found my original problem.
> 
> The 
>    do_write_oneword 
> routine in 
>   cfi_cmdset_0002.c 
> 
> was being given values for datum wider than the 16 bits
> we are allowed to write to the device.
> The readback being limited to 16 bits, of course , failed to match
> 
> 
> The data was being given to do_write_oneword by gc.c 

Why is gc.c passing values that aren't appropriate?

> Here is the error output
> 
> Last[3] is 66, datum is 8000066 addr 3028c
> Write of 49 bytes at 0x00030264 failed. returned -5, retlen 40
> jffs2_write_dirent in garbage_collect_dirent failed: -5
> 
> As you can see 8000066 is impossible to write to a 16 bit device.

Quite obvious.

> I put an extra check on the word size in do_write_oneword and the error just went away.

What check did you put in?  What do you mean by "the error just went
away?"  That sounds like a Heisenbug (race) more than a real solution.

-- 
Thayne Harbaugh
Linux Networx

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-11-17 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 13:37 Jffs2 write Error Phil Wilshire
     [not found] ` <1068937683.17897.21.camel@localhost>
2003-11-16  2:44   ` Phil Wilshire
2003-11-17 14:35     ` Thayne Harbaugh [this message]
2003-11-17 16:51       ` Phil Wilshire
     [not found] <E1AHKvt-0001UM-VZ@pentafluge.infradead.org>
2003-11-06 18:51 ` Joan Dyer
2003-11-08  0:24   ` David Woodhouse
2003-11-10 17:56     ` Joan Dyer

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=1069079731.14277.71.camel@tubarao \
    --to=tharbaugh@lnxi.com \
    --cc=Russ.Dill@asu.edu \
    --cc=philwil@earthlink.net \
    /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