[sancho]

Hi,
I pulled the octane out of storage it was for the last 3 years and booted it.
It went all the way to the login screen fine but suddenly some corruption appeared on the screen getting worse and worse.
Rebooting send it into a panic that I can't get it of without leaving it to "cool down" for a while.

Apart from removing all heatsinks on the graphic board anc cleaning evering pcb and chips, I am running out of idea.
I will dig out the config and do some logging from the serial see if I can get more info.

---

sancho@sp95:~$ hinv -vm
Location: /hw/node
PM10300MHZ Board: barcode KGV311 part 030-1355-001 rev M
Location: /hw/node/xtalk/15
IP30 Board: barcode KKP996 part 030-1467-001 rev D
Location: /hw/node/xtalk/15/pci/2
PWR.SPPLY.ER Board: barcode AAE0110121 part 060-0035-002 rev A
FP1 Board: barcode KBE934 part 030-0891-003 rev G
Location: /hw/node/xtalk/12
MOT10 Board: barcode JKT380 part 030-1241-002 rev H
1 300 MHZ IP30 Processor
Heart ASIC: Revision F
CPU: MIPS R12000 Processor Chip Revision: 2.3
FPU: MIPS R12010 Floating Point Chip Revision: 0.0
Main memory size: 1024 Mbytes
Xbow ASIC: Revision 1.4
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
Secondary unified instruction/data cache size: 2 Mbytes
Integral SCSI controller 0: Version QL1040B (rev. 2), single ended
Disk drive: unit 1 on SCSI controller 0 (unit 1)
Integral SCSI controller 1: Version QL1040B (rev. 2), single ended
IOC3/IOC4 serial port: tty1
IOC3/IOC4 serial port: tty2
IOC3 parallel port: plp1
Graphics board: ESI with texture option
Integral Fast Ethernet: ef0, version 1, pci 2
Iris Audio Processor: version RAD revision 12.0, number 1
PCI Adapter ID (vendor 0x10a9, device 0x0003) PCI slot 2
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 0
PCI Adapter ID (vendor 0x1077, device 0x1020) PCI slot 1
PCI Adapter ID (vendor 0x10a9, device 0x0005) PCI slot 3


sancho@sp95:~$ /usr/gfx/gfxinfo
Graphics board 0 is "IMPACTSR" graphics.
Managed (":0.0") 1280x1024
Product ID 0x2, 1 GE, 1 RE, 4 TRAMs
MGRAS revision 4, RA revision 0
HQ rev B, GE12 rev A, RE4 rev C, PP1 rev H,
VC3 rev A, CMAP rev F, Heart rev F
21" monitor (id 0xb)

(Could not contact X server; thus, no XSGIvc information available)


sp95 2# diskpatch -v
sc0d1l0: Disk SEAGATE ST336704LC 0003 Serial: 3CD007VF

[indy99]

sancho@sp95:~$ /usr/gfx/gfxinfo
......4 TRAMs ......

Try booting your Octane after removing the TRAM module.

[sancho]

I tried and nearly believed that it was the TRAM reaching the end of their adventure... but the time to prepare a tea and when I came back the screen looked like in the capture.
I will try with a real 1280x1024 screen as well to see if that changes something.

[soviet]

i suppose you already cleaned everthin on the octane ?, try settings your fans to high.
also the fan in your power supply is ok ?, i have the issue of this fan rotating slowly and i ended up replacing it.

[sancho]

Yes, the fans are working fine.
I disassembled it when I bought it something like 6 years ago but I never took off any heatsink and cleaned underneath.
Now, it went into a loop of panic :

Code:

Running power-on diagnostics...


Exception: <vector=Normal>
Status register: 0x34045083<CU1,CU0,FR,CH,IM7,IM5,IPL=???,KX,MODE=KERNEL,EXL,IE>
Cause register: 0x401c<CE=0,IP7,EXC=DBE>
Exception PC: 0xffffffff9fc3e418, Exception RA: 0x10000000
Data Bus error
HEART ISR :    0x8000000000000000<HEART_EXC>
HEART IMSR:    0x8000000000000000<HEART_EXC>
    Cause: 0x10000<WIDGET_ERR>
        Widget Error type: 0x8<PIO_RD_TIMEOUT>
        PIO rd timeout address: 0xc02c<CPU=0,IO_SPACE=0x0,DIDN=0xc,ADDR=0x2c>
  VID 0's saved user regs in hex (gpda=0xa800000020f25508):
  arg: 1 195d04040a1c10 1 195c0408000000
      100001800000000 195c0400000000 195d0404120c08 0
  tmp: 900000001c030000 0 3 5
  sve: 900000001c020000 900000001c120000 195c0408000000 0
      19120400000000 195d0400000244 195d0400000344 2
  t8 0 t9 195c0418000000 at 195c0401000024
  v0 1 v1 1 k1 ffffffffbad11bad
  gp 0 fp 195c0428000000 sp a800000020ffed70 ra 10000000

PANIC: Unexpected exception

[Press reset or ENTER to restart.]

If I reset, it goes back to this stage. I have to wait for it to "cool down".
When I started it first, it went fine and I could log in, network, cpu, memory but just display corruption.

[Raion]

Yeah that's something wrong with your graphics I suppose.

[sancho]

I made some progress :
I dismantled all the heatsink on the graphic card and the TRAM, it was way less dusty than what I though but no cigar.
Then I thought again about what soviet said and double checked the fan and look at this, the drive bay fan shroud moved and the fan was not turning anymore..... aaaargh...
Now it last...... longer. And each time that I reboot, the graphics are ok for 2 mins then it starts again.

I got a panic and a graphic crash later.

------The panic -----
WARNING: Xbow at /hw/node/xtalk/12 encountered Fatal error
xtalk PIO Read error in kernel mode
widgetnum: 0xc
srccpu: 0x0
sysioaddr: 0x1c02c574
xtalkaddr: 0x2c574
vaddr: 0x900000001c02c574
epc: 0xa8000000203416a4
ef: 0xffffffffffffb708
(NOTE: CPU 0=(NULL))

ALERT: PIO Error on XIO Bus /hw/node/xtalk/0/xbow[xbow# 0] port 12
Access attempted to offset 0x2c574
sync_vaddr: 0x900000001c02c574
sync_paddr: 0x1c02c574
PANIC: KERNEL FAULT
PC: 0xa8000000203416a4 ep: 0xffffffffffffb708
EXC code:28, `Data Bus Error '
Bad addr: 0xc000000000304054, cause: 0x871c<CE=0

Dumping to /hw/node/xtalk/15/pci/0/scsi_ctlr/0/target/1/lun/0/disk/partition/1/b lock at block 0, space: 0x2000 pages
Dumping low memory...
Dumping static kernel pages........
Dumping backtrace pages...
Dumping dynamic kernel pages........
Dumping buffer pages......
Dumping remaining in-use pages.................................................. ............................
Dumping free pages..........................................
Available dump space depleted.


[Press reset to restart the machine.]
----- panic end-----


------The crash -----
WARNING: Graphics error
gfx board #0
irnode=0xa800000020bde1b8, active_rnode=0xa80000004e789200
busy_dma: 0x900000001c020200/0xcc
status: 0x900000001c020000/0xe0148
fifo_status: 0x900000001c020008/0x4700cd67
bfifo_status: 0x900000001c020100/0x0
rebus_sync: 0x900000001c05821c/0x2
window: 0x900000001c008000/0x1a00
hqpc: 0x900000001c056000/0xcae
flag_set: 0x900000001c020010/0x40110180
hq_config: 0x900000001c011000/0x41085
gio_config: 0x900000001c011008/0x900f
re_status: 0x900000001c02c578/0x22000000000
WARNING: mgras: CFIFO timeout
X connection to :0.0 broken (explicit kill or server shutdown).
ALERT: RAD thread held off for more than 32 mS
XIO: fatal IO error 131 (Connection reset by peer) on X server ":0.0"
after 411 requests (411 known processed) with 0 events remaining.
4Dwm: I/O error on display:: :0.0

XIO: fatal IO error 131 (Connection reset by peer) on X server ":0.0"
after 1478 requests (1478 known processed) with 0 events remaining.
------crash end-----

As much as I would love to fix it... I am afraid that I have to get another graphic card. I guess I will be scouting for a V6/8.

[soviet]

What a shame maybe something fried when your fan was stuck.
Have you tried setting the fans in fast mode ?.

[Jacques]

The SSI / SSE cards run hot, very hot, and that is without TRAM. If the drive bay fan wasn't working then the gfx card probably coocked itself to death.

You will need a Cherokee PSU for VPro gfx, otherwise try and source a replacement card and see if your TRAMs still work. VPro runs quite a bit cooler than MGRAS.