[Intel-gfx] [Acer Aspire V5-573G] Black screen on boot due to low brightness setting
On 11/14/2013 02:24 PM, Jani Nikula wrote: > > Hi Mario - > > On Wed, 13 Nov 2013, Mario Kleinsasser gmail.com> wrote: >> In the last three weeks I've narrowed down the bug described in the >> subject through Ubuntu launchpad. My new Laptop (Acer Aspire V5-573G) >> with new Haswell CPU shows a black screen on reboot because the >> brightness is on zero level. I verified this behaviour with the latest >> mainline kernel from >> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ > > Thanks for the report. I'll have to ask you to try some kernels, and > logs running them, etc. that IMHO are better suited attached to a bug > report than cluttered on the mailing list. Please file a bug on > DRM/Intel at [1]. Reference your mail. There it will also pop up in our > bug team's searches, and has a better chance of not falling under the > radar. :) > >> I have done the bisect process and tracked the bug down to the >> following commit. >> >> For explanation: >> good commit means: The laptop starts with display brightness on full >> power, but low(er) resolution and the Fn+ keys are not working >> bad commit means: The laptop starts with black display (0 brightness), >> Fn+ keys are working and you can level up the brightness trough the >> Fn+ keys. The resolution is the native LCD hardware display resolution >> >> Bisect output: >> >> 70b12bb415463c1bd146b67c5fbf6784fd046ad9 is the first bad commit >> commit 70b12bb415463c1bd146b67c5fbf6784fd046ad9 >> Author: Paulo Zanoni >> Date: Tue Nov 20 13:32:30 2012 -0200 >> >> drm/i915: promote Haswell to full support >> >> Since it should be working a little bit better now. >> >> Signed-off-by: Paulo Zanoni >> Signed-off-by: Daniel Vetter >> >> :04 04 f93a7761de2157a8be61f20ca9a5499264bb5c55 >> 1fed098470278830f06b0bca1706f61ba231d38d M drivers >> >> For the full bug report and the additional hardware information please >> see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239183 >> >> I've also searched the LKML and maybe this bug could be in conjunction >> with http://marc.info/?t=13783778615&r=1&w=2 > > You only start using our driver for Haswell from the first "bad" commit, > and then we actually serve the ACPI opregion backlight requests. This > explains the backlight Fn keys in your good/bad commit explanations. If > this is a known bug in ACPI, it also explains the zero backlight. It's actually a bug in firmware and we try to work around it in ACPI video module :-) >From the description it indeed seems to be the firmware initial zero brightness level bug to me. Thanks, Aaron > > There's two branches I'd like you to try: > > 1) linux-next branch of [2]. This should contain a fix for some ACPI >initial backlight issues. (CC Aaron for this.) > > 2) backlight-rework branch of [3]. What the branch name says. > > Please add drm.debug=0xe module parameter and attach full dmesg to the > bug. > > > Thanks, > Jani. > > > [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI > [2] http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git > [3] git://gitorious.org/jani/drm.git > > >
[Intel-gfx] [Acer Aspire V5-573G] Black screen on boot due to low brightness setting
On Thu, Nov 14, 2013 at 8:29 AM, Aaron Lu wrote: > On 11/14/2013 02:24 PM, Jani Nikula wrote: >> >> Hi Mario - >> >> On Wed, 13 Nov 2013, Mario Kleinsasser > gmail.com> wrote: >>> In the last three weeks I've narrowed down the bug described in the >>> subject through Ubuntu launchpad. My new Laptop (Acer Aspire V5-573G) >>> with new Haswell CPU shows a black screen on reboot because the >>> brightness is on zero level. I verified this behaviour with the latest >>> mainline kernel from >>> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ >> >> Thanks for the report. I'll have to ask you to try some kernels, and >> logs running them, etc. that IMHO are better suited attached to a bug >> report than cluttered on the mailing list. Please file a bug on >> DRM/Intel at [1]. Reference your mail. There it will also pop up in our >> bug team's searches, and has a better chance of not falling under the >> radar. :) >> >>> I have done the bisect process and tracked the bug down to the >>> following commit. >>> >>> For explanation: >>> good commit means: The laptop starts with display brightness on full >>> power, but low(er) resolution and the Fn+ keys are not working >>> bad commit means: The laptop starts with black display (0 brightness), >>> Fn+ keys are working and you can level up the brightness trough the >>> Fn+ keys. The resolution is the native LCD hardware display resolution >>> >>> Bisect output: >>> >>> 70b12bb415463c1bd146b67c5fbf6784fd046ad9 is the first bad commit >>> commit 70b12bb415463c1bd146b67c5fbf6784fd046ad9 >>> Author: Paulo Zanoni >>> Date: Tue Nov 20 13:32:30 2012 -0200 >>> >>> drm/i915: promote Haswell to full support >>> >>> Since it should be working a little bit better now. >>> >>> Signed-off-by: Paulo Zanoni >>> Signed-off-by: Daniel Vetter >>> >>> :04 04 f93a7761de2157a8be61f20ca9a5499264bb5c55 >>> 1fed098470278830f06b0bca1706f61ba231d38d M drivers >>> >>> For the full bug report and the additional hardware information please >>> see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239183 >>> >>> I've also searched the LKML and maybe this bug could be in conjunction >>> with http://marc.info/?t=13783778615&r=1&w=2 >> >> You only start using our driver for Haswell from the first "bad" commit, >> and then we actually serve the ACPI opregion backlight requests. This >> explains the backlight Fn keys in your good/bad commit explanations. If >> this is a known bug in ACPI, it also explains the zero backlight. > > It's actually a bug in firmware and we try to work around it in ACPI > video module :-) > > From the description it indeed seems to be the firmware initial zero > brightness level bug to me. > > Thanks, > Aaron Bug filed as https://bugs.freedesktop.org/show_bug.cgi?id=71596 I will try the given branches and post my results in the filed bug. Thanks for information! Mario > >> >> There's two branches I'd like you to try: >> >> 1) linux-next branch of [2]. This should contain a fix for some ACPI >>initial backlight issues. (CC Aaron for this.) >> >> 2) backlight-rework branch of [3]. What the branch name says. >> >> Please add drm.debug=0xe module parameter and attach full dmesg to the >> bug. >> >> >> Thanks, >> Jani. >> >> >> [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI >> [2] http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git >> [3] git://gitorious.org/jani/drm.git >> >> >> >
[Intel-gfx] [Acer Aspire V5-573G] Black screen on boot due to low brightness setting
Hi Mario - On Wed, 13 Nov 2013, Mario Kleinsasser wrote: > In the last three weeks I've narrowed down the bug described in the > subject through Ubuntu launchpad. My new Laptop (Acer Aspire V5-573G) > with new Haswell CPU shows a black screen on reboot because the > brightness is on zero level. I verified this behaviour with the latest > mainline kernel from > http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ Thanks for the report. I'll have to ask you to try some kernels, and logs running them, etc. that IMHO are better suited attached to a bug report than cluttered on the mailing list. Please file a bug on DRM/Intel at [1]. Reference your mail. There it will also pop up in our bug team's searches, and has a better chance of not falling under the radar. :) > I have done the bisect process and tracked the bug down to the > following commit. > > For explanation: > good commit means: The laptop starts with display brightness on full > power, but low(er) resolution and the Fn+ keys are not working > bad commit means: The laptop starts with black display (0 brightness), > Fn+ keys are working and you can level up the brightness trough the > Fn+ keys. The resolution is the native LCD hardware display resolution > > Bisect output: > > 70b12bb415463c1bd146b67c5fbf6784fd046ad9 is the first bad commit > commit 70b12bb415463c1bd146b67c5fbf6784fd046ad9 > Author: Paulo Zanoni > Date: Tue Nov 20 13:32:30 2012 -0200 > > drm/i915: promote Haswell to full support > > Since it should be working a little bit better now. > > Signed-off-by: Paulo Zanoni > Signed-off-by: Daniel Vetter > > :04 04 f93a7761de2157a8be61f20ca9a5499264bb5c55 > 1fed098470278830f06b0bca1706f61ba231d38d M drivers > > For the full bug report and the additional hardware information please > see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239183 > > I've also searched the LKML and maybe this bug could be in conjunction > with http://marc.info/?t=13783778615&r=1&w=2 You only start using our driver for Haswell from the first "bad" commit, and then we actually serve the ACPI opregion backlight requests. This explains the backlight Fn keys in your good/bad commit explanations. If this is a known bug in ACPI, it also explains the zero backlight. There's two branches I'd like you to try: 1) linux-next branch of [2]. This should contain a fix for some ACPI initial backlight issues. (CC Aaron for this.) 2) backlight-rework branch of [3]. What the branch name says. Please add drm.debug=0xe module parameter and attach full dmesg to the bug. Thanks, Jani. [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI [2] http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git [3] git://gitorious.org/jani/drm.git -- Jani Nikula, Intel Open Source Technology Center
[Acer Aspire V5-573G] Black screen on boot due to low brightness setting
Dear mailing list! In the last three weeks I've narrowed down the bug described in the subject through Ubuntu launchpad. My new Laptop (Acer Aspire V5-573G) with new Haswell CPU shows a black screen on reboot because the brightness is on zero level. I verified this behaviour with the latest mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ I have done the bisect process and tracked the bug down to the following commit. For explanation: good commit means: The laptop starts with display brightness on full power, but low(er) resolution and the Fn+ keys are not working bad commit means: The laptop starts with black display (0 brightness), Fn+ keys are working and you can level up the brightness trough the Fn+ keys. The resolution is the native LCD hardware display resolution Bisect output: 70b12bb415463c1bd146b67c5fbf6784fd046ad9 is the first bad commit commit 70b12bb415463c1bd146b67c5fbf6784fd046ad9 Author: Paulo Zanoni Date: Tue Nov 20 13:32:30 2012 -0200 drm/i915: promote Haswell to full support Since it should be working a little bit better now. Signed-off-by: Paulo Zanoni Signed-off-by: Daniel Vetter :04 04 f93a7761de2157a8be61f20ca9a5499264bb5c55 1fed098470278830f06b0bca1706f61ba231d38d M drivers For the full bug report and the additional hardware information please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239183 I've also searched the LKML and maybe this bug could be in conjunction with http://marc.info/?t=13783778615&r=1&w=2 I'am not described to any of the mailing lists. Please CC me if it is possible! If you need any futher information please let me know! Mario Kleinsasser Additional information: lsb_release -rd Description:Ubuntu 13.10 Release:13.10 /usr/src/linux-headers-3.12.0-031200/scripts/ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux Fenrir 3.12.0-031200-generic #201311071835 SMP Thu Nov 7 23:36:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Gnu C 4.8 Gnu make 3.81 binutils 2.23.52.20130913 util-linux 2.20.1 mount support module-init-tools 9 e2fsprogs 1.42.8 pcmciautils018 PPP2.4.5 Linux C Library2.17 Dynamic linker (ldd) 2.17 Procps 3.3.3 Net-tools 1.60 Kbd1.15.5 Sh-utils 8.20 wireless-tools 30 Modules Loaded x86_pkg_temp_thermal parport_pc ppdev coretemp kvm_intel kvm rfcomm bnep crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev snd_hda_codec_hdmi snd_hda_codec_realtek acer_wmi sparse_keymap snd_hda_intel uvcvideo snd_hda_codec videobuf2_vmalloc snd_hwdep videobuf2_memops snd_pcm videobuf2_core videodev snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi arc4 snd_seq ath9k snd_seq_device ath3k ath9k_common ath9k_hw btusb ath snd_timer mac80211 bluetooth microcode cfg80211 snd rtsx_pci_ms psmouse soundcore memstick mei_me mei serio_raw lpc_ich mac_hid lp parport hid_generic usbhid hid rtsx_pci_sdmmc nouveau i915 mxm_wmi ahci ttm r8169 libahci i2c_algo_bit mii drm_kms_helper rtsx_pci drm wmi video cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz stepping: 1 microcode : 0x15 cpu MHz : 1600.027 cache size : 3072 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid bogomips: 4588.93 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz stepping: 1 microcode : 0x15 cpu MHz : 1688.613 cache size : 3072 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags
