AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090304150515.14cd62d1@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:exch1.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<richard.lareau@onstor.com>,<caeli.collins@onstor.com>,<john.culp@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	2779531E7C760D4491C96305019FEEB518521AC6B6@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 4 Mar 2009 15:05:58 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Brian Stark <brian.stark@onstor.com>
Cc: Rich LaReau <richard.lareau@onstor.com>, Caeli Collins
 <caeli.collins@onstor.com>, John Culp <john.culp@onstor.com>
Subject: Re: Infinium case 11580
Message-ID: <20090304150558.0b3ca656@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB518521AC6B6@exch1.onstor.net>
References: <2779531E7C760D4491C96305019FEEB51851C0CB4A@exch1.onstor.net>
	<2779531E7C760D4491C96305019FEEB518521AC638@exch1.onstor.net>
	<20090304143709.4b3df3c7@ripper.onstor.net>
	<2779531E7C760D4491C96305019FEEB518521AC6B6@exch1.onstor.net>
Organization: Onstor
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 Wed, 4 Mar 2009 14:42:30 -0800 Brian Stark <brian.stark@onstor.com>
wrote:

> The problem apparently occurs on the bottom slot, which does not
> involve the riser card.  
> 
> Could it be related to the CF vendor?  

I would have first guessed a bad CF card period, but then they said the
problem went away after they reseated the blade.  Which I'm somewhat
skeptical about, BTW.  But not the same problem as when a non-IDing CF
card that we haven't seen before is introduced.

So <mumble-fratz> my best guess would still be a bad CF card.  BTW, if
it does turn out to be a bad CF card, can we make sure that it makes
its way back to me eventually, so that I can use it to try to make the
software a little more helpful in identifying the problem?  Thanks.

> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, March 04, 2009 2:37 PM
> To: Rich LaReau
> Cc: Brian Stark; Caeli Collins; John Culp
> Subject: Re: Infinium case 11580
> 
> Definitely a hardware problem, either with the card itself of board:
> 
> The messages from the kernel while probing and setting up the
> pcmcia/CF:
> 
> 
> Yenta TI: socket 0000:00:07.0, mfunc 0x00000022, devctl 0x60
> irq 56: nobody cared (try booting with the "irqpoll" option)
> Call Trace:
> [<ffffffff82007170>] dump_stack+0x8/0x38
> [<ffffffff82050580>] __report_bad_irq+0x40/0xd8
> [<ffffffff820508a8>] note_interrupt+0x290/0x2d8
> [<ffffffff8204f7d0>] __do_IRQ+0x140/0x160
> [<ffffffff820011a4>] plat_irq_dispatch+0x1e4/0x1f0
> [<ffffffff82001840>] ret_from_irq+0x0/0x4
> [<ffffffff8202a4b8>] __do_softirq+0x78/0x140
> [<ffffffff8202a610>] do_softirq+0x90/0x98
> [<ffffffff82001840>] ret_from_irq+0x0/0x4
> [<ffffffff8204fdf0>] setup_irq+0x178/0x2a0
> [<ffffffff82050008>] request_irq+0xf0/0x110
> [<ffffffff82189b4c>] yenta_probe_cb_irq+0x64/0x120
> [<ffffffff8218a0dc>] ti12xx_override+0x15c/0x6b0
> [<ffffffff8218b684>] yenta_probe+0x59c/0x6f0
> [<ffffffff82138544>] pci_device_probe+0x84/0xa8
> [<ffffffff82150084>] driver_probe_device+0xa4/0x220
> [<ffffffff8215043c>] __driver_attach+0xfc/0x148
> [<ffffffff8214ef58>] bus_for_each_dev+0x58/0xb8
> [<ffffffff8214f49c>] bus_add_driver+0xb4/0x230
> [<ffffffff82138770>] __pci_register_driver+0x58/0xb0
> [<ffffffff822d46a8>] kernel_init+0xd0/0x2f8
> [<ffffffff82003930>] kernel_thread_helper+0x10/0x18
> 
> handlers:
> [<ffffffff8218b910>] (yenta_probe_handler+0x0/0x58)
> Disabling IRQ #56
> 
> It's getting an interrupt that it shouldn't, and so disables it.  It
> dumps stack at that point for diagnostic purposes.
> 
> This is similar to a problem an SE reported recently; apparently they
> reseated the blade in question and the problem disappeared.  At least,
> that's what I was told.  Since this system is a 3xxx, they obviously
> can't reseat the blade.
> 
> Is it possibly that the CF riser can get jostled loose in shipment?
> Or is that silly and ridiculous?  I'm just throwing out ideas here.
> 
> Cheers,
> 
> a
> 
> 
> On Wed, 4 Mar 2009 12:43:42 -0800 Rich LaReau
> <richard.lareau@onstor.com> wrote:
> 
> > 
> > At this point I think we've exhausted customer's patience, and will
> > probably need to do the RMA regardless.   
> > 
> > Attached are the dmsg we got from the last boot-- was that what you
> > needed?  We couldn't ever get a serial console to work.  
> > 
> > Let me know what you'd like me to do.
> > 
> > Rich
> > 
> > 
> > -----Original Message-----
> > From: Brian Stark 
> > Sent: Wednesday, March 04, 2009 12:28 PM
> > To: Rich LaReau; Caeli Collins; John Culp
> > Cc: Andy Sharp
> > Subject: Re: Infinium case 11580
> > 
> > I need to see the SSC console logs before we do an RMA.  Also, what
> > CF slot is primary and which is secondary?  Have you tried booting
> > without the suspect CF installed? 
> > 
> > Also, I'm copying Andy Sharp so that he can weigh in.
> > 
> > Note that we test both CF slots in Ops prior to shipment.
> > 
> > 
> > 
> > ----- Original Message -----
> > From: Rich LaReau
> > To: Brian Stark; Caeli Collins; John Culp
> > Sent: Wed Mar 04 12:23:04 2009
> > Subject: Infinium case 11580
> > 
> > 
> > 
> > Hi all,
> > 
> > We have an ongoing problem at Infinium in Chicago.  They needed to
> > upgrade to resolve a problem, but we could not get the secondary
> > flash to mount.  We shipped a new flash and when that one is used
> > the system won't come up at all (even though we're still booting
> > off the same, primary card!)  We tried several permutations, and
> > I'll have some dmsg logs shortly.  In the meantime, I think we
> > should RMA this unit and get him started fresh.  
> > 
> > System (3310 running 4.0.1.0)  is not in production, but customer is
> > pretty upset.  The unit is in a remote data center, so has been hard
> > to reach to get worked on.  
> > 
> > Fred is updating case and sending logs.  More to come.
> > 
> > Rich
