From owner-freebsd-security@freebsd.org Thu Jun 21 12:30:45 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 99294101D787 for ; Thu, 21 Jun 2018 12:30:45 +0000 (UTC) (envelope-from johannes@perceivon.net) Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::22c]) (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 38FDD7AB12 for ; Thu, 21 Jun 2018 12:30:45 +0000 (UTC) (envelope-from johannes@perceivon.net) Received: by mail-ua0-x22c.google.com with SMTP id f30-v6so1893281uab.11 for ; Thu, 21 Jun 2018 05:30:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=perceivon-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XQgE6gWvEbQqFyNxRl3yHqGMgn4d9bNcoQQxUQUM0zk=; b=Oaonws+MCPI8E4dkcDRNgb7I7BUk6pb2oIdNe7dFVcndxT6FhMD+nUegm/IARmR2td hjMnGOoSuSICZLejszLvf3BNkU2i2RfmLn2XPgLmj1bzjr0ALyvShD0WYqWB4QM+2G6e OEEiuMr13qRSIFNYgHE1mfjQQwhWLWV6CGvQ3nc/uHXUS/3Cb9CMHGs/qieZrVne2+5w FFl8e5Da9f9/Xlu69eMa7lpZzz1w11mBYDj09SBBVezaJV7llgG7bQ9GrD1UwagGU3hH uA6cyhWdC5Q2GTiQW9PDtTm/9UEzdHKCMiTJLy42LaAzUeFJelWKs/ugWHVX9OOKAS27 dYGw== 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=XQgE6gWvEbQqFyNxRl3yHqGMgn4d9bNcoQQxUQUM0zk=; b=mLjscI1QyyVaMG1fC+vgg4+LOqdHvtclxkd4bZ5tcF9wtCoHU9JSF2WVZBnEwu4/5/ aVK1UVFnh6PVzX0vbzXB2yQ5rlHoYqrCZpDpQ0g0vOoT6PHTBkBqGGruUIswHrjip58o TD/iTwtAV2YCQ9IEg2D7qbzz4hkhrQGIg5skc6MQWuIemKGRpO9S7LeDKzUvxH1PIurG gslQdgKY+jDIJkwRNoXYhdvEOlhcI9HCO2DFTQS8z7xm2tU7+IjZwpGBik09z+2WAeAT aaohppYmT9Wu4M4nW4GlAxgrVys1Y+3v49SUXs8LqtcdbO+6XS67GkT7ttBSL5IDGqE6 CTgg== X-Gm-Message-State: APt69E04+dpa/7nYcRwWtAsDMg62NA0JgLHvBDsWgIk49thLcTT2E0Re vUX8NZpeFtHtnS2n/0ZPULwuayI9VB7s+5qE0eHeQA== X-Google-Smtp-Source: ADUXVKISAPV+RQmZwu7FtE5wtfMvNvnQp8u6h5ZNzqClAT5ZErfC+Z7dfIlnAJKPLp/EAsf9Iuv3ppzxQt+eufDl420= X-Received: by 2002:ab0:19c2:: with SMTP id r2-v6mr16181358uai.110.1529584244457; Thu, 21 Jun 2018 05:30:44 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Meixner Date: Thu, 21 Jun 2018 15:30:32 +0300 Message-ID: Subject: Re: Recent security patch cause reboot loop on 11.1 RELEASE To: Denis Polygalov Cc: freebsd-security X-Mailman-Approved-At: Thu, 21 Jun 2018 13:58:33 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 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 12:30:45 -0000 If you put those modules into rc.conf's kld_list, will it reboot as well? According to the manpage, rc.conf is the faster way to load modules not essential to booting. On Thu, 21 Jun 2018, 3:15 pm 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... > > 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 > " >