Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Feb 2005 16:41:59 -0000
From:      "Alan Jay" <alan@cyclopsvision.co.uk>
To:        "'Doug White'" <dwhite@gumbysoft.com>
Cc:        freebsd-stable@freebsd.org
Subject:   RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard
Message-ID:  <20050215164253.C939F43D41@mx1.FreeBSD.org>
In-Reply-To: <20050214101303.R13953@carver.gumbysoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for this - the oddity is we have two identical machines and on one the
problem occurred we then moved the application over to the other machines that
had been working fine and it then exhibited the same symptoms - hence the
query about the broadcom controller.  I am hoping to so some further tests
using the other Ethernet controller on the board if I can get it plugged in
(unfortunately the machines are in a data center to which I don't have direct
access).

Thanks for the ideas.

ALan

> -----Original Message-----
> From: Doug White [mailto:dwhite@gumbysoft.com]
> Sent: Monday, February 14, 2005 6:16 PM
> To: Alan Jay
> Cc: freebsd-stable@freebsd.org
> Subject: Re: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan
> Motherboard
> 
> On Mon, 14 Feb 2005, Alan Jay wrote:
> 
> > I have FreeBSD 5.3 STABLE onto our new twin operteron Tyan Thunder K8S Pro
> > S2882 with 8Gb of RAM and had a reasonably stable operation for a few days
> we
> > installed a couple of databases one worked fine but the other kept on
> causing
> > the server to crash.
> 
> I'm about to gain access to an S2881, which is a similar board (different
> layout but same parts).
> 
> > I have searched the archive and there were issues last year but I couldn't
> > work out if these have been totally resolved?
> >
> > The adapter does work fine in low levels of loading but when pushed (it is
> > connected to a Gigabit switch) it seems to be the cause of the reboot - a
> what
> > appeared to be stable server with moderate Ethernet activity was fine
> upping
> > the activity with a new service caused regular reboots.
> >
> > There is no console message at the point of reboot to help that we have
> > spotted.
> 
> 
> Hm, triple fault or other hardware reset. This usually indicates bad
> hardware.  Have you tried swapping the RAM between the systems and seeing
> if the problem follows?  An unrecoverable ECC fault can cause a reboot,
> along with strangeness caused  by temperature/power supply/etc.  Or the
> board could be Just Plain Bad.
> 
> Considering you have one working machine, adn this is a very popular
> board, I don't think it s abasic problem with FreeBSD and this hardware.
> The worst thing reported is interrupt routing usually.
> 
> --
> Doug White                    |  FreeBSD: The Power to Serve
> dwhite@gumbysoft.com          |  www.FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050215164253.C939F43D41>