From owner-freebsd-bugs@freebsd.org Wed Jul 5 14:48:51 2017 Return-Path: Delivered-To: freebsd-bugs@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 22021DACA98 for ; Wed, 5 Jul 2017 14:48:51 +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 105A1830E4 for ; Wed, 5 Jul 2017 14:48:51 +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 v65EmoaD052742 for ; Wed, 5 Jul 2017 14:48:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220277] 11.1-BETA3 hangs on Dell Vostro V130 during boot Date: Wed, 05 Jul 2017 14:48:51 +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-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2017 14:48:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220277 --- Comment #17 from John Baldwin --- (In reply to Mark Johnston from comment #16) We could defer handling ACPI tasks until timers are working. That is proba= bly the simplest / shortest solution. More complicated would be to fix pause()= to always use sched_yield + spinning for all threads (not just thread0 as I suggested in my previous comment). The first approach can be tried by chan= ging the SYSINIT for acpi_taskq_init in sys/dev/acpica/Osd/OsdSchedule.c: Index: sys/dev/acpica/Osd/OsdSchedule.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/dev/acpica/Osd/OsdSchedule.c (revision 320674) +++ sys/dev/acpica/Osd/OsdSchedule.c (working copy) @@ -128,7 +128,8 @@ acpi_taskq_started =3D 1; } -SYSINIT(acpi_taskq, SI_SUB_CONFIGURE, SI_ORDER_SECOND, acpi_taskq_init, NU= LL); +SYSINIT(acpi_taskq, SI_SUB_KICK_SCHEDULER, SI_ORDER_SECOND, acpi_taskq_ini= t, + NULL); /* * Bounce through this wrapper function since ACPI-CA doesn't understand --=20 You are receiving this mail because: You are the assignee for the bug.=