From owner-freebsd-acpi@FreeBSD.ORG Wed Jun 25 15:22:21 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7D07DCE1 for ; Wed, 25 Jun 2014 15:22:21 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5722523E0 for ; Wed, 25 Jun 2014 15:22:21 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 49B01B9D0; Wed, 25 Jun 2014 11:22:20 -0400 (EDT) From: John Baldwin To: Eric McCorkle Subject: Re: ACPI error messages on Lenovo W540 Date: Wed, 25 Jun 2014 11:16:04 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <53A048B1.1080108@metricspace.net> <201406241000.35812.jhb@freebsd.org> <53AA1D05.6000304@metricspace.net> In-Reply-To: <53AA1D05.6000304@metricspace.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201406251116.04832.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 25 Jun 2014 11:22:20 -0400 (EDT) Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2014 15:22:21 -0000 On Tuesday, June 24, 2014 8:51:17 pm Eric McCorkle wrote: > On 06/24/2014 10:00, John Baldwin wrote: > > Ah, the nvidia driver calls _DSM and it has the bug. In its nvidia_acpi.c file > > it uses a Buffer instead of a Package for the fourth argument to _DSM. OTOH, the > > warning doesn't prevent the method from running, so the warning may be harmless. > > You can try contacting the nvidia folks to tell them about the warning and point > > out the bug in their _DSM wrapper in nvidia_acpi.c to see what they say. > > Will do. Is there a preferred point of contact? Just use the bug report details that come with the driver. They include an e-mail address you can use to send bug reports. -- John Baldwin