X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C73E4D.5903E0C6@onstor-exch02.onstor.net>; Mon, 22 Jan 2007 09:47:13 -0800
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: How to get crash dump from TXRX?
Date: Mon, 22 Jan 2007 09:47:13 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E9D970D@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E022289F1@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: How to get crash dump from TXRX?
thread-index: Acc91uSkfc+mn/cbQty3vgd5ORAo/gAAC4H7AB1VHBAAACpuQA==
From: "Henry Lau" <henry.lau@onstor.com>
To: "Ron Bhanukitsiri" <ronb@onstor.com>
Cc: "dl-Software" <dl-software@onstor.com>,
	"Jonathan Goldick" <jonathan.goldick@onstor.com>,
	"Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>

File a help desk defect if the ports cannot be connected after reset.
Normally, it should work.

Henry

-----Original Message-----
From: Ron Bhanukitsiri=20
Sent: Monday, January 22, 2007 9:42 AM
To: Henry Lau; dl-Software; Maxim Kozlovsky; Jonathan Goldick
Subject: RE: How to get crash dump from TXRX?

Thanks Henry,

Well I did find an instance of gdb64 running on compile2.  Didn't know
if someone was actively doing anything but I killed it last night
anyway.

I'm still having the same problem, both to 10.2.11.235 and 10.2.2.235.

Ron B[ee]

-----Original Message-----
From: Henry Lau=20
Sent: Sunday, January 21, 2007 7:46 PM
To: Ron Bhanukitsiri; dl-Software; Maxim Kozlovsky; Jonathan Goldick
Subject: RE: How to get crash dump from TXRX?

Hi Ron,

You may have another gdb64 already connected to the system. Try ps ax
|grep gdb64, kill the thread and reconect. If it still fails, you have
to logon as root to=20
10.2.11.235 with no password, port kill 4 to reset the port. Isn't it
10.2.2.235 instead of 10.2.11.235?


Henry

-----Original Message-----
From: Ron Bhanukitsiri
Sent: Sun 1/21/2007 7:39 PM
To: dl-Software; Maxim Kozlovsky; Jonathan Goldick
Subject: How to get crash dump from TXRX?
=20
A while back, I had set the TXRX so that it would *not* automatically
restart
when it crashed.  Can't even remember the command?  Does anyone know?

Anyway, the TXRX crashes, it goes into the command prompt in debug mode.
What are the commands I can type?  There is no help (help or ?) that I
can
see.  Finally, how do I make it continue and dump the core  to the core
volume?

Alternatively, I'd like to gdb64 the TXRX.  I've done it before a while
back, but
it doesn't seem to work one.  On my TXRX1 console, I see the port.  So
here's
what I did.  I first went to the TXRX1 console and type
	rts
	debug
and got the WAIT message.  I then went to compile2 and type.

gdb64 txrx
GNU gdb 5.1.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "--host=3Di686-pc-linux-gnu =
--target=3Dmips64"...
The target architecture is assumed to be mips:sb1
Breakpoint 1 at 0xffffffff830af4cc: file Panic.c, line 45.
(gdb) show architecture          =20
The target architecture is assumed to be mips:sb1
(gdb) show remoteaddressize
Undefined show command: "remoteaddressize".  Try "help show".
(gdb) show remoteaddresssize
The maximum size of the address (in bits) in a memory packet is 64.
(gdb) show mask-address
Zeroing of upper 32 bits of 64-bit addresses when talking to PMON
targets is off.
(gdb) target pmon 10.2.11.235:2004
10.2.11.235:2004: Bad file descriptor.
(gdb) quit

As you can see, it didn't connect to the TXRX :-(.  What's wrong?

Thanks,
Ron B[ee]


