All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: MaoXiaoyun <tinnycloud@hotmail.com>
Cc: xen devel <xen-devel@lists.xensource.com>, mchan@broadcom.com
Subject: Re: RE: bnx2 FTQ issues on 2.6.32 + xen 4.0.1;
Date: Sat, 30 Jul 2011 11:37:11 -0400	[thread overview]
Message-ID: <20110730153711.GA6541@dumpdata.com> (raw)
In-Reply-To: <BLU157-W57D9B36D086DFE1AC018BEDA360@phx.gbl>

On Sat, Jul 30, 2011 at 11:27:24PM +0800, MaoXiaoyun wrote:
> 
> I have below configuration in grub.conf, did u mean change 115200 to sth?
>  
> iommu=off x2apic=off console=com1,vga com1=115200,8n1

Hm, that is what I had in mind. That is not enough to get the data before your machine crashes?

When it crashes - you mean the watchdog timer hits - so your machine is still functioninig right?
Then you should be able to see the output of the driver in /var/log/messages,syslog I think?

You are still able to recover when the bnx drivers goes bonk, right?
>  
> thanks.
> 
>  
> 
> > Date: Sat, 30 Jul 2011 10:15:39 -0400
> > From: konrad.wilk@oracle.com
> > To: tinnycloud@hotmail.com
> > CC: mchan@broadcom.com; xen-devel@lists.xensource.com
> > Subject: Re: [Xen-devel] RE: bnx2 FTQ issues on 2.6.32 + xen 4.0.1;
> > 
> > > > > I've spent more time on this.
> > > > > It's easy to reproduce. I have two physical host, on top of which, totally start 15VMS, doing migrating over
> > > > > and over again. Since xen live migration invovle large mount of memory copy, so I can see that the network is
> > > > > saturated. About 16 hours later, the FTQ dump will show up.
> > > > > 
> > > > > I've debugged more. 
> > > > > Below debug code is added when FTQ happens.
> > > > > Does anyone know what is going on? 
> > > > 
> > > > No idea. Did Michael Chan send you a private email with some ideas?
> > > > 
> > > 
> > > Yep, Michael give me some debug patch. But unfortunately, when this bug show up, there is no enough time for the
> > > kernel to print all debugged log before it crashes. 
> > 
> > Can you use a serial console at a high baud rate?
>  		 	   		  

  reply	other threads:[~2011-07-30 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  5:38 bnx2 FTQ issues on 2.6.32 + xen 4.0.1; MaoXiaoyun
2011-07-04  7:09 ` MaoXiaoyun
2011-07-29 14:16   ` Konrad Rzeszutek Wilk
2011-07-30  1:52     ` MaoXiaoyun
2011-07-30 14:15       ` Konrad Rzeszutek Wilk
2011-07-30 15:27         ` MaoXiaoyun
2011-07-30 15:37           ` Konrad Rzeszutek Wilk [this message]
2011-07-30 15:48             ` MaoXiaoyun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110730153711.GA6541@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=mchan@broadcom.com \
    --cc=tinnycloud@hotmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.