On 2014-05-22 14:20, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
I've never seen a board with the ability to disable parity...
It's a clearpoint board. Technically it's just disabling the parity
circuitry CSR.
The "***EXEC PARITY ERROR STOP***" message is when you get a parity
error in the memory where the kernel resides.
RSX can deal with memory errors in other parts of the memory, by just
making that memory unavailable for programs to use. But it cannot do
this with the parts that the kernel use, so then it panics instead.
Ahh. Damn. I'd be okay if the only other memory board I had spare
wasn't PMI.
PMI? As the the PMI memory boards for the 11/83?
Did you know that those memory boards work just fine as normal Qbus memory boards? :-)
There's that 16K board...I could adjust the memory offsets.
Ugh! 16K is not much...
First bugcheck is essentially an illegal instruction in kernel mode.
(Error code=110 is illegal instruction, while facility=300 means the
executive.)
Ahh.
No idea why you got that one, though, unless it was a fallout of bad memory...
Johnny
On Thu, 22 May 2014, Johnny Billquist wrote:
With parity disabled and RSTS/E:
https://ghostbin.com/paste/ksd3c a bad ~50K? I can disable everything
above 512kByte which is...i forget how many words.
512Kbytes is 256Kword. :-)
Ahh.
But it's not clear that the address are in Kwords...
It's a 1M board...so it's either at the very upper end of memory or in the middle.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 22 May 2014, Johnny Billquist wrote:
On 2014-05-22 12:11, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
boot [1,54]rsx11m.sys
SYSTEM FAULT DETECTED AT PC=042714 FACILITY=000300 ERROR CODE=000110
CRASH -- CRASH DRIVER NOT LOADED
After disabling parity this is what it does consistently.
@004620/000776
Do I have a bad memory board? It's far, far too late to return this one...
Is that some output already at power on before anything is booted? That would mean some selftest failed.
Nope. The only output I get at power on is 173000 (halt switch in).
I commented earlier on the other error you saw, which definitely is a case of parity error...
Yeah.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 22 May 2014, Johnny Billquist wrote:
I've never seen a board with the ability to disable parity...
It's a clearpoint board. Technically it's just disabling the parity circuitry CSR.
The "***EXEC PARITY ERROR STOP***" message is when you get a parity error in the memory where the kernel resides.
RSX can deal with memory errors in other parts of the memory, by just making that memory unavailable for programs to use. But it cannot do this with the parts that the kernel use, so then it panics instead.
Ahh. Damn. I'd be okay if the only other memory board I had spare wasn't PMI.
There's that 16K board...I could adjust the memory offsets.
First bugcheck is essentially an illegal instruction in kernel mode.
(Error code=110 is illegal instruction, while facility=300 means the executive.)
Ahh.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-22 14:06, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
boot [1,54]rsx11m.sys
SYSTEM FAULT DETECTED AT PC=042714 FACILITY=000300 ERROR CODE=000110
CRASH -- CRASH DRIVER NOT LOADED
After disabling parity this is what it does consistently.
@004620/000776
Do I have a bad memory board? It's far, far too late to return this
one...
With parity disabled and RSTS/E:
https://ghostbin.com/paste/ksd3c a bad ~50K? I can disable everything
above 512kByte which is...i forget how many words.
512Kbytes is 256Kword. :-)
But it's not clear that the address are in Kwords...
Johnny
On 2014-05-22 12:11, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
boot [1,54]rsx11m.sys
SYSTEM FAULT DETECTED AT PC=042714 FACILITY=000300 ERROR CODE=000110
CRASH -- CRASH DRIVER NOT LOADED
After disabling parity this is what it does consistently.
@004620/000776
Do I have a bad memory board? It's far, far too late to return this one...
Is that some output already at power on before anything is booted? That would mean some selftest failed.
I commented earlier on the other error you saw, which definitely is a case of parity error...
Johnny
On 2014-05-22 11:43, Cory Smelosky wrote:
On Thu, 22 May 2014, Johnny Billquist wrote:
On 2014-05-22 11:26, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
What the hell?
boot [1,54]RSX11M.SYS
SYSTEM FAULT DETECTED AT PC=042714 FACILITY=000300 ERROR CODE=000110
CRASH -- CRASH DRIVER NOT LOADED
boot [1,54]rsx11m.sys
***EXEC PARITY ERROR STOP***
025746
@025746/000310
Uh. This doesn't make a whole lot of sense...
That sounds like a memory parity error to me...
I was just skimming through the memory board's manual for its parity
settings to see if perhaps it was disabled. Or enabled.
Doesn't look like there's a jumper for that. :(
Perhaps I have the model without parity...
I've never seen a board with the ability to disable parity...
The "***EXEC PARITY ERROR STOP***" message is when you get a parity error in the memory where the kernel resides.
RSX can deal with memory errors in other parts of the memory, by just making that memory unavailable for programs to use. But it cannot do this with the parts that the kernel use, so then it panics instead.
First bugcheck is essentially an illegal instruction in kernel mode.
(Error code=110 is illegal instruction, while facility=300 means the executive.)
Johnny
On Thu, 22 May 2014, Cory Smelosky wrote:
On Thu, 22 May 2014, Cory Smelosky wrote:
boot [1,54]rsx11m.sys
SYSTEM FAULT DETECTED AT PC=042714 FACILITY=000300 ERROR CODE=000110
CRASH -- CRASH DRIVER NOT LOADED
After disabling parity this is what it does consistently.
@004620/000776
Do I have a bad memory board? It's far, far too late to return this one...
With parity disabled and RSTS/E:
https://ghostbin.com/paste/ksd3c a bad ~50K? I can disable everything above 512kByte which is...i forget how many words.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 22 May 2014, Cory Smelosky wrote:
boot [1,54]rsx11m.sys
SYSTEM FAULT DETECTED AT PC=042714 FACILITY=000300 ERROR CODE=000110
CRASH -- CRASH DRIVER NOT LOADED
After disabling parity this is what it does consistently.
@004620/000776
Do I have a bad memory board? It's far, far too late to return this one...
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Great, now you are set. Sorry for not answering quickly enough!
To answer your question; it depends on the configuration.
With DECnet Phase IV a cluster member should be a routing node. With DECnet Phase V you should have a router in the same LAN (and Area, of course).
Kari
On 22.5.2014 12:25, Jordi Guillaumes i Pons wrote:
El 22/05/2014, a les 11.08, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> va escriure:
El 22/05/2014, a les 9.27, Kari Uusim ki <uusimaki at exdecfinland.org> va escriure:
For the DECnet cluster alias you need (at least) one routing node (L1) or a router.
Does any of the cluster nodes have routing enabled?
I hqve a L1 router and an area router in the same LAN. Is that enough, or should I enable routing in one of the cluster members?
Answering to myself: yes, enabling the boot member as L1 router fixed the thing and now the cluster alias is visible and accessible. Thanks!
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
.
