From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261794AbVGUPeX (ORCPT ); Thu, 21 Jul 2005 11:34:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261805AbVGUPb7 (ORCPT ); Thu, 21 Jul 2005 11:31:59 -0400 Received: from upco.es ([130.206.70.227]:15273 "EHLO mail1.upco.es") by vger.kernel.org with ESMTP id S261775AbVGUPaM (ORCPT ); Thu, 21 Jul 2005 11:30:12 -0400 Date: Thu, 21 Jul 2005 17:30:18 +0200 From: Romano Giannetti To: Linux Kernel Mailing List Cc: acpi-devel@lists.sourceforge.net Subject: try acpi -V & acpi -V & acpi -V (was Linux v2.6.13-rc3) Message-ID: <20050721153018.GA31835@pern.dea.icai.upco.es> Mail-Followup-To: Romano Giannetti , Linux Kernel Mailing List , acpi-devel@lists.sourceforge.net References: <200507211209.46039.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <200507211209.46039.rjw@sisk.pl> User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hmmm... switched today on my Vaio laptop to 2.6.13-rc3. Known (see http://bugme.osdl.org/show_bug.cgi?id=4124) is still here. A fact that could help, or not, chasing it down: when there are problems with acpi events, it happens the following too: # acpi -V & acpi -V & acpi -V [2] 23884 [3] 23885 Battery 1: charged, 0% Thermal 1: ok, 73.0 degrees C AC Adapter 1: on-line [2] - 23884 done acpi -V rukbat:~/tmp% Battery 1: charged, 0% Thermal 1: ok, 73.0 degrees C AC Adapter 1: on-line [3] + 23885 done acpi -V Battery 1: charging, 93%, 06:22:58 until charged Thermal 1: ok, 73.0 degrees C AC Adapter 1: on-line It happens just sometime, bust repeating acpi -V & acpi -V in fast succession it gives a 0% reading in few tries. Kernel is vanilla, no patch applied. HTH, Romano -- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569