On Tue, May 20, 2025 at 10:05 PM Lexi Winter wrote:
>
> hello,
>
> i have just MFC'd the sysctl net.link.bridge.member_addrs to stable/14.
> for detail see:
> https://cgit.freebsd.org/src/commit/?h=stable/14&id=ff1980d569c8167d38cda5f2713664866d9802bc
>
> in short, if you have a bridge with a lot
From: Chandrakanth Patil
Date: Mon, May 6, 2024 at 10:24 PM
Subject: NIC RoCE Driver
To: Warner Losh
Hi Warner,
We have submitted the new NIC RoCE driver for review a week back. Could you
please review and provide the feedback.
Below are the patches link:
https://reviews.freebsd.org/D45005
I'll remind everybody that ifconfig has had IFCONFIG_FORMAT since
```
commit 7c2aa744374aa3449ad81f60852e74ad73d823e6
Author: Allan Jude
Date: Tue May 31 17:30:08 2016 +
ifconfig(8) now supports some output formatting options
```
so we've already 7 years into this process. This is nothi
On Fri, Apr 26, 2024, 9:33 PM Bakul Shah wrote:
>
>
> > On Apr 26, 2024, at 5:02 PM, Mike Karels wrote:
> >
> > On 26 Apr 2024, at 18:06, Warner Losh wrote:
> >
> >> On Fri, Apr 26, 2024 at 4:21 PM Mike Karels wrote:
> >>
> >>> On
On Fri, Apr 26, 2024 at 4:21 PM Mike Karels wrote:
> On 26 Apr 2024, at 15:49, Mike Karels wrote:
>
> > On 26 Apr 2024, at 15:01, Warner Losh wrote:
> >
> >> This has to be a FAQ
> >>
> >> I'm porting a program from Linux, I often see an error
This has to be a FAQ
I'm porting a program from Linux, I often see an error like:
./test/mock-ifaddrs.c:95:19: error: no member named 's6_addr32' in 'struct
in6_addr'
95 | ipv6->sin6_addr.s6_addr32[3] = 0;
| ~~~ ^
but yet, we kinda define them,
The following CI tests have been failing for a while (weeks?). I've
disabled them in CI and filed bugs.
sys.net.if_bridge_test.span
sys.netpfil.pf.forward.v6
sys.netpfil.pf.set_tos.v6
sys.netpfil.pf.killstate.v6
https://bugs.freebsd.org/260461
https://bugs.freebsd.org/260460
https://bugs.freebsd.
On Wed, Dec 2, 2020 at 5:13 PM Brooks Davis wrote:
> I'd like to propose that we remove the ndis(4) driver prior to FreeBSD
> 13. It was a clever idea in the early 2000's when the market was
> flooded with 10/100 NICs with Windows-only drivers, but that hasn't been
> the case for ages and the dr
On Sun, May 12, 2019, 9:28 PM Rodney W. Grimes <
freebsd-...@gndrsh.dnsmgr.net> wrote:
> > Eugene Grosbein wrote:
> > > 11.05.2019 22:59, Julian H. Stacey wrote:
> > >
> > > >> 11.05.2019 21:32, Julian H. Stacey wrote:
> > > >>
> > > I've posted a review to remove obsolete 10 and 10/100 Ether
On Sun, May 12, 2019, 12:00 PM Eugene Grosbein wrote:
> 12.05.2019 8:21, Warner Losh wrote:
>
> > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet
> drivers
> > >> as previous approved in FCP-101.
> > >> The follow
On Sat, May 11, 2019, 12:52 PM Eugene Grosbein wrote:
> 11.05.2019 21:32, Julian H. Stacey wrote:
>
> >> I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers
> >> as previous approved in FCP-101.
> >> The following drivers are slated for
> >> removal from FreeBSD-HEAD (to be Fre
On Sat, May 11, 2019, 12:03 PM Rodney W. Grimes <
freebsd-...@gndrsh.dnsmgr.net> wrote:
> > > I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers
> > > as previous approved in FCP-101.
> > > The following drivers are slated for
> > > removal from FreeBSD-HEAD (to be FreeBSD-13):
On Fri, Feb 1, 2019, 11:05 AM Brooks Davis On Fri, Feb 01, 2019 at 04:00:50AM -0800, Rodney W. Grimes wrote:
> > > On Thu, Jan 31, 2019 at 11:43:44PM +, Brooks Davis wrote:
> > > > We are currently planning to remove the following less-popular 10/100
> > > > Ethernet drivers in the March/April
On Wed, Oct 24, 2018 at 5:02 AM Bob Bishop wrote:
>
> > On 24 Oct 2018, at 01:23, Warner Losh wrote:
> >
> > On Tue, Oct 23, 2018 at 6:02 PM Rodney W. Grimes <
> > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> >
> >> -- Start of PGP signed section
On Wed, Oct 24, 2018 at 6:19 AM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > > On 24 Oct 2018, at 01:23, Warner Losh wrote:
> > >
> > > On Tue, Oct 23, 2018 at 6:02 PM Rodney W. Grimes <
> > > freebsd-...@pdx.rh.cn85.dnsmgr.ne
On Tue, Oct 23, 2018 at 6:02 PM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> -- Start of PGP signed section.
> > On Tue, Oct 23, 2018 at 04:26:45PM -0700, Rodney W. Grimes wrote:
> > > > On Tue, Oct 23, 2018 at 5:07 PM Rodney W. Grimes <
> > > > freebsd-...@pdx.rh.cn85.dnsmgr.ne
On Tue, Oct 23, 2018 at 5:26 PM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Tue, Oct 23, 2018 at 5:07 PM Rodney W. Grimes <
> > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> >
> > > > On Tue, Oct 23, 2018 at 11:33:35PM +0200, Julian H. Stacey wrote:
> > > > > > I'd also sug
On Tue, Oct 23, 2018 at 3:57 PM Julian H. Stacey wrote:
> Doug Hardie wrote:
> > I have a number of production servers that only have bge and I don't see
> that listed in either category. None of them are running FreeBSD 12 yet as
> it has not been released. Also there are some with rl. Those
On Tue, Oct 23, 2018 at 5:07 PM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Tue, Oct 23, 2018 at 11:33:35PM +0200, Julian H. Stacey wrote:
> > > > I'd also suggest that rl stands in stark contrast to the cs, wb, sn,
> smc,
> > > > sf, tl, tx and vr drivers, which nobody ha
On Wed, Oct 17, 2018 at 11:52 AM Matthieu Volat wrote:
> Would it be possible to set a wiki page/section in 12 that display the
> current status of removal of those devices? That might be easier for people
> to look at their hardware actual state rather than try to trace every
> answer to this th
On Mon, Oct 8, 2018 at 11:03 AM Brooks Davis wrote:
> On Sun, Oct 07, 2018 at 11:25:48AM +0200, Andrea Venturoli wrote:
> > On 10/4/18 3:07 PM, Warner Losh wrote:
> >
> > > At the root of this problem is the community's long resistance to
> having
> > &g
On Fri, Oct 5, 2018 at 9:05 AM Andrew Turner wrote:
>
> > On 3 Oct 2018, at 22:05, Brooks Davis wrote:
> >
> Please direct replies to freebsd-arch <<<
> >
> > FCP-01010 (https://github.com/freebsd/fcp/blob/master/fcp-0101.md)
> > outlines a plan to deprecate most 10/100 Ethernet drivers in
On Fri, Oct 5, 2018 at 8:46 AM Julian H. Stacey wrote:
> > >>> Please direct replies to freebsd-arch <<<
> >
> > FCP-01010 (https://github.com/freebsd/fcp/blob/master/fcp-0101.md)
> > outlines a plan to deprecate most 10/100 Ethernet drivers in FreeBSD 12
> > and remove them in FreeBSD 13 to redu
On Thu, Oct 4, 2018 at 12:18 PM Eugene Grosbein wrote:
> 05.10.2018 0:38, Warner Losh wrote:
>
> > I'd also suggest that rl stands in stark contrast to the cs, wb, sn, smc,
> > sf, tl, tx and vr drivers, which nobody has mentioned in this thread, and
> > which I do
On Thu, Oct 4, 2018 at 11:47 AM Ian Lepore wrote:
> On Thu, 2018-10-04 at 11:38 -0600, Warner Losh wrote:
> > On Thu, Oct 4, 2018 at 11:26 AM Ian Lepore wrote:
> >
> > >
> > > On Thu, 2018-10-04 at 10:21 -0600, Warner Losh wrote:
> > > >
> > &g
On Thu, Oct 4, 2018 at 11:26 AM Ian Lepore wrote:
> On Thu, 2018-10-04 at 10:21 -0600, Warner Losh wrote:
> > On Thu, Oct 4, 2018 at 10:15 AM Michelle Sullivan
> > wrote:
> >
> > >
> > > tech-lists wrote:
> > > >
> > > >
> >
On Thu, Oct 4, 2018 at 10:15 AM Michelle Sullivan
wrote:
> tech-lists wrote:
> >
> > I'm astonished you're considering removing rl given how common it is.
> >
>
> I'll second that comment - though no disrespect to Brooks. Brooks as
> far as I can see is just the messenger.
>
Absent good data, o
On Thu, Oct 4, 2018 at 9:59 AM Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Thu, Oct 4, 2018 at 9:46 AM Cy Schubert
> > wrote:
> >
> > > I'm willing to help out with rl(4) as I have one here. Others, not
> > > scheduled for removal, that I can help one way or another are a
On Thu, Oct 4, 2018 at 9:46 AM Cy Schubert
wrote:
> I'm willing to help out with rl(4) as I have one here. Others, not
> scheduled for removal, that I can help one way or another are are NICs,
> including wireless, currently installed here.
>
There's an iflib man page that's a decent place to st
On Thu, Oct 4, 2018 at 8:40 AM Alexey Dokuchaev wrote:
> On Thu, Oct 04, 2018 at 02:26:44PM +, Mark Linimon wrote:
> > On Thu, Oct 04, 2018 at 08:44:11AM +, Alexey Dokuchaev wrote:
> > > OK I guess I can understand removing 10 (I personally haven't seen
> > > one in a very long time) but
On Thu, Oct 4, 2018 at 2:45 AM Alexey Dokuchaev wrote:
> Looking at the commits they require near zero maintenance. What exactly
> is the burden here?
>
I believe that characterization is incorrect. There's a burden. And it's
death of a thousand cuts. And many of those cuts have been inflicted
On Thu, Oct 4, 2018 at 6:53 AM Luciano Mannucci
wrote:
> On Thu, 4 Oct 2018 13:03:01 +0700
> Eugene Grosbein wrote:
> > > The current list of drivers that will STAY in the tree is:
> > >
> > > dc, ffec, fxpl, hme, le, sis, vr, xl
> >
> > "fxpl" should have been "fxp" here, I suppose.
>
Yes.
>
imp added a comment.
So why doesn't the lle* code set mpsafe to 1? After re-reading the man page
several times, I'm thinking that's the solution here. It already uses other
locks and reference counts to synchronize things, so why get Giant involved at
all?
REVISION DETAIL
https://reviews.fre
imp added a comment.
For the lle* code, it looks like the reference count for the data structure
improperly doesn't cover the implicit use of the mutex by the callout system.
That seems to be the real bug here, no? Protecting a mutex with a reference
count without holding a reference to that mu
imp accepted this revision.
imp added a comment.
I think we're ready to land. It fixes all the issues discussed, and enhanced
testing shows no additional errors.
INLINE COMMENTS
kern/kern_timeout.c:1159 "When the callout wheel runs, it will ignore this
callout" maybe is a better phrase to use
imp added a comment.
Except for the signed / unsigned issue, I like this change. However, please get
approval from some of the networking guys before committing.
INLINE COMMENTS
sys/netinet/ip_input.c:1450 Shouldn't this be unsigned?
sys/netinet/ip_output.c:129 shouldn't this be unsigned?
imp added a comment.
I agree that the kernel test framework should be done differently as well.
I didn't realize the number of mechanical changes my request to use the macros
produced :(
INLINE COMMENTS
sys/sys/callout_test.h:1 I'm not sure that the callout_test.h belong in sys.
Seems like n
imp added a comment.
For the commit, I'd separate out the timeout fix from the kernel testframework.
REVISION DETAIL
https://reviews.freebsd.org/D1711
To: rrs, gnn, rwatson, adrian, sbruno, lstewart, hselasky, imp
Cc: delphij, neel, erj, freebsd-net
On Nov 17, 2014, at 12:46 AM, Craig Rodrigues wrote:
> Hi,
>
> PROPOSAL
> ==
> I would like to get feedback on the following proposal.
> In the head branch (CURRENT), I would like to enable
> VIMAGE with this commit:
>
>
> PATCH
> ==
>
> Index: sys/conf/NOTES
> ==
On Apr 1, 2014, at 12:58 AM, Yonghyeon PYUN wrote:
> On Mon, Mar 31, 2014 at 07:57:28AM -0700, Chris H wrote:
>>> On Sun, Mar 30, 2014 at 01:12:20PM -0700, chr...@ultimatedns.net wrote:
Greetings,
I'm not sure whether this best belonged on net@, or stable@
so I'm using both. :)
>>
On Sep 14, 2013, at 2:44 AM, Anuranjan Shukla wrote:
> At Juniper Networks, interface name size was needed to be longer than what
> FreeBSD has. We're trying to reduce our local changes to FreeBSD to allow us
> an easier time upgrading to newer FreeBSD releases, and support the
> modularization
On Sep 6, 2013, at 7:11 PM, Adrian Chadd wrote:
> Yeah, why is VM_KMEM_SIZE only 12mbyte for MIPS? That's a little low for a
> platform that has a direct map that's slightly larger than 12mb :)
>
> Warner? Juli?
All architectures have it at 12MB, except sparc64 where it is 16MB. This can be
ch
On Aug 5, 2013, at 11:20 AM, Adrian Chadd wrote:
> .. and I bet it's not a design pattern, and this is total conjecture on my
> part:
>
> * the original drivers weren't SMP safe;
> * noone really sat down and figured out how to correctly synchronise
> all of this stuff;
> * people did the minim
On Aug 22, 2012, at 12:54 PM, Adrian Chadd wrote:
> On 22 August 2012 05:02, John Baldwin wrote:
>> On Tuesday, August 21, 2012 12:34:42 pm Adrian Chadd wrote:
>>> Hi,
>>>
>>> What about just creating an ETHER_ADDR_COPY(dst, src) and putting that
>>> in a relevant include file, then hide the ug
On Aug 22, 2012, at 6:02 AM, John Baldwin wrote:
> On Tuesday, August 21, 2012 12:34:42 pm Adrian Chadd wrote:
>> Hi,
>>
>> What about just creating an ETHER_ADDR_COPY(dst, src) and putting that
>> in a relevant include file, then hide the ugliness there?
>>
>> The same benefits will likely app
On Aug 21, 2012, at 1:42 AM, Wojciech Puchar wrote:
>>
>> Even without this tagging, the code to do a structure level copy of 6 bytes
>> is going to be tiny...
>
> true.
>
> just to make sure it will be absolutely portable how about
>
> bcopymacaddress(dst,src)
>
> and then define it whatev
On Aug 21, 2012, at 5:26 AM, Marius Strobl wrote:
> On Mon, Aug 20, 2012 at 01:20:29PM -0600, Warner Losh wrote:
>>
>> On Aug 20, 2012, at 1:17 PM, Wojciech Puchar wrote:
>>
>>>>> or use ++.
>>>>>
>>>>> i think it is always al
On Aug 20, 2012, at 1:17 PM, Wojciech Puchar wrote:
>>> or use ++.
>>>
>>> i think it is always aligned to 2 bytes and this should produce usable code
>>> on any CPU? should be 6 instructions on MIPS and PPC IMHO.
>>
>> We should tag it as __aligned(2) then, no? If so, then the compiler shoul
On Aug 20, 2012, at 10:48 AM, Wojciech Puchar wrote:
>> #if defined(__i386__) || defined(__amd64__)
>> *dst = *src;
>> #else
>> bcopy(src, dst, ETHER_ADDR_LEN);
> #else
> short *tmp1=((*short)src),*tmp2=((*short)dst);
> *tmp2=*tmp1; *(tmp2+1)=*(tmp1+1); *(tmp2+2)=*(tmp1+2);
>
> or use ++.
>
On Aug 20, 2012, at 8:46 AM, Mitya wrote:
> Hi.
> I found some overhead code in /src/sys/net/if_ethersubr.c and
> /src/sys/netgraph/ng_ether.c
>
> It contains strings, like bcopy(src, dst, ETHER_ADDR_LEN);
> When src and dst are "struct ether_addr*", and ETHER_ADDR_LEN equal 6.
> This code call
On Jan 28, 2012, at 4:00 PM, Juli Mallett wrote:
> It makes me wonder if the understanding of the relationship in FreeBSD
> isn't backwards. Yes, the MAC sits on a bus and is memory-mapped, but
> you can conceptualize of it as a child of the PHY, rather than the
> parent of it, especially in syst
I'd say this PR is off the mark. I use PC Card and CardBus cards all the time.
The Xircom patch in question should be in -current already. I likely haven't
MFC'd it. There are two classes of problems lingering from the old days: the
Xircom one (where a certain type of CIS fails, but so far o
In message: <20100527.001534.807935107107604070@bsdimp.com>
"M. Warner Losh" writes:
: at the point in the boot scripts you want to use it. Even if you have
: / and /usr separate on NFS partitions, you can specify netfs_types=""
: in the NFS root's
In message: <4bfe04e5.1010...@semmy.ru>
Sergey Matveychuk writes:
: 26.05.2010 20:38, Julian Elischer wrote:
: > On 5/26/10 9:32 AM, M. Warner Losh wrote:
: >> In message:<4bfd158d.7020...@freebsd.org>
: >> Sergey Matveychuk writes:
: >> : Does is po
In message: <4bfd158d.7020...@freebsd.org>
Sergey Matveychuk writes:
: Does is possible to move setfib(1) to /sbin for smooth using it in
: rc.d scripts?
It is small enough. I think that's a good idea.
However, it would only be a problem if we are mounting / and /usr off
NFS as sepa
OK. I'd like to propose the following patch for ipfilter:
Index: sys/contrib/ipfilter/netinet/ip_compat.h
===
--- sys/contrib/ipfilter/netinet/ip_compat.h(revision 205838)
+++ sys/contrib/ipfilter/netinet/ip_compat.h(working
In message:
Marius Nünnerich writes:
: On Tue, Feb 9, 2010 at 18:34, M. Warner Losh wrote:
: > Greetings,
: >
: > I've found a few inconsistencies in the sockaddr stuff in the tree.
: > I'm not sure where to go to get a definitive answer, so I thought I'
Greetings,
I've found a few inconsistencies in the sockaddr stuff in the tree.
I'm not sure where to go to get a definitive answer, so I thought I'd
start here.
I got here looking at the recent wake breakage on mips. It turns out
that the warning was:
src/usr.sbin/wake/wake.c: In function 'find
In message: <4b6e2b40.1070...@elischer.org>
Julian Elischer writes:
: M. Warner Losh wrote:
: > I have a problem. All systems are running freebsd-current form
: > sometime in the last month, although similar systems running
: > 8.0-RELEASE exhibit exactly the same prob
In message: <4b6e2b40.1070...@elischer.org>
Julian Elischer writes:
: M. Warner Losh wrote:
: > I have a problem. All systems are running freebsd-current form
: > sometime in the last month, although similar systems running
: > 8.0-RELEASE exhibit exactly the same prob
I have a problem. All systems are running freebsd-current form
sometime in the last month, although similar systems running
8.0-RELEASE exhibit exactly the same problem. rpc.lockd on an NFS
client is doing something that baffles my mind entirely, maybe you can
help. Please bear with me, this is
In message: <261c29700904300029s6757d39ei86fbf69ef816f...@mail.gmail.com>
Miki writes:
: 2009/4/30 M. Warner Losh
:
: > In message: <261c2970090434k4bc02635m2729a0a54c09c...@mail.gmail.com>
: >Miki writes:
: > : 2009/4/29 M. Warner Losh
: &
In message: <261c2970090434k4bc02635m2729a0a54c09c...@mail.gmail.com>
Miki writes:
: 2009/4/29 M. Warner Losh
:
: > : I have a problem with a D-Link DFE-670TXD which is handled by if_ed :
: > : the link state is constantly going down and up :
: > : Apr 28 14:
: I have a problem with a D-Link DFE-670TXD which is handled by if_ed :
: the link state is constantly going down and up :
: Apr 28 14:21:33 iut-mir-o kernel: ed0: link state changed to DOWN
: Apr 28 14:21:35 iut-mir-o kernel: ed0: link state changed to UP
...
: the problem appear with the followin
In message: <20090401100939.gb12...@michelle.cdnetworks.co.kr>
Pyun YongHyeon writes:
: On Wed, Apr 01, 2009 at 01:32:46AM -0600, M. Warner Losh wrote:
: > I've encountered a number of PHY chips that need auto negotiation
: > kicked off to come out of ISO state.
I've encountered a number of PHY chips that need auto negotiation
kicked off to come out of ISO state. This makes sense, because the
ukphy driver never seems to take the PHY out of isolation state
otherwise.
Index: ukphy.c
===
--- uk
From: Max Laier
Subject: Re: HEADS UP: vimage - virtualized global variables in the network
stack
Date: Sat, 13 Dec 2008 20:45:16 +0100
> On Saturday 13 December 2008 20:33:53 Bjoern A. Zeeb wrote:
> ...
> > This state of having the variables in parallel, global and in the
> > container struct,
In message: <[EMAIL PROTECTED]>
John Baldwin <[EMAIL PROTECTED]> writes:
: On Monday 25 August 2008 02:23:16 am M. Warner Losh wrote:
: > I did this a few years ago when trying to track down a problem with
: > some realtek network chips that I was having probl
I did this a few years ago when trying to track down a problem with
some realtek network chips that I was having problems with at Timing
Solutions. I'd like to get this into the tree, since it was helpful
then.
Comments?
Warner
diff -ur src/sys/pci/if_rl.c newcard/src/sys/pci/if_rl.c
--- src/sys
In message: <[EMAIL PROTECTED]>
Roman Kurakin <[EMAIL PROTECTED]> writes:
: M. Warner Losh wrote:
: > I've been shepherding this patch in my p4 tree for a long time. It
: > removes the obsolete support for other systems in if_spppsubr.c. Is
: > there a reas
I've been shepherding this patch in my p4 tree for a long time. It
removes the obsolete support for other systems in if_spppsubr.c. Is
there a reason I shouldn't commit this?
Warner
Index: if_spppsubr.c
===
--- if_spppsubr.c (
In message: <[EMAIL PROTECTED]>
"Bruce M. Simpson" <[EMAIL PROTECTED]> writes:
: Other than that, line disciplines can go away.
In the past I've uesd line disciplines to implement a keyboard driver
for the Apple Newton Keyboard (serial protocol) so I could use it at
any point after the
In message: <[EMAIL PROTECTED]>
Robert Watson <[EMAIL PROTECTED]> writes:
:
: On Mon, 26 May 2008, Bruce M. Simpson wrote:
:
: >> Given that this is (a) 2008 and (b) 8.x we're talking about, are there
: >> really that many consumers of SLIP to warrant it being carried forward at
: >
looks like somebody took out my bogus filter for mii addresses.
Grump. Will track this down.
Warner
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
In message: <[EMAIL PROTECTED]>
Joe Holden <[EMAIL PROTECTED]> writes:
: M. Warner Losh wrote:
: > Greetings,
: >
: > I have a friend who is having problems with a service he's running.
: > He gets billions and billions of connections to this service a da
Greetings,
I have a friend who is having problems with a service he's running.
He gets billions and billions of connections to this service a day.
Somewhere between 10^8 and 10^9 connections, he notices that his
servers lose the ability to accept new connections. These are TCP
connections.
This
OK. I'm getting very frustrated with my TCP connections hanging. It
happens when I log into remote sites, when I try to encode dvds, etc.
It is driving me nuts. This is with current from today. Current from
5 or 6 weeks ago doesn't seem to be bothered by this issue.
Has anybody else seen it?
In message: <[EMAIL PROTECTED]>
Harti Brandt <[EMAIL PROTECTED]> writes:
: On Thu, 7 Dec 2006, Harti Brandt wrote:
:
: HB>On Thu, 7 Dec 2006, M. Warner Losh wrote:
: HB>
: HB>MWL>In message: <[EMAIL PROTECTED]>
: HB>MWL>Harti Brandt
In message: <[EMAIL PROTECTED]>
Harti Brandt <[EMAIL PROTECTED]> writes:
: MWL>Does anybody have experience with using FreeBSD 4.x or 6.x NFS clients
: MWL>against a Windows 2003 NFS server? What is the performance relative
: MWL>to using a FreeBSD NFS server? What is the stability?
In message: <[EMAIL PROTECTED]>
Harti Brandt <[EMAIL PROTECTED]> writes:
:
: Hi Warner,
:
: On Wed, 6 Dec 2006, M. Warner Losh wrote:
:
: MWL>Does anybody have experience with using FreeBSD 4.x or 6.x NFS clients
: MWL>against a Windows 2003 NFS server? What
Does anybody have experience with using FreeBSD 4.x or 6.x NFS clients
against a Windows 2003 NFS server? What is the performance relative
to using a FreeBSD NFS server? What is the stability? Does locking
work? Does the Windows 2003 server have extensions that grok file
system flags?
Thanks m
Does anybody know if the FreeBSD ipv6 stack has passed the IOL Silver
or Gold levels from the University of New Hampshire?
Warner
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail
In message: <[EMAIL PROTECTED]>
Brooks Davis <[EMAIL PROTECTED]> writes:
: and act as though the interface is not there. We could then consider
: either holding the interface for a configurable or computed length
: of time or adding some sort of refcounting (probably impractical).
Ref
From: Dmitry Morozovsky <[EMAIL PROTECTED]>
Subject: hosts.allow default behaviour: IPv6 on its own lines
Date: Thu, 16 Feb 2006 14:03:37 +0300 (MSK)
> Dear colleagues,
>
> at least rpcbind brokes on parsing hosts.allow file when built with NO_INET6:
>
> Feb 16 13:55:41 ... rpcbind: error: /etc/
I beleive that umodem implements the usb cdc acm interface.
Warner
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
In message: <[EMAIL PROTECTED]>
"Bjoern A. Zeeb" <[EMAIL PROTECTED]> writes:
: * all PHY drivers currently seem to use mii_phy_detach for
: device_detach. If any implements his own function it will be
: responsible for freeing the ivars allocated in miibus_probe. This
: should per
In message: <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
: Hello, all!
:
:
: Today I have bought myself new Proxim Orinoco Gold b/g card
: to replace my old Lucent Orinoco b one.
:
: New card is working fine with the ath driver, but...
: Signal strength and radio perfomance are very
In message: <[EMAIL PROTECTED]>
Bernd Walter <[EMAIL PROTECTED]> writes:
: On Tue, May 18, 2004 at 09:05:52PM +0800, wsk wrote:
: > hi,folks:
: > It seems that the ttyd0 isn't the dialin line to login , and
: > the cuaa0 like is both the dialin/out device!under 4.9 above
: > and 5.X .bu
In message: <[EMAIL PROTECTED]>
Lorenzo Vicisano <[EMAIL PROTECTED]> writes:
: Warner,
:
: On Sun, Jan 11, 2004 at 02:23:57PM -0700, M. Warner Losh wrote:
: > In message: <[EMAIL PROTECTED]>
: > Lorenzo Vicisano <[EMAIL PROTECTED]> writes:
:
In message: <[EMAIL PROTECTED]>
Lorenzo Vicisano <[EMAIL PROTECTED]> writes:
: However after upgrding the Prism firmware (1.1.0 -> 1.1.1)
: the lock up stopped.
You really really really want to be using 1.4.5 firmware. Older
firmware is known to be buggy.
Warner
_
In message: <[EMAIL PROTECTED]>
Brooks Davis <[EMAIL PROTECTED]> writes:
: Six years and eight months ago, net/if.h was split into if.h and
: if_var.h. At the time, if_var.h was included at the end if if.h as
: follows (this is the current code, but it's equivalent):
...
: Does this so
In message: <[EMAIL PROTECTED]>
Daniel Dias Goncalves <[EMAIL PROTECTED]> writes:
: The device SMC 2602W PCI works in the FreeBSD?
: vendor = 'Admtek Inc'
unlikely. The adm wireless driver is still being ported.
Warner
___
[EMAIL PROT
In message: <[EMAIL PROTECTED]>
Nathan Clark <[EMAIL PROTECTED]> writes:
: I have an IBM Thinkpad 600X which dual boots 5.1-Current and XP-Pro. I
: purchased a Netgear MA401 wireless 802.11b card which worked fine under
: both OS's for about a week. This past Saturday, however, I was
In message: <[EMAIL PROTECTED]>
Wes Peters <[EMAIL PROTECTED]> writes:
: Only if the spec says those are the only valid ranges. Then we have to
: keep up to date with changes in the spec, too. Either some simple sanity
: checks or checking for truly valid lengths -- 0, 40 bits, 128
The code that prints out the keys for the 802.11 wireless stuff has
the following it it:
void
ieee80211_status (int s, struct rt_addrinfo *info __unused)
{
...
if (ireq.i_len == 0 || ireq.i_len > 13)
continue;
...
}
Should that check really
De: Terry Lambert <[EMAIL PROTECTED]> [ Data: 2003-03-05 ]
[ Subjecte: Re: Removal of netns - politically correct version ]
> On the other hand, there's no compelling reason to dike it out,
> if it can be made to work. I would argue that ISA support is
> more or less just as obsolete, as i
In message: <[EMAIL PROTECTED]>
Andrew Gallatin <[EMAIL PROTECTED]> writes:
:
: M. Warner Losh writes:
: > In message: <[EMAIL PROTECTED]>
: > Andrew Gallatin <[EMAIL PROTECTED]> writes:
: > : The IFNET_RLOCK() called in if_sl
In message: <[EMAIL PROTECTED]>
Andrew Gallatin <[EMAIL PROTECTED]> writes:
: The IFNET_RLOCK() called in if_slowtimo() is a global lock for the
: list of ifnet structs to ensure that no devices are removed or added
: while something may be using it. There is one ifnet list in the syst
I was right (and I think you are too). We do have lock issues.
dc_attach does approximately:
DC_LOCK
ether_attach() (which does a IFNET_WLOCK/UNLOCK pair)
DC_UNLOCK
(this sets the lock order to be DC_LOCK, IFNET_WLOCK).
However in if_slowtimo we have:
if_slowtimo(arg)
{
... IFNET_RLOCK()
In message: <[EMAIL PROTECTED]>
Terry Lambert <[EMAIL PROTECTED]> writes:
: "M. Warner Losh" wrote:
: > In message: <[EMAIL PROTECTED]>
: > Nate Lawson <[EMAIL PROTECTED]> writes:
: > : I was looking into some "could sleep mes
1 - 100 of 127 matches
Mail list logo
