lkcd
[Top] [All Lists]

Re: Alpha lcrash initialization problem - can't access memory

To: Tom Morano <tjm@xxxxxxx>
Subject: Re: Alpha lcrash initialization problem - can't access memory
From: Brian Hall <brianw.hall@xxxxxxxxxx>
Date: Tue, 02 May 2000 15:54:15 -0600 (MDT)
Cc: "Matt D.Robinson" <yakker@xxxxxxxxxxxxxx>, lkcd@xxxxxxxxxxx
In-reply-to: <3908B22A.B11911EB@sgi.com>
Reply-to: Brian Hall <brianw.hall@xxxxxxxxxx>
Sender: owner-lkcd@xxxxxxxxxxx
So basically everywhere I see a GET_BLOCK(whatever, 4, &something), I should
change the 4 to an 8?

On 27-Apr-2000 Tom Morano wrote:
> The parameters to init_liballoc() are OK. Based on this, I would guess that
> some memory is getting stomped on in or below the kl_init_kern_info()
> function
> call. You might check the block of memory causing the SEGV after returning
> from the init_liballoc() call and before the kl_init_kern_info() call. See if
> it
> looks OK at that point (I would guess the contents of this memory is change
> by
> the time you get to register_cmds()). If that's the case, then walk through
> the 
> kl_init_kern_info() function and see where the memory contents changes. From 
> looking at the kl_init_kern_info() function, I can't see where the problem
> might 
> occur (it basically just does symbol lookups and reads in the contents of
> memory 
> into some local variables).  Since the Alpha is 64 bit, I assume that the
> amount
> of
> memory being read in for these values is 8 bytes instead of 4 (and that the
> local
> variables, NUM_PHYSPAGES and MEM_MAP have been changed also). Little things
> like
> that might be a factor. Anyway, that's how I would approach narrowing it
> down.

-- 
http://www.bigfoot.com/~brihall
Linux Consultant

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