On 7/16/11 5:43 AM, Vlad Galu wrote:
Hello,
A couple of years ago, Stef Walter proposed a patch[1] that enforced the scope
of routing messages. The general consesus was that the best approach would be
the OpenBSD way - transporting the FIB number in the message and letting the
user applicatio
Hi all,
I apologise up front for the cross-posting. Please redirect all future
queries about this to freebsd-wirel...@freebsd.org.
I guess the cat is out of the bag (and it hasn't killed anyone yet.)
For the last 6 or so months, the if_ath driver and net80211 802.11n
support has been updated to (
Hello.
How to determine which module contains specific functinos?. For example
we have arptimer in netinet/if_ether.c.
But how to find in which ko it compiles?
Iv tried
ls /boot/kernel/ | grep ko.symbols | xargs strings | grep -i arptimer
but that didnt work :(
Thanks in advance.
_
On 7 September 2011 16:51, Vladimir Budnev wrote:
> Hello.
>
> How to determine which module contains specific functinos?. For example we
> have arptimer in netinet/if_ether.c.
> But how to find in which ko it compiles?
> Iv tried
> ls /boot/kernel/ | grep ko.symbols | xargs strings | grep -i arpt
On 07.09.2011 11:17, Julian Elischer wrote:
On 7/16/11 5:43 AM, Vlad Galu wrote:
Hello,
Hello!
A couple of years ago, Stef Walter proposed a patch[1] that enforced
the scope of routing messages. The general consesus was that the best
approach would be the OpenBSD way - transporting the FIB nu
On Wed, Sep 07, 2011 at 04:51:48PM +0400, Vladimir Budnev wrote:
> Hello.
>
> How to determine which module contains specific functinos?. For example
> we have arptimer in netinet/if_ether.c.
> But how to find in which ko it compiles?
> Iv tried
> ls /boot/kernel/ | grep ko.symbols | xargs string
The following reply was made to PR kern/136426; it has been noted by GNATS.
From: Nikos Vassiliadis
To: bug-follo...@freebsd.org, nvass9...@gmx.com
Cc:
Subject: Re: kern/136426: [panic] spawning several dhclients in parallel panics
the kernel
Date: Wed, 07 Sep 2011 17:23:18 +0300
Please clos
Hello list!
(CC'in Jack Vogel since this is intel drivers/hardware specific question)
There are some techniques for assigning network traffic to different NIC
RX queues (bound to different CPUs/cores).
The main problem for all techniques is avoiding any possible packet
reordering in single flo
Arp - is a part of INET (ipv4).
But arp proto can be used with any other L3 proto to resolve L2 addr from L3
addr.
TCP/IP is L4 proto and it can work without IPv4 - on IPv6.
--
Rozhuk Ivan
> -Original Message-
> From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-
> n...@free
Synopsis: [panic] spawning several dhclients in parallel panics the kernel
State-Changed-From-To: open->closed
State-Changed-By: vwe
State-Changed-When: Wed Sep 7 16:39:59 UTC 2011
State-Changed-Why:
closing this per submitters request
thank you for reporting, Nikos
Responsible-Changed-From-To
Hi,
On Mon, Sep 5, 2011 at 2:59 AM, Arnaud Lacombe wrote:
> Hi folks,
>
> We have been trying to track down a bad mbuf management for about two
> weeks on a customized 7.1 base. I have finally been able to reproduce
> it with a stock FreeBSD 7-STABLE (kernel from r225276, userland from
> 7.4).
>
I have seen this, but I don't have any hot ideas right off the top of my
head yet :(
Jack
On Wed, Sep 7, 2011 at 4:19 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Mon, Sep 5, 2011 at 2:59 AM, Arnaud Lacombe wrote:
> > Hi folks,
> >
> > We have been trying to track down a bad mbuf management for abo
On Wed, 2011-09-07 at 16:19 -0700, Arnaud Lacombe wrote:
> Hi,
>
> On Mon, Sep 5, 2011 at 2:59 AM, Arnaud Lacombe wrote:
> > Hi folks,
> >
> > We have been trying to track down a bad mbuf management for about two
> > weeks on a customized 7.1 base. I have finally been able to reproduce
> > it wit
Hi,
On Wed, Sep 7, 2011 at 8:18 PM, Sean Bruno wrote:
> On Wed, 2011-09-07 at 16:19 -0700, Arnaud Lacombe wrote:
>> Hi,
>>
>> On Mon, Sep 5, 2011 at 2:59 AM, Arnaud Lacombe wrote:
>> > Hi folks,
>> >
>> > We have been trying to track down a bad mbuf management for about two
>> > weeks on a custo
14 matches
Mail list logo