David Christensen wrote:
The next test is to diable the LOM's management firmware
but boot to
an active network. Get the User Diag utility at the bottom of
http://www.broadcom.com/support/ethernet_nic/netxtremeii.php.
Run the uxdiag utility with the command line:
"C:\>uxdiag -c 0 -mfw 0 -c 1
> > The next test is to diable the LOM's management firmware
> but boot to
> > an active network. Get the User Diag utility at the bottom of
> > http://www.broadcom.com/support/ethernet_nic/netxtremeii.php.
> > Run the uxdiag utility with the command line:
> > "C:\>uxdiag -c 0 -mfw 0 -c 1 -mfw
David Christensen wrote:
Can you try a different test? Power-on the system with the network
cable attached to an idle switch (i.e. keep all network
traffic from
being forwarded to the NIC during driver initialization). Does the
system power up successfully? Repeatedly? The problem I saw wa
> > Can you try a different test? Power-on the system with the network
> > cable attached to an idle switch (i.e. keep all network
> traffic from
> > being forwarded to the NIC during driver initialization). Does the
> > system power up successfully? Repeatedly? The problem I saw was
> > c
David Christensen wrote:
After fighting with the update process for a bit and then learning
about the live cycle manager I have managed to test the
R610 with the
5.0.9 firmware.
On the face of it, it seems that this resolves the issue.
After a reboot this morning the error has resurfaced and
> > After fighting with the update process for a bit and then learning
> > about the live cycle manager I have managed to test the
> R610 with the
> > 5.0.9 firmware.
> >
> > On the face of it, it seems that this resolves the issue.
> >
> After a reboot this morning the error has resurfaced and
Hello All:
I have a question about the implementation of IPsec version 3 in FreeBSD.
We are porting from FreeBSD 5.4 to 7.2 and currently run an IPv6 application
with IPsec version 2 and IKEv1 open source from the KAME group. Since the
KAME group disbanded (around when 5.4 was released), I don't
The following reply was made to PR kern/124127; it has been noted by GNATS.
From: Mark Atkinson
To: pyu...@gmail.com
Cc: bug-follo...@freebsd.org
Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) --
recovering
Date: Thu, 29 Oct 2009 10:47:47 -0700 (PDT)
- Original Mes
Tom Judge wrote:
David Christensen wrote:
Thanks for the rapid response.
Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834
Will that work?
Yes, that release does include a good version of BCM5709 bootcode
(v5.06).
I couldn't really tell until I downloaded the file and lo
The following reply was made to PR kern/124127; it has been noted by GNATS.
From: Pyun YongHyeon
To: Mark Atkinson
Cc: freebsd-net@freebsd.org, bug-follo...@freebsd.org
Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) --
recovering
Date: Thu, 29 Oct 2009 09:49:09 -0700
On Thu, Oct 29, 2009 at 06:52:34AM -0700, Mark Atkinson wrote:
> Wow, not sure what to blame for that charset nightmare. Apologies.
> Here's the original message:
>
> On the unpatched -current kernel, built
>
> FreeBSD hellfire.filament.org 9.0-CURRENT FreeBSD 9.0-CURRENT #14: Mon
> Oct 19 09:12
Wow, not sure what to blame for that charset nightmare. Apologies.
Here's the original message:
On the unpatched -current kernel, built
FreeBSD hellfire.filament.org 9.0-CURRENT FreeBSD 9.0-CURRENT #14: Mon
Oct 19 09:12:03 PDT 2009
I recieved the following panic today related to this:
Fatal tr
2009/10/29 Brooks Davis :
>> btw, wouldn't it be nice not to bother with loader.conf when using
>> . syntax?
>> This patch will load if_vlan automatically in this case:
>
> Sorry but my reation is: eww. There's no way I'd commit that. You'd be
> randomly loading the vlan code for any interface th
The following reply was made to PR kern/140036; it has been noted by GNATS.
From: Bernhard Schmidt
To: bug-follo...@freebsd.org, ka...@mit.edu
Cc:
Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock
and iwn0 softc lock
Date: Thu, 29 Oct 2009 08:19:44 +0100
Hi,
Rem
The following reply was made to PR kern/139145; it has been noted by GNATS.
From: Sten Spans
To: "Li, Qing"
Cc: freebsd-gnats-sub...@freebsd.org, freebsd-net@freebsd.org
Subject: RE: kern/139145: IPv6 blackhole / reject routes broken
Date: Thu, 29 Oct 2009 08:33:03 +0100 (CET)
On Wed, 28 Oct 2
On Wed, 28 Oct 2009, Li, Qing wrote:
I remember looking at this bug and tried to reproduce it ...
If my memory serves me right, I believe this bug was fixed by
svn r197364, committed on 9/20. RC1 was built on 9/17.
Another symptom of this bug is the "route get" command issued
on any lo0 addre
16 matches
Mail list logo
