From owner-freebsd-current@freebsd.org Thu Sep 26 17:21:06 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 491ED12DF85 for ; Thu, 26 Sep 2019 17:21:06 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f65.google.com (mail-ot1-f65.google.com [209.85.210.65]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46fMCN4csTz4Z5B for ; Thu, 26 Sep 2019 17:21:04 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f65.google.com with SMTP id s22so2695641otr.6 for ; Thu, 26 Sep 2019 10:21:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=joFteJayOR3od67n3zxph0QtQwI+/erS4eOMFxRaTlg=; b=b9wMyVoUOVnYSBlYWWBXcbcwOkunFpwvqffZiG4flEhz/5H1szcdtXpXcx51pYkCry V2xkvKs2rSTbdfgMMhQhXG3NX3FqzMrGrNuSvrtZNTgsTX6IlMKoiJN7FEZQcZL1f1UX aYtQaCJZx8cmpDO3yomFo+wRBvbqBZL5ROtOB53gPxq+bjoK7Jf/Qprv0oM5e9CKTZfw JFl6ZcCuC9i9QQUbBfu0WaJ9oleLpy4HpHUx+T7zy3/ebUez7tGT8iSkommWOzFaVTq7 kgR2aAQAgfOsSWm7v8BL4QEu1HEmY+Esfkb8EHWiBsfLYdIlE+WpzUA94orbLwtHDpV3 nNGw== X-Gm-Message-State: APjAAAX/BcCGCgKYggEeNdrsqdROuRORP8hhjsQbQSW+XKl56ipAlISg H/rkOf2TgEgINWPnwbHggShW/dxRlP1qp4uwxkQ= X-Google-Smtp-Source: APXvYqye0G09xTV9Vap3Mi1Auvvu/bhk+zKzWYz3YFnNG1+/S/d8EYOHsMNbf7kv3jBXyxLMnED+fRR20UHCtXwP0fg= X-Received: by 2002:a9d:378a:: with SMTP id x10mr3583628otb.222.1569518463209; Thu, 26 Sep 2019 10:21:03 -0700 (PDT) MIME-Version: 1.0 References: <20190926170241.GG44691@kib.kiev.ua> In-Reply-To: <20190926170241.GG44691@kib.kiev.ua> From: Alan Somers Date: Thu, 26 Sep 2019 11:20:51 -0600 Message-ID: Subject: Re: panic: Unregistered use of FPU in kernel To: Konstantin Belousov Cc: FreeBSD CURRENT X-Rspamd-Queue-Id: 46fMCN4csTz4Z5B X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.210.65 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-3.10 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[65.210.85.209.rep.mailspike.net : 127.0.0.18]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[65.210.85.209.list.dnswl.org : 127.0.5.0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-1.10)[ipnet: 209.85.128.0/17(-3.29), asn: 15169(-2.18), country: US(-0.05)]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Sep 2019 17:21:06 -0000 On Thu, Sep 26, 2019 at 11:02 AM Konstantin Belousov wrote: > On Thu, Sep 26, 2019 at 09:45:43AM -0600, Alan Somers wrote: > > The latest VM snapshot > (FreeBSD-13.0-CURRENT-amd64-20190920-r352544.qcow2) > > instapanics on boot: > > > > panic: Unregistered use of FPU in kernel > > > > stack trace: > > ... > > sse42_crc32c > > readsuper > > ffs_sbget > > g_label_ufs_taste_common > > g_label_taste > > g_new_provider_event > > g_run_events > > fork_exit > > ... > > > > Has anybody touched this area recently? I'll try to narrow down the > commit > > range. > > Start with disassembling the faulting instruction. I suspect that somehow > vital compiler switches like -mno-sse got omitted in the build. > No problem with compiler switches here. The C file uses inline assembly to generate a crc32q instruction, in crc32_sse42.c:257. But why would that generate a floating point exception? The instruction doesn't appear to be using any floating point registers. This is on a Kaby Lake CPU. crc32q %rsi, %rbx