New kernel + install uploaded.
Anders Magnusson
bug is found and fixed now and it seems as it swaps OK for me anyway.
The plain kernel is in /pub/NetBSD/arch/vax/snapshot/19981201/binary/kernel.
I have also generated a kernel that uses sysinst and can be booted
from the net. This hopefully means that we can forget copy/edlabel :-)
I have also rewritten the boot program, it now can handle gzipped binaries
and have a syntax much more like the i386 one. "boot netbsd -as" instead
of some cryptic B/43...
I also generated a tape bootfile, suitable to boot from TK50. It should
just boot up and start sysinst directly. This file may also be possible
to load from RX33, but I haven't tried.
That should be all for now; just walk around in the
/pub/NetBSD/arch/vax/snapshot/19981201 subdirectory on ftp.netbsd.org
and try it out. I will go away tomorrow and will stay unavailable until
next year something.
Merry Christmas,
Ragge
Andrew Gillham
> I have just uploaded a new kernel to the last snapshot. The "vget/vref"
> bug is found and fixed now and it seems as it swaps OK for me anyway.
Thanks Ragge!
I still have the problem of running out of space in kmem_map.
Here is the error:
# make init_main.o
cc -O2 -Werror -Wall -Wmissing-prototypes -Wstrict-prototypes -Wno-main -I. -I.
./../../../arch -I../../../.. -nostdinc -DVAX43 -DVAX46 -DCOMPAT_VAX1K -DLKM -DM
AXUSERS=8 -D_KERNEL -D_VAX_INLINE_ -c ../../../../kern/init_main.c
panic: malloc: out of space in kmem_map
syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up
This is on a VS3100/M38 netbooted from a NetBSD/i386 machine. Booting
with 'b/40' doesn't seem to help. Neither does the '-d' parameter to
boot.
Any ideas?
-Andrew
--
-----------------------------------------------------------------
Andrew Gillham | This space left blank
gil...@whirlpool.com | inadvertently.
I speak for myself, not for my employer. | Contact the publisher.
Richard Dickens
I've just booted the new kernel image on my MV3100/10 and it seems to come
up fine.
It even detected the RZ25 and RRD42 on the SCSI bus.
However I still don't get an console output, is this supposed to be
working now?
Also I can't seem to get anything to mount on the CDROM drive using either
-t CD9660 or msdos.
One last thing, is there a standard disktab entry for RZ disks or does it
just get auto detected?
RichardD
shsrms
Merry Christmas, Happy Saturnalia, Happy new year!
I will get to play with the new kernel after Christmas...I might be able
to get my 3100 powered up!!
Still playing with my alpha, the uvIIs are running GREAT! with 1.3.2
bob
--
real address is shsrms at erols dot com
The Herbal Gypsy and the Tinker.
Tom Ivar Helbekkmo
> I have just uploaded a new kernel to the last snapshot. The
> "vget/vref" bug is found and fixed now and it seems as it swaps OK
> for me anyway.
Unfortunately, it doesn't help me. :-( With your new kernel, I get
different crashes, but it still does crash. My KA650 now experiences
"stray interrupt scb0, vec 0x60" events, which means a memory write
timed out -- but as I've said, NetBSD/vax 1.3F is rock solid, and the
MicroVAX Diagnostic Monitor is unable to find a memory problem. An
example of a crash is seen in this dmesg output (as before, it boots
fine, but when i go and do "make obj" in an NFS-mounted /usr/src with
a local /usr/obj, it goes down within minutes):
NetBSD 1.3I (GENERIC) #2: Sat Dec 19 21:23:38 CET 1998
ragge@subzero:/multi/src/sys/arch/vax/compile/GENERIC
MicroVAX 3500/3600
realmem = 16736256
avail mem = 13090816
Using 204 buffers containing 835584 bytes of memory.
[...]
scheduler: no room for pid 142(cron), free 1
stray interrupt scb 0, vec 0x60
stray interrupt scb 0, vec 0x60
stray interrupt scb 0, vec 0x60
stray interrupt scb 0, vec 0x60
machine check 10
vap 80 istate1 86f49fd8 istate2 e8e0fc00 pc fcc07802 psl 8000031c
dmaser=0x88<QBNXM,LOSTERR> qbear=0xc dmaear=0x0
parity error: flushing cache
memory err!
panic: mchk
syncing disks... Trap: type 2, code 0, pc 8000066a, psl 4080000
panic: trap
NetBSD 1.3I (GENERIC) #2: Sat Dec 19 21:23:38 CET 1998
ragge@subzero:/multi/src/sys/arch/vax/compile/GENERIC
MicroVAX 3500/3600
realmem = 16736256
panic: Segv in kernel mode: pc 86f47010 addr 86f47010
syncing disks... panic: ptelen fault in system space: addr ffffffb0 pc 80027e5e
NetBSD 1.3I (GENERIC) #2: Sat Dec 19 21:23:38 CET 1998
ragge@subzero:/multi/src/sys/arch/vax/compile/GENERIC
MicroVAX 3500/3600
realmem = 16736256
avail mem = 13090816
[...]
Note that it still crashes again on the first reboot after a "real"
crash, with a "Segv in kernel mode" panic -- it always seems to do
this with a post-1.3F kernel. On the off chance that this is a
hardware problem in my KA650/MS650 combination, I swapped the boards
for a KA630/MS630 kit, and, as before, it didn't even finish booting
before bombing out with an "access fault with no process".
Maybe I have some other hardware that it doesn't like? Again, this
would be something that doesn't affect 1.3F, but screws up 1.3I...
Anything I can do to gather more information? Please let me know!
-tih
--
Popularity is the hallmark of mediocrity. --Niles Crane, "Frasier"