--On Thursday, July 12, 2007 16:11:11 -0700 David Christensen
<[EMAIL PROTECTED]> wrote:
Dave, perhaps you could answer my question?
I'm using the 0.9.6 driver with 6.1 RELEASE. I don't use
jumbo frames, so
the only problem I've experienced is the link state going up and down
occasionally.
D
> Dave, perhaps you could answer my question?
>
> I'm using the 0.9.6 driver with 6.1 RELEASE. I don't use
> jumbo frames, so
> the only problem I've experienced is the link state going up and down
> occasionally.
>
> Does the more current driver solve the link state problem?
> If it does,
--On Thursday, July 12, 2007 15:10:31 -0700 David Christensen
<[EMAIL PROTECTED]> wrote:
I'm sorry I haven't been able to get to the root of your problems
Tom. My biggest challenge is trying to duplicate the a loaded system
which seems to be an important component of the failure you're seeing.
> Firstly I am not trying to slate David's efforts, however
> there are and
> have been some big problems with the driver.
>
> As for the IPMI integration, our management controllers are
> set to used
> the remote access controller NIC (Set as dedicated in the
> bios) rather
> than share the
Tom Judge wrote:
Julian Elischer wrote:
Tom Judge wrote:
Josh Paetzel wrote:
On Wednesday 11 July 2007, Tom Judge wrote:
Hi Paul,
From the testing that I have been doing for the last few months
the driver in 6.2 is stable if you are not using jumbo frames and
there is a light-moderate netwo
Gary Palmer wrote:
On Thu, Jul 12, 2007 at 10:31:41AM +0100, Tom Judge wrote:
Julian Elischer wrote:
Tom Judge wrote:
Josh Paetzel wrote:
On Wednesday 11 July 2007, Tom Judge wrote:
Hi Paul,
From the testing that I have been doing for the last few months
the driver in 6.2 is stable if you a
On Thu, Jul 12, 2007 at 10:31:41AM +0100, Tom Judge wrote:
> Julian Elischer wrote:
> >Tom Judge wrote:
> >>Josh Paetzel wrote:
> >>>On Wednesday 11 July 2007, Tom Judge wrote:
> Hi Paul,
>
> From the testing that I have been doing for the last few months
> the driver in 6.2 is st
Doug Ambrisko wrote:
Tom Judge writes:
|
| I am very surprised at that. The driver in 6.1 was un-usable in our
| environment. 6.2 makes it usable with standard frames under moderate
| load. However use jumbo frames and it all falls apart, and unfortunately
| the network these systems are pl
Tom Judge writes:
| Julian Elischer wrote:
| > Tom Judge wrote:
| >> Josh Paetzel wrote:
| >>> On Wednesday 11 July 2007, Tom Judge wrote:
| Hi Paul,
|
| From the testing that I have been doing for the last few months
| the driver in 6.2 is stable if you are not using jumbo fra
Julian Elischer wrote:
Tom Judge wrote:
Josh Paetzel wrote:
On Wednesday 11 July 2007, Tom Judge wrote:
Hi Paul,
From the testing that I have been doing for the last few months
the driver in 6.2 is stable if you are not using jumbo frames and
there is a light-moderate network load.
However
--On July 11, 2007 1:51:04 PM -0500 Josh Paetzel <[EMAIL PROTECTED]> wrote:
I was running the driver from STABLE until about March and it would
bounce the link up and down a couple times a day even under
relatively moderate load. (50-60 mbps) So perhaps there have been
improvements since then,
Tom Judge wrote:
Josh Paetzel wrote:
On Wednesday 11 July 2007, Tom Judge wrote:
Hi Paul,
From the testing that I have been doing for the last few months
the driver in 6.2 is stable if you are not using jumbo frames and
there is a light-moderate network load.
However if you want to use Jumbo
Josh Paetzel wrote:
On Wednesday 11 July 2007, Tom Judge wrote:
Hi Paul,
From the testing that I have been doing for the last few months
the driver in 6.2 is stable if you are not using jumbo frames and
there is a light-moderate network load.
However if you want to use Jumbo frames the driver
On Wednesday 11 July 2007, Paul Schmehl wrote:
> >
> > Paul, I was never able to solve the link up/link down problems
> > with the driverI was using the drivers from STABLE for a
> > while, and without jumbo frames everything worked somewhat ok
> > most of the timethe ultimate solution was
On Wednesday 11 July 2007, Tom Judge wrote:
> Paul Schmehl wrote:
> > I'm running 6.1 RELEASE (i386) and I've been replacing the
> > if_bce.c file with a slightly newer one that at least got the
> > driver working without hard lockups that required a reboot to
> > fix. (Rather problematic on a rem
--On Wednesday, July 11, 2007 12:30:21 -0500 Josh Paetzel <[EMAIL PROTECTED]>
wrote:
On Wednesday 11 July 2007, Tom Judge wrote:
Paul Schmehl wrote:
> I'm running 6.1 RELEASE (i386) and I've been replacing the
> if_bce.c file with a slightly newer one that at least got the
> driver working wit
Paul Schmehl wrote:
I'm running 6.1 RELEASE (i386) and I've been replacing the if_bce.c file
with a slightly newer one that at least got the driver working without
hard lockups that required a reboot to fix. (Rather problematic on a
remotely located web server.)
If I download the latest driv
I'm running 6.1 RELEASE (i386) and I've been replacing the if_bce.c file
with a slightly newer one that at least got the driver working without hard
lockups that required a reboot to fix. (Rather problematic on a remotely
located web server.)
If I download the latest driver from cvs (1.33), s
18 matches
Mail list logo
