From: Matthew Garrett <mjg59@srcf.ucam.org>
To: intel-gfx@lists.freedesktop.org, joeyli <jlee@suse.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
platform-driver-x86@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [BUG] i915/intel-acpi.c: failed to get supported _DSM functions (was: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off)
Date: Tue, 6 Dec 2011 13:46:07 +0000 [thread overview]
Message-ID: <20111206134607.GA11462@srcf.ucam.org> (raw)
In-Reply-To: <20111205205647.GA1757@archminux>
On Mon, Dec 05, 2011 at 09:56:47PM +0100, Baptiste Jonglez wrote:
> CC-ing intel-gfx@lists.freedesktop.org (see below)
> On Mon, Dec 05, 2011 at 11:00:41AM +0800, joeyli wrote:
> > > [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
> > >
> > > (attached is the relevant part of dmesg [1])
> > >
> > >
> >
> > Have no idea for this _DSM error, need help from drm and acpi experts.
>
> It definitely looks like an ACPI issue.
> That function is defined in `drivers/gpu/drm/i915/intel_acpi.c'.
> The whole file was added more than a year ago by commit 723bfd707a97
> (see the relevant thread on intel-gfx@ [1]) to "add _DSM support".
> One of the first comment is about "Calpella", which is exactly the
> platform of my laptop (as shown by lshw)
Ignore that - it's entirely harmless.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-12-06 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111204160728.GA27292@archminux>
2011-12-05 3:00 ` [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+] joeyli
2011-12-05 20:56 ` [BUG] i915/intel-acpi.c: failed to get supported _DSM functions (was: [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off) Baptiste Jonglez
2011-12-06 13:46 ` Matthew Garrett [this message]
2011-12-06 21:51 ` [Dual-LVDS Acer Iconia laptop] i915/DRM issue: one screen stays off [3.2-rc4+] Baptiste Jonglez
2011-12-06 22:12 ` Benjamin Tissoires
2011-12-06 22:31 ` Baptiste Jonglez
2011-12-08 10:11 ` Benjamin Tissoires
2011-12-11 16:30 ` Baptiste Jonglez
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=20111206134607.GA11462@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jlee@suse.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/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).