Date: Tue, 6 Nov 2012 13:41:51 -0500 From: Eitan Adler <lists@eitanadler.com> To: CeDeROM <cederom@tlen.pl> Cc: Adrian Chadd <adrian@freebsd.org>, freebsd-current@freebsd.org Subject: Re: 9.1-RC3 feels okay :-) Message-ID: <CAF6rxgnKGxECDn=8bSW2WjUXBcd0%2BZayhy6cmdguXj4CD9sUdQ@mail.gmail.com> In-Reply-To: <CAFYkXjk9mgdugUV-n8ACQZnf0n9EUS%2Bktq_6cAYYC52DzXtyqQ@mail.gmail.com> References: <CAFYkXjnLp8WC7=pCoWuEMjnHWAAA68exE3PCs7n=xfz2VLLH8w@mail.gmail.com> <CAJ-Vmok2fpA9d8A9jnNHUe3Ur7Cnr0bDSOiYufDE2Q4xnp2jYw@mail.gmail.com> <CAFYkXjk9mgdugUV-n8ACQZnf0n9EUS%2Bktq_6cAYYC52DzXtyqQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 November 2012 12:32, CeDeROM <cederom@tlen.pl> wrote: > On Tue, Nov 6, 2012 at 5:10 PM, Adrian Chadd <adrian@freebsd.org> wrote: >> Please file a bug about the intel wifi crash! > > Hello Adrian! :-) Should I attach kernel core dump / backtrace or > simply write that "kernel crash on unstable wifi connection or when > switching radio on and off multiple times or switching wpa_supplicant > multiple times" is enough? :-) Please include a kernel backtrace. Do you have debugging symbols enabled? This is really important: *be responsive*. Hardware bugs are difficult to diagnose and fix, so the more information you provide, and the more you are able to test patches or answer questions, the easier it will be get this resolved. If you can provide a reproducible step-by-step directions to see the bug, even better. -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgnKGxECDn=8bSW2WjUXBcd0%2BZayhy6cmdguXj4CD9sUdQ>