From owner-freebsd-security@freebsd.org Wed Aug 8 15:57:50 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 4CB72105FFD6 for ; Wed, 8 Aug 2018 15:57:50 +0000 (UTC) (envelope-from pravkin.a@bks.tv) Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B384383213 for ; Wed, 8 Aug 2018 15:57:49 +0000 (UTC) (envelope-from pravkin.a@bks.tv) Received: by mail-lj1-x233.google.com with SMTP id w16-v6so2100986ljh.12 for ; Wed, 08 Aug 2018 08:57:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bks-tv.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=8S5VL4I/DoiohRz+AF9w18pkQaWMkGSZ6ja+TqDgypg=; b=hZ0Dl/pQvDE//oTooS3MMzqz1PiHt6T1ljtB1YRSdz1kso0Snr5UzW3nfk5SC6AV1T YOH+foqj5QB2VFb9c68QTicoS8SjWYRI9tmssJcZAEyfDy1RW1QNXdA8RdEBVGlIAdvy 0/wNuMTpbQnkLJa4viIXfUritNt0XVpHQfRnqBxLz62BIIYgr/8J9qLe9thXPqObCuBz ypT/YYKIcV5vJi/BBJWp0ghgIeRwSSZ/joisvAMRcnNuiwvLNFUlqRgv2gDsCg6EN5fN up0DwS0teWoZ1lqdpNngIyirkgBE3yHLlu6k2eduMJOhPmgO3au0LDLh8W0rhIYWv3F4 AY5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=8S5VL4I/DoiohRz+AF9w18pkQaWMkGSZ6ja+TqDgypg=; b=bcD5De0fMTngcWWyP05n18Sa6pNxwQ25EA586KfktnBK4n/HFjNo+3PMf/XZnd46Kk tLxJ25+9HMfzc594AHnmgHcMag64+Fq7odRb73d8DRYlVeU9/ZWrmbYbhD7domiIpP2T +ULVQsaDdzgI22ObH/1rmgn/1MU89hnR85IvQ9qPCE8qFq7+GqJx8PHvPW+A8noONUtE GA4JkWupVp6mTY3t+gFvxbbM0S1Vk1xfUijovCfcWlKtn/jf9wa/5HlzjKoWEkMeAItu u1l4e06FVFnQurJxcH7p85enKOYwI4iraqUgSWqSfesuOnTalrHsBAme2NaxJG72aFuY SqCQ== X-Gm-Message-State: AOUpUlG97pF76evPnChRAiPmzEonpSdJgLo6A0N7YHn+CBCWzI92uDK9 qLOqYV91dWmGRiNcztpqkCRzDDVMdd/fAg== X-Google-Smtp-Source: AA+uWPw9ONLCdh6la3kGLG5Q3loLiBRH/6pDwt6gQyo7xi9eBx3EE6nHRpEacUpu6eLKdYmz6xvf2w== X-Received: by 2002:a2e:97c8:: with SMTP id m8-v6mr1565105ljj.52.1533743867980; Wed, 08 Aug 2018 08:57:47 -0700 (PDT) Received: from fduch.bks-tv.ru ([31.132.174.227]) by smtp.gmail.com with ESMTPSA id a16-v6sm726872ljj.28.2018.08.08.08.57.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Aug 2018 08:57:47 -0700 (PDT) Date: Wed, 8 Aug 2018 18:57:37 +0300 From: "Alexander M. Pravkin" To: Denis Polygalov Cc: freebsd-security Subject: Re: Recent security patch cause reboot loop on 11.1 RELEASE Message-ID: <20180808155735.GA64503@fduch.bks-tv.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Aug 2018 15:57:50 -0000 On Thu, Jun 21, 2018 at 09:13:54PM +0900, Denis Polygalov wrote: > Seems like I did not cc my reply to the mailing list. > Doing it now because I found a hint which may > lead to the cause of the reboot loop. > > Removing: > > linux_load="YES" > linprocfs_load="YES" > linsysfs_load="YES" > > prevent the reboot loop in multi-user mode but > leave me without Linux emulation... Same thing when upgrading two amd64 machines from 11.1-p9, 11.1-p10 to 11.2-p1. Panic occurs when boot process is almost complete (most of rc.d scripts started) and looks like this: fault virtual address = 0x134 fault code = supervisor read data, page not present current process = 800 (kldload) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: ... #8 0x................ at VBoxDrvFreeBSDModuleEvent+0x117 ... And yes, virtualbox-ose-kmod was installed and enabled on both machines. Disabled it, completed freebsd-update install, and reinstalled kmod package: everything is OK now. Conclusion: don't forget that 3rd-party kernel modules can break things during/after upgrade. > Regards, > Denis. > > > Hi Gordon, > > > > this is real hardware. I found the reason (see below). > > Setting hw.lazy_fpu_switch=1 in /boot/loader.conf makes no difference. > > No panic messages. > > I can tell you when it happen. Here is the boot messages: > > ... skipped ... > > Timecounters tick every 1.000 msec > > nvme cam probe device init > > ugen2.1: at usbus2 > > ugen1.1: at usbus1 > > ugen0.1: at usbus0 > > uhub0: on usbus2 > > uhub1: on usbus0 > > uhub2: on usbus1 > > uhub1: 2 ports with 2 removable, self powered > > uhub2: 2 ports with 2 removable, self powered > > uhub0: 4 ports with 4 removable, self powered > > > > <---- here screen (local monitor) goes black and machine restarted. > > > > ada0 at ata2 bus 0 scbus8 target 0 lun 0 > > ada0: ATA8-ACS SATA 3.x device > > ada0: Serial Number WD-WMC1P0D1KEHJ > > ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes) > > ada0: 1907729MB (3907029168 512 byte sectors) > > da0 at ciss0 bus 0 scbus0 target 0 lun 0 > > da0: Fixed Direct Access SCSI device > > da0: 135.168MB/s transfers > > da0: Command Queueing enabled > > da0: 858293MB (1757784604 512 byte sectors) > > Trying to mount root from ufs:/dev/da0s1a [rw]... > > > > I noticed that I can boot the *patched* kernel in single user mode. > > Removing these 3 lines from the /boot/loader.conf fixed rebooting loop problem: > > > > linux_load="YES" > > linprocfs_load="YES" > > linsysfs_load="YES" > > > > This machine is used as a test bench to test stuff > > before deploying on a production server. > > We need Linux emulation support on the production > > server to run closed source software... > > So... maybe this will help someone. > > > > Blaming evil penguins, > > Denis > > > > On 21/06/2018 4:19 PM, Gordon Tetlow wrote: > > 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 > > > _______________________________________________ > freebsd-security@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" -- С уважением, Правкин Александр ООО "Брянск Связь-ТВ" +7 (4832) 595-000 доб. 458 JID: pravkin.a@bks.tv