From: "Pali Rohár" <pali.rohar@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: 3.19-rc1 errors when opening LID
Date: Fri, 26 Dec 2014 16:52:53 +0100 [thread overview]
Message-ID: <201412261652.54112@pali> (raw)
In-Reply-To: <3406993.nnu7vUsHIn@vostro.rjw.lan>
[-- Attachment #1: Type: Text/Plain, Size: 2922 bytes --]
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@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2014-12-26 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 18:51 3.19-rc1 errors when opening LID Pali Rohár
[not found] ` <549B926B.1050000@gmail.com>
2014-12-25 8:48 ` [Intel-gfx] " Pali Rohár
[not found] ` <549C4278.5080707@gmail.com>
2014-12-27 8:19 ` Pali Rohár
2014-12-27 20:22 ` Rafael J. Wysocki
2014-12-27 20:17 ` Joe Perches
2014-12-26 15:12 ` Rafael J. Wysocki
2014-12-26 15:52 ` Pali Rohár [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201412261652.54112@pali \
--to=pali.rohar@gmail.com \
--cc=airlied@linux.ie \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).