On Sat, 29 Jun 2002, Klaus Heinz wrote:

> while compiling X on a fresh install of 1.6_BETA3 (200206260000) I
> suddenly could not use /bin/ls anymore. Any use of 'ls' or '/bin/ls'
> by me or as 'root' produced the usage message
>
>   $ ls
>   usage: ls [-1ACFLRSTWacdfgiklmnopqrstux] [file ...]
>
> Other commands worked fine, so I could use /altroot/bin/ls (after
> 'ldconfig /altroot/usr/lib' in order to use the 1.5.2 a.out binaries in
> /altroot).
>
> I stopped the compiler run, stopped the 'window' command that was
> running at this time and found myself in ddb. 'trace' showed this:
>
>   cpu_Debugger(8, e, 851000, c6f46, 7285c80) +6
>   panic(2495ea, 851000, 7285cd8, 1dd47e, 8) +9e
>   panictrap(8, 851000, 73a6ae00, 7285d2c) +5e
>   trapmmufault(8, 851000, 73a6ae00, 7285d2c, 7248cb4) +2bc
>   trap(8, 851000, 73a6ae00) +30e
>   pmap_enter_ptpage(595940, 1c000) +37a
>   pmap_enter(595940, 1c000, cc5c000, 5, 20) +84
>   uvm_fault(70beed8, 22000, 0, 1) +5cc
>   trapmmufault(88, 1429000, 23ea2, 7285fac, 7248cb4) +144
>   trap(8, 1429000, 23ea2) +30e
>   faultstkadj() + 0
>
> Trying to produce a dump failed. Although it said 'dumping to dev ...
> succeeded' the machine did not reboot but stuck again with
>
>   uvm_fault(0x27c4c8, 0x0, 0, 0x1) -> 0xe
>     type 8, code[mmu, ssw] 1468200
>   panic mmu fault
>     stopped in pid 276 (bash) at cpu_Debugger +0x6    unlk a6
>
>
> After resetting the machine, 'savecore' could not find any crash dump.

  Hmmm.  I'm running 1.6_BETA2 on my A2000/Zeus and do not see any
problems when running an X build [other than errors in the source code -
which I've just committed the fixes].  I'm just about ready to upgrade to
a newer build (which will be BETA3).  It's also possible that it may be a
60060 specific problem (my Zeus is 68040).

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA