public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Li <lkml@chrisli.org>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: 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>
Subject: Re: [Intel-gfx] i915 black screen introduced by ACPI changes
Date: Mon, 11 Mar 2013 15:16:08 +0200	[thread overview]
Message-ID: <87txoit6uf.fsf@intel.com> (raw)
In-Reply-To: <CANeU7Q=_+qt5C3G2uKhQYq_hh9kOg5c8=uAvjQzRwvx_xOe2hA@mail.gmail.com>

On Tue, 05 Mar 2013, Chris Li <lkml@chrisli.org> wrote:
> On Mon, Mar 4, 2013 at 3:16 PM, Chris Li <lkml@chrisli.org> wrote:
>>>> Two things to test:
>>>> - Can you please check whether any of the backlight drivers in
>>>> /sys/class/backlight does anything? You need to frob the brightness
>>>> file. Please also list all the drivers you have.
>
> This is the kernel with the ACPI change causing the black screen.
>
> lrwxrwxrwx. 1 root root 0 Mar  4 15:20 acpi_video0 ->
> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0
> lrwxrwxrwx. 1 root root 0 Mar  4 15:20 acpi_video1 ->
> ../../devices/pci0000:00/0000:00:02.0/backlight/acpi_video1
> lrwxrwxrwx. 1 root root 0 Mar  4 15:20 intel_backlight ->
> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/intel_backlight
>
> Here is the interesting part. The brightness and max_brightness is all
> set to 4648,
> However, the actual brightness is 0. The bl_power is also 0. I think
> you are on to some thing.

Hi Chris -

Interesting snippets from your dmesgs:

1) good

[    0.000000] Linux version 3.6.0-rc6+ (chrisl@ideapad.lan) (gcc version 4.7.2 20121109 (Red Hat 4.7.2-8) (GCC) ) #25 SMP Wed Feb 20 12:55:06 PST 2013
...
[    5.341431] [drm:intel_panel_get_max_backlight], max backlight PWM = 4648
[    5.341442] [drm:intel_panel_actually_set_backlight], set backlight PWM = 4648
[    5.342572] [drm:intel_panel_get_max_backlight], max backlight PWM = 4648
[    5.342578] [drm:intel_panel_actually_set_backlight], set backlight PWM = 4648

2) bad

[    0.000000] Linux version 3.8.0-rc7+ (chrisl@ideapad.lan) (gcc version 4.7.2 20121109 (Red Hat 4.7.2-8) (GCC) ) #23 SMP Tue Feb 19 19:24:57 PST 2013
...
[    5.692853] [drm:asle_set_backlight], bclp = 0x800000ff
[    5.692865] [drm:intel_panel_get_max_backlight], max backlight PWM = 4648
[    5.692870] [drm:intel_panel_actually_set_backlight], set backlight PWM = 4648
[    5.693401] [drm:asle_set_backlight], bclp = 0x80000000
[    5.693408] [drm:intel_panel_get_max_backlight], max backlight PWM = 4648
[    5.693413] [drm:intel_panel_actually_set_backlight], set backlight PWM = 0

(We've added another debug print to asle_set_backlight.)

For some reason we get two asle requests in a row. In the good kernel
it's the same request twice, in the bad kernel the second requests is
for 0 backlight. The register dumps seem to confirm this.

Please try a recent kernel, with and without the the bisected bad commit

commit a57f7f9175b8ccbc9df83ac13860488913115de4
Author: Bob Moore <robert.moore@intel.com>
Date:   Fri Aug 17 10:55:02 2012 +0800

    ACPICA: Add Windows8/Server2012 string for _OSI method.

reverted. Is the difference the same? Check reg dumps and dmesgs with
drm.debug=0xe.


Thanks,
Jani.

  reply	other threads:[~2013-03-11 13:15 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                               ` Jani Nikula [this message]
2013-03-14 20:10                                 ` [Intel-gfx] " Chris Li
2013-03-14 20:49                                   ` Chris Li
2013-03-15  7:29                                     ` Jani Nikula
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=87txoit6uf.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=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