Date: Tue, 30 Dec 2003 11:34:17 -0600 From: Peter Schultz <pmes@bis.midco.net> To: Scott Long <scottl@freebsd.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi_cpu.c Message-ID: <3FF1B719.1010609@bis.midco.net> In-Reply-To: <3FEF5981.8040103@freebsd.org> References: <200312282215.hBSMFPYS067707@repoman.freebsd.org> <3FEF5981.8040103@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote: > Nate Lawson wrote: > >>njl 2003/12/28 14:15:24 PST >> >> FreeBSD src repository >> >> Modified files: >> sys/dev/acpica acpi_cpu.c >> Log: >> Don't attach throttling if the P_BLK is 0, even if the P_BLK_LEN is 6. >> This is more strict but no known systems have this problem. >> >> Revision Changes Path >> 1.29 +1 -1 src/sys/dev/acpica/acpi_cpu.c >> > > > This reminds me.... > > My Dell 8200 laptop used to work reasonably well with ACPI, the only > problem being that the ASL was doing the pass-by-reference/pass-by-value > mixup that resulted in a lot of 'cannot allcoate 0 byte' problems. With > a patch that worked around this, most acpi functions seemed to work. > With the latest ACPI, the patch that I had seems to have been > integrated, but now there are new problems. The battery reporting seems > to no longer work, and I get a lot of the following > messages on the console: > > -0166: *** Error: UtAllocate: Attempt to allocate zero bytes > > What information do you need to track this down? > One needs the ASL file, at least that's what jhb needed to solve my problem. One must know about BIOSes, should study the ACPI docs and be able to speak hex in order to hack ASL. `dumpacpi' and `iasl' are helpful to get started. Minimally, you can try changing any check for "*Windows*" to "FreeBSD". That's what I've done to get ACPI working back to how it was in the past. It's still not perfect but I'm becoming conviced it's buggy DSDT that leads to most ACPI related issues. I get three errors compiling my OEM ASL, so I wonder how many errors others are getting. Is there any way for the OS to deal with this? Pete...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FF1B719.1010609>