AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<David.Olien@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	17428	6C678488C5CEE74F813A4D1948FD2DC7B7BF8C48@cosmail02.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 31 Mar 2010 12:12:21 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Olien, David" <David.Olien@lsi.com>
Subject: Re: My cougar just went catatonic
Message-ID: <20100331121221.1c396ded@ripper.onstor.net>
In-Reply-To: <6C678488C5CEE74F813A4D1948FD2DC7B7BF8C48@cosmail02.lsi.com>
References: <6C678488C5CEE74F813A4D1948FD2DC7B7BF8B8B@cosmail02.lsi.com>
	<98BD48946A20FF48932378FFD26CE9057DF136CB@cosmail01.lsi.com>
	<6C678488C5CEE74F813A4D1948FD2DC7B7BF8BB5@cosmail02.lsi.com>
	<20100330163843.78d957a4@ripper.onstor.net>
	<6C678488C5CEE74F813A4D1948FD2DC7B7BF8C44@cosmail02.lsi.com>
	<6C678488C5CEE74F813A4D1948FD2DC7B7BF8C48@cosmail02.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi David,

Please include the entire console log starting from the
PROM waiting for image to be loaded.

Thanks,

a


On Tue, 30 Mar 2010 20:19:45 -0600 "Olien, David" <David.Olien@lsi.com>
wrote:

> Sorry here's yet a better attachment.
> Vim did some strange indenting on the previous one.
> 
> 
> 
> -----Original Message-----
> From: Olien, David 
> Sent: Tuesday, March 30, 2010 7:12 PM
> To: Olien, David; Sharp, Andy
> Subject: RE: My cougar just went catatonic
> 
> Sorry, my stack trace attachment somehow wasn't what I expected.  
> Don't know what I messed up there.
> 
> Here's a new attachment, hopefully a more readable stack trace. 
> This is best read on a Linux machine.
> 
> Dave
> 
> 
> -----Original Message-----
> From: Olien, David
> Sent: Tuesday, March 30, 2010 4:58 PM
> To: Sharp, Andy
> Subject: RE: My cougar just went catatonic
> 
> OK, using the serial console, I was able to get the Tuxrx kernel to
> boot.  But it panics.  Looks like something In the module
> initialization for the embedded Ethernet.
> 
> Attached is a stack trace (didn't feel like pasting it Into
> outlook... ugh!)
> 
> dave
> 
> 
> 
> -----Original Message-----
> From: Andrew Sharp [mailto:andy.sharp@lsi.com]
> Sent: Tuesday, March 30, 2010 4:39 PM
> To: Olien, David
> Subject: Re: My cougar just went catatonic
> 
> Feel free to cut-n-paste the output and send it to me if you are
> having any trouble figuring out what the problems might be.  I've
> only done it 10,000 times ~:^)
> 
> Cheers,
> 
> a
> 
> On Tue, 30 Mar 2010 16:49:39 -0600 "Olien, David"
> <David.Olien@lsi.com> wrote:
> 
> > The serial line seems to be working.  I'm seeing some information 
> > about the txrx cores booting.  Very helpful. I'll see if I can
> > debug why the tuxrx kernel isn't getting loaded.
> > 
> > dave
> > 
> > From: Hardiman, Richard
> > Sent: Tuesday, March 30, 2010 3:23 PM
> > To: Olien, David; Scheer, Larry; Sharp, Andy
> > Subject: RE: My cougar just went catatonic
> > 
> > Hey David,
> > Sorry about that I was connecting your TxRx console.
> > --> TxRx settings are 10.2.203.235 9042
> > Let me know if you have any problems with the new console
> > connection. Have a good day!
> > ________________________________
> > From: Olien, David
> > Sent: Tuesday, March 30, 2010 3:13 PM
> > To: Olien, David; Scheer, Larry; Hardiman, Richard; Sharp, Andy
> > Subject: RE: My cougar just went catatonic
> > 
> > I see on my serial console that my cougar is rebooting.  Thanks!
> > 
> > dave
> > 
> > From: Olien, David
> > Sent: Tuesday, March 30, 2010 3:06 PM
> > To: Scheer, Larry; Hardiman, Richard; Sharp, Andy
> > Subject: My cougar just went catatonic
> > 
> > I had been connected to the SSC's serial console on my cougar, 
> > examining log files.  I left my desk for about 30 minutes.  Came
> > back to my desk, and I can't get any response from it, either on
> > the serial console or via ping.  Could someone take a look and see
> > what's up, maybe reset it?
> > 
> > dave
