kern/149185: [rum] [panic] panic in rum(4) driver on 8.1-R
rpaulo at freebsd.org
Thu Aug 5 10:10:07 UTC 2010
The following reply was made to PR kern/149185; it has been noted by GNATS.
From: Rui Paulo <rpaulo at freebsd.org>
To: Bernhard Schmidt <bschmidt at techwires.net>
Cc: Alex Kozlov <spam at rm-rf.kiev.ua>,
bug-followup at freebsd.org,
nox at freebsd.org
Subject: Re: kern/149185: [rum] [panic] panic in rum(4) driver on 8.1-R
Date: Thu, 5 Aug 2010 10:38:44 +0100
On 5 Aug 2010, at 10:34, Bernhard Schmidt wrote:
> On Thu, Aug 5, 2010 at 11:11, Alex Kozlov <spam at rm-rf.kiev.ua> wrote:
>> On Thu, Aug 05, 2010 at 10:05:39AM +0200, Bernhard Schmidt wrote:
>>> On Thu, Aug 5, 2010 at 08:52, Alex Kozlov <spam at rm-rf.kiev.ua> =
>>>> On Wed, Aug 04, 2010 at 10:02:35PM +0200, Juergen Lock wrote:
>>>>> Regarding the 8.1 if_rum(4) panics... I got a similar one, =
>>>>> a dump and tried to gather some info for someone who knows the =
>>>>> The zero divide fault was because (apparently) rate was =
>>>>> as is
>>>>> ((struct ieee80211_node *) =
>>>>> i.e. struct ieee80211_txparam &vap->iv_txparms in case it =
>>>> Yes, its seems that ratectl framework sometimes set ni->ni_txrate =
>>>> This can be mitigated by patch  or by setting ucastrate option =
>>>> ifconfig. Still real issue need to be solved.
>>> The real issue is that prior to an association (RUN state)
>>> ieee80211_ratectl_node_init() is not called, therefore iv_bss is not
>>> configured in any way.
>> ieee80211_ratectl_node_init() called from iv_newstate when switching =
>> IEEE80211_S_RUN state. Most drivers do the same. Is it wrong?
>> Some call it from iv_newassoc, but this marked /* XXX move */
> It is not wrong, but to late. Before RUN state and the iv_newassoc()
> call, you have to send frames for scanning and authentication, those
> need a valid rate too. I wonder if we can call node_init() in
> ieee80211_vap_setup() or something similar, that would definitely be
> early enough.
vap_setup() runs once and we need need to call node_init for each node =
connected to an AP or for the AP node when the vap is a STA.
More information about the freebsd-net