Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Mar 2007 19:54:58 +0300
From:      Ruslan Ermilov <ru@FreeBSD.org>
To:        Nate Lawson <njl@FreeBSD.org>
Cc:        cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/dev/acpica acpi_ec.c
Message-ID:  <20070306165458.GA24644@rambler-co.ru>
In-Reply-To: <200702270014.l1R0EKrp034231@repoman.freebsd.org>
References:  <200702270014.l1R0EKrp034231@repoman.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--zYM0uCDKw75PZbzx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Nate,

On Tue, Feb 27, 2007 at 12:14:20AM +0000, Nate Lawson wrote:
> njl         2007-02-27 00:14:20 UTC
>=20
>   FreeBSD src repository
>=20
>   Modified files:
>     sys/dev/acpica       acpi_ec.c=20
>   Log:
>   Rework EC I/O approach.  Implement burst mode, including proper handlin=
g of
>   case where it asynchronously exits burst mode on its own.  Handle diffe=
rent
>   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.
>  =20
>   Hopefully this should be the first step of addressing reports of timeout
>   errors during battery or thermal access, especially on HP/Compaq laptop=
s.
>   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.
>  =20
>   PR:             kern/98171
>  =20
>   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
=66rom a verbose boot log to track it down?  (I can grab a
text from serial console, etc.)


Cheers,
--=20
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer

--zYM0uCDKw75PZbzx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (FreeBSD)

iD8DBQFF7ZziqRfpzJluFF4RAgd1AKCIq8g3UNOfJ4/K1fJIh6X0Et+1TQCfXA7Q
R/s92XUuddfViSAgPa5Vauo=
=HNAb
-----END PGP SIGNATURE-----

--zYM0uCDKw75PZbzx--



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