Date: Tue, 13 Nov 2018 20:50:20 +0100 From: Polytropon <freebsd@edvax.de> To: B J <va6bmj@gmail.com> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Kernel Panics With Firefox 63.x Message-ID: <20181113205020.afc446d9.freebsd@edvax.de> In-Reply-To: <CAP7QzkO8=A-DVa7GxEXv0gpJL4MnDirz6DVfzF%2B6GdAF9h7aag@mail.gmail.com> References: <CAP7QzkN_6sGAh66Am2oTfDmazWUD6Gxq2d5ss-kNewjcRoc5RA@mail.gmail.com> <20181113182954.1d7060bd.freebsd@edvax.de> <CAP7QzkN66pSTOmw0HAPsDAzRgxRtLXRgoqFZnAvNoXW1eLq5uQ@mail.gmail.com> <20181113201830.f0eec001.freebsd@edvax.de> <CAP7QzkO8=A-DVa7GxEXv0gpJL4MnDirz6DVfzF%2B6GdAF9h7aag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Nov 2018 19:37:39 +0000, B J wrote: > On 11/13/18, Polytropon <freebsd@edvax.de> wrote: > > On Tue, 13 Nov 2018 18:28:53 +0000, B J wrote: > >> On 11/13/18, Polytropon <freebsd@edvax.de> wrote: > >> > On Tue, 13 Nov 2018 16:44:04 +0000, B J wrote: > >> >> I recently upgraded my system and that included Firefox. It's been > >> >> troublesome ever since. Often, it would crash for no apparent reason > >> >> and this morning, it started taking down my entire system. The result > >> >> was that my machine would have to reboot. > >> >> > >> >> Now I can't use Firefox at all without having my machine going into a > >> >> kernel panic. > >> > > >> > Could you get any useful information from the kernel dump? > >> > >> I haven't looked at it in detail. From the info file in /var/crash: > >> > >> Panic String: ufs_dirbad: /: bad dir ino 719 at offset 512: mangled > >> entry > >> > >> The core.txt file gives a lot more information in detail. > > > > Oh! This looks like a file system problem! Even though > > it sounds strange, file system inconsistencies can cause > > lots of problems, up to a complete system crash. > > <snip> > > Thanks for the info. It looks like I've got some work ahead of me. > I'll look into that once I finish building FF from ports which, as I'm > writing this, is still in progress after about 2 hours. I'd suggest you interrupt the build right now. It _could_ happen that a file system inconsistency causes a defective binary to be generated without you noticing. Perform the forced fsck in SUM first, then "make clean", and finally restart the build - just to be sure... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181113205020.afc446d9.freebsd>