[Top] [All Lists]

Re: problems showing up as XFS problems on kernels after 2.6.28-git2

To: Danny ter Haar <dth@xxxxxxx>
Subject: Re: problems showing up as XFS problems on kernels after 2.6.28-git2
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 7 Jan 2009 13:31:15 -0500
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20090107182415.GA12039@xxxxxxx>
References: <20090107165218.GA11132@xxxxxxx> <20090107180246.GA15218@xxxxxxxxxxxxx> <20090107182415.GA12039@xxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
On Wed, Jan 07, 2009 at 07:24:15PM +0100, Danny ter Haar wrote:
> 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)

And error when compiling the kernel or you got the same error again?
In case you can actually reproduce this error, I would be very
interested in a metadump of the filesystem that causes this 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).

The dbuegging should be really easy as long you actually have a tree /
config with which the oops happened so that the oops has the same
addresses.  Compared to your config we would need CONFIG_DEBUG_INFO,
but that's something we could turn on after the fact as it shouldn't
change the reported address.  After that we can just do a trivial
command in gdb to find the source lines for the addresses reported
(this can easily be done on the system where you compile the kernel,
doesn't have to be on the NAS box).

Btw, turning on CONFIG_XFS_DEBUG would be useful to see more output
in case you can reproduce this issue.  Just make sure to turn it
off again when you want to use the box for a real workload..

<Prev in Thread] Current Thread [Next in Thread>