Port-vax archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: netbsd on vax 11/730; booting in sim
Yup, it happened again.
I got as far as compiling in libm when it hung.
Manuel Bouyer wrote:
On Thu, Jan 08, 2009 at 09:18:07PM +0100, Johnny Billquist wrote:
How long ago did you try it ? It looks like the pagedaemon issues that
got fixed by ad@ some time ago (the fixes are in netbsd-5 too now)
I think it was late november or early december.
The pagedaemon infinite loop was fixed on 12 decemeber in HEAD and pulled
up to netbsd-5 on 27 decemeber. Make sure to try a netbsd-5 kernel which
includes the fix.
This was now definitely with a newer kernel than that.
Sure, I can try again. I'll fire up my 4000/90 tonight, install the
latest 5.0_BETA and start a built. We'll see how long it takes for it to
hang (I definitely expects it to still hang, but we'll see...)
If it does please try to enter ddb and 'show uvm'
login: Stopped in pid 2087.1 (vax--netbsdelf-l) at
netbsd:cpu_Debugger+0x15: m
fpr $h5, r1
db> sho uvm
Current UVM status:
pagesize=4096 (0x1000), pagemask=0xfff, pageshift=12
30985 VM pages: 12061 active, 8060 inactive, 1229 wired, 6532 free
pages 5327 anon, 14592 file, 1431 exec
freemin=154, free-target=205, wired-max=10328
faults=24222935, traps=98111291, intrs=23252933, ctxswitch=6789578
softint=6155554, syscalls=98360535, swapins=42, swapouts=52
fault counts:
noram=43, noanon=0, pgwait=0, pgrele=0
ok relocks(total)=6819(6819), anget(retrys)=2388950(352),
amapcopy=2403398
neighbor anon/obj pg=2386916/37979563, gets(lock/unlock)=9601381/6467
cases: anon=1587886, anoncow=789259, obj=7998320, prcopy=1603061,
przero=120
65607
daemon and swap counts:
woke=156, revs=149, scans=171225, obscans=99003, anscans=6415
busy=0, freed=105418, reactivate=0, deactivate=204424
pageouts=406, pending=6011, nswget=354
nswapdev=1, swpgavail=32767
swpages=32767, swpginuse=78, swpgonly=35, paging=0
db>
Now, the machine sits in ddb. Anything else you want me to do?
I stopped the machine after it had been sitting quite for about an hour
and a half. It is not responding to the network (well, right now it is
also in ddb, so obviously not...).
Johnny
Home |
Main Index |
Thread Index |
Old Index