Subject: Re: gcc failure & uvm panic
To: Darren Reed <avalon@coombs.anu.edu.au>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: current-users
Date: 01/28/2000 10:16:47
On Fri, 28 Jan 2000 19:21:04 +1100 (Australia/NSW) 
 Darren Reed <avalon@coombs.anu.edu.au> wrote:

 > (Apologies for typos in advance, laptop panic'd)
 > This is with a 1.4Q snapshot.

I generally find that these sorts of problems are the result of
bad memory.

Sure wish PC hardware didn't suck...

 > 
 > First problem.
 > 
 > pmap_page_remove: unmanaged apge?
 > uvm_fault(0xf64c643c, 0x10000, 0, 3) -> 1
 > kernel: page fault trap, code=0
 > 
 > db>t
 > uvm_pagefree(f03c55bc) at uvm_pagefree+0x1a5
 > uvm_anfree(f641abe0) at uvm_anfree+0x5b
 > amap_wipeout(f64ac16c,f64cf3d4,f64cf3d4,0,f64c5ec4) at amap_wipeout+0x3b
 > amap_unref(f64cf3d4,0) at amap_unref+0x1a
 > uvm_unmap_detach(f64ab750,0,f64c643c,f64bedc8,f64ab750) at uvm_unmap_detach+0x21
 > uvm_unmap(f64c643c,0,efbfe000,f64c643c,f64c5f24) at uvm_unmap+0x9f
 > uvm_deallocate(f64c643c,0,efbfe000) at uvm_deallocate+0x38
 > exit1(f64bedc8,2100,f64c5fa8,f0211d9d,f64bedc8) at exit1+0x13c
 > sys_exit(f64bedc8,f64c5f88,f64c5f80,48208b10,ffffffff) at sys_exit+0x14
 > syscall() at syscall+0x1ed
 > --- syscall (number 1) ---
 > 
 > Second problem.
 > Compiling a -current kernel:
 > 
 > cc -O2 -Werror -Wall -Wmissing-prototypes -Wstrict-prototypes -Wnopointer-arith -Wno-main -I. -I../../../../arch -I../../../.. -nostdinc -I../../../../../crypto-intl/sys -I../../../../../gnu/sys -DLKM -DMAXUSERS=32 -D_KERNEL -Di386 -c ../../../../dev/w
  scons/wsemulconf.c
 > /usr/src/gnu/usr.bin/egcs/cc1/../../../dist/gcc/c-decl.c:4365: Internal compiler error in function grokdeclarator
 > -- wsdisplay.o --
 > /usr/src/gnu/usr.bin/egcs/common/../../../dist/gcc/stor-layout.c:218: Internal compiler error in function layout_decl
 > 
 > (then it panic'd - see above)

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>