Date: Wed, 2 May 2018 21:10:01 -0500 From: Tim Chase <freebsd@tim.thechases.com> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: ath0: could not map interrupt (again?) Message-ID: <20180502211001.550d290c@bigbox.christie.dr> In-Reply-To: <CAJ-Vmo=uAB4Yv8fTu6yP5tDh82FtgFHQFDRWOGmNLYsABTvENw@mail.gmail.com> References: <20180502165745.59a5bfc4@bigbox.christie.dr> <CAJ-Vmo=uAB4Yv8fTu6yP5tDh82FtgFHQFDRWOGmNLYsABTvENw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-05-02 23:21, Adrian Chadd wrote: > CAn you try booting freebsd-head and see if it's any better? At your advice, I created a boot image of 12.0-CURRENT r333017 but see the same "could not map interrupt" in my dmesg that I got on 11.x -tim PS: thanks for the boot-from-a-memstick-snapshot suggestion...much faster than the svn+buildworld+buildkernel I'd been trying.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180502211001.550d290c>