linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Glenn Toshi Martin" <glenn@centurysys.co.jp>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: 405GP f_dentry panics
Date: Thu, 11 Jan 2001 09:58:52 +0900	[thread overview]
Message-ID: <007b01c07b69$aa98ff70$0664a8c0@centurysys.co.jp> (raw)
In-Reply-To: 3A5C823A.6353DCE2@home.se


Hi all,

We have a custom 405GP board and the "Walnut" board. We are using the
2.4-test2 (Version released Nov 26 2000) kernel supplied via the Montavista
web site. Our custom board has an IDE harddisk while the Walnut board uses
NFS. We are experiencing f_dentry = 0 problems when untarring a 750 MB file
(This seems to lead to memory corruption and hence kernel panics). The
problem is more pronounced when using the IDE but nevertheless occurs when
using the Walnut board over NFS. This appears to be a known problem, but
would like to know whether the problem can be fixed, and if so what is
required to fix it? Or is there a better workaround to the ones currently
available?
We have another problem that may relate to the above. During the untar
process of large files including the one mentioned above, we get a file
system error "Could not write to file: bad file descriptor" every now and
then (both NFS and IDE, more frequently on the IDE). Could anyone shed light
on this problem?

Thanks

Glenn


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-01-11  0:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10 15:39 2.4 Kernel for mpc860 Thomas
2001-01-10 18:55 ` Borlizzi Giacomo
2001-01-11  0:58 ` Glenn Toshi Martin [this message]
2001-01-11 17:56   ` 405GP f_dentry panics Frank Rowand
2001-01-18 19:35     ` Booting MCP750 stand alone Tom Shaver
2001-01-18 16:50       ` Matt Porter

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='007b01c07b69$aa98ff70$0664a8c0@centurysys.co.jp' \
    --to=glenn@centurysys.co.jp \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).