Date: Mon, 27 Feb 2017 19:27:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-acpi@FreeBSD.org Subject: [Bug 217247] [acpi] r265474 makes 11.0R unusable with Atom 330 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217247-13733-vjBneN2MHR>