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 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
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
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
; 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
(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
On 11 Mar 2013, at 16:37, "Bob Armstrong" <bob at jfcl.com> 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.
Thanks,
Bob Armstrong
<install.log>
Oops, looks like my email server was misconfigured and my message got lost.
What version of simh?
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
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.
Thanks,
Bob Armstrong