Subject: Re: PC164: access to user space memory stops system
krebs@qkal.sap-ag.de
Date: Fri Sep 03 1999 - 00:12:40 PDT
> On Thu, Sep 02, 1999 at 01:25:36PM +0200, krebs@qkal.sap-ag.de wrote:
> > since the do_clear_user routine stops my system (PC164 500Mhz with
> > 256 MB), i wrote my own version of it. and the result is the same,
> > as soon as i try to write the address (0x2000011CC3C) ...
>
> What the hell are you doing? The do_clear_user routine is fine.
i know, since my routine had the same results on the system.
> I disbelieve you are hanging on the same virtual address every time.
believe it or not, this is exactly what happens. i can reproduce it
everytime i try to boot from milo (from CD and disk).
i haven't yet managed to boot the system from srm, cause all kernels
i tried produced:
halted CPU 0
halt code=2
kernel stack not valid halt
PC=0
> > i don't know what causes this behaviour:
> > -corrupt memory or cache? (it works fine under nt)
>
> NT doesn't turn on machine checks. Linux does, but you should be
> getting one if you have memory problems.
upgraded the ram to 256mb about a year ago, not one machine check
under nt since then and the machine was up and running most of the
time.
i think the problem is really the machine, i got it when i was still
with digital and as far as i know it's one of the first pc164 build,
so probably there's something a mess inside the machine :-(.
Andreas
-- _____________________________________________________________________________Andreas S. Krebs
CEC Karlsruhe, SAP AG, krebs@qkal.sap-ag.de _____________________________________________________________________________
-- To unsubscribe: send e-mail to axp-list-request@redhat.com with 'unsubscribe' as the subject. Do not send it to axp-list@redhat.com
This archive was generated by hypermail 2a22 : Tue Sep 07 1999 - 16:15:05 PDT