From: Santiago Garcia Mantinan <manty@udc.es>
To: Alexander Viro <viro@math.psu.edu>
Cc: Santiago Garcia Mantinan <manty@udc.es>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at inode.c:654!
Date: Mon, 28 May 2001 10:13:20 +0200 [thread overview]
Message-ID: <20010528101320.A853@man.beta.es> (raw)
In-Reply-To: <Pine.GSO.4.21.0105261404010.413-100000@weyl.math.psu.edu>
> Lovely... It's one of the long lists and these asserts (lines 650 and 654)
> are exactly what would happen if it was corrupted at some place. OTOH, it
> may be for real - i.e. real inodes in wrong state getting on the list, rather
> than corrupted pointer.
You were right, corrupted pointer.
It was due to general memory corruption caused by RAM problems, sorry, it
happened just as I switched to 2.4.5 and I blamed it, it probably started
failing now, after months without any problem, because of the high
temperatures we are having this days.
Thanks for your help and sorry to have disturbed you all for not making a
memtest before :-(
Regards...
--
Manty/BestiaTester -> http://manty.net
next prev parent reply other threads:[~2001-05-28 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 17:37 kernel BUG at inode.c:654! Santiago Garcia Mantinan
2001-05-26 18:12 ` Alexander Viro
2001-05-28 8:13 ` Santiago Garcia Mantinan [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-18 18:51 Kurt Roeckx
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=20010528101320.A853@man.beta.es \
--to=manty@udc.es \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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