lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTikuBj0uCuyPRiDLD_iWypFN2MoTHQ@mail.gmail.com>
Date:	Tue, 17 May 2011 15:56:06 +0800
From:	Michael Chang <mchang@...ell.com>
To:	Melchior FRANZ <melchior.franz@...il.com>
Cc:	Takashi Iwai <tiwai@...e.de>, linux-kernel@...r.kernel.org,
	Joey Lee <jlee@...ell.com>, chris@...is-wilson.co.uk,
	dri-devel@...ts.freedesktop.org
Subject: Re: i915/kms/backlight-combo mode problem

2011/5/16 Melchior FRANZ <melchior.franz@...il.com>:

> I don't even know what an LBPC is, other than a variable named like that.
> So I'd need a hint for how to test that.

It resides at your vga adapter's pci configuration space, offset 0xf4.

You can know your LPBC value by:
  $ lspci -xxx -s 00:02.0 | awk '/^f0:/ {print $6}'

And alter it's value via setpci (assuming set it to max)
  $ setpci -s 00:02.0 F4.B=ff

I assume you've tried this .. as you report setpci works for you. :)

>From your new attached log, In booting phase your LPBC is set to 255
and actual brightness is maximum (255*2890=736950). I see no other
change after it until manual brightness change. This is a totally
reversed to your problem.

Could you help to get the LPBC value in the initial dark condition? If
it's not corresponds to 255, maybe something sneaks and changes it but
not logged.

[    3.125522] [drm:is_backlight_combination_mode],
BLM_COMBINATION_MODE = 1073741824
[    3.125525] [drm:intel_panel_get_max_backlight], max backlight PWM = 736950
[    3.125527] [drm:intel_panel_set_backlight], set backlight PWM = 736950
[    3.125529] [drm:is_backlight_combination_mode],
BLM_COMBINATION_MODE = 1073741824
[    3.125531] [drm:is_backlight_combination_mode],
BLM_COMBINATION_MODE = 1073741824
[    3.125533] [drm:intel_panel_get_max_backlight], max backlight PWM = 736950
[    3.125535] [drm:intel_panel_set_backlight], set backlight max = 736950
[    3.125537] [drm:intel_panel_set_backlight], set backlight lbpc = 255
[    3.125544] [drm:intel_panel_set_backlight], set backlight level = 2890

> Yes, that's the case. (Except that after closing the lid it's off again.)

Maybe this is another clue for root cause. Would it be convenient for
you to gather the log?

 1. $ dmesg -c
 2. Close the lid
 3. Open the lid
 4. $ dmesg > dmesg.lid

Thanks a lot,
Michael Chang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ