Re: [Intel-gfx] 3.19-rc1 errors when opening LID

2014-12-27 Thread Joe Perches
On Sat, 2014-12-27 at 21:22 +0100, Rafael J. Wysocki wrote: [] > +++ linux-pm/include/acpi/acpi_bus.h > @@ -589,7 +589,8 @@ static inline u32 acpi_target_system_sta > > static inline bool acpi_device_power_manageable(struct acpi_device *adev) > { > - return adev->flags.power_manageable; > +

Re: [Intel-gfx] 3.19-rc1 errors when opening LID

2014-12-27 Thread Rafael J. Wysocki
On Saturday, December 27, 2014 09:19:49 AM Pali Rohár wrote: > Hello, > > in attachment is output of ls -l /sys/bus/acpi/devices from both > 3.13 and 3.19 kernels. > > Anyway Gabriele Mazzotta wrote me that new acpi devices could be > created after commit faae404ebdc6bba (ACPICA: Add "Windows

Re: [Intel-gfx] 3.19-rc1 errors when opening LID

2014-12-27 Thread nick
Pali, This seems to be a likely culprit. Would you mind building a kernel before that commit was merged in order to test if it works. Regards Nick On 2014-12-27 03:19 AM, Pali Rohár wrote: > Hello, > > in attachment is output of ls -l /sys/bus/acpi/devices from both > 3.13 and 3.19 kernels. >

Re: [Intel-gfx] [PATCH] drm/i915: Ban Haswell from using RCS flips

2014-12-27 Thread shuang . he
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang...@intel.com) -Summary- Platform Delta drm-intel-nightly Series Applied PNV 363/364

[Intel-gfx] [PATCH] drm/i915: Ban Haswell from using RCS flips

2014-12-27 Thread Chris Wilson
Like Ivybridge, we have reports that we get random hangs when flipping with multiple pipes. Extend commit 2a92d5bca1999b69c78f3c3e97b5484985b094b9 Author: Chris Wilson Date: Tue Jul 8 10:40:29 2014 +0100 drm/i915: Disable RCS flips on Ivybridge to also apply to Haswell. Reported-by: Scot

Re: [Intel-gfx] 3.19-rc1 errors when opening LID

2014-12-27 Thread Pali Rohár
Hello, in attachment is output of ls -l /sys/bus/acpi/devices from both 3.13 and 3.19 kernels. Anyway Gabriele Mazzotta wrote me that new acpi devices could be created after commit faae404ebdc6bba (ACPICA: Add "Windows 2013" string to _OSI support). Maybe this another output could help you: