From owner-freebsd-security@freebsd.org Thu Jun 21 07:19:02 2018 Return-Path: Delivered-To: freebsd-security@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 A3A781010C52 for ; Thu, 21 Jun 2018 07:19:02 +0000 (UTC) (envelope-from gordon@tetlows.org) Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C2438FB37 for ; Thu, 21 Jun 2018 07:19:02 +0000 (UTC) (envelope-from gordon@tetlows.org) Received: by mail-ua0-x22d.google.com with SMTP id c2-v6so1386599uae.4 for ; Thu, 21 Jun 2018 00:19:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tetlows.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xZMyo9VoU5T6ZEbHcRmjVjL7U90ERiF2otXtF0SJF2Y=; b=AZyBpRgj6xa1D7YH7Y1MPzkKNTwgsPximzdhvUw7mwvbJFI+uouucrhZAZgXy8hiBV tSr2KsULng5ohh5m6WQ5jJVyRN3TI2rjSGZ3j2GF5OQM3vyEJ/zGatDPHopWy8Bp1J2E toEGrd2PWlE6YeLL8+cVTI4FROLFI1rrxYje0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xZMyo9VoU5T6ZEbHcRmjVjL7U90ERiF2otXtF0SJF2Y=; b=ZkLttiDycEgIh9KxE91lXXgyjHWT0kJy9Cp1ZX0mCfkTSQ/2Qb8NwxDzX+SklTTIUI kg+9RidTrakc7otb4CB/GLHFSB8r1b7Os3sSHDzMl7FcjY9LsAmYAoNNmBAGasiF0Bmt RtAy5azQMo/U0wb7LLZCBmVzGwmUvEcNCxZrpmEu30aYexJ1DiYCLFsGU7SynLcPW4F2 aCRM2JoYlbPY+yri9/TTFfkKA6/cOQMDTFNfbLqKuuPDLYqZVPjmPtd1lkuBY5IWic48 SkLlW2cei2j4sP1bHAQIlIb1scQYOsaUzwzlwnF/1YOx40iuy7Z3m85YjG93kNgGxMDd 1/yg== X-Gm-Message-State: APt69E0fRwez4u049Z31xE3gyb7zFj2CzFlJAA5r6Iq4p+xeZCIEDfgU T8wsSo+KX+nw8r6ML9/SBUFfcu9z0Woq+hp4klJzZ4hby8z6 X-Google-Smtp-Source: ADUXVKIhjSlN8MAFO9LGKXstmLCGjRbg1cihyLjt2DdI3O0pKaLXxQrf4+KpJ1OK/3yizimLyHcwg9beufG94cvaLhg= X-Received: by 2002:ab0:1446:: with SMTP id c6-v6mr15474980uae.12.1529565541709; Thu, 21 Jun 2018 00:19:01 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ab0:4546:0:0:0:0:0 with HTTP; Thu, 21 Jun 2018 00:19:01 -0700 (PDT) In-Reply-To: References: From: Gordon Tetlow Date: Thu, 21 Jun 2018 00:19:01 -0700 Message-ID: Subject: Re: Recent security patch cause reboot loop on 11.1 RELEASE To: Denis Polygalov Cc: freebsd-security Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2018 07:19:03 -0000 On Wed, Jun 20, 2018 at 11:14 PM, Denis Polygalov wrote: > What I did is following: > > # uname -a > FreeBSD my_host_name 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #0: Tue > May 8 05:21:56 UTC 2018 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > # freebsd-update fetch > Looking up update.FreeBSD.org mirrors... 3 mirrors found. > Fetching metadata signature for 11.1-RELEASE from update6.freebsd.org... done. > Fetching metadata index... done. > Inspecting system... done. > Preparing to download files... done. > > The following files will be updated as part of updating to 11.1-RELEASE-p11: > /boot/kernel/kernel > > Installing this update cause endless reboot loop. > > # cat /boot/loader.conf > kern.maxfiles="32768" > zfs_load="YES" > linux_load="YES" > linprocfs_load="YES" > linsysfs_load="YES" > > # dmesg |grep CPU > CPU: Intel(R) Xeon(TM) CPU 3.40GHz (3400.19-MHz K8-class CPU) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > SMP: AP CPU #1 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > acpi_perf0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: CPU supports Enhanced Speedstep, but is not recognized. > est: CPU supports Enhanced Speedstep, but is not recognized. > > The machine is HP ProLiant ML350 Sorry to hear you are having a problem. Just to confirm, this is running on hardware and not on a Xen hypervisor, correct? Assuming it's running directly on the hardware, can you see if setting: hw.lazy_fpu_switch=1 in /boot/loader.conf makes any difference? Is there any panic message? Thanks, Gordon