Date: Wed, 18 Apr 2007 20:35:41 +0800 From: "Rong-en Fan" <grafan@gmail.com> To: "Tom Evans" <tevans.uk@googlemail.com> Cc: =?BIG5?B?SmFzb24gQ2hhbmcgsWmzx6XN?= <jsc@ntu.edu.tw>, freebsd-stable@freebsd.org Subject: Re: bge watchdog timeout -- resetting problem on recent update Message-ID: <6eb82e0704180535y1f23bd99p4f17a1e123605ba6@mail.gmail.com> In-Reply-To: <1176897566.1540.14.camel@zoot.mintel.co.uk> References: <20070418093837.GA32573@ccms.ntu.edu.tw> <1176897566.1540.14.camel@zoot.mintel.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/18/07, Tom Evans <tevans.uk@googlemail.com> wrote:
> On Wed, 2007-04-18 at 17:38 +0800, Jason Chang 張傑生 wrote:
> > Dear All,
> >
> > After recent cvsup and make world, my server suffered from the
> > bge watchdog timeout -- resetting problem. Manually revert the
> > bge related source to older version and compiled a new kernel
> > may solve the problem. So I guess the recent committed source
> > does not go well with bge nics onboard of IBM e326m servers.
>
> Hi Jason
>
> Can you add
>
> hw.pci.enable_msi=0
> hw.pci.enable_msix=0
>
> to /boot/loader.conf and reboot and see if that solves the problem.
>
> I saw this problem a while ago on my -CURRENT with a misbehaving MSI on
> my motherboard. (I may have this completely wrong; I'm not even 100%
> sure the MSI stuff has been MFC'ed to -STABLE).
MSI stuffs are MFC'ed to 6.x since April 1 by jhb@, but I
thought to use MSI, one MUST set hw.pci.enable_{msi,msix} to
1 in loader.conf as the commit log said.
But from the revision changes that Jason posted, the most
suspicious part is MSI...
Regards,
Rong-En Fan
>
> Cheers
>
> Tom
>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e0704180535y1f23bd99p4f17a1e123605ba6>