From: Jeffrey Hutzelman <jhutz@cmu.edu>
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: Fri, 20 May 2005 15:53:07 -0400 [thread overview]
Message-ID: <2D6D4407013EDC38C0E580C0@sirius.fac.cs.cmu.edu> (raw)
In-Reply-To: <20050520191207.15E3D29528@smtpauth.easystreet.com>
On Friday, May 20, 2005 12:12:05 PM -0700 ted creedon
<tcreedon@easystreet.com> wrote:
> Gcc -dumpmachine #should prints out i586-suse-linux for a P III here.
>
> I'd try a fresh single processor machine and force a 2.6 kernel, module
> and afs recompile for a i586.
>
> SuSE 9.3 costs $90 and it solved a similar problem noted in the mailings.
> In fact the YasT installed openafs binaries ran fine.
>
> The ksymoops man page has a script to tail -f /var/log/messages|ksymoops1
> explained.
>
> Are you sure there isn't a memory problem? I'm running out of ideas.
> tedc
You're really trying too hard. The oops in question clearly shows EIP in
osi_Panic(), which is _supposed_ to result in a crash. So, stop trying to
analyze the mechanism by which osi_Panic forces a fault, and instead go
look at your logs and tell us what the panic string was.
next prev parent reply other threads:[~2005-05-20 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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] <20050512140505.6574EB01E@smtpauth.easystreet.com>
2005-05-19 8:38 ` 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=2D6D4407013EDC38C0E580C0@sirius.fac.cs.cmu.edu \
--to=jhutz@cmu.edu \
--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®