From: "Pali Rohár" <pali.rohar@gmail.com>
To: nick <xerofoify@gmail.com>
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,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [Intel-gfx] 3.19-rc1 errors when opening LID
Date: Thu, 25 Dec 2014 09:48:38 +0100 [thread overview]
Message-ID: <201412250948.38808@pali> (raw)
In-Reply-To: <549B926B.1050000@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 4234 bytes --]
I know how to use git... first I wanted to report errors because
maybe it could be known problem or somebody else can come with
quick patch even without bisetcing (like for other problems which
I reported).
Anyway those acpi devices which are mentioned in log do not exist
in 3.13 kernel (I do not see them in /sys/devices)
Any idea why 3.19 kernel create new acpi devices which 3.13
kernel did not?
On Thursday 25 December 2014 05:28:27 nick wrote:
> Pali,
> Do you known how to run git bisect as this is probably the
> best way to continue. Otherwise, I can teach you how it's not
> hard if your willing to learn :). Cheers Nick
>
> On 2014-12-24 01:51 PM, Pali Rohár wrote:
> > Hello!
> >
> > With new 3.19-rc1 kernel every time when I open LID on my
> > laptop, kernel prints these error lines to dmesg:
> >
> > [25566.368133] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]]
> > *ERROR* Unclaimed register detected. Please use the
> > i915.mmio_debug=1 to debug this problem. [25566.368134]
> > [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed
> > register before interrupt [25566.368192]
> > [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR*
> > Unclaimed register detected. Please use the
> > i915.mmio_debug=1 to debug this problem. [25566.368232]
> > [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR*
> > Unclaimed register detected. Please use the
> > i915.mmio_debug=1 to debug this problem.<4>[25568.446011]
> > i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has
> > bogus alignment
> > [25568.447018] pci_bus 0000:02: Allocating resources
> > [25568.447055] pci_bus 0000:03: Allocating resources
> > [25568.447135] pci_bus 0000:04: Allocating resources
> > [25568.447168] pci_bus 0000:05: Allocating resources
> > [25568.447195] pci_bus 0000:06: Allocating resources
> > [25568.447228] pci_bus 0000:0e: Allocating resources
> > [25568.447323] i915 0000:00:02.0: BAR 6: [??? 0x00000000
> > flags 0x2] has bogus alignment [25568.447557] i915
> > 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus
> > alignment [25568.447735] i915 0000:00:02.0: BAR 6: [???
> > 0x00000000 flags 0x2] has bogus alignment [25568.447847]
> > i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has
> > bogus alignment [25568.448399] i915 0000:00:02.0: BAR 6:
> > [??? 0x00000000 flags 0x2] has bogus alignment
> > [25568.448438] i915 0000:00:02.0: BAR 6: [??? 0x00000000
> > flags 0x2] has bogus alignment [25568.448566] acpi
> > MSFT1111:00: Cannot transition to power state D3cold for
> > 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 for
> > parent in (unknown) [25568.448581] acpi ELAN1010:00: Cannot
> > transition to power state D3cold for 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 [25568.448890] pci_bus
> > 0000:01: Allocating resources [25568.448905] i915
> > 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus
> > alignment [25568.449064] i915 0000:00:02.0: BAR 6: [???
> > 0x00000000 flags 0x2] has bogus alignment [25568.449472]
> > i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has
> > bogus alignment
> >
> > With older kernel (3.13) I do not see these errors, so it is
> > regression. Can you look at it? If it is needed, I can
> > provide other logs, ACPI/DSTD dumps, etc.
> >
> >
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-12-25 8:48 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 ` Pali Rohár [this message]
[not found] ` <549C4278.5080707@gmail.com>
2014-12-27 8:19 ` [Intel-gfx] " 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
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=201412250948.38808@pali \
--to=pali.rohar@gmail.com \
--cc=airlied@linux.ie \
--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=rjw@rjwysocki.net \
--cc=xerofoify@gmail.com \
/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).