Good afternoon,
I am trying to run down a root cause of a link failure between two of my
HP Proliant DL350's. pciconf shows them as the 82571EB chip. These are
a 4 port card on the HP.
We are doing some routing code in the kernel and have a call to our entry
function in the forwarding path in
On 11/13/2010 02:27 PM, Ryan Stone wrote:
It looks to me that you're getting a ton of input drops. That's
presumably the cause of your issue. You can get the em driver to
print debug information to the console by running:
# sysctl dev.em.3.stats=1
# sysctl.dev.em.3.debug=1
The output should
On 11/13/2010 05:23 PM, Milen Dzhumerov wrote:
Hi all,
We're investigating some ways to perform symbolic execution of distributed systems and
we're looking for real-world programs to test. The "routed" daemon[1] which is
included with FreeBSD seemed like a good candidate and I was wondering
On 11/13/2010 09:08 PM, Jack Vogel wrote:
The stats changed quite a bit for 8.1, they are much more informative now,
and they can be collected from anywhere not just the console.
I don't quite understand what you are trying to do, debug an em problem
or just debug a problematic situation by us
On 4/5/11 10:38 AM, fbsdm...@dnswatch.com wrote:
>
> On Mon, April 4, 2011 5:07 pm, Eitan Adler wrote:
>> On Mon, Apr 4, 2011 at 7:35 PM, David Somayajulu
>> wrote:
>>
>>> Hi All,
>>> Is there some way I can setup a running FreeBSD - (I use PCBSD7.2) - to
>>> break into kgdb when the system pan
All,
We have a requirement for fail-to-wire that we are meeting by using these
types of bypass NIC's. We have some from Silicom where they provided us
a modified em(4) driver, but now we have a few NICs coming that are straight
from Intel. However the website doesn't list the correct driver(s) f
Can somebody confirm my assumption on the following:
If I am supporting ALTQ in a driver, then I should use the
IFQ_DRV_DEQUEUE() macro. If I am not supporting ALTQ then
it is okay IFQ_DEQUEUE() macro? If not what's the difference?
Slightly confused...
Thanks,
Patrick
__
On 8/24/11 11:42 AM, Sergey Kandaurov wrote:
> On 24 August 2011 22:12, Patrick Mahan wrote:
>> Can somebody confirm my assumption on the following:
>>
>> If I am supporting ALTQ in a driver, then I should use the
>> IFQ_DRV_DEQUEUE() macro. If I am not supporti
Not sure if this is the correct list, but I am working as part of
a kernel team that is using FreeBSD 8.0 for it's base OS.
We have had a ongoing issue with our bootloader (u-boot) with it
being unable to tftp from the tftp server running on our FreeBSD
server. We traced the issue down to the tf
See inline -
Janne Huttunen wrote:
Hi!
The selection of anonymous port in FreeBSD seems to act
a bit weird (bug?). This was first observed on actual
use on FreeBSD 6.2, but I have verified that the it
behaves the same on a December snapshot of CURRENT too.
1. A process creates an UDP socket an
All,
I have seen a few mentions on the mailing lists in regard to issues
with em(4) and FreeBSD 8.0 with regard to throughput.
We are also seeing similar issues on HP Proliant systems with
this HP GE interfaces. Previously we were running FreeBSD 6.2 and
iperf was showing ~900 Mbits/sec between
>
>[12]
>http://caia.swin.edu.au/newtcp/tools/caia_modularcc_v0.9.4_9.x.r203910.patch
>
>[13] http://caia.swin.edu.au/newtcp/tools/modularcc-readme-0.9.4.txt
>
I believe these are incorrect. I find these documents at the following URLs:
[12]
http://caia.swin.edu.au/urp/newtcp/tools/caia_modul
All,
Hoping for a little insight as I am not a user of multicast nor
do I know much about the servers that use them.
In my day job, I am helping with the moving of my company's product
from FreeBSD 6.2 (i386) to FreeBSD 8.0 (amd64). One of the daemons
wants to use 224.0.0.9 (routed? rip?) multi
he BSD box itself? If so, the app should determine
what interfaces to send on, and then use that. Can you recompile the
daemon for 8?
Pierre
Patrick Mahan wrote:
All,
Hoping for a little insight as I am not a user of multicast nor
do I know much about the servers that use them.
In my day
I am the first to admit I don't understand ALTQ and it's impact on QoS but
that said, I am trying to learn.
I have the following three systems. All systems are running FreeBSD 8.0-p2
Release.
I am attempting to learn how AltQ can be used to prioritized and setup banddwith
pipelines.
At the end
All,
I am looking for (again) some understanding of AltQ and how it works
w.r.t. packet through put. I posted earlier this month regarding how
to initially configure AltQ (thanks to everyone's help) and now have
it working over the em(4) drive on a FreeBSD 8.0 platform (HP DL350 G5).
I had to b
See my responses inline - PLM
On 07/30/2010 04:30 PM, Luigi Rizzo wrote:
On Fri, Jul 30, 2010 at 04:07:04PM -0700, Patrick Mahan wrote:
All,
I am looking for (again) some understanding of AltQ and how it works
w.r.t. packet through put. I posted earlier this month regarding how
to initially
17 matches
Mail list logo