The following reply was made to PR kern/144642; it has been noted by GNATS.
From: Arthur Hartwig <a_hart...@fastmail.fm>
To: bug-follo...@freebsd.org, a_hart...@fastmail.fm
Cc:
Subject: Re: kern/144642: [rum] [panic] Enabling rum interface causes panic
Date: Mon, 23 Aug 2010 22:16:37 +1000
The problem still exists in FreeBSD 8.1 Release.
This patch stops by panic soon after setting the interface up:
# diff -b -C 7 if_rum.c.orig if_rum.c
*** if_rum.c.orig Tue Aug 10 15:05:51 2010
--- if_rum.c Tue Aug 10 20:34:20 2010
***************
*** 2109,2122 ****
--- 2109,2127 ----
rum_prepare_beacon(struct rum_softc *sc, struct ieee80211vap *vap)
{
struct ieee80211com *ic = vap->iv_ic;
const struct ieee80211_txparam *tp;
struct rum_tx_desc desc;
struct mbuf *m0;
+ /* Guard against default ni_chan */
+ if (vap->iv_bss->ni_chan == IEEE80211_CHAN_ANYC) {
+ return 0;
+ }
+
m0 = ieee80211_beacon_alloc(vap->iv_bss,&RUM_VAP(vap)->bo);
if (m0 == NULL) {
return ENOBUFS;
}
tp =&vap->iv_txparms[ieee80211_chan2mode(ic->ic_bsschan)];
rum_setup_tx_desc(sc,&desc, RT2573_TX_TIMESTAMP, RT2573_TX_HWSEQ,
#
At the suggestion of Alex Kozlov I ran the shell script:
for i in `jot - 1 200`; do sudo /etc/rc.d/netif start; done
on my 2x800MHz PIII system and it did not panic. Alex ran it on some more
recent systems and still saw panics. While I think FreeBSD should be "bullet
proof" I believe this patch should still be accepted since it makes the system
at least somewhat more robust.
The code for the newer run driver makes the same kind of test as suggested by
this patch before calling ieee80211_beacon_alloc().
_______________________________________________
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"
