Alpha ds20 serial console going to com2

[syslost]

Alpha ds20
Console serial
SRM v6.2-1
PALcode: vms v1.96-77
VMS 7.3-1

This is one of those cases where the server worked until it was moved
to another building.

Now, when I power up the ds20, the console output goes to com2 (s/b
com1). When I try to boot the system, it hangs at "jumping to
bootstrap code". I have to powercycle the server from the front panal
switches to get the >>> prompt back.

Any ideas on how/why the console is going to com2?

Here's the boot screen:

P00>>>b -fl 1,1 dkb400.4.0.2001.1
(boot dkb400.4.0.2001.1 -flags 1,1)
block 0 of dkb400.4.0.2001.1 is a valid boot block
reading 1022 blocks from dkb400.4.0.2001.1
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 7fc00(523264)
initializing HWRPB at 2000
initializing page table at 3ff52000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

And show config:
P00>>>show config
Test DS20B

SRM Console: V6.2-1
PALcode: OpenVMS PALcode V1.96-77, Tru64 UNIX PALcode V1.90-72

Processors
CPU 0 Alpha EV6 pass 2.3 500 MHz SROM Revision: V1.82
Bcache size: 4 MB

Core Logic
Cchip DECchip 21272-CA Rev 2.1
Dchip DECchip 21272-DA Rev 2.0
Pchip 0 DECchip 21272-EA Rev 2.2
Pchip 1 DECchip 21272-EA Rev 2.2

TIG Rev 4.14
Arbiter Rev 2.10 (0x1)

MEMORY

Array # Size Base Addr
------- ---------- ---------
0 512 MB 000000000
1 512 MB 020000000

Total Bad Pages = 0
Total Good Memory = 1024 MBytes


PCI Hose 00
Bus 00 Slot 05/0: Cypress 82C693
Bridge to Bus
1, ISA
Bus 00 Slot 05/1: Cypress 82C693 IDE
dqa.0.0.105.0

Bus 00 Slot 05/2: Cypress 82C693 IDE
dqb.0.1.205.0

Bus 00 Slot 05/3: Cypress 82C693 USB


Bus 00 Slot 07: DEC PowerStorm
vga0.0.0.7.0

Bus 00 Slot 08: DEC KZPSA
pkd0.7.0.8.0 SCSI Bus ID 7


PCI Hose 01
Bus 00 Slot 07: DECchip 21152-AA
Bridge to Bus
2, PCI
Bus 00 Slot 08: QLogic ISP10x0
pkc0.6.0.8.1 SCSI Bus ID 6

Bus 00 Slot 09: DECchip 21140-AA
ewb0.0.0.9.1
00-00-F8-03-D4-ED
Bus 02 Slot 00: NCR 53C875
pka0.7.0.2000.1 SCSI Bus ID 7

dka400.4.0.2000.1 RRD47

Bus 02 Slot 01: NCR 53C875
pkb0.6.0.2001.1 SCSI Bus ID 6

dkb0.0.0.2001.1 RZ2DD-LS

dkb100.1.0.2001.1 RZ1CF-CF

dkb200.2.0.2001.1 RZ2DD-LS

dkb300.3.0.2001.1 RZ2DD-LS

dkb400.4.0.2001.1 RZ2DD-LS

dkb500.5.0.2001.1 RZ2DD-LS

Bus 02 Slot 02: DE500-AA Network Controller
ewa0.0.0.2002.1
00-06-2B-00-72-78


ISA
Slot Device Name Type Enabled BaseAddr IRQ
DMA
0
0 MOUSE Embedded Yes 60 12
1 KBD Embedded Yes 60 1
2 COM1 Embedded Yes 3f8 4
3 COM2 Embedded Yes 2f8 3
4 LPT1 Embedded Yes 3bc 7
5 FLOPPY Embedded Yes 3f0 6
2

P00>>>

show fru
(one of the other ds20 shows this same line for the motherboard)
P00>>>show fru
FRUname E Part# Serial# Model/Other Alias/Misc
SMB0 00 ?????????????????? @????_____ ??????????
??????????
SMB0.CPU0 00 54-24758-03 NI96070661 Ô?

SMB0.CPU0.FAN 00 70-33599-01 - CPU Fan

SMB0.PCI0 00 DEC PowerStorm

SMB0.PCI1 00 DEC KZPSA

SMB0.PCI3 00 DECchip 21152-AA

SMB0.PCI4 00 QLogic ISP10x0

SMB0.PCI5 00 DECchip 21140-AA

SMB0.DIMM0 00

SMB0.DIMM1 00

SMB0.DIMM2 00

SMB0.DIMM3 00

SMB0.DIMM4 00

SMB0.DIMM5 00

SMB0.DIMM6 00

SMB0.DIMM7 00

SFM 00 54-25580-01 - SvrMgmt Compaq

PWR0 00 H7899-AA - Power Compaq

FAN1 00 70-31351-01 - System Fan Compaq

P00>>>

[d b turner]

Check

1) keyboard is working correctly
2) Keyboard and mouse are in the right ports
3) Keyboard matches the keyboard listed in

show kbd_hardware_type

My guess is the keyboard is flaking out

Funnily enough, in the past 3 weeks we have had customers call telling us
they need to buy a new system and in my stupidity (and perhaps honesty) I
tell them to check their keyboard
The problem seems to be the LK461-A2 and LK46W
They seem to die after about 3 years

The LK411 seems to be built a lot better


Oh by the way, for LK411, 461 and LK46W the kbd_type in the srm should be
lk411
FOr a PC style keyboard it should be PCXAL


David


"syslost" <***@gmail.com> wrote in message news:***@j33g2000cwa.googlegroups.com...
Alpha ds20
Console serial
SRM v6.2-1
PALcode: vms v1.96-77
VMS 7.3-1

This is one of those cases where the server worked until it was moved
to another building.

Now, when I power up the ds20, the console output goes to com2 (s/b
com1). When I try to boot the system, it hangs at "jumping to
bootstrap code". I have to powercycle the server from the front panal
switches to get the >>> prompt back.

Any ideas on how/why the console is going to com2?

Here's the boot screen:

P00>>>b -fl 1,1 dkb400.4.0.2001.1
(boot dkb400.4.0.2001.1 -flags 1,1)
block 0 of dkb400.4.0.2001.1 is a valid boot block
reading 1022 blocks from dkb400.4.0.2001.1
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 7fc00(523264)
initializing HWRPB at 2000
initializing page table at 3ff52000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

And show config:
P00>>>show config
Test DS20B

SRM Console: V6.2-1
PALcode: OpenVMS PALcode V1.96-77, Tru64 UNIX PALcode V1.90-72

Processors
CPU 0 Alpha EV6 pass 2.3 500 MHz SROM Revision: V1.82
Bcache size: 4 MB

Core Logic
Cchip DECchip 21272-CA Rev 2.1
Dchip DECchip 21272-DA Rev 2.0
Pchip 0 DECchip 21272-EA Rev 2.2
Pchip 1 DECchip 21272-EA Rev 2.2

TIG Rev 4.14
Arbiter Rev 2.10 (0x1)

MEMORY

Array # Size Base Addr
------- ---------- ---------
0 512 MB 000000000
1 512 MB 020000000

Total Bad Pages = 0
Total Good Memory = 1024 MBytes


PCI Hose 00
Bus 00 Slot 05/0: Cypress 82C693
Bridge to Bus
1, ISA
Bus 00 Slot 05/1: Cypress 82C693 IDE
dqa.0.0.105.0

Bus 00 Slot 05/2: Cypress 82C693 IDE
dqb.0.1.205.0

Bus 00 Slot 05/3: Cypress 82C693 USB


Bus 00 Slot 07: DEC PowerStorm
vga0.0.0.7.0

Bus 00 Slot 08: DEC KZPSA
pkd0.7.0.8.0 SCSI Bus ID 7


PCI Hose 01
Bus 00 Slot 07: DECchip 21152-AA
Bridge to Bus
2, PCI
Bus 00 Slot 08: QLogic ISP10x0
pkc0.6.0.8.1 SCSI Bus ID 6

Bus 00 Slot 09: DECchip 21140-AA
ewb0.0.0.9.1
00-00-F8-03-D4-ED
Bus 02 Slot 00: NCR 53C875
pka0.7.0.2000.1 SCSI Bus ID 7

dka400.4.0.2000.1 RRD47

Bus 02 Slot 01: NCR 53C875
pkb0.6.0.2001.1 SCSI Bus ID 6

dkb0.0.0.2001.1 RZ2DD-LS

dkb100.1.0.2001.1 RZ1CF-CF

dkb200.2.0.2001.1 RZ2DD-LS

dkb300.3.0.2001.1 RZ2DD-LS

dkb400.4.0.2001.1 RZ2DD-LS

dkb500.5.0.2001.1 RZ2DD-LS

Bus 02 Slot 02: DE500-AA Network Controller
ewa0.0.0.2002.1
00-06-2B-00-72-78


ISA
Slot Device Name Type Enabled BaseAddr IRQ
DMA
0
0 MOUSE Embedded Yes 60 12
1 KBD Embedded Yes 60 1
2 COM1 Embedded Yes 3f8 4
3 COM2 Embedded Yes 2f8 3
4 LPT1 Embedded Yes 3bc 7
5 FLOPPY Embedded Yes 3f0 6
2

P00>>>

show fru
(one of the other ds20 shows this same line for the motherboard)
P00>>>show fru
FRUname E Part# Serial# Model/Other Alias/Misc
SMB0 00 ?????????????????? @????_____ ??????????
??????????
SMB0.CPU0 00 54-24758-03 NI96070661 Ô?

SMB0.CPU0.FAN 00 70-33599-01 - CPU Fan

SMB0.PCI0 00 DEC PowerStorm

SMB0.PCI1 00 DEC KZPSA

SMB0.PCI3 00 DECchip 21152-AA

SMB0.PCI4 00 QLogic ISP10x0

SMB0.PCI5 00 DECchip 21140-AA

SMB0.DIMM0 00

SMB0.DIMM1 00

SMB0.DIMM2 00

SMB0.DIMM3 00

SMB0.DIMM4 00

SMB0.DIMM5 00

SMB0.DIMM6 00

SMB0.DIMM7 00

SFM 00 54-25580-01 - SvrMgmt Compaq

PWR0 00 H7899-AA - Power Compaq

FAN1 00 70-31351-01 - System Fan Compaq

P00>>>

[Hoff Hoffman]

Post by syslost
Alpha ds20
Console serial
SRM v6.2-1
PALcode: vms v1.96-77
VMS 7.3-1
This is one of those cases where the server worked until it was moved
to another building.
Now, when I power up the ds20, the console output goes to com2 (s/b
com1). When I try to boot the system, it hangs at "jumping to
bootstrap code". I have to powercycle the server from the front panal
switches to get the >>> prompt back.

Try plugging into com1. A number of the Alpha SRM implementations
can potentially send output to multiple com ports (but might not be
reading I/O from the alternate ports), and this can be quite confusing.

On this box, either com1 or the graphics head is the console port.

I must assume the keyboard here is plugged into the terminal which is
then plugged into the com2 port, and (based on the description provided)
the terminal and the keyword all appear to be working. (The other
configuration alternative here is to have the keyboard plugged into the
keyboard and mouse connections on the box, and to have a display
connected to the graphics controller -- to have the console set to
GRAPHICS, in other words. Well, that or to have the terminal plugged
into com1, and to have the CONSOLE variable set to SERIAL.)

BTW, if you see the self-test messages from the SROM loads, your
console is probably set to SERIAL. If you don't see the self-tests
prior to launching SRM, then your console is probably set to GRAPHICS.
If set to GRAPHICS, ensure that you are looking at the GRAPHICS console
and not at the com ports, or press BREAK a few times on the serial line
and (when you get to the prompt) reset the CONSOLE environment variable
to SERIAL.

I'd upgrade the SRM here, too. You're about six or seven version
behind current, too, FWIW -- V7.1 is the most recent release for this
box. (And your OpenVMS is also behind revision, but I'll consider and
recommend the console upgrade first here, for obvious reasons.)

If this isn't the console selection or such, then the failure at the
bootstrap jump would tend to imply a problem with the SCSI, or the
system device.

I might also see if the hardware service folks can crack open the box
and re-seat the boards, and re-seat all the disks, too. Moving
computers around can loosen up internal connections, of course.