Date: Sat, 25 Feb 2012 00:03:29 -0800 From: Adrian Chadd <adrian@freebsd.org> To: "Sevan / Venture37" <venture37@gmail.com> Cc: freebsd-wireless@freebsd.org Subject: Re: wi driver Message-ID: <CAJ-VmokDSQo9xnkrjShFXoXxqg2FGVmPym1CPy_KAb0=d6WAUw@mail.gmail.com> In-Reply-To: <4F46216D.5040704@gmail.com> References: <4F36DAB0.2020803@gmail.com> <4f36df71.2139440a.10ce.fffffb81@mx.google.com> <CAJ-Vmok6RMthnC0ESKXU20LVvqczdN6wcTpGbSqNS7JEaODsWg@mail.gmail.com> <4F370F21.3030300@gmail.com> <CAJ-Vmo=Kf2VystjqLG48s0EJHy=4TazYD1azWDaxY5G48=1JYQ@mail.gmail.com> <4F46216D.5040704@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I've just committed a fix to wi_info_intr(). The problem was that the vap list is empty (ie you hadn't created a VAP but brought up the interface) - so it paniced. Yes, I now have a BIG stack of these things. But I'm seeing interrupt storms; so I don't think my NIC is going to work well. That, and WPA doesn't work. :-) Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokDSQo9xnkrjShFXoXxqg2FGVmPym1CPy_KAb0=d6WAUw>