BroadcomBCM5704C 10/100/1000 on TyanThunder K8S pro S2882 twin[Alan Jay] Operteron

[Alan Jay]

> -----Original Message-----
> From: Doug White [mailto:dwhite at gumbysoft.com]
> Sent: Friday, March 11, 2005 7:11 AM
> To: Alan Jay
> Cc: freebsd-amd64 at freebsd.org
> Subject: RE: BroadcomBCM5704C 10/100/1000 on TyanThunder K8S pro S2882
> twin[Alan Jay] Operteron
> 
> On Thu, 10 Mar 2005, Alan Jay wrote:
> 
> >
> > > From: Doug White <dwhite at gumbysoft.com>
> > >
> > > On Mon, 7 Mar 2005, Alan Jay wrote:
> > >
> > > > Well after upgrading to the latest -STABLE via cvsup and makeworld
> > > makekernel
> > > > etc we have been doing some more tests over the weekend.
> > >
> > > When did you run this cvsup?
> >
> > [Alan Jay] March 2nd.
> 
> Being that its been a week  you might give this another spin.

[Alan Jay] Did so this weekend.  CVSUP'd to the latest version
 
> > [Alan Jay] We have done that but the serial terminal is attached to a
> terminal
> > concentrator and it seems to timeout before logging any useful
> information.
> > When we succeeded there was nothing on the serial console in the way of a
> > panic message.  Sorry not sure how to do a backtrace or crashdump?
> 
> See the section on kernel debugging in the Developer's Handbook. You
> activate crashdumps by nominating a partition that is at least as large as
> memory with the 'dumpdev' rc.conf variable (and can be enabled at runtime
> with the 'dumpon' command).  Once the machine panics and creates the
> crashdump, on the ensuing reboot savecore will automatically run and
> extract the crashdump. With the crashdump in hand you can use kgdb and a
> debugging kernel image to figure out what happened.

[Alan Jay] I tried to understand this but may have missed something in how to
do it as not sure if it is working or not.
 
> > > > By the way over the weekend the latest -STABLE which is marked 5.4-
> > > PRERELEASE
> > > > 2 seemed much better than 5.3 had and the initial problems took much
> > > longer to
> > > > appear.  Though once the problems started to appear, they repeated
> > > themselves
> > > > rebooting every 1-2hrs until we removed the tests data.
> 
> Right, but a failed fan keeps that nice cool air from getting to the
> burning hot parts. :)

[Alan Jay] Well the fans all see m fine and having reinstalled we thought we
would do some more tests.  As a first step we decided to use the option to set
the memory to be limited to 4Gb.  Unfortunately the computer crashed shortly
after starting the test and I didn't manage to get anything useful out of the
above commands which I must not have fully understood.  Unfortunately no
additional information on why it crashed but even with only 4Gb of RAM in play
it fell over quite quickly

Anyway the report back is that the latest version Prerelase 3 still have this
problem.

Regards
ALan
 
> --
> Doug White                    |  FreeBSD: The Power to Serve
> dwhite at gumbysoft.com          |  www.FreeBSD.org