From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Li <lkml@chrisli.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
len.brown@intel.com, feng.tang@intel.com,
intel-gfx <intel-gfx@lists.freedesktop.org>,
linux-kernel@vger.kernel.org, robert.moore@intel.com,
Linus Torvalds <torvalds@linux-foundation.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [Intel-gfx] i915 black screen introduced by ACPI changes
Date: Fri, 15 Mar 2013 09:29:56 +0200 [thread overview]
Message-ID: <87ip4tf7d7.fsf@intel.com> (raw)
In-Reply-To: <CANeU7QmJx=3m94ut0SYGEes4-C9khTMWbpee1u0rD4-esUpV=Q@mail.gmail.com>
On Thu, 14 Mar 2013, Chris Li <lkml@chrisli.org> wrote:
> Hi, I attach the two demsg and with and without the bad commit
> on the intel nightly branch. Without the bad commit it actually works.
> However, on the tip of intel nightly. the moeset work around does not work
> there any more.
Hi Chris, thanks for the dmesgs.
So the diff in the dmesgs from intel nightly (bad) to the same with
a57f7f9175b8ccbc9df83ac13860488913115de4 reverted (good) wrt backlight
boils down to this, repeated a few times:
-[drm:asle_set_backlight], bclp = 0x80000000
+[drm:asle_set_backlight], bclp = 0x800000ff
[drm:intel_panel_get_max_backlight], max backlight PWM = 4648
-[drm:intel_panel_actually_set_backlight], set backlight PWM = 0
-[drm:asle_set_backlight], bclp = 0x80000000
+[drm:intel_panel_actually_set_backlight], set backlight PWM = 4648
+[drm:asle_set_backlight], bclp = 0x800000ff
[drm:intel_panel_get_max_backlight], max backlight PWM = 4648
-[drm:intel_panel_actually_set_backlight], set backlight PWM = 0
+[drm:intel_panel_actually_set_backlight], set backlight PWM = 4648
Fun. The BIOS seems to ask for zero backlight. Maybe it means something
else for Windows 8. White is the new black or something.
> Let me know if you need any thing else from me.
Just one idea, please attach hexdumps of
/sys/kernel/debug/dri/0/i915_opregion (with debugfs mounted there,
obviously) for both kernels. Maybe we're missing something there that
the BIOS thinks Windows 8 should handle.
I've never used the acpi_osi= kernel parameter, but it looks like you
could workaround this with acpi_osi="!Windows 2012". Please check that
running the "bad" kernel.
BR,
Jani.
next prev parent reply other threads:[~2013-03-15 7:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 4:43 i915 black screen introduced by ACPI changes Chris Li
2013-02-19 18:08 ` Jesse Barnes
2013-02-19 20:18 ` Chris Li
2013-02-19 20:52 ` Jesse Barnes
2013-02-20 7:17 ` Chris Li
2013-02-20 10:57 ` Daniel Vetter
2013-02-20 19:29 ` Chris Li
2013-02-20 19:33 ` Chris Li
2013-02-20 19:37 ` Chris Li
2013-02-20 19:45 ` Chris Li
2013-02-20 20:01 ` Chris Li
2013-02-20 20:19 ` Daniel Vetter
2013-02-20 20:23 ` Chris Li
2013-02-20 20:43 ` Chris Li
2013-02-20 21:04 ` Chris Li
2013-02-22 22:42 ` Chris Li
2013-03-04 17:11 ` Chris Li
2013-03-04 17:49 ` Daniel Vetter
2013-03-04 17:50 ` Daniel Vetter
2013-03-04 23:16 ` Chris Li
2013-03-04 23:33 ` Chris Li
2013-03-11 13:16 ` [Intel-gfx] " Jani Nikula
2013-03-14 20:10 ` Chris Li
2013-03-14 20:49 ` Chris Li
2013-03-15 7:29 ` Jani Nikula [this message]
2013-03-15 9:00 ` Chris Li
2013-03-15 9:06 ` Chris Li
2013-03-15 9:33 ` Chris Li
2013-03-19 8:13 ` Chris Li
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=87ip4tf7d7.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=feng.tang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@chrisli.org \
--cc=robert.moore@intel.com \
--cc=rui.zhang@intel.com \
--cc=torvalds@linux-foundation.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