Date: Sun, 13 Nov 2011 01:35:44 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-mobile@freebsd.org Subject: Re: other bwn panic Message-ID: <4EBEE6B0.5040906@yandex.ru> In-Reply-To: <CAJ-Vmo=JWS2DqJ494LQqZ_ETcbDFJq4eNwqi0dUeZC1haQdCXA@mail.gmail.com> References: <4EBBD13C.2010705@yandex.ru> <CAJ-Vmok%2BUcGUS8fVm6WehyEZBUJKr5TmL3RnKwOQbiMdcpb6Mw@mail.gmail.com> <4EBCDAF2.5020605@yandex.ru> <CAJ-Vmo=JWS2DqJ494LQqZ_ETcbDFJq4eNwqi0dUeZC1haQdCXA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adrian Chadd wrote on 12.11.2011 22:37: > On 11 November 2011 00:21, Ruslan Mahmatkhanov <cvs-src@yandex.ru> wrote: > >> Yes, but i'm not sure what exact version it was. Firmware version is >> still the same as it was on 9-CURRENT, but after some recent if_bwn or >> wireless stack changes this errors now happens constantly, but this >> panic was for the first time. > > Well, we'll need to know which firmware/driver version last worked > right before we have any chance of fixing what's going on. > > > > Adrian And if it help anyhow - i lost my source code that i just finished but wasn't saved last changes in process of panicking. I now have 0-sized file :(. -- Regards, Ruslan Tinderboxing kills... the drives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EBEE6B0.5040906>