Date: Tue, 4 Oct 2011 05:02:03 -0600 From: PseudoCylon <moonlightakkiy@yahoo.ca> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: Panic in AHDEMO mode (was: net-mgmt/aircrack-ng on FreeBSD 7+ / call for testing) Message-ID: <CAFZ_MYLx5E3O7U1O2LcBwfk_mZjQVbXgMdsd0tZ8PSR0oOMcYA@mail.gmail.com> In-Reply-To: <CAJ-Vmo=M7NN=k4K=t-PK0hUQ7mjQkdvSN3etK3_MNjuCReXErA@mail.gmail.com> References: <CAFZ_MYJEV24QLD%2BhOE%2Bzh331xWp2_cnLu7GwV8rT-roi1qYv5Q@mail.gmail.com> <CAJ-Vmo=M7NN=k4K=t-PK0hUQ7mjQkdvSN3etK3_MNjuCReXErA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 4, 2011 at 1:33 AM, Adrian Chadd <adrian@freebsd.org> wrote: > Or perhaps find out why the bss isn'et setup right and fix that? I prefer this. ^^^ 0xffff fault happened on different occasions. As far as I remember, in iv_update_beacon, iv_newstate, if_start. So, I added some extra tests or used ic_curchan instead in run(4) to avoid panic. We should make sure ni_chan is properly set before anyone else uses it. AK
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFZ_MYLx5E3O7U1O2LcBwfk_mZjQVbXgMdsd0tZ8PSR0oOMcYA>