public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Danny ter Haar <dth@dth.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: problems showing up as XFS problems on kernels after 2.6.28-git2
Date: Wed, 7 Jan 2009 19:24:15 +0100	[thread overview]
Message-ID: <20090107182415.GA12039@dth.net> (raw)
In-Reply-To: <20090107180246.GA15218@infradead.org>

Quoting Christoph Hellwig (hch@infradead.org):
> > Any kernel i try to boot after 2.6.28-git2 (i tried git4-9) 
> > sooner or later gives me an XFS error:

> The recover_uiunlinks code changed recently.  Do you still have the
> exactly kernel tree version config around so you take a look using
> gdb what exact line of code the oops is?

Since compiling a kernel on the native hardware takes "forever"
i compile them at my laptop (ubuntu 32bits) and move the kernel
to the NAS.
This morning i compiled tried git9 (still an error)
I have copied the config & system.map file to the same dir on
my server ( http://www.dth.net/kernel/c3/ )


I'm not familiar with the debugging, do you have pointer where
i could find how to do this ?
In the mean time i'll try and google some info on how...

I could copy the whole source tree over to the machine and give you 
(root) access to the machine so you can take a look yourself (if needed).

Danny

-- 

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

  reply	other threads:[~2009-01-07 18:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090107165218.GA11132@dth.net>
2009-01-07 18:02 ` problems showing up as XFS problems on kernels after 2.6.28-git2 Christoph Hellwig
2009-01-07 18:24   ` Danny ter Haar [this message]
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
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: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=20090107182415.GA12039@dth.net \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox