RE: [GIT PATCH] ACPI for 2.6.14

[Brown, Len]

>There are a few bugs which I'd identified as arising from the acpi tree
>while it was in -mm.  Is this patch likely to drag them into mainline?
>
>They include:
>
>
>http://bugzilla.kernel.org/show_bug.cgi?id=4977
>            Summary: ACPI 20050708 fails on HP RX2600 platform

This was filed against ACPICA 20050708
which had a known problem with module-level code.
The ACPI patch now contains ACPICA 20050902 which
fixes that issue, and this system needs to be
re-tested with the latest patch.

>http://bugzilla.kernel.org/show_bug.cgi?id=4867
>            Summary: bug in ACPI crashes machine when reading
>                     /proc/acpi/thermal_zone/THRM/temperature

UNREPRODUCIBLE.
test system died and is no longer available.

>http://bugzilla.kernel.org/show_bug.cgi?id=4980
>            Summary: krash on entering mem sleep

The submitter confirmed that suspend to memory now works on this box.

The remaining issue on this box is related to the EC and battery,
and we're getting contradictory feedback on it.
Frankly, I think we need broader testing, and
pushing the latest ec code into 2.6.14 now is the best
way to get that.  If it turns out to be a mistake
we can always turn back time and revert
drivers/acpi/ec.c to the one that shipped in 2.6.12 --
but the one in the latest patch has proven to be
superior to 2.6.13 on other systems.

>Plus we have all the battery monitor woes, but they're in 
>2.6.13 already.

Re: 2.6.13 regressions vs 2.6.12, I'm aware of these:

  http://bugzilla.kernel.org/show_bug.cgi?id=5165
  smp c-states on Pentium 4 with hyperthreading causes big slow-down

  http://bugzilla.kernel.org/show_bug.cgi?id=5171
  2.6.13 SMP kernel crash on boot at pm_idle_save()

I saw lots of transient battery issues from 2.6.13-rc3
until 2.6.13-rc6, but the ones I followed went away
as of 2.6.13 final.  Do you have your eye on others
besides 4980?

thanks,
-Len
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/