Re: Kernel BUG

[Mark Fortescue <mark@mtfhpc.demon.co.uk>]

Hi Trond,

The error occoures well after the NFS root is up and running (during the
link phase of a gcc compilation of hello.c). I thought it might be part of
the NFS system due to the backtrace.

I am currently working on a GCC-3.4.3, Binutils-2.15 version to see if it
is a compiler/binary utilities issue. The problem I have is that
GCC-3.4.3, Binutils-2.15 does not cope with printk("%llu") so I know that
there is a high potential for failure with this combination.

If it works OK, I will try with GCC-3.4.3, Binutils-2.16.1 and GCC-4.0.2,
Binutils-2.15 to try and eliminate compiler/binutils issues.

Once I have eliminated compiler/binutils bugs/features then I will start
to concentrate on the Kernel to try to identify the initial point of
failure.

Regards
	Mark Fortescue.

On Thu, 3 Nov 2005, Trond Myklebust wrote:

> On Thu, 2005-11-03 at 18:10 +0000, Mark Fortescue wrote:
> > Hi Trond,
> > 
> > I am running a sparc-linux kernel using an NFS Root and it is falling over
> > with the trace below.
> > 
> > My Kernel is not a standard kernel (I have had to tweek it to get the
> > SBUS GC3 and the 82077 floppy to work on my OPUS Sparc 1 clone).
> > 
> > Can you advise me on any known issues in the NFS Client code that might
> > enter NULL pointers into the 'slot->slots[i]' in __lookup_tag.
> > 
> > If there are none that you are aware of, are there any specific areas that
> > I should investigate with printk statements.
> 
> NFS does not ever directly access the radix tree internals: it always
> uses the API, and it always protects those operations using the
> NFS_I(inode)->req_lock.
> 
> Are you sure that radix_tree_init() is being called before the NFSroot
> stuff is started? To me, this whole thing smells of memory scribble.
> 
> Cheers,
>   Trond
> 
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/