Summary: | Backlight does not ignite in specific situations | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Cedric Sodhi <manday> | ||||
Component: | DRM/Intel | Assignee: | Jesse Barnes <jbarnes> | ||||
Status: | CLOSED INVALID | QA Contact: | |||||
Severity: | critical | ||||||
Priority: | medium | CC: | ben, chris, daniel, eugeni, jbarnes, mike | ||||
Version: | XOrg git | ||||||
Hardware: | All | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Cedric Sodhi
2011-09-28 11:16:55 UTC
By today, I've had the LCD replaced three times, the motherboard once, and three BIOS updates ran, because I suspected it to be an inverter/HW issue. Since the issue is still not resolved and there is no indication of it in windows, I must strongly assume it is in the kernel. Created attachment 51920 [details] [review] obey backlight power sequencing delays Please test this kernel patch and report if anything changes in the backlight behavior. No high hopes that this fixes it, but imo worth a try. (In reply to comment #2) > Created an attachment (id=51920) [details] > obey backlight power sequencing delays > > Please test this kernel patch and report if anything changes in the backlight > behavior. > > No high hopes that this fixes it, but imo worth a try. No. I noticed a slight difference in the flicker when the backlight initially turns off, but other than that and also in particular regard to bringing the backlight back on, there is no change. Please refer to [1] for additonal information. Though there is nothing significant new, it is worth noting that the kernel succeeds in bringing the backlight up, in the following cases: *Laptop lid is opened after closed for a few seconds (upon closing the lid, the backlight shortly flickers on, to then go off and go on again, if the lid is opened after a few seconds) *Xrandr rotates the screen while X is running with its driver *The unit is on battery power and THERE HAS NO ATTEMPT BEEN MADE to turn the backlight on/increase brightness while the unit is on AC, since the backlight went off the last tiem *The backlight is turned back on due to resuming from turning the screen off in a screensaver-fashion or the system comes back from any sort of power safe, such as suspend (In reply to comment #5) > This looks like a duplicate of bug 36823. No it is not, as explained there. No need to suggest it in both threads redundantly. I also noticed that it appears not to depend on the manner in which the backlight turned off, but exclusively on the manner in which it is tried to be turned on. If, for example, no attempt to turn the backlight on while on AC after it has gone off on boot has been made, and instead we wait a bit so that the power-save type of blank-screen "would" turn it off, it will successfully ignite after "any key" press, which returns from the power-save type of blank-screen (if no measures have been taken, it will immediately go off again, though, because the "desired brightness" is still 0 at that point, due to the bug on boot.). Any suggestion would be greatly appreciated! There was one recent patch on LKML related to backlight value saving - http://lkml.org/lkml/2011/10/13/95 - could you please try it? (In reply to comment #8) > There was one recent patch on LKML related to backlight value saving - > http://lkml.org/lkml/2011/10/13/95 - could you please try it? It does what it say on the box: The backlight doesn't initially go to the brightest state after opening the lid. Other than that, there is no change, esp. with regard to not being able to turn it on in the situations elaborated above. Does anyone know in how far the mechanisms of igniting the backlight differ? Id est: Why does it work in one csae but not in the other. Why not simply use the working mechanism, always!? Ok, this bug is lacking a bit on information. Please attach dmesg with drm.debug=0xe added to your commandline. I'm working on a few backlight fixes right now, so with the information from dmesg I could (hopefully) attach a few patches for you to try. I for my part can no longer provide any information for I am no longer in possession of the specific hardware. I can only refer you to https://bugzilla.kernel.org/show_bug.cgi?id=34582 which has received some attention since I filed it. If no one else can reproduce this issue, I have no objections to closing it as whatever you like. Ok, closing because the hw is gone. Thanks for reporting this anyway. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.