From owner-freebsd-acpi@freebsd.org  Mon Feb 27 19:27:12 2017
Return-Path: <owner-freebsd-acpi@freebsd.org>
Delivered-To: freebsd-acpi@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 675A0CF025E
 for <freebsd-acpi@mailman.ysv.freebsd.org>;
 Mon, 27 Feb 2017 19:27:12 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4BB8EE6A
 for <freebsd-acpi@FreeBSD.org>; Mon, 27 Feb 2017 19:27:12 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1RJRBqR077183
 for <freebsd-acpi@FreeBSD.org>; Mon, 27 Feb 2017 19:27:12 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-acpi@FreeBSD.org
Subject: [Bug 217247] [acpi] r265474 makes 11.0R unusable with Atom 330
Date: Mon, 27 Feb 2017 19:27:12 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-RELEASE
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: stephane_freebsd@lesimple.fr
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-acpi@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217247-13733-vjBneN2MHR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217247-13733@https.bugs.freebsd.org/bugzilla/>
References: <bug-217247-13733@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi/>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 19:27:12 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217247

--- Comment #5 from St=C3=A9phane Lesimple <stephane_freebsd@lesimple.fr> -=
--
(In reply to Konstantin Belousov from comment #3)

You're right, the early stage of the boot is the same between 10.3 and 11.0.
The massive slowdown starts somewhat late in the boot process. What I called
"boot process" here is timed from the "Booting..." message (right after the
kernel is loaded) up to the moment where ttyv0 shows the "login:" prompt. T=
hose
two moments are easier to measure with a stopwatch. So this probably includ=
es
the start time of most (limited) userland stuff from the bare release memst=
ick
image, run with the "livecd" option.

Does that sounds more reasonable? In any case, I can for sure provide dmesgs
and kern.{eventtimer,timecounter} for 10.3 and 11.0.

--=20
You are receiving this mail because:
You are the assignee for the bug.=