From: Simon Haynes <simon@baydel.com>
To: Estelle HAMMACHE <estelle.hammache@st.com>,
"Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: oops line 231 of latest readinode.c
Date: Wed, 17 Nov 2004 18:02:05 +0000 [thread overview]
Message-ID: <6C6262B2548F@baydel.com> (raw)
In-Reply-To: <419B8EFF.17DCE55B@st.com>
This crash happened on one of several systems which I have been running for
over a year. This crash came out of the blue when the system was updating a
logfile with a message. It has performed many writes during this time and I
have never seen this problem before. As far as trying to reproduce the
problem is concerned.
Some time ago I used a program to exercise the flash to try and track other
problems and as I said before I have never seen this oops before. Besides
performing more flash exercising tests I would not have a clue how I could
reproduce this.
So in summary this crash was out of the blue and I suspect that I can not
easily reproduce it without understanding more about what happened.
Cheers
Simon.
On Wednesday 17 Nov 2004 5:48 pm, Estelle HAMMACHE wrote:
> Simon Haynes wrote:
> > newfrag->ofs)' and then in the next if as newfrag->ofs contains -1. The
> > oops
>
> It seems very strange that newfrag->ofs contains -1. If you can reproduce
> it could you check where it was filled with this strange value ?
>
> Estelle
next prev parent reply other threads:[~2004-11-17 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 15:56 oops line 231 of latest readinode.c Simon Haynes
2004-11-17 17:33 ` Artem B. Bityuckiy
2004-11-17 17:48 ` Estelle HAMMACHE
2004-11-17 18:02 ` Simon Haynes [this message]
2004-11-20 18:04 ` David Woodhouse
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=6C6262B2548F@baydel.com \
--to=simon@baydel.com \
--cc=dedekind@infradead.org \
--cc=estelle.hammache@st.com \
--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