if_run and wlan_amrr: kernel panics on 8.2-PRERELEASE amd64
Alexander Zagrebin
alex at zagrebin.ru
Wed Jan 19 11:23:34 UTC 2011
Hi!
On 19.01.2011 09:37:12 +0100, Bernhard Schmidt wrote:
> > Case 2: wlan_amrr.ko loaded manually _after_ if_run.ko but before
> > creation of the wlan interface
> >
> > stable/8: panic on rate control
> > rev217511: no panic, but rate control doesn't work; tx rate is
> > fixed on 1 Mbit/s
>
> That sounds rather weird to me, I can't imagine how the module loading
> order should make any difference. Well, at least, before creating the
> VAP, because that is the point where that stuff gets initialized/used.
It seems you're right. I couldn't reproduce it again.
May be I have missed anything. Sorry...
> Do you have anything configured in rc.conf maybe? That would create the
> VAP right after loading if_run.ko even before you are able to load
> wlan_amrr.ko.
Yes, I have wlans_run0="wlan0" and create_args_wlan0=... in the rc.conf,
but while testing I've used `ifconfig wlan0 destroy` after `kldload if_run`.
May be it was mistyping...
Also I've noticed that messages like
"ieee80211_load_module: load the wlan_amrr module by hand for now." has
disappeared from the log. Is it normal?
So there is the one issue only: the panic if runfw.ko and wlan_amrr.ko
both loaded via loader.conf.
Have you any ideas?
Will be rev. 217511 MFC'd on the 20 january?
--
Alexander Zagrebin
More information about the freebsd-net
mailing list