All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Danny ter Haar <dth@dth.net>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: problems showing up as XFS problems on kernels after 2.6.28-git2
Date: Sat, 17 Jan 2009 18:38:24 +1100	[thread overview]
Message-ID: <20090117073824.GK8071@disturbed> (raw)
In-Reply-To: <20090116204346.GA5117@dth.net>

On Fri, Jan 16, 2009 at 09:43:46PM +0100, Danny ter Haar wrote:
> Quoting Danny ter Haar (dth@dth.net):
> > I'm stuck in trying to bisect the problem.
> > I restarted from scratch and same result:
> 
> [SNIP for bravery] 
> 
> > In the mean time i compiled/ran 2.6.29-rc1-git3 but it (as expected) barfed:
> > 
> > Al netconsole loggins are in my directory: http://www.dth.net/kernel/c3/
> > 
> > [F1] ;-)
> 
> This was to my way to say "HELP"

Sorry for not getting back to you sooner. I think that Alexander
tripped over this same problem during his bisect.  If you follow the
thread from here:

http://oss.sgi.com/archives/xfs/2009-01/msg00496.html

You'll see that Alexander had the same problem and managed
to continue the bisect once he copied the xfs_btree_trace.h
header file from top-of-tree back into the broken commits.

I hope this helps (and I hope that the bisect lands on the
same commit that it did for Alexander).

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-01-17  7:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 16:52 problems showing up as XFS problems on kernels after 2.6.28-git2 dth
2009-01-07 18:02 ` Christoph Hellwig
2009-01-07 18:24   ` Danny ter Haar
2009-01-07 18:31     ` Christoph Hellwig
2009-01-07 18:44       ` Danny ter Haar
2009-01-07 18:52         ` Christoph Hellwig
2009-01-07 22:09           ` Danny ter Haar
2009-01-08  0:38           ` Danny ter Haar
2009-01-07 18:56         ` Christoph Hellwig
2009-01-07 19:01           ` Danny ter Haar
2009-01-08 21:56           ` Danny ter Haar
2009-01-09  0:46             ` Dave Chinner
2009-01-09  1:26               ` Danny ter Haar
2009-01-09  2:08                 ` Dave Chinner
2009-01-09  6:10                   ` Danny ter Haar
2009-01-09 19:44                     ` Christoph Hellwig
2009-01-09 19:51                       ` Danny ter Haar
2009-01-09 19:58                         ` Christoph Hellwig
2009-01-09 21:42                           ` Danny ter Haar
2009-01-09 22:01                             ` Christoph Hellwig
2009-01-09 22:23                               ` Danny ter Haar
2009-01-13 20:04                               ` Danny ter Haar
2009-01-16 20:43                                 ` Danny ter Haar
2009-01-17  7:38                                   ` Dave Chinner [this message]
2009-01-17 23:25                                     ` Danny ter Haar
2009-01-18  2:50                                       ` Danny ter Haar
2009-01-19  3:17                                       ` Dave Chinner
2009-01-14 19:42 ` Tino Keitel
2009-01-14 19:44 ` Tino Keitel
2009-01-14 19:44   ` Tino Keitel

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=20090117073824.GK8071@disturbed \
    --to=david@fromorbit.com \
    --cc=dth@dth.net \
    --cc=hch@infradead.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.