From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: dri-devel@lists.freedesktop.org, Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org
Subject: Re: has the i915 "black screen" boot issue returned? [BISECTED]
Date: Fri, 28 Jan 2011 15:04:26 +0000 [thread overview]
Message-ID: <1bdc18$jdthb8@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101280948340.2715@localhost6.localdomain6>
On Fri, 28 Jan 2011 09:51:01 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
> sadly, no change -- still black screen. again, rebooted
> successfully under commit 8a327f23. just to be clear, here's "git
> diff":
>
> $ git diff
> diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h
> index 7180013..e035f3c 100644
> --- a/include/linux/acpi_io.h
> +++ b/include/linux/acpi_io.h
> @@ -7,7 +7,7 @@
> static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys,
> acpi_size size)
> {
> - return ioremap_cache(phys, size);
> + return ioremap(phys, size);
> }
Ok, that implies the new mapping is fine and not the cause of the issue.
Instead you have some OpRegion related regression hidden until till now
because the conflicting mapping disabled it for i915.
That would be easy to test by returning early in intel_opregion_setup():
diff --git a/drivers/gpu/drm/i915/intel_opregion.c
b/drivers/gpu/drm/i915/intel_
index 9efccb9..8c93201 100644
--- a/drivers/gpu/drm/i915/intel_opregion.c
+++ b/drivers/gpu/drm/i915/intel_opregion.c
@@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev)
u32 asls, mboxes;
int err = 0;
+ return -ENOTSUPP;
+
pci_read_config_dword(dev->pdev, PCI_ASLS, &asls);
DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls);
if (asls == 0) {
--
Chris Wilson, Intel Open Source Technology Centre
WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: dri-devel@lists.freedesktop.org, Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org
Subject: Re: has the i915 "black screen" boot issue returned? [BISECTED]
Date: Fri, 28 Jan 2011 15:04:26 +0000 [thread overview]
Message-ID: <1bdc18$jdthb8@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101280948340.2715@localhost6.localdomain6>
On Fri, 28 Jan 2011 09:51:01 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
> sadly, no change -- still black screen. again, rebooted
> successfully under commit 8a327f23. just to be clear, here's "git
> diff":
>
> $ git diff
> diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h
> index 7180013..e035f3c 100644
> --- a/include/linux/acpi_io.h
> +++ b/include/linux/acpi_io.h
> @@ -7,7 +7,7 @@
> static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys,
> acpi_size size)
> {
> - return ioremap_cache(phys, size);
> + return ioremap(phys, size);
> }
Ok, that implies the new mapping is fine and not the cause of the issue.
Instead you have some OpRegion related regression hidden until till now
because the conflicting mapping disabled it for i915.
That would be easy to test by returning early in intel_opregion_setup():
diff --git a/drivers/gpu/drm/i915/intel_opregion.c
b/drivers/gpu/drm/i915/intel_
index 9efccb9..8c93201 100644
--- a/drivers/gpu/drm/i915/intel_opregion.c
+++ b/drivers/gpu/drm/i915/intel_opregion.c
@@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev)
u32 asls, mboxes;
int err = 0;
+ return -ENOTSUPP;
+
pci_read_config_dword(dev->pdev, PCI_ASLS, &asls);
DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls);
if (asls == 0) {
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-28 15:04 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 11:37 has the i915 "black screen" boot issue returned? Robert P. J. Day
2011-01-27 10:15 ` Chris Wilson
2011-01-27 10:37 ` Robert P. J. Day
2011-01-27 11:47 ` Robert P. J. Day
2011-01-27 11:56 ` Chris Wilson
2011-01-27 12:12 ` Robert P. J. Day
2011-01-27 12:17 ` Chris Wilson
2011-01-27 12:27 ` Robert P. J. Day
2011-01-27 13:00 ` Robert P. J. Day
2011-01-27 13:42 ` Robert P. J. Day
2011-01-27 13:52 ` Chris Wilson
2011-01-27 13:55 ` Robert P. J. Day
2011-01-27 14:07 ` Chris Wilson
2011-01-27 14:13 ` Robert P. J. Day
2011-01-27 18:40 ` Robert P. J. Day
2011-01-27 21:39 ` Robert P. J. Day
2011-01-27 22:33 ` Robert P. J. Day
2011-01-28 8:59 ` Chris Wilson
2011-01-28 9:24 ` Robert P. J. Day
2011-01-28 9:29 ` Chris Wilson
2011-01-28 13:53 ` has the i915 "black screen" boot issue returned? [BISECTED] Robert P. J. Day
2011-01-28 14:02 ` Chris Wilson
2011-01-28 14:10 ` Robert P. J. Day
2011-01-28 14:10 ` Robert P. J. Day
2011-01-28 14:32 ` Robert P. J. Day
2011-01-28 14:36 ` Chris Wilson
2011-01-28 14:36 ` Chris Wilson
2011-01-28 14:51 ` Robert P. J. Day
2011-01-28 15:04 ` Chris Wilson [this message]
2011-01-28 15:04 ` Chris Wilson
2011-01-28 15:08 ` Robert P. J. Day
2011-01-28 15:11 ` Chris Wilson
2011-01-28 15:27 ` Robert P. J. Day
2011-01-28 15:39 ` Chris Wilson
2011-01-28 15:54 ` Robert P. J. Day
2011-01-28 16:03 ` Chris Wilson
2011-01-28 16:23 ` Robert P. J. Day
2011-01-28 16:30 ` Chris Wilson
2011-01-28 18:38 ` Robert P. J. Day
2011-01-29 10:02 ` Robert P. J. Day
2011-02-01 12:05 ` Robert P. J. Day
2011-02-01 12:12 ` Chris Wilson
2011-02-01 12:56 ` Robert P. J. Day
2011-01-28 16:30 ` Robert P. J. Day
2011-01-28 20:12 ` Rafael J. Wysocki
2011-01-28 20:21 ` Robert P. J. Day
2011-01-28 20:21 ` Robert P. J. Day
2011-01-28 20:46 ` Robert P. J. Day
2011-01-28 11:35 ` has the i915 "black screen" boot issue returned? Robert P. J. Day
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='1bdc18$jdthb8@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.