From owner-freebsd-bugs@FreeBSD.ORG Sat Aug 31 14:10:01 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E0D72A4C for ; Sat, 31 Aug 2013 14:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CCD2023E3 for ; Sat, 31 Aug 2013 14:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r7VEA1lJ043791 for ; Sat, 31 Aug 2013 14:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7VEA1n2043790; Sat, 31 Aug 2013 14:10:01 GMT (envelope-from gnats) Date: Sat, 31 Aug 2013 14:10:01 GMT Message-Id: <201308311410.r7VEA1n2043790@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Andriy Gapon Subject: Re: kern/181632: 9.2-RC3 - on resume from suspend, disk operations are slower X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Andriy Gapon List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Aug 2013 14:10:01 -0000 The following reply was made to PR kern/181632; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@FreeBSD.org, mvharding@gmail.com Cc: Subject: Re: kern/181632: 9.2-RC3 - on resume from suspend, disk operations are slower Date: Sat, 31 Aug 2013 17:03:17 +0300 Hmm... I am very very surprised that that commit could have such consequences. Are you sure that it is it? As to the debugging I really don't know what to look for. Could you please describe your CPU? Perhaps use procstat -kk -a | fgrep -i acpi to check if there are any threads stuck somewhere in acpi after a resume. Maybe also compare output of sysctl hw.acpi and dev.cpu before and after a resume, with and without r244616. -- Andriy Gapon