Synopsis: [fxp] [panic] fxp(4) related kernel panic
State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Wed Mar 18 06:09:32 UTC 2009
State-Changed-Why:
Is this still issue on latest stable?
I think I've fixed all known buffer exhausation issues of fxp(4).
Would you
I'm developing a kernel module that will be doing inspection and
needed access to raw network frames,
so I turned to netgraph as the solution.However it seems that
netgraph will not permit a module
to unload once it's participated in a mkpeer/connect operation.
Rebooting to remove a modul
On Tue, 17 Mar 2009, Sam Leffler wrote:
Sean C. Farley wrote:
*snip*
Is the AP made by Aruba Networks?
On RELENG_7, I needed a newer version (v0.5.11 instead of v0.5.10) of
wpa_supplicant for it to associate correctly. With v0.5.10, I could
see DHCP requests from my laptop but no respons
Old Synopsis: panic in net/if_mib.c
New Synopsis: [if_mib] [panic] panic in net/if_mib.c
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Mar 18 03:23:58 UTC 2009
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebs
On Tue, Mar 17, 2009 at 07:44:43AM +, Bruce Simpson wrote:
> Hi,
>
> I noticed that ae(4) got MFC'ed to RELENG_7 before Wake-on-Lan support did.
>
I think WOL MFC was done before ae(4) MFC.
> However, WOL support is now there, and it looks like the change can just
> go in:
>
> http://w
On 03/17/09 07:44, Bruce Simpson wrote:
> Hi,
>
> I noticed that ae(4) got MFC'ed to RELENG_7 before Wake-on-Lan support did.
>
> However, WOL support is now there, and it looks like the change can just
> go in:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ae/if_ae.c.diff?r1=1.1.2%3AR
I made a minor change to ifconfig to try kldloading the interface name
specified on the create wlandev (ifconfig already tries for
normal invocations, just needed to try with the wlandev interface)
/usr/src/sbin/ifconfig/ifieee80211.c
--- ifieee80211.c.original 2009-03-17 16:53:29.0
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Sam Leffler
To: "Sean C. Farley"
Cc: Matthias Apitz ,
Matthias Apitz , freebsd-net@freebsd.org,
Bruce Simpson , bug-follo...@freebsd.org
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine wit
Bruce Simpson wrote:
Coleman Kane wrote:
If you are looking for a reliable test case, this might be it for you,
but I think you need a wlan interface to test it with:
* Install net/avahi from ports
* Set avahi_daemon_enable="YES" in rc.conf
* Configure VAP params for wlan0 card in rc.conf
Sean C. Farley wrote:
On Tue, 17 Mar 2009, Matthias Apitz wrote:
El día Tuesday, March 17, 2009 a las 10:39:32AM +, Bruce Simpson
escribió:
Matthias Apitz wrote:
as requested the output of dmesg(1) and the ath0 related part of
'pciconf -lv'; pls note also that the Wifi works fine in gen
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: "Sean C. Farley"
To: Matthias Apitz
Cc: Bruce Simpson , freebsd-net@FreeBSD.org,
Matthias Apitz , bug-follo...@freebsd.org
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP
o
On Tue, 17 Mar 2009, Matthias Apitz wrote:
El día Tuesday, March 17, 2009 a las 10:39:32AM +, Bruce Simpson escribió:
Matthias Apitz wrote:
as requested the output of dmesg(1) and the ath0 related part of
'pciconf -lv'; pls note also that the Wifi works fine in general,
i.e. with the AP
A suitably kludgy fix for this issue has now been committed to HEAD.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Coleman Kane wrote:
If you are looking for a reliable test case, this might be it for you,
but I think you need a wlan interface to test it with:
* Install net/avahi from ports
* Set avahi_daemon_enable="YES" in rc.conf
* Configure VAP params for wlan0 card in rc.conf
* Log in and run "dh
On Tue, 2009-03-17 at 08:12 +, Bruce Simpson wrote:
> Sam Leffler wrote:
> > It is the same issue but the root cause is unclear. There is much
> > code that does assumes ifma_protospec might be NULL and checks for
> > it. In my case (creating a wlan ifnet and then destroying it on
> > ejec
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Matthias Apitz
To: Bruce Simpson
Cc: Matthias Apitz , freebsd-net@freebsd.org,
bug-follo...@freebsd.org
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or
IP does not work
Date:
as requested the output of dmesg(1) and the ath0 related part of
'pciconf -lv'; pls note also that the Wifi works fine in general, i.e.
with the AP in my office (WPA) and in my home (WEP);
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,
El día Tuesday, March 17, 2009 a las 10:39:32AM +, Bruce Simpson escribió:
> Matthias Apitz wrote:
> >as requested the output of dmesg(1) and the ath0 related part of
> >'pciconf -lv'; pls note also that the Wifi works fine in general, i.e.
> >with the AP in my office (WPA) and in my home (WEP
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Bruce Simpson
To: Matthias Apitz
Cc: bug-follo...@freebsd.org, freebsd-net@FreeBSD.org
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP
or IP does not work
Date: Tue, 17 Mar 2009 10:39:3
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Matthias Apitz
To: bug-follo...@freebsd.org
Cc: freebsd-net@FreeBSD.org, Bruce Simpson
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or
IP does not work
Date: Tue, 17 Mar 2009 11:36:5
Matthias Apitz wrote:
as requested the output of dmesg(1) and the ath0 related part of
'pciconf -lv'; pls note also that the Wifi works fine in general, i.e.
with the AP in my office (WPA) and in my home (WEP);
Is this an ASUS Eee PC? If so, which model is it? It looks like a 901.
I tested
On Tue, Mar 17, 2009 at 02:23:13PM +0530, srikanth jampala wrote:
> Hi all
Hi.
> This is my first posting.
>
> I want the notifications about the SA (security association) add/delete
> events,
> from the kernel to my externel kernel module.
>
> How can I do this... ?
Such events are notifi
Hi all
This is my first posting.
I want the notifications about the SA (security association) add/delete
events,
from the kernel to my externel kernel module.
How can I do this... ?
Thanks in advance for ur suggestions.
Sriknath
___
freebsd-net@f
Hi,
One crucial piece of info missing is exactly which Atheros part you are
using, can you please attach
this to the PR? you can get this from pciconf -lv and look for the
ath0, also please post your boot time
dmesg / or when you insert the part. thanks.
Matthias Apitz wrote:
The following
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Matthias Apitz
To: bug-follo...@freebsd.org, g...@unixarea.de
Cc:
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or
IP does not work
Date: Tue, 17 Mar 2009 09:42:43 +0100
I forgot t
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Bruce Simpson
To: freebsd-gnats-sub...@freebsd.org
Cc: lini...@freebsd.org, freebsd-b...@freebsd.org,
freebsd-net@FreeBSD.org, Matthias Apitz ,
Sam Leffler
Subject: Re: kern/132722: [ath] Wifi ath0 associates f
Hi,
Can you please try cvsupping RELENG_7 sources to after this date:
%%%
Date: Thu Mar 12 03:09:11 2009
New Revision: 189720
URL: http://svn.freebsd.org/changeset/base/189720
%%%
The Atheros open source HAL from HEAD was MFC'd and this may or may not
fix your problem.
thanks,
BMS
___
Old Synopsis: Wifi ath0 associates fine with AP, but DHCP or IP does not work
New Synopsis: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not
work
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Mar 17 08:21:07 UT
Sam Leffler wrote:
It is the same issue but the root cause is unclear. There is much
code that does assumes ifma_protospec might be NULL and checks for
it. In my case (creating a wlan ifnet and then destroying it on
eject) the patch below is sufficient. I don't care to dig right now
to unde
Bruce Simpson wrote:
Hi,
I noticed that ae(4) got MFC'ed to RELENG_7 before Wake-on-Lan support did.
However, WOL support is now there, and it looks like the change can just
go in:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ae/if_ae.c.diff?r1=1.1.2%3ARELENG_7&tr1=1.1&r2=1.3%3AHEAD&t
Hi,
I noticed that ae(4) got MFC'ed to RELENG_7 before Wake-on-Lan support did.
However, WOL support is now there, and it looks like the change can just
go in:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ae/if_ae.c.diff?r1=1.1.2%3ARELENG_7&tr1=1.1&r2=1.3%3AHEAD&tr2=1.3
I am tied up
31 matches
Mail list logo
