From owner-freebsd-acpi@FreeBSD.ORG Tue May 5 23:53:00 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E09651065676; Tue, 5 May 2009 23:53:00 +0000 (UTC) (envelope-from amesbury@umn.edu) Received: from mta-m3.tc.umn.edu (mta-m3.tc.umn.edu [134.84.135.123]) by mx1.freebsd.org (Postfix) with ESMTP id 97A5D8FC23; Tue, 5 May 2009 23:53:00 +0000 (UTC) (envelope-from amesbury@umn.edu) Received: from [160.94.247.212] (optimator.oitsec.umn.edu [160.94.247.212]) by mta-m3.tc.umn.edu (UMN smtpd) with ESMTP Tue, 5 May 2009 18:37:59 -0500 (CDT) X-Umn-Remote-Mta: [N] optimator.oitsec.umn.edu [160.94.247.212] #+LO+TS+AU+HN X-Umn-Classification: local Message-ID: <4A00CDD6.4080303@umn.edu> Date: Tue, 05 May 2009 18:37:58 -0500 From: Alan Amesbury User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: Jung-uk Kim References: <49F8B859.7060908@umn.edu> <4A006E9A.7060806@icyb.net.ua> <200905051609.38689.jkim@FreeBSD.org> <200905051743.03520.jkim@FreeBSD.org> In-Reply-To: <200905051743.03520.jkim@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Garbled output from kgdb? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 23:53:01 -0000 Jung-uk Kim wrote: > The attached patch is for -STABLE. Note that it is only compile > tested on amd64. The platform in question is 7.1-RELEASE-p5/amd64, and the patch you supplied looks like it applies cleanly to it. While I am unable to pin down the specific trigger of this flaw (the host simply panicked a couple times while under moderate-to-heavy use), I'm willing to apply the patch to the host's current source tree, provided you and John Baldwin are in agreement that it's safe to do so. Note that's not meant to imply I don't trust your coding skills; I'm just not ready to modify production assets without a second look. ;-) Thanks again for your help on this. I appreciate it! -- Alan Amesbury OIT Security and Assurance University of Minnesota