Date: Thu, 4 Aug 2016 14:40:38 -0700 From: "K. Macy" <kmacy@freebsd.org> To: Christian Schwarz <me@cschwarz.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: iwm load panic Message-ID: <CAHM0Q_Nj2ALXiqVbBukbJKN7WZWp0T_KRD=sFW9hX8qotjWihA@mail.gmail.com> In-Reply-To: <20160804162320.GC26444@csarch> References: <CAHM0Q_Mv6LW0Dg%2BuzMs2_%2Bbk8QOexD7yi%2Bwao0PGp8h4stiWFA@mail.gmail.com> <c2bb6ad1-1a1c-9b93-92c8-f222ece4e40b@selasky.org> <CAHM0Q_Pn7Ps%2B8sMaSL2K9GSQN8XiAPcfMeRA33ND%2BUodj5Hj4w@mail.gmail.com> <20160804162320.GC26444@csarch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, August 4, 2016, Christian Schwarz <me@cschwarz.com> wrote: > Any idea which revision/commit introduced this regression? > > (I want to test iwm + freebsd-base-graphics on my laptop tonight and > hence avoid crashers like this one in advance.) > > @mmacy: is the revision in the current drm-next-4.6 branch of > https://github.com/FreeBSDDesktop/freebsd-base-graphics.git > > Yes. That is what I run on my Skylake based gen4 carbon x1. 8260 support was just added, so I don't know if it's possible to use new hardware without exposing one's self to this bug. In fairness, 80-85% of the time it loads just fine, and this bug looks much easier to fix than the various issues I am looking at right now. Once loaded the driver has worked quite satisfactorily. -M > Thanks, > > -- > Christian Schwarz > > > _______________________________________________ > freebsd-current@freebsd.org <javascript:;> mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org > <javascript:;>" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHM0Q_Nj2ALXiqVbBukbJKN7WZWp0T_KRD=sFW9hX8qotjWihA>