> On Mon, 21 Oct 1996, Jared Mauch wrote:
>
> > Seeing a few of these in my logs:
> >
> > Exception at c012d84f (c012d85e)
> > Exception at c012d84f (c012d85e)
> > Exception at c012d84f (c012d85e)
> > Exception at c012d84f (c012d85e)
> >
> >
> > Should I be concerned and send bug reports about these in, with
> > my System.map references to the function calls that are printing these?
> >
> > (I'n not just getting these same few addresses either, I get them
> > around in various other functions too).
> >
> > - jared
> >
> >
> >
>
> I too get such exceptions. In my case the situation is
>
> Oct 22 15:02:45 pc7212 kernel: Exception at c012d63b (c012d64a)
> Oct 22 15:03:41 pc7212 kernel: Exception at c012d63b (c012d64a)
> Oct 22 15:10:06 pc7212 kernel: Exception at c012d63b (c012d64a)
> Oct 22 15:12:45 pc7212 kernel: Exception at c012d63b (c012d64a)
> Oct 22 15:12:55 pc7212 kernel: Exception at c012d63b (c012d64a)
>
> I don't know what this means, but I do know that I get page faults, i.e.,
> page_fault is called. The relevant System.map tells me of nothing at c012d63b,
> if that's relevant. Anyone got an idea of what's going on and how to track it
> down? BTW, I do have libc-5.4.7 and I'm on a laptop with Pico Power Tech.
> system chip, if that's relevant.
>
How much memory to you guys have in your machines. I never had a problem
until I upgraded my system to 32meg. Unfortunately I ended up with some
70ns ram for the upgrade and no return possible. When I added a wait state
these exceptions seem to have disappeared.
Colten Edwards