sunblade 1000, solaris 8 (02/02) and recommended patches

sunblade 1000, solaris 8 (02/02) and recommended patches

Post by Ian Didda » Wed, 30 Jul 2003 19:42:01



Hi - got me a problem.

Sunblade 1000 - vanilla install of solaris 8 (02/02 - everything plus
OEM).  Applied latest recommended patches (downloaded from sunsolve
just last week).

Box boots fine, and is avialbel on the network.  Then after maybe 30
minutes or so it just dies - powers itself off!

I wondered if it was because of the "power saving stuff" so I ran
un-sysconfig and re-did the usual stuff...  but I noticed it deffo
didn't ask me about power-saving options.  So I have no idea of this
is what is occuring or not!

There is nothing shown in the messages file.  The following was shown
on the console (well, laptop and hyperterminal session!)

ultra25 console login:
RED State Exception
CPU: 0000.0000.0000.0000
TL=0000.0000.0000.0005  TT=0000.0000.0000.0034
   TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
TSTATE=0000.0091.0000.1503

TL=0000.0000.0000.0004  TT=0000.0000.0000.0034
   TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
TSTATE=0000.0091.0000.1503

TL=0000.0000.0000.0003  TT=0000.0000.0000.0034
   TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
TSTATE=0000.0091.0000.1503

TL=0000.0000.0000.0002  TT=0000.0000.0000.0034
   TPC=0000.0000.1000.70f8  TnPC=0000.0000.1000.70fc
TSTATE=0000.0091.0000.1503

TL=0000.0000.0000.0001  TT=0000.0000.0000.0064
   TPC=0000.0000.0000.0000  TnPC=0000.0000.0000.0004
TSTATE=0000.0044.0000.1602

Has anybody any ideas?   The company that owns this box (I'm a
contractor) has no sun maintenenace on it (or any other sunblade 1000
come to that!) so I can't call Sun for any ideas.

cheers

Ian

 
 
 

sunblade 1000, solaris 8 (02/02) and recommended patches

Post by Remc » Wed, 30 Jul 2003 21:02:39


Hi Ian,

Some steps:
POST your system with nvram settings: diag-switch? true
                                                            diag-level max
                                                             auto-boot?
false

Whatch if possible you Serial A port with a null modem cabel connected to a
laptop/vt100/...

when it finished check: on the ok-prompt show-post-results.. if it says pass
=1 it should be okay
if not... you will get to see the problem area

Problem area's: Memory/ CPU/ Systemboard

Re-install your memory first. 1 bank only and if thats okay the second bank
(4 modules per bank)
Do you have 1 or 2 cpu's? If you have 1 reinstall the cpu, If you have 2
install only 1 and see if problem occurs.
and try the same wit the other cpu

See:
http://sunsolve.sun.com/handbook_pub/Devices/System_Board/SYSBD_SunBl...
For the memory and CPU placement.

If you are unluckly... it's a systemboard problem... I suspect a
memory/contact problem.

Hth


Quote:> Hi - got me a problem.

> Sunblade 1000 - vanilla install of solaris 8 (02/02 - everything plus
> OEM).  Applied latest recommended patches (downloaded from sunsolve
> just last week).

> Box boots fine, and is avialbel on the network.  Then after maybe 30
> minutes or so it just dies - powers itself off!

> I wondered if it was because of the "power saving stuff" so I ran
> un-sysconfig and re-did the usual stuff...  but I noticed it deffo
> didn't ask me about power-saving options.  So I have no idea of this
> is what is occuring or not!

> There is nothing shown in the messages file.  The following was shown
> on the console (well, laptop and hyperterminal session!)

> ultra25 console login:
> RED State Exception
> CPU: 0000.0000.0000.0000
> TL=0000.0000.0000.0005  TT=0000.0000.0000.0034
>    TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
> TSTATE=0000.0091.0000.1503

> TL=0000.0000.0000.0004  TT=0000.0000.0000.0034
>    TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
> TSTATE=0000.0091.0000.1503

> TL=0000.0000.0000.0003  TT=0000.0000.0000.0034
>    TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
> TSTATE=0000.0091.0000.1503

> TL=0000.0000.0000.0002  TT=0000.0000.0000.0034
>    TPC=0000.0000.1000.70f8  TnPC=0000.0000.1000.70fc
> TSTATE=0000.0091.0000.1503

> TL=0000.0000.0000.0001  TT=0000.0000.0000.0064
>    TPC=0000.0000.0000.0000  TnPC=0000.0000.0000.0004
> TSTATE=0000.0044.0000.1602

> Has anybody any ideas?   The company that owns this box (I'm a
> contractor) has no sun maintenenace on it (or any other sunblade 1000
> come to that!) so I can't call Sun for any ideas.

> cheers

> Ian


 
 
 

sunblade 1000, solaris 8 (02/02) and recommended patches

Post by Florian Stiass » Wed, 30 Jul 2003 21:14:32



Quote:>Hi - got me a problem.

>Sunblade 1000 - vanilla install of solaris 8 (02/02 - everything plus
>OEM).  Applied latest recommended patches (downloaded from sunsolve
>just last week).

>Box boots fine, and is avialbel on the network.  Then after maybe 30
>minutes or so it just dies - powers itself off!

>I wondered if it was because of the "power saving stuff" so I ran
>un-sysconfig and re-did the usual stuff...  but I noticed it deffo
>didn't ask me about power-saving options.  So I have no idea of this
>is what is occuring or not!

>There is nothing shown in the messages file.  The following was shown
>on the console (well, laptop and hyperterminal session!)

>ultra25 console login:
>RED State Exception
>CPU: 0000.0000.0000.0000
>TL=0000.0000.0000.0005  TT=0000.0000.0000.0034
>   TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
>TSTATE=0000.0091.0000.1503

>TL=0000.0000.0000.0004  TT=0000.0000.0000.0034
>   TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
>TSTATE=0000.0091.0000.1503

>TL=0000.0000.0000.0003  TT=0000.0000.0000.0034
>   TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
>TSTATE=0000.0091.0000.1503

>TL=0000.0000.0000.0002  TT=0000.0000.0000.0034
>   TPC=0000.0000.1000.70f8  TnPC=0000.0000.1000.70fc
>TSTATE=0000.0091.0000.1503

>TL=0000.0000.0000.0001  TT=0000.0000.0000.0064
>   TPC=0000.0000.0000.0000  TnPC=0000.0000.0000.0004
>TSTATE=0000.0044.0000.1602

>Has anybody any ideas?   The company that owns this box (I'm a
>contractor) has no sun maintenenace on it (or any other sunblade 1000
>come to that!) so I can't call Sun for any ideas.

>cheers

>Ian

I had this on a blade 100, the cpu was changed:

RED State Exception

            TL=0000.0000.0000.0005  TT=0000.0000.0000.0010
               TPC=0000.0000.0000.4200  TnPC=0000.0000.0000.4204  TSTATE=0000.0044.1500.1500
            TL=0000.0000.0000.0004  TT=0000.0000.0000.0010
               TPC=0000.0000.0000.4c80  TnPC=0000.0000.0000.4c84  TSTATE=0000.0044.1504.1400
            TL=0000.0000.0000.0003  TT=0000.0000.0000.0064
               TPC=0000.0000.6224.4174  TnPC=0000.0000.6224.4178  TSTATE=0000.0044.1500.1500
            TL=0000.0000.0000.0002  TT=0000.0000.0000.0020
               TPC=0000.0000.0000.0400  TnPC=0000.0000.0000.0404  TSTATE=0000.0044.1500.1500
            TL=0000.0000.0000.0001  TT=0000.0000.0000.0020
               TPC=0000.0000.f004.a830  TnPC=0000.0000.f04a.e8ac  TSTATE=0000.0044.1500.0400

---
                        \|/
                        o o
 ___________________oOO_(_)_OOo______________________________________

 
 
 

sunblade 1000, solaris 8 (02/02) and recommended patches

Post by Jerr » Wed, 30 Jul 2003 22:19:27


 We had problems with 2 blade 1000 that would die intermittently - problem
wound up being the power cutout switch that gets depressed when you put on
the side panel - soldered both of them closed - no more problem.


Quote:> Hi - got me a problem.

> Sunblade 1000 - vanilla install of solaris 8 (02/02 - everything plus
> OEM).  Applied latest recommended patches (downloaded from sunsolve
> just last week).

> Box boots fine, and is avialbel on the network.  Then after maybe 30
> minutes or so it just dies - powers itself off!

> I wondered if it was because of the "power saving stuff" so I ran
> un-sysconfig and re-did the usual stuff...  but I noticed it deffo
> didn't ask me about power-saving options.  So I have no idea of this
> is what is occuring or not!

> There is nothing shown in the messages file.  The following was shown
> on the console (well, laptop and hyperterminal session!)

> ultra25 console login:
> RED State Exception
> CPU: 0000.0000.0000.0000
> TL=0000.0000.0000.0005  TT=0000.0000.0000.0034
>    TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
> TSTATE=0000.0091.0000.1503

> TL=0000.0000.0000.0004  TT=0000.0000.0000.0034
>    TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
> TSTATE=0000.0091.0000.1503

> TL=0000.0000.0000.0003  TT=0000.0000.0000.0034
>    TPC=0000.0000.1000.6d30  TnPC=0000.0000.1000.6d34
> TSTATE=0000.0091.0000.1503

> TL=0000.0000.0000.0002  TT=0000.0000.0000.0034
>    TPC=0000.0000.1000.70f8  TnPC=0000.0000.1000.70fc
> TSTATE=0000.0091.0000.1503

> TL=0000.0000.0000.0001  TT=0000.0000.0000.0064
>    TPC=0000.0000.0000.0000  TnPC=0000.0000.0000.0004
> TSTATE=0000.0044.0000.1602

> Has anybody any ideas?   The company that owns this box (I'm a
> contractor) has no sun maintenenace on it (or any other sunblade 1000
> come to that!) so I can't call Sun for any ideas.

> cheers

> Ian

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---
 
 
 

sunblade 1000, solaris 8 (02/02) and recommended patches

Post by ultraspa.. » Fri, 01 Aug 2003 12:48:04



Quote:>>TL=0000.0000.0000.0001  TT=0000.0000.0000.0064
>>   TPC=0000.0000.0000.0000  TnPC=0000.0000.0000.0004
>>TSTATE=0000.0044.0000.1602

>I had this on a blade 100, the cpu was changed:

>RED State Exception
>            TL=0000.0000.0000.0001  TT=0000.0000.0000.0020
>               TPC=0000.0000.f004.a830  TnPC=0000.0000.f04a.e8ac  TSTATE=0000.0044.1500.0400

yet those are entirely different failures.  the first is easily a software
bug where some code jumped to address 0, yours is certainly more likely
to be failed hardware.  why do you feel they are related?
 
 
 

1. LILO booting error(L 02 02 02 02 02 - - - - )

I have a problem.
I want to set LILO correctly and multi booting.
1st hard disk - 5G linux.
2nd hard disk - 40G win2000

When settng linux, I made a floppy booting diskette.
Floppy booting is OK.

hda1 = /boot
hda2 = /
And set LILO(version 21) at MBR

lilo.conf file
===============================
boot = /dev/hda
map = /boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
default=linux
lba32

image=/boot/vmlinuz-2.4.2-3
    label=linux
    read-only
    root=/dev/hda1
    append="hdd=ide-scsi"
===============================

After booting, display message following.
L 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02
02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02
02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02

I got message's meaning at this site. but I don't know why.
http://metalab.unc.edu/pub/linux/system/boot/lilo/lilo-u-21.ps.gz

Another trying - after rewriting boot=/dev/fd0 in lilo.conf for floppy disk
booting.
-- then booting using floppy disk. I had a the same message.

Why get this error?
Please ...

2. highmem pci dma mapping does not work, missing cast in asm-i386/pci.h

3. How to find whether Solaris 8(02/04) or Solaris 8(02/02) ?

4. No Login prompt when I dial into my Linux box

5. LILO hangs with "02 02 02..." message

6. Enterprise/binary garbage web page

7. Deadline Extension: Federated Conference 2002 (DOA'02, ODBASE'02, CoopIS'02)

8. Help with XSiS 5597?

9. Solaris 2.6 and Recommended patch Cluster 1999.02.10

10. Solaris 02/02 Companion CD Questions KDE and Gnome

11. Solaris 8 02/02

12. Solaris 8 - how do I tell if MU7 is installed on 02/02?

13. Solaris 8 (02/02) installation