[PATCH] Please test: new ACPI release (20041105) import
Nate Lawson
nate at root.org
Wed Nov 17 12:14:37 PST 2004
Søren Schmidt wrote:
> There are nasties in the bat stuff, I have to comment out various parts
> of it to get the ASUS to boot at all :(
>
> <soapbox>
> This brings up the question: do we have a maintainer for ACPI and why
> arent these issues being dealt with ? I for one have reported these
> issue for ages including as much debug as is possible, but it seems to
> be silently ignored (and yes 5.3-RELEASE is just as broken)...
> </soapbox>
cvs logs will show who is active in each area of acpi. I'm sure that's
a rhetorical question though.
As for your particular problems, the battery issue may be related to
your system not operating according to the locking model. I fixed one
thermal problem for brooks@ where his ASL generated notifies every time
we read the temperature and the notify handler read the temperature. It
may be something similar. Send me the ASL and I'll take a look. The
suspend/resume issue has not been isolated but you can start by checking
where it gets with a serial console attached (if it gets that far) or by
putting some beep code in the resume handler to see if it even gets
called (Warner has the patch in his tree, it may make sense to commit it
under some option to help with debugging.)
I'd love it if more people would help with debugging. I'm sure you can
relate to maintaining a subsystem where behavior is widely divergent
even among the same model device, OEM bugs are rampant and undocumented,
and you don't have access to a system that can repeat the behavior that
the submitter is reporting.
As donations@ shows, I'm willing to accept problem laptops on loan or
for donation. Currently, I own an IBM R32, T23, Sony PCG-F390, and Abit
SMP. All work correctly including suspend/resume to RAM for the laptops.
-Nate
More information about the freebsd-acpi
mailing list