HECnet

hecnet@lists.dfupdate.se

1 participants
15557 discussions

Trying to build SIMH from git (on OpenIndiana)

by wonko＠4amlunch.net

Thoughts? -brian wonko at zaphod$ make vax lib paths are: /lib /usr/lib using libm: /lib/libm.so using librt: /lib/librt.so using libpthread: /lib/libpthread.so /usr/include/pthread.h using libdl: /lib/libdl.so /usr/include/dlfcn.h using libpcap: /usr/include/pcap.h *** *** vax Simulator being built with: *** - compiler optimizations and no debugging support. GCC Version: 4.3.3. *** - dynamic networking support using Solaris provided libpcap components. *** gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fno-unsafe-loop-optimizations -fno-strict-overflow -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so sim_BuildROMs.c -o BIN/BuildROMs BIN/BuildROMs rm -f BIN/BuildROMs gcc -std=c99 -U__STRICT_ANSI__ -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fno-unsafe-loop-optimizations -fno-strict-overflow -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO -DHAVE_DLOPEN=so VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c VAX/vax_octa.c VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c VAX/vax_sysdev.c VAX/vax_sys.c VAX/vax_syscm.c VAX/vax_syslist.c PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I PDP11 -DUSE_SHARED -I/usr/include/ -o BIN/microvax3900 -lsocket -lnsl -lm -lrt -lpthread -ldl In file included from sim_serial.h:89, from scp.c:223: sim_tmxr.h:55: error: redefinition of typedef 'SERHANDLE' sim_serial.h:81: error: previous declaration of 'SERHANDLE' was here In file included from sim_console.c:122: sim_serial.h:81: error: redefinition of typedef 'SERHANDLE' sim_tmxr.h:55: error: previous declaration of 'SERHANDLE' was here In file included from sim_serial.h:89, from sim_tmxr.c:324: sim_tmxr.h:55: error: redefinition of typedef 'SERHANDLE' sim_serial.h:81: error: previous declaration of 'SERHANDLE' was here In file included from sim_serial.h:89, from sim_serial.c:127: sim_tmxr.h:55: error: redefinition of typedef 'SERHANDLE' sim_serial.h:81: error: previous declaration of 'SERHANDLE' was here make: *** [BIN/microvax3900] Error 1 wonko at zaphod$

12 years, 2 months

Area 9 is (slowly) coming back online

by Mark＠infocomm.com

On Monday, March 11, 2013 at 7:21 PM, Gregg Levine wrote: On Mon, Mar 11, 2013 at 10:10 PM, Brian Hechinger <wonko at 4amlunch.net> wrote: I've been battling idle on Solaris for a whole now. Haven't figured it out yet though. -brian On Mar 11, 2013, at 20:26, "b4" <b4 at gewt.net> wrote: Hello all, I have been in the middle of moving things around and I've got my area router back up and I have the proper things forwarded now. ;) Everything should come back up completely before too long. One major caveat: SIMH in Solaris 10 zones...am I doing something wrong or is SET CPU IDLE disallowed in this scenario? If so, it looks like i'll throttle the execution rate as well as running the VMs on 10BASE-T ports. ;) Idling for any simulator requires that the host system's clock tick be <= the size of the simulated system's clock tick. VAX systems have a clock tick of 10ms. Idling for simulated VAX systems works best if the host clock tick is 1ms. Windows systems have a user mode programmatically settable clock tick size (a facility useful for some media playback capabilities). On Windows systems simh will set the host's clock tick to 1ms while a simulator is running. We haven't seen programmatically settable host clock tick sizes on other platforms. In general, other platforms have a tick size which can be changed in some system specific way (which might require building a kernel with a desired tick size) or not changeable at all. This issue comes up often enough that adding how to make these system specific adjustments would be a useful addition to the simh FAQ. Any feedback on this subject will be welcome. Recent simh code will display what it has determined to be the host's clock size if simh believes the host's clock tick is too small to support idling when you attempt to enable idling. Recent simh code can always display host system's tick size with the 'EXAMINE TIMER OS_SLEEP_MIN_MS' command. The latest simh code is available from https://github.com/simh/simh/archive/master.zip. Gregg Levine wrote: Idle on some items that are not Linux or FreeBSD or NetBSD may not work because of how they interpret the timer. Same goes for trying to get the idle function to work on Windows. I haven't heard from anyone who's had issues getting idling to work on Windows. If you know of such a case, I would be interested to explore what may be happening in this case. Thanks. - Mark Pizzolato

12 years, 2 months

RSX-11M v4.1 SYSGEN - OK, I give up - what am I doing wrong?

by bqt＠softjar.se

On 2013-03-12 14:44, Bob Armstrong wrote: I'm just throwing ideas out, as I don't know for sure why have the problem. Interestingly, 11M v3.2 BL26 works fine, even after the SYSGEN, but I don't have DECnet for that. 11M v4.0 BL32 and 11M v4.1 BL35 both fail after SYSGEN in exactly the same way. 11M v4.2 BL56 works, but won't fit on an RL02 anymore (or at least I can't figure out how to fit it on such). I had to build it on an RD drive instead - that's of no consequence on simh (where hardware is free!), but isn't going to work on the real machine. I think any version of 11M should be able to fit on an RL02. But there might be some special considerations that are needed. I seem to remember building such a thing, about 20 years ago... Johnny

12 years, 2 months

RSX-11M v4.1 SYSGEN - OK, I give up - what am I doing wrong?

by bob＠jfcl.com

I'm just throwing ideas out, as I don't know for sure why have the problem. Interestingly, 11M v3.2 BL26 works fine, even after the SYSGEN, but I don't have DECnet for that. 11M v4.0 BL32 and 11M v4.1 BL35 both fail after SYSGEN in exactly the same way. 11M v4.2 BL56 works, but won't fit on an RL02 anymore (or at least I can't figure out how to fit it on such). I had to build it on an RD drive instead - that's of no consequence on simh (where hardware is free!), but isn't going to work on the real machine. Bob

12 years, 2 months

Area 9 is (slowly) coming back online

by gregg.drwho8＠gmail.com

On Mon, Mar 11, 2013 at 10:10 PM, Brian Hechinger <wonko at 4amlunch.net> wrote: I've been battling idle on Solaris for a whole now. Haven't figured it out yet though. -brian On Mar 11, 2013, at 20:26, "b4" <b4 at gewt.net> wrote: Hello all, I have been in the middle of moving things around and I've got my area router back up and I have the proper things forwarded now. ;) Everything should come back up completely before too long. One major caveat: SIMH in Solaris 10 zones...am I doing something wrong or is SET CPU IDLE disallowed in this scenario? If so, it looks like i'll throttle the execution rate as well as running the VMs on 10BASE-T ports. ;) -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Experiments Hello! Idle on some items that are not Linux or FreeBSD or NetBSD may not work because of how they interpret the timer. Same goes for trying to get the idle function to work on Windows. In any case Cory nice to see you're largely back online. And whatever else the problem it will all be Dave's fault. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

12 years, 2 months

Area 9 is (slowly) coming back online

by wonko＠4amlunch.net

I've been battling idle on Solaris for a whole now. Haven't figured it out yet though. -brian On Mar 11, 2013, at 20:26, "b4" <b4 at gewt.net> wrote: Hello all, I have been in the middle of moving things around and I've got my area router back up and I have the proper things forwarded now. ;) Everything should come back up completely before too long. One major caveat: SIMH in Solaris 10 zones...am I doing something wrong or is SET CPU IDLE disallowed in this scenario? If so, it looks like i'll throttle the execution rate as well as running the VMs on 10BASE-T ports. ;) -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Experiments

12 years, 2 months

Area 9 is (slowly) coming back online

by b4＠gewt.net

Hello all, I have been in the middle of moving things around and I've got my area router back up and I have the proper things forwarded now. ;) Everything should come back up completely before too long. One major caveat: SIMH in Solaris 10 zones...am I doing something wrong or is SET CPU IDLE disallowed in this scenario? If so, it looks like i'll throttle the execution rate as well as running the VMs on 10BASE-T ports. ;) -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Experiments

12 years, 2 months

RSX-11M v4.1 SYSGEN - OK, I give up - what am I doing wrong?

by b4＠gewt.net

On 11 Mar 2013, at 17:44, "Bob Armstrong" <bob at jfcl.com> wrote: What version of simh? PDP-11 simulator V3.8-2 Hmmm. The bug i'm thinking of wasn't in that release, so it's not that. Bob

12 years, 2 months

RSX-11M v4.1 SYSGEN - OK, I give up - what am I doing wrong?

by bob＠jfcl.com

Try creating a new RSX11M.SYS, which is a bit smaller, and then rerun the VMR command, Nope - no change, but thanks for the idea. I didn't think that was it - notice that it actually gets far enough to print the MCR ">" before it dies - boo [1,54]rsx11m RSX11M V4.1 BL35 SYSTEM CRASH AT LOCATION 025614 REGISTERS R0=025232 R1=056270 R2=010464 R3=034766 R4=033262 R5=000000 SP=000710 PS=030010 - so I don't think it's having a problem loading the memory image. It's something after that which dies ... Bob

12 years, 2 months

RSX-11M v4.1 SYSGEN - OK, I give up - what am I doing wrong?

by bob＠jfcl.com

; The response to the following question specifies the highest interrupt ; vector. If you respond with a value less than or equal to 400, SYSGEN ; will assign the value associated with the highest interrupt vector ; specified during the Peripheral Section. Therefore, if your system ; will include devices that are not specified during the Peripheral ; Section and which have vectors above 400 (devices such as K-series and ; certain communication devices), specify that value in the next question. 0 .LE. 400 .... -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Steve Davidson Sent: Monday, March 11, 2013 2:39 PM To: hecnet at Update.UU.SE Subject: RE: [HECnet] RSX-11M v4.1 SYSGEN - OK, I give up - what am I doing wrong? (14) Highest Interrupt Vector. The default is zero (0). I am pretty sure that must be changed to reflect the hardware installed. -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist Sent: Monday, March 11, 2013 17:31 To: hecnet at Update.UU.SE Cc: Bob Armstrong Subject: Re: [HECnet] RSX-11M v4.1 SYSGEN - OK, I give up - what am I doing wrong? On 2013-03-11 21:37, Bob Armstrong wrote: I'm trying to SYSGEN an 11M 4.1 system from the distribution on RL01s using a dual RL PDP-11/23+ (which is simh in this case, so I know the hardware works). I'm letting it autoconfigure and I'm taking pretty much the default answer for everything. The build seems to go without error and yet the resulting system crashes as soon as it boots. I give up - what am I doing wrong? Somebody give me a clue, please! The simh log is attached. When RSX is building the system, it at one point creates the new system image to run, called [1,54]RSX11M.SYS. The relevant line is PIP RSX11M.SYS/CO/NV/BL:498.=RSX11M.TSK Now, your machine only have 128kW. That is 256 kByte. Of this, 8 kByte goes away because of the I/O page. Leaving 248 kByte. This is 496 disk blocks. It *might* be that your disk file is too big, making the system assume that it can place stuff in memory that don't exist. RSX11M.SYS is pretty close to just a memory dump. Try creating a new RSX11M.SYS, which is a bit smaller, and then rerun the VMR command, and try booting that file instead and see if that helps? Johnny

12 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet