Folks, I hate to be snotty, but gosh, I don't think this thread really
belongs in a discussion about -stable. Bad enough that the sendmail
created so many "me too's" but wouldn't -chat be a better place for
california laws?
Sam
--
Just because you're moving fa
=0x0037168c
rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
class = network
Is this card supported by FreeBSD? If yes, by which driver?
mfg sam
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.o
Hi
That's a shame. But I look forward to test it, if you get the time, to
work on it.
mfg sam
Am 20.06.2012, 23:09 Uhr, schrieb Adrian Chadd :
Hi,
On 20 June 2012 14:02, sam wrote:
or if you prefer pciconf:
none12@pci0:8:0:0: class=0x028000 card=0x21001a3b chip=0x0037168
ion 1
DH_generate_key"
What is wrong and how to fix it?
Any help will be gratefull!
Thanks!
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e the /dev/random
> driver, OpenSSL (and consequently lots of crypto tools (like SSH))
> will fail with strange errors.
>
>
> Thanks!
> --
> Mark Murray
It works! Thanks for your help!
sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e and device drivers bpf0, bpf1, bpf2, and bpf3 are in /dev.
I don't know whatelse I should configure. Can someone help me?
My OS is FreeBSD 5.0-CURRENT #21.
Thanks!
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Please take a minute to review the attachment. Thank you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Any good reason why the the patch in this PR hasn't yet been
committed to the tree?
Thanks for your consideration.
Take care,
--Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, Aug 17, 2001 at 10:07:29AM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Sam Habash writes:
> : Any good reason why the the patch in this PR hasn't yet been
> : committed to the tree?
>
> lack of time on my part.
I see you've been busy latel
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 in socket buffers so that
the data value returned by kevent()'s EVFILT_READ filter on non
> 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
problems please contact me (or Warner).
This work is the first step towards significant improvements in the wireless
support.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
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
> 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
1
and get 802.11 frames by the driver printed with:
ifconfig wi0 debug link2
Setting the sysctl value to >1 will give more verbose output which is
unlikely to be useful. I have to commit some mods to tcpdump and bpf before
you can use tcpdump to tap packets at the 802.11 link layer.
Sam
To U
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 1.3.6 (I know some of the intermediate
versions had problems especially in hostap mode). You can get 1.4.9
firmware at http://www.netgate.com/support/prism_firmware/.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> 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
hile my laptop
switches
> over, it transfers at ~5600Kb/s. I don't use wicontrol at all. My
transfer
> test is just 67MB of mp3s off the fbsd machine. If you need any more
info,
> just drop me a message.
I have no answer for you. There's just not that much difference between
face. I changed wicontrol to deal with this; it would be good if
dstumbler did likewise. Otherwise I can look at adding a backwards
compatibility entry for WI_RID_SCAN_REQ.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
AIM. Wasn't aware it had been released.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Just curious. Thanks!
This can quickly turn into a bikeshed, but suggest ones. We're looking for
good benchmarks. lmbench, rawio, and bonniee are rather "micro" in nature
(not bad, just limited in their usefulness).
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> 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 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
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
> 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: se
> * 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.
Thanks for pointing out the problem. I just committed a fix.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
now. This is a bug in the HAL that I've got fixed but is
taking forever to verify correctness. With luck I'll have new stuff
committed this week (but that's what I thought last week...).
Sorry, it was my bad :(
Sam
___
[EMAIL PRO
e Win2K driver to run any of the firmware update tools. How did you
upgrade your firmware? If anyone has the bits+pieces to rev firmware I'd
like it so I can test the wi driver w/ different firmware revs.
Sam
___
[EMAIL PROTECTED] mailing list
ht
FreeBSD than to Linux.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
d these as modules, install them, and do
kldload ath
Module dependencies will do the rest.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
what M_NOTIFICATION is used for but if it's applied sparingly
it might be better to use an m_tag instead.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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
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
dump -i ath0 -y IEEE802_11
As to dstumbler, it is intimately tied to the wi driver at the moment. I
have a version that works w/ wi and ath drivers but it's a major rewrite
and incomplete. If someone wants to pick it up I'd be happy to pass the
(incomplete) work on...
Sam
___
irq 11 at device 0.0 on
cardbus1 FreeBSD 5.1-CURRENT #0: Wed Aug 20 16:59:24 CEST 2003
Any solution for that Sam? I can remember you mentioned you have fix for
that a couple of weeks ago and that you will submit it in a week time or
so.
I have seen the problem but have been unable to resolve it. Grab a
ifferent from -current that is was hard to tell if the
problems I saw (lost packets) were due to this change or others.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
domain.c solved the problem
> for me.
> Additional side notice: netgraph is compiled statically into
> the kernel, no separate module.
Thanks, will fix it.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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
> 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-curr
are trying to
do.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
h) in promiscuous mode. The bridge manual page is
wrong and I will fix it.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nd your setup (station, adhoc, hostap, 11a, 11b, 11g).
Also try sysctl debug.ieee80211=1 and/or ifconfig ath0 debug and look at
the debug messages.
Obviously stuff worked for me before I committed (and I tested all types of
cards).
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.
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...
> 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
th0 mediaopt turbo
I verified turbo mode was in use by disabling it on either station or AP
side and with things mismatched the station/AP couldn't see each other.
With turbo mode enabled on each side I was able to associate and
communicate as normal;
y the driver.)
> Then I typed:
>
># ifconfig ath0 mode 11a mediaopt turbo
> atalk 0.0 range 0-0 phase 2
>
> Does it think I'm doing appletalk or something?
Hmm, didn't see this, will have to check.
>
> It seems to s
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/netine
> 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 uns
> 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
> 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 t
nning this week's
> current).
>
> ... Now, that said, some of my disassociation problems on the laptop
> seem to have cured (associating with other access points) ...
>
> So I need help with this really large bug in the wi code.
Please send me your config. I'll d
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]"
on't see PFIL_HOOKS defined. You need it for IPFILTER. Part of my
changes removed some cruft that automatically configured PFIL_HOOKS when
IPFILTER was configured. Guess I need to update NOTES and add something to
UPDATING.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 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:/
Yes, I noticed this late last week. I think it's been busted for <1 week. I
tried to pinpoint the commit but ran out of time.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
a few months ago here. (Not very well
> > > compared with ddb. E.g., calling a function is usually fatal.)
> >
> > Hmm, that's not what Sam or I are seeing. How old is your kernel?
> > You *are* able to continue, right? Everything else works for me.
>
> I di
et fixed before the
5.2 release. The most likely one you'll see is when ejecting a network card
from a laptop.
Please contact me directly if you see any problems that look related to these
changes.
Sam
___
[EMAIL PROTECTE
sy to overlook.
Yeah, probably. I wouldn't notice it. I agree that it's important to conform
to local style, regardless of whether it conflicts with style(9).
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhoc
> turbo mode 11a
Apparently adhoc mode is currently busted. It's at the top of my todo list
and I may even get to it this week...
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
t; If all else fails, read the source code... 8-).
>
> )) I've tried to, but... had to ask here. So all is left is to ask Luigi
> and Intel.
I cannot comment on 5.1-R, but I am running DEVICE_POLLING tests today with
-current and 2 em NICS and systat -vm shows no interrupts for the IRQs where
the NICs are. I can only guess that either 5.1-R has a bug or the polling
support was not in the driver at that point.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
A_ALTSTAT, ATA_A_IDS | ATA_A_RESET);
DELAY(1);
ATA_IDX_OUTB(ch, ATA_ALTSTAT, ATA_A_IDS);
-DELAY(1);
+DELAY(10);
+ATA_IDX_INB(ch, ATA_ERROR);
/* wait for BUSY to go inactive */
for (timeout = 0; timeout < 310; timeout++) {
Sam
__
oc
page_alloc
slab_zalloc
uma_zone_slab
uma_zalloc_bucket
uma_zalloc_arg
uma_zalloc_arg
ffs_vget
ufs_lookup
ufs_vnoperate
vfs_cache_lookup
ufs_voperate
lookup
nfs_namei
nfsrv_lookup
nfssvc_nfsd
nfssvc
Contact me for more details. This really needs to be fixed.
Sam
_
at are blocked on locks. If you have witness
in your kernel then show locks would also be useful. If you don't have
witness in your system then rebuild your kernel with it.
The most recent round of changes were to lock the routing table. These went
in 10/3 and were extensive. They could
for [ base station MAC address ]
I just committed a fix to the ath driver for the WEP problem; let me know if
you have any more trouble. I verified 40-, 104-, and 128-bit WEP keys work
for me. As a bonus I also sped up WEP traffic through the driver.
Sam
Yes, I'm aware of this one. Thank you.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
licly
> available :)
>
> I suspect this is fallout from the multicast code reorg that bms has been
> working on.
Yup; it's on my list of bugs to look at.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/li
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
n my kernel
> may be I need try another way to make the bridge work?
LOR's will not cause a system crash. If a LOR causes a problem it will likely
deadlock your system.
The two LORs shown above are known and should not be a problem.
Sam
urse
> ~~~cut~~~
Any chance you can get a stack trace the next time this happens? The LOR by
itself is hard to go from...
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
MPSAFE
netisrs.
The following drivers are marked MPSAFE:
ath, em, ep, fxp, sn, wi, sis
I've got changes coming for bge. Other drivers probably can be marked MPSAFE
but I'm only doing it for those drivers that I can test.
Sam
--- Begin Message ---
sam 2003/10/29 10
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
Here are a couple of backtraces:
I'll deal with it. The icmp_redirect LOR was next on my list...
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e ran many jumbogram tests of machines connected with a cross-over cable
and em devices at each end. If you've got a swtch in the middle make sure it
does the right thing.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.
op+0x50
> in6_ifinit(c200,c2437600,c8f45a2c,1,1be) at in6_ifinit+0x147
> in6_update_ifa(c200,c8f45a1c,0,0,20080fe) at in6_update_ifa+0x500
> in6_ifadd(c8f45b34,0,40,0,0) at in6_ifadd+0x22a
I've got fixes for almost all the outstanding LOR's and recursive lock
ast few days. One of their manifestations is that SMP kernels always
> panic in sbdrop() on shutdown.
I'm looking at something similar now. If you have a stack trace please send
it to me (along with any other info). You might also try booting
debug.mpsaf
gt;rt_ifp->if_flags & IFF_LOOPBACK))
> The ro->ro_rt->rt_ifp would be pointing the the ifp that was gone
> and panic. This one wasn't to bad except for crashing during a suspend/
> resume sequence the other panic is happening randomly through the day.
>
I have a line on this one and should have a fix soon.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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
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.
> I get,
> >
> > Debugger()
> > panic()
> > propagate_priority()
> > _mtx_lock_sleep()
> > _mtx_lock_flags()
> > softclock()
> > ithread_loop()
> > fork_exit()
> > fork_trampoline()
> >
> > I have a crash dump and kernel.debug if furt
ged to get a coredump.
>
> The contents of the rt pointer passed to RTFREE() does really not look
> right to me. These in particular:
> rt_llinfo = 0xc0f95880 "\220ǼÁ\200qùÀ"
> rn_Key = 0xc1bcc7a0 "0AùÀ8AùÀ"
>
> Anyone got any ideas
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 lis
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
695a690 rtentry (rtentry) @
> /opt/src/sys/netinet/ip_input.c:352 Stack backtrace:
These go away with forthcoming changes (so I've ignored them).
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic: mutex inp not owned at /usr/src/sys/netinet/ip_output.c:218
> cpuid= -;
> Debugger("panic")
> Stopped atDebugger+0x55: xchgl %ebx,in_Deubbger,0
> db>
I'll commit the fix today. I was waiting for testing feedback from the 1st
y setting the media when operating
in hostap mode. It should be ignored, but I'm not sure exactly what will
happen. Locking the tx rate on the client side makes more sense and should
be honored correctly.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
radio that's not yet
supported by the HAL. I hope to have something to try next week.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
uot;unable to attach hardware" and the
> sys/contrib/dev/ath/ah.h indicates an incompatibily in this hardware
> revision.
>
> Does anybody have a "secret" patch do make it working ? :-)
There should be an update this week to add support for the card (actually
radi
-
> lock order reversal
> 1st 0xc3a23090 rtentry (rtentry) @
> HEAD/compile-20031119-1814/sys/net/rtsock.c:389 2nd 0xc396587c radix node
> head (radix node head) @ HEAD/compile-20031119-1814/sys/net/route.c:1114
>
> STATE:
> "go away with forthcoming change
hing.)
Better, use
tcpdump -e -i ath0 -y IEEE802_11
and verify the 802.11 frames are actual duplicates. They should not be unless
there's a bug in the duplicate suppression logic in the 802.11 code.
Sam
___
[EMAIL PROT
. I think the switch should not be made until this is resolved. netbsd
went through this recently and made an effort to bring performance of a
dynamic root in line with a static root before making the change.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
write), eip = 0x282c50af, esp = 0xbfbfe9ec,
> ebp =
> 0xbfbfea08 ---
>
Thanks, I've got a fix for this.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
^^
>not
>
> > Are you on a multi-homed system? -sc
>
> Ack! If ever there was a missing word to change the meaning of an
> email! What I meant to say was you're *not* alone in this... I'm
> having this problem on m
o'd (or at least m_flags) then the assertion may trip.
It's arguable what the correct solution is for these problems but you should
be able to safely remove the assert until we can make a sweep over the
drivers as the existing code has been around for a while (not to imply this
makes
il the driver can be changed
> to not report them.
I changed this a while ago; phy errors are no longer counted as input errors.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, s
) at fork_trampoline+0x1a
> --- trap 0x1, eip=0, esp=0xd67e6d7c, ebp=0 ---
Fixed last night.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ock.
>
> I think this kassert should be removed.
>
> Do you guys concurr?
Warner has this pending with some other fixes; perhaps he can accelerate
doing the commit? The assert is actually just bogus (if_start can be called
under certain conditions with IFF_OACTIVE set.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
<- AUTH response
ASSOC ->
<- PROBE response
<- ASSOC response
and then the client retries again ad infinitum.
If you've got an AP running with recent source and a wi card please contact
me.
Sam
___
[EMAIL PROTECTED] mail
anges "soon". I'm hoping to resolve the problem.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
1 - 100 of 203 matches
Mail list logo
