From: Dimitris Zilaskos <dzila@tassadar.physics.auth.gr>
To: ted creedon <tcreedon@easystreet.com>
Cc: openafs-info@openafs.org, linux-kernel@vger.kernel.org
Subject: RE: [OpenAFS] Re: Openafs 1.3.78 and kernel 2.4.29 oopses , same for 2.4.30 and openafs 1.3.82
Date: Thu, 19 May 2005 11:38:37 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.62.0505191135590.32055@tassadar.physics.auth.gr> (raw)
In-Reply-To: <20050512140505.6574EB01E@smtpauth.easystreet.com>
> Dimitris,
>
> Glad to be of help. Send a response to the mailing list after a week or so
> of operation.
>
> This is a very important step and not documented.
>
> ted
>
> -----Original Message-----
> From: Dimitris Zilaskos [mailto:dzila@tassadar.physics.auth.gr]
> Sent: Wednesday, May 11, 2005 10:07 PM
> To: ted creedon
> Cc: openafs-info@openafs.org; linux-kernel@vger.kernel.org
> Subject: RE: [OpenAFS] Re: Openafs 1.3.78 and kernel 2.4.29 oopses , same
> for 2.4.30 and openafs 1.3.82
>
> On Mon, 9 May 2005, ted creedon wrote:
>
>> Looks like a compile problem if there's a symbol table error.
>>
>> To eliminate that as a cause:
>> Make bzImage;make modules;make modules_install;make install; Reboot
>> into the new image Run regen.sh then ./configure and built a new
>> openafs system; install ane test it.
>>
>> I think there may be small differences in the m4 macros between
>> various operating systems.
>>
>> This is the only way I can get reliable compiles. I have had one
>> server crash with 1.3.81 but I suspect the software raid filesystem.
>>
It's been 9 days now of heavy usage , and not a single oops
occured again. Problem solved:)
Best regards ,
--
=============================================================================
Dimitris Zilaskos
Department of Physics @ Aristotle University of Thessaloniki , Greece
PGP key : http://tassadar.physics.auth.gr/~dzila/pgp_public_key.asc
http://egnatia.ee.auth.gr/~dzila/pgp_public_key.asc
MD5sum : de2bd8f73d545f0e4caf3096894ad83f pgp_public_key.asc
=============================================================================
next parent reply other threads:[~2005-05-19 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050512140505.6574EB01E@smtpauth.easystreet.com>
2005-05-19 8:38 ` Dimitris Zilaskos [this message]
[not found] <20050519131517.B0079B01C@smtpauth.easystreet.com>
2005-05-20 16:17 ` Dimitris Zilaskos
2005-05-20 18:06 ` ted creedon
2005-05-20 18:53 ` Dimitris Zilaskos
2005-05-20 19:12 ` ted creedon
2005-05-20 19:53 ` Jeffrey Hutzelman
2005-05-20 20:34 ` Dimitris Zilaskos
2005-05-20 19:47 ` ted creedon
2005-05-20 18:20 ` ted creedon
2005-05-20 20:26 ` Dimitris Zilaskos
[not found] <20050509132508.55483B024@smtpauth.easystreet.com>
2005-05-12 5:07 ` Dimitris Zilaskos
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=Pine.LNX.4.62.0505191135590.32055@tassadar.physics.auth.gr \
--to=dzila@tassadar.physics.auth.gr \
--cc=linux-kernel@vger.kernel.org \
--cc=openafs-info@openafs.org \
--cc=tcreedon@easystreet.com \
/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
all inboxes | Powered by JetHome®