On Monday 01 December 2003 05:25 pm, Leo Bicknell wrote:
> In an effort to cut down on Sam's load...
>
> This is a known issue. Evidently there are some low level radio
> counters that are incorrectly being reported as input errors.
> Basically they should be ignored until the driver can be change
On Thursday 27 November 2003 06:38 am, Bjoern A. Zeeb wrote:
> On Thu, 27 Nov 2003, Yuriy Tsibizov wrote:
>
> Hi,
>
> > >i got a panic on recent -CURRENT:
> > >
> > ># tcpdump -i lo0 port 23 &
> > >[1] 507
> > >listening on lo0
> > >
> > ># telnet localhost
> > >Trying ::1...
> > >
> > >Wed Nov 26
On Wednesday 26 November 2003 01:40 pm, Sean Chittenden wrote:
> > > Is my expectation wrong or is there a pertinent IPFW2 bug in a current
> > > 5.2-BETA kernel?
> >
> > You're alone in this, though cjc hasn't been able to reproduce this.
>
>^^^
>not
>
> > Are you on a multi-homed
On Wednesday 26 November 2003 04:00 am, Дейтер Александр Валериевич wrote:
> i got a panic on recent -CURRENT:
>
> # tcpdump -i lo0 port 23 &
> [1] 507
> listening on lo0
>
> # telnet localhost
> Trying ::1...
>
> Wed Nov 26 14:51:23 MSK 2003
> Debugger+0x55: xchgl %ebx,in_Debugger.0
> db> tr
>
On Monday 24 November 2003 07:06 pm, Andrew Gallatin wrote:
> M. Warner Losh writes:
> > In message: <[EMAIL PROTECTED]>
> > I'm just saying that most of the developers I'm talking to on IRC say
> > this tread is insane, has no content and they are blowing it off
> > because of that. A concret
On Monday 24 November 2003 09:07 am, Barney Wolff wrote:
> Off-the-wall suggestion: run tcpdump -e and check whether both responses
> are coming from the same host. Unless you're running WEP, you many have
> an unexpected guest. (WEP is no guarantee, but it's better than nothing.)
Better, use
On Wednesday 19 November 2003 02:12 pm, Bjoern A. Zeeb wrote:
> Hi,
>
> is anybody involved in fixing perhaps going to put up a site with all the
> wellknown LORs and perhaps a state (like: work in progress (by ...),
> ingorable, ...).
>
> I have seen three the last minutes where at least two seem
On Sunday 16 November 2003 04:46 pm, Neilson Henriques wrote:
> Hi !
>
> After read the man page of ath(4) driver I decided to
> buy a DWL-G520 but it is insisting to not joy with me. :-(
> I tried to replace the board, replace the machine, reinstall
> the FreeBSD and cvsup the toda
On Thursday 13 November 2003 06:19 am, Eric Anderson wrote:
> >hi,
> >
> >i get this when inserting my Netgear WG511T card into my laptop:
> >
> >ath0: mem 0x8801-0x8801 irq 11 at device 0.0 on
> >cardbus0
> >ath0: unable to attach hardware; HAL status 13
> >device_probe_and_attach: ath0 a
On Tuesday 11 November 2003 01:52 pm, Johann Hugo wrote:
> Hi
>
> I've just started playing with some D-link DWL-AG520 PCI adapters with the
> Atheros 5212 chipset.
>
> The one adapter is configured in hostap mode, and the other one as a
> client. When I set the media option to a lower speed that t
On Tuesday 11 November 2003 08:40 am, Steve Ames wrote:
> Code from yesterday evening (11/10 around 5PM EST). Just updated this
> morning. I saw no updates to ip_output.c but there were changes to a couple
> of other files in sys/netinet so figured I'd give it a whirl...
>
> panic: mutex inp not ow
On Monday 10 November 2003 02:27 pm, Steve Ames wrote:
> On Mon, Nov 10, 2003 at 05:19:06PM -0500, Steve Ames wrote:
> > New /usr/src from around 4:30PM EST:
> >
> > Mon Nov 10 17:16:14 EST 2003
> > lock order reversal
> > 1st 0xc6761890 rtentry (rtentry) @ /opt/src/sys/net/route.c:182
> > 2nd 0xc6
On Monday 10 November 2003 02:19 pm, Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, Sam Leffler writes:
> >On Monday 10 November 2003 11:37 am, Larry Rosenman wrote:
> >> I removed my wi0 card (with DHCLIENT running), and got the following
> >> panic on a -CURR
On Monday 10 November 2003 11:37 am, Larry Rosenman wrote:
> I removed my wi0 card (with DHCLIENT running), and got the following panic
> on a -CURRENT from yesterday:
Thanks. Working on it...
Sam
___
[EMAIL PROTECTED] mailing list
http://list
On Friday 07 November 2003 12:54 pm, Steve Kargl wrote:
> On Fri, Nov 07, 2003 at 11:31:45AM -0800, Steven G. Kargl wrote:
> > I have a Dell 4150 laptop using dhcp and ntpd on the
> > xl0 interface. I did "ifconfig xl0 down" and received
> > the following panic (hand transcribed :-( ).
> >
> > pan
On Friday 07 November 2003 07:49 am, Jaco H. van Tonder wrote:
> Hi All,
>
> I get panics at random times of the day with -CURRENT from 20031105, with
> absolutely no load on the machine.
>
> The machine acts as a dial-up server/gateway/firewall for my local lan. I
> managed to get a coredump.
>
>
I've disabled the MPSAFE operation of the network drivers. I was trying to
commit only part of the work to be move Giant "up" in the networking code but
it appears that's not possible.
I'll wait for things to stabilize before trying again.
Sam
Index: subr_bus.c
On Monday 03 November 2003 12:58 pm, Andrea Campi wrote:
> Hi,
>
> after updating my laptop to last sunday sources, it panics very often with
> one of two panics. Sam, any chance you might know what's up?
>
> Note that both panics seem (to my untrained eye at least) to be related
> to spammed route
On Friday 31 October 2003 07:49 pm, Doug Ambrisko wrote:
> I'm getting this panic a fair amount when dhclient is running on with the
> an(4) driver. My Atheros based card appears to have broke so I can't
> use that now (it doesn't work in Windows either). Here is the dmesg:
>
> lock order rever
On Friday 31 October 2003 09:04 am, Bruce Evans wrote:
> My simple make benchmark now takes infinitely longer with ULE under SMP,
> since make -j 16 with ULE under SMP now hangs nfs after about a minute.
> 4BSD works better. However, some networking bugs have developed in the
> last few days. On
On Thursday 30 October 2003 10:30 am, othermark wrote:
> I'll me too this one..
>
> Another backtrace with a different call sequence (via ipv6), exact same LOR
>
> lock order reversal
> 1st 0xc2177c90 rtentry (rtentry) @ /usr/src/sys/net/route.c:182
> 2nd 0xc206537c radix node head (radix node he
On Thursday 30 October 2003 04:46 am, Michal Mertl wrote:
> I wanted to test gigabit network performance and found out that current
> (from 5.0 to up to date -current) doesn't fully work with jumbograms (MTU
> set to 6000), Intel adapters and nfs (both UDP and TCP).
>
> I checked that the same thin
On Thursday 30 October 2003 07:33 am, Daniel C. Sobral wrote:
> I could have stuck a LONG time on this one if I wasn't testing something
> that results in the very thing that causes the panic. I don't have the
> exact details, but what I did is the following:
>
> ifconfig fxp0 10.0.2.6/16 (well, th
On Thursday 30 October 2003 01:22 am, Pawel Jakub Dawidek wrote:
> On Wed, Oct 29, 2003 at 11:52:48AM -0700, Sam Leffler wrote:
> +> I'm committing changes to mark various network drivers' interrupt
> handlers +> MPSAFE. To insure folks have a way to backout if they
I'm committing changes to mark various network drivers' interrupt handlers
MPSAFE. To insure folks have a way to backout if they hit problems I've also
added a tunable that lets you disable this w/o rebuilding your kernel. By
default all network drivers that register an interrupt handler INTR_M
On Tuesday 28 October 2003 04:40 pm, Jiri Mikulas wrote:
> FreeBSD 5.1-CURRENT #3: Tue Oct 28 23:51:52 CET 2003
>
> ~~~cut~~~
> recursed on non-recursive lock (sleep mutex) rtentry @
> /usr/src/sys/net/route.c:565
> first acquired @ /usr/src/sys/net/route.c:182
> panic: recurse
> ~~~cut~~~
Any cha
On Wednesday 22 October 2003 07:36 pm, Marcos Biscaysaqu wrote:
> Hi There.
> With the debug on in hte kernel "ZABU" I found this when my Atheros card
> crash:
>
> lock order reversal
> 1st 0xc36c1e84 rl0 (network driver) @ pci/if_rl.c:1485
> 2nd 0xc0766280 bridge (bridge) @ net/bridge.c:777
> St
This fixes adhoc mode for wi devices. Adhoc mode is still not working
correctly for ath devices. No eta on fixing it.
Sam
--- Begin Message ---
sam 2003/10/17 14:54:59 PDT
FreeBSD src repository
Modified files:
sys/net80211 ieee80211_output.c ieee80211_var.h
On Wednesday 15 October 2003 09:08 am, Doug White wrote:
> On Tue, 14 Oct 2003, David Cornejo wrote:
> > I'm trying to compile a multicast application and the system panics every
> > time I run configure:
>
> Might be nice toknow which multicast application, if its publicly
> available :)
>
> I sus
On Wednesday 15 October 2003 03:21 am, Pawel Jakub Dawidek wrote:
> Hello.
>
> Already reported?
>
> lock order reversal
> 1st 0xc47b6490 rtentry (rtentry) @ /usr/src/sys/net/route.c:182
> 2nd 0xc44be77c radix node head (radix node head) @
> /usr/src/sys/net/route.c:133
Yes, I'm aware of this on
On Tuesday 16 September 2003 08:12 pm, Kenneth D. Merry wrote:
> I've got a Netgear WAG511 (Atheros 5212-based card) and a Netgear FWAG114
> wireless router.
>
> I've been trying to get the card and the router talking under FreeBSD.
> (Both 802.11a and 802.11g work fine under Windows on the same ma
On Sunday 12 October 2003 11:03 am, Andre Guibert de Bruet wrote:
> On Sun, 12 Oct 2003, Josef Karthauser wrote:
> > On Sun, Oct 12, 2003 at 02:48:01PM +0200, Soren Schmidt wrote:
> > > It seems Josef Karthauser wrote:
> > > > I've just built and installed a new kernel, the first since Aug 6th.
> >
I've been getting this panic a lot in the past week. Unfortunately it's on my
file server so I can't use gdb to get more details than what ddb provides
(the kernel is on the machine that's panic'd). This is a UP x86 box. The
stack trace is:
pmap_enter
kmem_malloc
page_alloc
slab_zalloc
uma_z
On Saturday 11 October 2003 03:20 am, Antony T Curtis wrote:
> On Sat, 2003-10-11 at 10:36, Antony T Curtis wrote:
> > Hi, I cvsuped at about 10/10/03 11PM GMT and rebuilt world and kernel.
> >
> > It locks up after displaying:
> >
> > GEOM: create disk ad0 dp=0xc456d370
> > ad0: 28615MB [58140/16
On Thursday 09 October 2003 05:57 am, Michael O. Boev wrote:
> > -Original Message-
> > From: Terry Lambert [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, October 09, 2003 5:19 PM
> > To: Michael O. Boev
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: Why is em nic generating interrupts?
> >
> >
On Wednesday 08 October 2003 08:45 pm, Marcos Biscaysaqu wrote:
> Hi There.
> I have 2 PCI wireless card with the Atheros chipset some one know
> how can i setup a point-to-point with 2 of this wireless card on
> Freebsd, I could made work Access Point client, but i couln't adhoc
> turbo mode 1
On Wednesday 08 October 2003 05:27 pm, Daniel Eischen wrote:
> One of my buddies is having panics with if_em after the last
> set of changes a couple of weeks ago. He runs dhclient
> on the interface to get a lease from a cable modem. The
> panic is a recurse on a non-recursive mutex. I haven't
I just committed a large set of changes to lock routing table entries. I've
been running with these changes for several months w/o ill effects but as
always beware. You will see some LOR's that I expect will go away with
forthcoming work from Andre Oppermann. If not they'll get fixed before t
On Tuesday 30 September 2003 04:01 am, Bruce Evans wrote:
> On Tue, 30 Sep 2003, Greg 'groggy' Lehey wrote:
> > On Tuesday, 30 September 2003 at 16:23:35 +1000, Bruce Evans wrote:
> > > On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote:
> > >> After building a new kernel, remote serial gdb no longer w
On Monday 29 September 2003 01:30 am, Greg 'groggy' Lehey wrote:
> After building a new kernel, remote serial gdb no longer works. When
> I issue a 'continue' command, I lose control of the system, but it
> doesn't continue running. Has anybody else seen this?
Yes, I noticed this late last week.
> Tonight's current breaks compiling IPFILTER. It complains that it
> can't find the 'PFIL_OUT' symbol.
Read UPDATING; you need PFIL_HOOKS in your kernel config file.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/list
> vimes# diff GENERIC VIMES
> 25c25
> < ident GENERIC
> ---
>> ident VIMES
> 63,66c63,66
> < options INVARIANTS #Enable calls of extra sanity
> checking < options INVARIANT_SUPPORT #Extra sanity checks of
> internal structures, required by INVARIANTS <
I'm looking into it. Everything built+ran fine with the last commit...
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> Obviously I don't understand enough about locks. A recent (last week
> or two) checkin screwed the wi driver such that it panic's saying that
> ic_nodelock is used recursively first in line 525 and then in 547 of
> net80211/ieee80211_node.c.
>
> On my own, I tried chaging line 87 to mtx_init()
> After cvsup, buildworld error in usr.sbin/ipftest
>
> [snip]
Dang, my bad. Will deal with it.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTE
> Sam Leffler wrote:
>>> Could we add PFIL_HOOKS to GENERIC, while we're at it? Please?
>>
>>
>> Eventually this will happen. Almost certainly in time for 5.2.
>
> It was due for 5.0-RELEASE, it hasn't made it in for 5.1-RELEASE and post
> 5.1-R
> Could we add PFIL_HOOKS to GENERIC, while we're at it? Please?
Eventually this will happen. Almost certainly in time for 5.2.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, se
The following changes should be transparent but just in case they are not
please be aware...
Sam
> sam 2003/09/23 10:54:04 PDT
>
> FreeBSD src repository
>
> Modified files:
> sys/net bridge.c pfil.h pfil.c
> sys/netinet ip_input.c ip_output.c
> Hmm. One other thing I'm seeing is that when I configure a 128 bit key
> with ifconfig or wicontrol (wicontrol shows all 28 characters -- 0x plus
> 26 hex characters), ifconfig still thinks it is a 104 bit key. This is
> because ireq.i_len is 13.
>
You must not have the up to date ifconfig.
> I've got a Netgear WAG511 (Atheros 5212-based card) and a Netgear FWAG114
> wireless router.
>
> I've been trying to get the card and the router talking under FreeBSD.
> (Both 802.11a and 802.11g work fine under Windows on the same machine.)
>
> I'm using -current from September 15th.
>
> Anyw
> On Tue, Sep 16, 2003 at 09:29:07AM -0700, Sam Leffler wrote:
>>
>> Please send me your kernel config and tell me again exactly what fails.
>> I will try to reproduce your problem.
>>
>> Sam
> After your yesterday/today commits, I got panic while doi
I just committed changes to bridge, ipfw, and dummynet. I've been running
these for a while but beware. I'm aware of two LOR issues that I want to
sort out later, after some more changes have gone in. Regardless, if you
encounter problems let me know...
Sam
> Yes, I was referring to bridging two wireless interfaces.
David Young (of netbsd) has plans for WDS support that should fit into the
existing 802.11 layer. With his design you should be able to bridge WDS
links using the standard bridge support. No ETA.
Sam
__
> I just built a kernel with latest sources, unfortunately, my ath(4) card
> stopped working. The device is there, devd sets ip address, route etc.,
> just as it did before the upgrade - the problem is that the link is dead,
> there's _nothing_ going over the link. It also seems to re-associate w
> I think what he meant was that at on state was known (I don't know the
> current state) that as the wi could not be but in promiscuous mode it
> could not be used for bridging.. Bridging requires promiscuous mode
> (or some very tricky proxy-arp stuff).
You can put wi (and ath) in promiscuous m
> Is the ath(4) driver, like the wi(4) driver, incapable of performing
> bridging?
Sorry, answered too quickly. ath and wi have the same restrictions. You
can use bridging to hookup a wired and wireless network but not two
wireless networks. I can't tell from your posting what you are trying to
> Is the ath(4) driver, like the wi(4) driver, incapable of performing
> bridging?
Yes. Bridging happens outside the operation of the driver.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
I've committed a number of changes to lock the "middlware" parts of the
network subsystem. There's still more to come; I'm moving slowly to insure
each batch gets exposure. All the pending changes can be found at:
http://www.freebsd.org/~sam
The major changes that will go in next week are: brid
> latest kernel causes a panic early during boot:
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x68
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc02667cf
> stack pointer = 0x10:0xc0641cf8
> frame pointer
> Please try out this patch if you have a "sis" based network card.
>
> It sets a 400usec interrupt holdoff, and this seems to have a profound
> impact on network performance.
>
> The patch is relative to FreeBSD-current but probably applies on
> 5.0, 5.1 and even 4.x as well.
>
> In my tests, u
Me and a couple of my friends work on small freebsd version for embedded
systems. We all noticed that our wifi cards with atheros chip have
problems with the ath driver. The system keeps on spitting out following
messages before the link, that is already very slow dies:
ath_rate_ctl: 54M -> 48M (0
Ive got a Dlink DWL-G520 that Ive installed into a Freebsd system. Ive
set up the card with the following
ifconfig_ath0="inet 10.0.0.1 netmask 255.255.255.0 ssid daves channel 10
media DS11 mediaopt hostap"
This system was cvsuped and buildworld about 3 days ago. The card appears
to be working b
On Wed, 6 Aug 2003, Sam Leffler wrote:
> Shouldn't that be 0.9.5.2? I run the latest current, and
> hw.ath.hal.version is 0.9.5.2.
>
You're right; I committed a slightly older version to FreeBSD than to
Linux.
Any chance that you could commit the newer version? Or are
I just have to ask: is this in any way related to the a/b/g network
card in my laptop that shows up as:
[EMAIL PROTECTED]:3:0: class=0x028000 card=0x00011028 chip=0x432414e4 rev=0x02
hdr=0x00 vendor = 'Broadcom Corporation'
class= network
if ("broadcom" == "atheros")
use ath d
While trying to port the SCTP-KAME code to CURRENT,
I noticed that M_NOTIFICATION is missing from
in CURRENT, but it is present in the KAME version of this
file.
Any reason not to apply this patch?
--- sys/sys/mbuf.h.orig Sat Sep 13 19:34:07 2003
+++ sys/sys/mbuf.h Sat Sep 13 19:34:14 20
Sorry for the lame post, but here goes.
Madwifi works fine on linux laptops, but need support in Freebsd.
The post I read I seem to remember saying that it (madwifi) was native
in current?
I took a new hd in a Dell laptop. Did an ftp install of 5.1 stable.
Cvsuped to current for source and ports
Verify you have the latest HAL using
sysctl hw.ath
The version should be 0.9.5.3 or better (can't remember if I committed .4
or .3).
Shouldn't that be 0.9.5.2? I run the latest current, and
hw.ath.hal.version is 0.9.5.2.
You're right; I committed a slightly older version to FreeBSD than to Linux
I have a few Orinoco cards, and they 'work' in both ad-hoc and
infrastructure mode. However with dhclient it gets tricky, because it
will only work the first time dhclient assigns an address to the card.
Whenever it tries to refresh it or whatever, I start getting those
timeout and busy bit errors,
[Not sure about cross-posting but I'll leave it for now.]
I've recompiled -CURRENT with support for atheros cards.
I have two cards, one PCI(desktop) and one PCMCIA(laptop). Both are
Proxim 11a/b/g combo cards with AR5212 chips. The cards are recognized
fine.
pciconf -l -vv shows:
[EMAIL PROTECTED
> *) Powersavemode seems to be not supported at all (and thus it eats the
> battery like a "make world"):
>
># ifconfig ath0 powersave on
> ifconfig: SIOCS80211: Invalid argument
man ath(4)
The man page says "not fully", not "not supported at all".
I'll fix the man page :) Actually, there are sev
"Sam" == Sam Leffler <[EMAIL PROTECTED]> writes:
Sam> If you've got an AP running with recent source and a wi card
Sam> please contact me.
I don't know if this is related, but I have a wi card running in
access point mode and is disassociates under high traffic.
Ok, I've investigated this further. The strange thing is: whenever the
connections to the outside drop, I can ping and connect to any host in my
LAN (10.0.0.0/24), but I _cannot_ ping 10.0.0.138 from the WLAN client,
which is the inside interface of the ADSL router and thus the default
route. I can
I just bought a Netgear WAG511 card and a Netgear WG602 Accesspoint. I
run the card in 11g mode under current, and I'm having some problems:
*) Powersavemode seems to be not supported at all (and thus it eats the
battery like a "make world"):
# ifconfig ath0 powersave on
ifconfig: SIOCS80211: Inval
[cross-posting removed]
Note: SCO is suing people who have touched Linux code with code
from commercial OS's derived from System V. SGI's IRIX, from
which XFS comes, is derived from System V, so there is some legal
risk involved to anyone doing a port: SCO may sue you, too. I
don't know if this
My work to support the Atheros 802.11 hardware is now entirely in the tree
and enabled for use. The ath driver supports all Atheros hardware devices
and makes FreeBSD the first open source system to support 802.11a and
802.11g*. There are still issues with the driver. man ath(4) for details.
I've committed the changes to switch the 802.11 support over to the code in
sys/net80211. The new code is significantly different as it has been
revamped to support multi-mode devices, add fine-grained locking, and
support more of the 802.11 protocol. Drivers that depend on the code have
been
I'm having trouble getting a kernel with the Atheros driver to compile. I
get the following error during linking:
You need to patch some files to use the wlan code in sys/net80211 and not
the code in sys/net. I will either commit the remaining changes or post a
patch that contains the changes "
I'm trying to pin down a problem where prism-based AP's constructed from
"wlan" code and the wi driver don't work right. I'm seeing the following
when a client/station trys to associate with an AP of this sort:
client AP
AUTH->
<- AUTH response
ASSOC ->
<- PRO
> * Alfred Perlstein <[EMAIL PROTECTED]> [030316 21:19] wrote:
> > um..
> >
> ...
> 840 _FLAGS_OUTRANGE) {
> 841 WI_UNLOCK(sc);
> 842 return;
> 843 }
> 844 KASSERT((ifp->if_flags & IFF_OACTIVE) == 0,
> 845 ("wi_
> I found on tty0 the following backtrace. I infer, because it died in
> malloc, that it has something to do with netisr problem. I had to
> copy it by hand.
>
> backtrace(c04b7645,4,1,0,c40be100) at backtrace+0x17
> malloc(3c
> The commit message for src/sys/netipsec/ipsec.c r1.1
> mentions that FAST_IPSEC and INET6 should not be used
> together. As far as I can tell from the commit log,
> nothing has changed that would negate that recommendation
> since the import. However, when compiling a -current (as
> of today) k
> * De: Sam Leffler <[EMAIL PROTECTED]> [ Data: 2003-02-25 ]
> [ Subjecte: Re: Errors with wireless ]
> > > wi0: tx failed, retry limit exceeded
> >
> > If this happens again show the output of sysctl hw.wi.
>
> I get those constantly when doing e.g.
> I'm getting a LOT of these.
>
> ether_input: drop bdg packet, bif 0x5
This was a stray debugging printf I forgot to remove. Update your system.
> wi0: tx failed, retry limit exceeded
If this happens again show the output of sysctl hw.wi.
Sam
To Unsubscribe: send mail to [EMAIL PROTECT
This may affect your ipfw/ipf rules. If you are happy with the current
behaviour then add IPSEC_FILTERGIF to your kernel config file.
Sam
- Original Message -
From: "Sam Leffler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[E
> At 9:47 PM -0800 2003/02/13, Sam Leffler wrote:
>
> >> SpecFS (NFS ops/sec benchmark)
> >
> > List price on SPEC SFS97 R1 is $900. And my recollection is that it
was
> > involved to setup and run.
>
> $450 for educational organizations. Wouldn
> On Thursday 13 February 2003 11:28 pm, Sam Leffler wrote:
> > > At 4:36 PM -0800 2003/02/13, Scott Long wrote:
> > > > - the classic 'worldstone'
> > > > - webstone - /usr/ports/www/webstone
> > > > - Fstress - http://www
> At 4:36 PM -0800 2003/02/13, Scott Long wrote:
>
> > - the classic 'worldstone'
> > - webstone - /usr/ports/www/webstone
> > - Fstress - http://www.cs.duke.edu/ari/fstress
> > - ApacheBench - /usr/ports/www/p5-ApacheBench
> > - netperf - /usr/ports/benchmarks/netperf
>
>
> About benchmarks...
>
> FWIW, the reiserfs people were excited about SCO's
> release of AIM:
>
> http://caldera.com/developers/community/contrib/aim.html
>
> but the announcement went rather unnoticed in
> freebsd-fs.
>
Thanks. I've worked with AIM. Wasn't aware it had been released.
> > : dstumbler breaks; on startup it reports
> > : "unable to ioctl device socket: Input/output error".
> >
> > As root or no?
>
> I have a rebuilt system finally that I could test this against and I'm
> actually getting a different error message on startup of dstumbler:
>
> error: unable to i
> Alright, I have disabled IPSec and updated the firmware to read:
> wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9)
>
> sysctl kern.wi_txerate=0 gives: sysctl: unknown oid 'kern.wi_txerate'
>
Sigh, I screwed up the sysctl's--just fixed it. This one is now located at
hw.wi.txerate and mu
> On Sun, Jan 19, 2003 at 07:46:11PM -0800, Sam Leffler wrote:
> > Finally, you may want to try different station firmware in your Dlink
> > card. I run 1.4.9 in my Senao (Prism 2.5) cards with good success. I
> > don't recall whether there were issues with
> I have noticed the following with the new wi0. I have the 802.11
connection
> between my laptop running XP and my current box running as a hostap. I
also
> have a IPSec tunnel between the current box and the laptop, but I don't
> think this could be causing the problems.
> While transferring fi
> A couple things regarding this new wireless driver - the
> wepkey option to ifconfig no longer seems to work; I get a
> "SIOCS80211: Invalid argument". Secondly and more importantly,
> even when the wepkey is set via wicontrol, I can't seem to get
> any connectivity at all anymore.
>
I fixed th
> On Thu, 16 Jan 2003, Sam Leffler wrote:
> >...
> > to your config files. This probably belongs in UPDATING.
>
> NB the new wi(4) is probably also an issue for ports/net/bsd-airtools,
> to be resolved or documented before MFC. (copied maintainer)
Why, did they not wor
Sorry, for the new wi driver you need to add:
device wlan
to your config files. This probably belongs in UPDATING.
Sam
- Original Message -
From: "Matt Haught" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 15, 2003 9:59 PM
Subject: Re: HEADS UP: new wi driver
I just committed a new version of the wi driver. This driver is very
different in that it depends on a common core implementation of the 802.11
state machine and mgmt protocols. There should be no visible differences
(for now) between the old driver and the new but beware. If you encounter
probl
> On Fri, 10 Jan 2003, Sam Leffler wrote:
> > unless the mbufs are specifically tagged as such. I'm not clear on
exactly
> > what sb_ctl is supposed to count; the comment in the cvs log is unclear:
> >
> > "Track the number of non-data chararacters stored i
> On Fri, Jan 10, 2003 at 09:57:36PM +1100, Tim Robbins wrote:
>
> > On Fri, Jan 10, 2003 at 01:30:16AM -0800, Juli Mallett wrote:
> >
> > > Lately, the data field for sockets, which holds bytes ready (in the
EVFILT_
> > > READ case) to be read, is computed to be zero. This means that if you
have
> > Maybe we should put in the release notes, that:
> >
> > "PFIL_HOOKS is required for IPFILTER"
>
> The right thing is to force the dependency in the code (I don't think
> there's a way to express it to config). The ipfilter code should probably
> have something like
>
> #ifndef PFIL_HOOKS
> #er
> Maybe we should put in the release notes, that:
>
> "PFIL_HOOKS is required for IPFILTER"
The right thing is to force the dependency in the code (I don't think
there's a way to express it to config). The ipfilter code should probably
have something like
#ifndef PFIL_HOOKS
#error "You must spec
1 - 100 of 114 matches
Mail list logo
