On Friday 26 December 2014 16:12:49 Rafael J. Wysocki wrote: > On Wednesday, December 24, 2014 07:51:48 PM Pali Rohár wrote: > > --nextPart5943893.pKyMBm5Emp > > Content-Type: Text/Plain; > > > > charset="utf-8" > > > > Content-Transfer-Encoding: quoted-printable > > > > Hello! > > > > With new 3.19-rc1 kernel every time when I open LID on my > > laptop, kernel pr= > > > ints these error lines to dmesg: > Does your syste suspend when the lid is closed and resume when > it is open? > No, I disabled all autosuspend and autohibernate settings. When I close LID system is running. > > > [25568.448566] acpi MSFT1111:00: Cannot transition to power > > state D3cold fo= r parent in (unknown) > > [25568.448572] acpi INT33C2:00: Cannot transition to non-D0 > > state from D3 [25568.448577] acpi MSFT0002:00: Cannot > > transition to power state D3cold fo= r parent in (unknown) > > [25568.448581] acpi ELAN1010:00: Cannot transition to power > > state D3cold fo= r parent in (unknown) > > [25568.448587] acpi INT33C3:00: Cannot transition to non-D0 > > state from D3 [25568.448590] acpi INT33C0:00: Cannot > > transition to non-D0 state from D3 [25568.448594] acpi > > INT33C1:00: Cannot transition to non-D0 state from D3 > > [25568.448598] acpi INT33C4:00: Cannot transition to non-D0 > > state from D3 [25568.448602] acpi INT33C5:00: Cannot > > transition to non-D0 state from D3 [25568.448623] acpi > > device:41: Cannot transition to power state D3cold for = > > parent in (unknown) > > [25568.448627] acpi INT33C6:00: Cannot transition to non-D0 > > state from D3 > > All of the above mean that power transitions were not carried > out for some devices, because they were in unexpected power > states to start with. > > They are devices on the Intel LPSS as far as I can say (CCing > Mika and Andy). > Just to note: all above acpi devices do not exist in 3.13 kernel, at least I do not see them in /sys/bus/acpi/. > > [25568.448890] pci_bus 0000:01: Allocating resources > > [25568.448905] i915 0000:00:02.0: BAR 6: [??? 0x00000000 > > flags 0x2] has bog= us alignment > > [25568.449064] i915 0000:00:02.0: BAR 6: [??? 0x00000000 > > flags 0x2] has bog= us alignment > > [25568.449472] i915 0000:00:02.0: BAR 6: [??? 0x00000000 > > flags 0x2] has bog= us alignment > > > > With older kernel (3.13) I do not see these errors, so it is > > regression. > > It only is a regression if it leads to functional problems. > Do you see any? > Ok. I do not see functional problems, but I see above messages in dmesg log every time when I open LID. > > Ca=n you look at it? If it is needed, I can provide other > > logs, ACPI/DSTD dump= s, etc. > > It looks like 3.13 didn't try to use some devices that are now > used in 3.19-rc1 and something doesn't work entirely as > expected. -- Pali Rohár pali.rohar@xxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part.
