Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 06 Mar 2007 10:06:14 -0800
From:      Nate Lawson <nate@root.org>
To:        Ruslan Ermilov <ru@FreeBSD.org>
Cc:        cvs-src@FreeBSD.org, Nate Lawson <njl@FreeBSD.org>, src-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/dev/acpica acpi_ec.c
Message-ID:  <45EDAD96.9060202@root.org>
In-Reply-To: <20070306165458.GA24644@rambler-co.ru>
References:  <200702270014.l1R0EKrp034231@repoman.freebsd.org> <20070306165458.GA24644@rambler-co.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Ruslan Ermilov wrote:
> Hi Nate,
> 
> On Tue, Feb 27, 2007 at 12:14:20AM +0000, Nate Lawson wrote:
>> njl         2007-02-27 00:14:20 UTC
>>
>>   FreeBSD src repository
>>
>>   Modified files:
>>     sys/dev/acpica       acpi_ec.c 
>>   Log:
>>   Rework EC I/O approach.  Implement burst mode, including proper handling of
>>   case where it asynchronously exits burst mode on its own.  Handle different
>>   values of hz in sleep loop.  Provide more debugging options to tune EC
>>   behavior.  These tunables/sysctls may be temporary and are not for user
>>   access if the EC is working properly.  Burst mode is now on by default for
>>   testing and the poll interval has been increased from 100 to 500 us and
>>   total timeout from 100 to 500 ms.
>>   
>>   Hopefully this should be the first step of addressing reports of timeout
>>   errors during battery or thermal access, especially on HP/Compaq laptops.
>>   It is reasonably stable and should not cause a loss of functionality or
>>   performance on systems that were previously working.  Testing shows an
>>   increase of responsiveness by ~75% on one system.
>>   
>>   PR:             kern/98171
>>   
>>   Revision  Changes    Path
>>   1.69      +206 -109  src/sys/dev/acpica/acpi_ec.c
> 
> I'm having a problem with this commit.  My ThinkPad 600X
> panics on boot with this change.  If I back it out, all
> gets back to normal.  What information do you need except
> from a verbose boot log to track it down?  (I can grab a
> text from serial console, etc.)

panic message and location, for starters.


-- 
Nate



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45EDAD96.9060202>