kern/149185: [rum] [panic] panic in rum(4) driver on 8.1-R

[Bernhard Schmidt]

The following reply was made to PR kern/149185; it has been noted by GNATS.

From: Bernhard Schmidt <bschmidt at techwires.net>
To: Alex Kozlov <spam at rm-rf.kiev.ua>, bug-followup at freebsd.org
Cc: nox at freebsd.org, rpaulo at freebsd.org
Subject: Re: kern/149185: [rum] [panic] panic in rum(4) driver on 8.1-R
Date: Thu, 5 Aug 2010 10:05:39 +0200

 On Thu, Aug 5, 2010 at 08:52, Alex Kozlov <spam at rm-rf.kiev.ua> wrote:
 > On Wed, Aug 04, 2010 at 10:02:35PM +0200, Juergen Lock wrote:
 >> =A0Regarding the 8.1 if_rum(4) panics... =A0I got a similar one, extract=
 ed
 >> a dump and tried to gather some info for someone who knows the code:
 >>
 >> =A0The zero divide fault was because (apparently) rate was unitialized,
 >> as is
 >>
 >> =A0 =A0 =A0 ((struct ieee80211_node *) m->M_dat.MH.MH_pkthdr.rcvif)->ni_=
 vap->iv_txparms[0]
 >>
 >> i.e. struct ieee80211_txparam &vap->iv_txparms[0] in case it matters.
 > Yes, its seems that ratectl framework sometimes set ni->ni_txrate to 0
 > This can be mitigated by patch [1] or by setting ucastrate option in
 > 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.
 
 I'll look into that if no one beats me.
 
 --=20
 Bernhard