From: Lee Revell <rlrevell@joe-job.com>
To: Joshua Baker-LePain <jlb17@duke.edu>
Cc: Gregory Brauer <greg@wildbrain.com>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com,
Jakob Oestergaard <jakob@unthought.net>,
Chris Wedgwood <cw@f00f.org>
Subject: Re: kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD)
Date: Thu, 19 May 2005 17:49:30 -0400 [thread overview]
Message-ID: <1116539371.23186.6.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.58.0505191740550.7094@chaos.egr.duke.edu>
On Thu, 2005-05-19 at 17:42 -0400, Joshua Baker-LePain wrote:
> And now I've got some OOPSes:
Did these come after the Oops you first posted, or had you rebooted
since?
If you have not rebooted since the previous Oops, then these are not
useful.
Lee
next prev parent reply other threads:[~2005-05-19 21:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 20:45 kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD) Gregory Brauer
2005-05-14 18:47 ` Chris Wedgwood
2005-05-18 17:38 ` Gregory Brauer
2005-05-18 17:59 ` Chris Wedgwood
2005-05-18 19:52 ` Jakob Oestergaard
2005-05-18 20:00 ` Joshua Baker-LePain
2005-05-18 20:20 ` Jakob Oestergaard
2005-05-18 20:53 ` Gregory Brauer
2005-05-18 20:43 ` Gregory Brauer
2005-05-19 19:43 ` Joshua Baker-LePain
2005-05-19 21:00 ` Joshua Baker-LePain
2005-05-19 21:09 ` Lee Revell
2005-05-19 21:16 ` Joshua Baker-LePain
2005-05-19 21:29 ` Steve Lord
2005-05-19 21:32 ` Steve Lord
2005-05-19 21:38 ` Joshua Baker-LePain
2005-05-19 21:43 ` Steve Lord
2005-05-19 21:35 ` Chris Wedgwood
2005-05-19 21:27 ` Chris Wedgwood
2005-05-19 21:42 ` Joshua Baker-LePain
2005-05-19 21:48 ` Joshua Baker-LePain
2005-05-19 22:03 ` Gregory Brauer
2005-08-18 18:49 ` kristina clair
2005-08-18 22:58 ` Nathan Scott
2005-08-19 14:59 ` kristina clair
2005-05-19 21:49 ` Lee Revell [this message]
2005-05-19 21:52 ` Joshua Baker-LePain
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=1116539371.23186.6.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=cw@f00f.org \
--cc=greg@wildbrain.com \
--cc=jakob@unthought.net \
--cc=jlb17@duke.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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