From owner-freebsd-questions@freebsd.org Tue Nov 13 19:18:41 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB83A112E9D6 for ; Tue, 13 Nov 2018 19:18:40 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2588E73C18 for ; Tue, 13 Nov 2018 19:18:39 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.193.180.181]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPA (Nemesis) id 1MsYzD-1fT2Nh45ed-00u0rD; Tue, 13 Nov 2018 20:18:31 +0100 Date: Tue, 13 Nov 2018 20:18:30 +0100 From: Polytropon To: B J Cc: freebsd-questions Subject: Re: Kernel Panics With Firefox 63.x Message-Id: <20181113201830.f0eec001.freebsd@edvax.de> In-Reply-To: References: <20181113182954.1d7060bd.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:XR6FAqaEdfP+H+Tkad/NJZ1t9pH672oE8mDCp6BdIqvbcybOqMl c4VAC1k8Hi9lrUo53/VmGcbXGcZnMd++VO/8h+ycoZtED+gmtHOV+iZ7gZ8qFmsqDUitmtZ xYAwRPkDvAqeSTkzf/RwxjjQrtRDJFqZZA1oLs9xnXbjBgnfPpeE0DqFZWjXYOXCw4Dij0m q/pCDWeQ4l8pxums8Xb0Q== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V01:K0:juCmzlr+xvo=:qCriESc+et5PIygT8jaFmi nRBxSAADvLVR9CGJWYdoEw0qe8Is6im+AeYZaVOL1Khqgy6+MlXCWqGmrJDe/faYPBXgGxFYJ LqVbz4pdNVn5Fr+6gabgbvhhluBqs65wAX1HpNVY41U1RAWAmZjNwInCgEBbBHIoJWTuaPvji Xvr8Y+IpQLCKE5+0JSczA0wbMchwlpVsptF42lFbW0HYCoyZ9etINkh3MpdJYtMoLKuK+U4PR 42zNymDqzDMQ9BTclXgzFRtHIR+claa5KFSHlovQr2OfNDn1pe1lDeZ37MLA0IHY7QHcBn+/q vLpyxM3FmxPs2jebIOdHpiIAjvpELgFj0R95EviWUeEkkAOGVkGUpq+YnVHfyn6g2PNMkd6MZ U0eV+FXq9LBbR46HMte2bFPeqNMmR+69ADnPgjhdYfiZhHm6B13LUtSQ6hAQT5A5WzUT++kcd VufmyDDSK1ZXt22lk1G9SMmAgnIbQUoxlYlJCrmIPbl4NTAAQ9FuLizc5myxozG81I5yL4uCj q91Acfsd9sHfhILU5IkU1JfhVBfoKm9SvMvD+2203EHmtQaqClCP8+Z+EUGTLQecBul5sQWqw 2UMkp3zieBJ1HJHNQtdLG9+BxyBRSaFMCoa7zlQmPMP0Lrr4W2IyMm3L7YWZNJuoSMTsBKHN6 tEG5gwssvg9Rs0aUwk76arSSxVBrew8oJphaTN1Zxm3EVhaVNjvPMmKTp/Nu1zNlEctVpfJqh ac5Nqgm52VqSBdm9u6FDYUPkkQuPQHij/m+w+yCqPAqJx4zgHP8UstKszxASg/xfhkgBYvgbp +xMFjP+Mv6we3CKbDZctwkRMYuOTQ== X-Rspamd-Queue-Id: 2588E73C18 X-Spamd-Result: default: False [1.49 / 200.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: mx00.schlund.de]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[181.180.193.92.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; IP_SCORE(0.14)[ipnet: 212.227.0.0/16(0.08), asn: 8560(0.64), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.38)[-0.376,0]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.11)[0.115,0]; NEURAL_HAM_LONG(-0.78)[-0.784,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[131.126.227.212.list.dnswl.org : 127.0.5.0]; MID_CONTAINS_FROM(1.00)[]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2018 19:18:41 -0000 On Tue, 13 Nov 2018 18:28:53 +0000, B J wrote: > On 11/13/18, Polytropon 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. I've been experiencing this kind of problem in the past, so allow me to share my experience and solution: First, boot your system into single-user mode ("boot -s" at the boot prompt). Then perform a fsck of all your file systems, especially /: # fsck / YOu can use the form "fsck -yf /" when you are familiar with the implications of the -y and -f flag; to achieve this, read "man fsck" carefully. If all file systems have been returned to a consistent state, mount them and proceed normal startup: # mount -a # exit Afterwards, check /etc/rc.conf, and make sure you have the following setting: background_fsck="NO" This entry is essential! It will force a successful fsck run at system startup. Background fsck has often shown to be a problem, as the system boots into a somewhat inconsistent state, and this can lead to all kinds of errors... > >> Any suggestions? Thanks. > > > > Others than replacing Firefox with a better browser? ;-) > > > > What you could do: Re-install Firefox (most recent version). > > Also make sure all of its dependencies are up to date. In > > worst case, it's "just" a memory leak. > > I re-installed it using pkg but that didn't do any good. Maybe it's not Firefox, but one of its dependencies... > > Check if the Firefox + system crashes happen when visiting > > "complicated pages" (i. e., those involving lots of JS, or > > those containing FLV, MP4 or WebM media content). > > For some reason, the last few versions I've been running on that > machine have had problems with YouTube videos. Most of the crashes > after my last system upgrade have occurred when I'm viewing one. This looks like a codec / dependency error. YouTube has made the transition to "HTML 5 video" and does no longer need "Flash". The codecs and general player functionality has to be in the web browser now. > This morning, I couldn't even start FF without it crashing my machine. > I'm thinking that some configuration file might be corrupted but I > haven't the foggiest as to where to look for it. This really looks like you should investigate for a possible file system problem as explained above. > Right now, I'm building FF from ports. Maybe that'll help. Make sure you also rebuild all ports it depends on. > As for > Opera, I've never really liked it and the version I installed using > pkg (Opera 12) is reaching the end of its service life. I can't even > view YouTube videos with it. Interestingly, Opera was the only browser where everything worked for me. Sure, it requires some time to configure it into a state where it becomes usable, but that is true for Firefox and Chrome, too. The out-of-the-box experience is just plain terrible. > As an aside, I've got almost the identical system installed on another > hard drive on my machine. I launched it with no problem. I also have > another machine set up the same way: 2 FreeBSD systems on separate > HDs. I tried FF with one of them and it launched without problem. > > This is a bit of a head-scratcher..... Again, from my experience: It _could_ be a defective GPU. As the GPU is involved in media decode operations, a faulty GPU can cause the system to hang or to surprisingly reboot. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...