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
When it crashes - you mean the watchdog timer hits - so your machine is still
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?
> > Date: Sat, 30 Jul 2011 10:15:39 -0400
> > From: konrad.wilk@xxxxxxxxxx
> > To: tinnycloud@xxxxxxxxxxx
> > CC: mchan@xxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx
> > 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?
Xen-devel mailing list