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:<Joachim.Thiessen@lsi.com>,<Caeli.Collins@lsi.com>,<Rich.LaReau@lsi.com>,<Brian.Stark@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	D3E7A1CF653678408D37D2A9AFE865E30115E3B130@cosmail03.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 25 Aug 2009 23:32:55 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Thiessen, Joachim" <Joachim.Thiessen@lsi.com>
Cc: "Collins, Caeli" <Caeli.Collins@lsi.com>, "LaReau, Rich"
 <Rich.LaReau@lsi.com>, "Stark, Brian" <Brian.Stark@lsi.com>
Subject: Re: Defect  SiByte Watchdog message after Bobcat to Cougar
 configuration transition TED00027247
Message-ID: <20090825233255.0f3d9329@ripper.onstor.net>
In-Reply-To: <D3E7A1CF653678408D37D2A9AFE865E30115E3B130@cosmail03.lsi.com>
References: <ee5e3a65-38da-485a-ac59-015f11339916@exch1.onstor.net>
	<D3E7A1CF653678408D37D2A9AFE865E30115E3B130@cosmail03.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

On Tue, 25 Aug 2009 17:37:33 -0600 "Thiessen, Joachim"
<Joachim.Thiessen@lsi.com> wrote:

> Hello Andy,
> 
> I cannot decide if this will be fixed, but I encountered the SiByte
> Watchdog message again. This time it was a regular Cougar 6000
> installation. As soon as I receive the SiByte Watchdog message, I
> have to race to reboot blade one, otherwise the whole system hangs
> and becomes unusable. 
> 
> In this case, the red System LED turned on and the SiByte message
> appeared. If I wait too long, the clusterDB will turn off and the
> system will hang. I had to reboot blade one to reset the System LED
> and stop the SiByte Watchdog message. 

Hm, well, we clearly need to look into that.  Just know that the message
is a symptom, not the error itself.  Ie., it doesn't have anything to do
with the watchdog having a problem, it's more like the watchdog timer
is getting close to rebooting the system because it appears to be
almost hung.

Just curious, what do you mean by "...the clusterDB will turn off..."?

Cheers,

a

> Regards...
> 
> ...Joachim
> 
> ________________________________________
> From: andy.sharp@lsi.com [andy.sharp@lsi.com]
> Sent: Tuesday, August 25, 2009 11:12 AM
> To: Sharp, Andy; Thiessen, Joachim
> Subject: Defect  SiByte Watchdog message after Bobcat to Cougar
> configuration transition TED00027247
> 
> Area_of_problem: SW-Initial Configuration
> Headline: SiByte Watchdog message after Bobcat to Cougar
> configuration transition id: TED00027247
> Note_Entry:
> There doesn't seem to be any impact from this, and of course it's hard
> to reproduce.  What's going on is that some daemon, possibly the vsvr
> daemon, is going critical and using up a lot of the SSC.  Whatever
> it's problem is, it eventually gets solved and the problem goes away.
> 
> I would say this is a WBTF (won't bother to fix).
> 
> Project:
> Severity: 2-Major
> State: Assigned
> Submitter: joachimt
> Release_Project: 4.0.2.3
> 
