to add a acpi=force for your case.
It's actually set to force_ht, so it sounds like some blacklisting is
now stricter than it used to be. However, given that acpi=force seems to
work, how about just doing the following?
commit a8d9241dad684f7dda46889f00c9e627773e868e
Author: Matthew Garrett m
to
avoid other bugs - and we're failing to fix those bugs as a result.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
that we should be doing this on all hardware,
perhaps with a kernel option to disable it for embedded devices that
really need that 64K. The low-memory corruption issue seems to be very
widespread.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line unsubscribe
The polling interval (in deciseconds) was accidently interpreted as
being in milliseconds in one codepath, resulting in excessively frequent
polling. Ensure that the conversion is performed.
Signed-off-by: Matthew Garrett m...@redhat.com
---
diff --git a/drivers/acpi/thermal.c b/drivers/acpi
);
+tz-polling_frequency*100);
if (IS_ERR(tz-thermal_zone))
return -ENODEV;
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message
rather than the Intel one. That bug's been
fixed, so now you're following the Intel codepath - unfortunately
there's no way to do that without kernel-level graphics support, which
means DRM.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line unsubscribe kernel
” (there was a thread on dri-devel about that).
It seems fixed with a patch from Matthew Garrett applied to
drm-intel/for-airlied but I don't think this has been applied to Linus
master.
Any pointers to the patch, please?
Doesn't ring any bells for me...
--
Matthew Garrett | [EMAIL PROTECTED
On Mon, Dec 08, 2008 at 05:19:49PM +0100, Yves-Alexis Perez wrote:
Doesn't ring any bells for me...
This was the “irq spinning” thread on dri-devel.
Looks like the patch was from Keith, not me?
Unrelatedly, I didn't get the Cc:ed copy of this mail. Did you get a
bounce?
--
Matthew Garrett
