WARNING on i915 - intel_panel

WARNING on i915 - intel_panel

[Pedro Ribeiro]

Hi,

I'm getting this error consistently with the Debian 3.14.4 after
resuming from hibernation:

[  931.032142] ------------[ cut here ]------------
[  931.032209] WARNING: CPU: 0 PID: 4715 at
/build/linux-Zc5oK7/linux-3.14.4/drivers/gpu/drm/i915/intel_panel.c:723
i965_enable_backlight+0x122/0x150 [i915]()
[  931.032219] backlight already enabled
[  931.032223] Modules linked in: ctr ccm cpufreq_stats
cpufreq_userspace cpufreq_conservative cpufreq_powersave pci_stub
vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp
xt_conntrack iptable_filter iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables fuse
vmwgfx ttm vmxnet3 tp_smapi(O) thinkpad_ec(O) loop ppdev lp btusb
bluetooth 6lowpan_iphc crc16 snd_hda_codec_conexant
snd_hda_codec_generic coretemp kvm_intel uvcvideo kvm
videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media
psmouse serio_raw arc4 evdev iwldvm snd_hda_intel snd_hda_codec
snd_hwdep snd_pcm_oss thinkpad_acpi mac80211 snd_mixer_oss nvram
snd_pcm snd_seq_midi i2c_i801 snd_seq_midi_event lpc_ich snd_rawmidi
mfd_core snd_seq snd_seq_device snd_timer iwlwifi cfg80211 snd wmi
soundcore rfkill battery ac parport_pc tpm_tis parport i915 tpm video
drm_kms_helper drm i2c_algo_bit i2c_core acpi_cpufreq mei_me mei
processor button xfs crc32c libcrc32c lzo sg hid_generic usbhid hid
sd_mod crct10dif_generic sr_mod crc_t10dif cdrom crct10dif_common
firewire_ohci firewire_core crc_itu_t ahci libahci libata scsi_mod
thermal thermal_sys uhci_hcd ehci_pci ehci_hcd usbcore usb_common
e1000e ptp pps_core
[  931.032448] CPU: 0 PID: 4715 Comm: kworker/u8:89 Tainted: G
  O 3.14-1-amd64 #1 Debian 3.14.4-1
[  931.032456] Hardware name: LENOVO 7417PLU/7417PLU, BIOS 7VET95WW
(3.25 ) 10/10/2012
[  931.032470] Workqueue: events_unbound async_run_entry_fn
[  931.032476]  0000000000000009 ffffffff814b9b42 ffff8800a6369af8
ffffffff8105f0a2
[  931.032488]  ffff880232b04000 ffff8800a6369b48 ffff8802301ac000
00000000e0000000
[  931.032498]  ffff8800b870d000 ffffffff8105f107 ffffffffa0392f9b
ffffffff00000018
[  931.032508] Call Trace:
[  931.032522]  [<ffffffff814b9b42>] ? dump_stack+0x41/0x51
[  931.032532]  [<ffffffff8105f0a2>] ? warn_slowpath_common+0x72/0x90
[  931.032541]  [<ffffffff8105f107>] ? warn_slowpath_fmt+0x47/0x50
[  931.032576]  [<ffffffffa0366782>] ? gen4_read32+0x32/0xa0 [i915]
[  931.032609]  [<ffffffffa034f2f2>] ? i965_enable_backlight+0x122/0x150 [i915]
[  931.032644]  [<ffffffffa035025c>] ?
intel_panel_enable_backlight+0x9c/0xe0 [i915]
[  931.032676]  [<ffffffffa03663c0>] ? gen4_write64+0x90/0x90 [i915]
[  931.032709]  [<ffffffffa0330181>] ? i9xx_crtc_enable+0x2e1/0x400 [i915]
[  931.032743]  [<ffffffffa03329ee>] ? __intel_set_mode+0x85e/0x15a0 [i915]
[  931.032779]  [<ffffffffa0338c49>] ?
intel_modeset_setup_hw_state+0xb09/0xc10 [i915]
[  931.032808]  [<ffffffffa02fd2ca>] ? __i915_drm_thaw+0x15a/0x210 [i915]
[  931.032834]  [<ffffffffa02fd3d1>] ? i915_resume+0x51/0x70 [i915]
[  931.032844]  [<ffffffff812b0da0>] ? pci_pm_suspend_noirq+0x190/0x190
[  931.032854]  [<ffffffff8136cd8e>] ? dpm_run_callback+0x2e/0x70
[  931.032862]  [<ffffffff8136ce9c>] ? device_resume+0x8c/0x180
[  931.032870]  [<ffffffff8136cfa4>] ? async_resume+0x14/0x40
[  931.032880]  [<ffffffff8108503d>] ? async_run_entry_fn+0x2d/0x120
[  931.032890]  [<ffffffff81078b9d>] ? process_one_work+0x16d/0x420
[  931.032899]  [<ffffffff81079756>] ? worker_thread+0x116/0x3b0
[  931.032908]  [<ffffffff81079640>] ? rescuer_thread+0x330/0x330
[  931.032917]  [<ffffffff8107f911>] ? kthread+0xc1/0xe0
[  931.032925]  [<ffffffff8107f850>] ? kthread_create_on_node+0x180/0x180
[  931.032934]  [<ffffffff814c73cc>] ? ret_from_fork+0x7c/0xb0
[  931.032943]  [<ffffffff8107f850>] ? kthread_create_on_node+0x180/0x180
[  931.032950] ---[ end trace a83af26b25b25474 ]---

My hardware is a Lenovo T400 with a GM45.

Does this mean anything to you? Please let me know if there is
anything else you need.

Regards,
Pedro

Re: WARNING on i915 - intel_panel

[Jani Nikula]

On Sat, 24 May 2014, Pedro Ribeiro <pedrib@gmail.com> wrote:
> Hi,
>
> I'm getting this error consistently with the Debian 3.14.4 after
> resuming from hibernation:

Does this ever happen on a fresh boot or when resuming from suspend to
ram?

BR,
Jani.


>
> [  931.032142] ------------[ cut here ]------------
> [  931.032209] WARNING: CPU: 0 PID: 4715 at
> /build/linux-Zc5oK7/linux-3.14.4/drivers/gpu/drm/i915/intel_panel.c:723
> i965_enable_backlight+0x122/0x150 [i915]()
> [  931.032219] backlight already enabled
> [  931.032223] Modules linked in: ctr ccm cpufreq_stats
> cpufreq_userspace cpufreq_conservative cpufreq_powersave pci_stub
> vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc
> nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp
> xt_conntrack iptable_filter iptable_nat nf_conntrack_ipv4
> nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables fuse
> vmwgfx ttm vmxnet3 tp_smapi(O) thinkpad_ec(O) loop ppdev lp btusb
> bluetooth 6lowpan_iphc crc16 snd_hda_codec_conexant
> snd_hda_codec_generic coretemp kvm_intel uvcvideo kvm
> videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media
> psmouse serio_raw arc4 evdev iwldvm snd_hda_intel snd_hda_codec
> snd_hwdep snd_pcm_oss thinkpad_acpi mac80211 snd_mixer_oss nvram
> snd_pcm snd_seq_midi i2c_i801 snd_seq_midi_event lpc_ich snd_rawmidi
> mfd_core snd_seq snd_seq_device snd_timer iwlwifi cfg80211 snd wmi
> soundcore rfkill battery ac parport_pc tpm_tis parport i915 tpm video
> drm_kms_helper drm i2c_algo_bit i2c_core acpi_cpufreq mei_me mei
> processor button xfs crc32c libcrc32c lzo sg hid_generic usbhid hid
> sd_mod crct10dif_generic sr_mod crc_t10dif cdrom crct10dif_common
> firewire_ohci firewire_core crc_itu_t ahci libahci libata scsi_mod
> thermal thermal_sys uhci_hcd ehci_pci ehci_hcd usbcore usb_common
> e1000e ptp pps_core
> [  931.032448] CPU: 0 PID: 4715 Comm: kworker/u8:89 Tainted: G
>   O 3.14-1-amd64 #1 Debian 3.14.4-1
> [  931.032456] Hardware name: LENOVO 7417PLU/7417PLU, BIOS 7VET95WW
> (3.25 ) 10/10/2012
> [  931.032470] Workqueue: events_unbound async_run_entry_fn
> [  931.032476]  0000000000000009 ffffffff814b9b42 ffff8800a6369af8
> ffffffff8105f0a2
> [  931.032488]  ffff880232b04000 ffff8800a6369b48 ffff8802301ac000
> 00000000e0000000
> [  931.032498]  ffff8800b870d000 ffffffff8105f107 ffffffffa0392f9b
> ffffffff00000018
> [  931.032508] Call Trace:
> [  931.032522]  [<ffffffff814b9b42>] ? dump_stack+0x41/0x51
> [  931.032532]  [<ffffffff8105f0a2>] ? warn_slowpath_common+0x72/0x90
> [  931.032541]  [<ffffffff8105f107>] ? warn_slowpath_fmt+0x47/0x50
> [  931.032576]  [<ffffffffa0366782>] ? gen4_read32+0x32/0xa0 [i915]
> [  931.032609]  [<ffffffffa034f2f2>] ? i965_enable_backlight+0x122/0x150 [i915]
> [  931.032644]  [<ffffffffa035025c>] ?
> intel_panel_enable_backlight+0x9c/0xe0 [i915]
> [  931.032676]  [<ffffffffa03663c0>] ? gen4_write64+0x90/0x90 [i915]
> [  931.032709]  [<ffffffffa0330181>] ? i9xx_crtc_enable+0x2e1/0x400 [i915]
> [  931.032743]  [<ffffffffa03329ee>] ? __intel_set_mode+0x85e/0x15a0 [i915]
> [  931.032779]  [<ffffffffa0338c49>] ?
> intel_modeset_setup_hw_state+0xb09/0xc10 [i915]
> [  931.032808]  [<ffffffffa02fd2ca>] ? __i915_drm_thaw+0x15a/0x210 [i915]
> [  931.032834]  [<ffffffffa02fd3d1>] ? i915_resume+0x51/0x70 [i915]
> [  931.032844]  [<ffffffff812b0da0>] ? pci_pm_suspend_noirq+0x190/0x190
> [  931.032854]  [<ffffffff8136cd8e>] ? dpm_run_callback+0x2e/0x70
> [  931.032862]  [<ffffffff8136ce9c>] ? device_resume+0x8c/0x180
> [  931.032870]  [<ffffffff8136cfa4>] ? async_resume+0x14/0x40
> [  931.032880]  [<ffffffff8108503d>] ? async_run_entry_fn+0x2d/0x120
> [  931.032890]  [<ffffffff81078b9d>] ? process_one_work+0x16d/0x420
> [  931.032899]  [<ffffffff81079756>] ? worker_thread+0x116/0x3b0
> [  931.032908]  [<ffffffff81079640>] ? rescuer_thread+0x330/0x330
> [  931.032917]  [<ffffffff8107f911>] ? kthread+0xc1/0xe0
> [  931.032925]  [<ffffffff8107f850>] ? kthread_create_on_node+0x180/0x180
> [  931.032934]  [<ffffffff814c73cc>] ? ret_from_fork+0x7c/0xb0
> [  931.032943]  [<ffffffff8107f850>] ? kthread_create_on_node+0x180/0x180
> [  931.032950] ---[ end trace a83af26b25b25474 ]---
>
> My hardware is a Lenovo T400 with a GM45.
>
> Does this mean anything to you? Please let me know if there is
> anything else you need.
>
> Regards,
> Pedro
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center

Re: WARNING on i915 - intel_panel

[Pedro Ribeiro]

On 26 May 2014 10:22, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Sat, 24 May 2014, Pedro Ribeiro <pedrib@gmail.com> wrote:
>> Hi,
>>
>> I'm getting this error consistently with the Debian 3.14.4 after
>> resuming from hibernation:
>
> Does this ever happen on a fresh boot or when resuming from suspend to
> ram?
>
> BR,
> Jani.
>

Hi Jani,

it seems to happen only on resume from disk (after waking up from
hibernation, not suspend to ram), and only from the 2nd resume
forward. It doesn't happen on fresh boot.

Regards,
Pedro

>>
>> [  931.032142] ------------[ cut here ]------------
>> [  931.032209] WARNING: CPU: 0 PID: 4715 at
>> /build/linux-Zc5oK7/linux-3.14.4/drivers/gpu/drm/i915/intel_panel.c:723
>> i965_enable_backlight+0x122/0x150 [i915]()
>> [  931.032219] backlight already enabled
>> [  931.032223] Modules linked in: ctr ccm cpufreq_stats
>> cpufreq_userspace cpufreq_conservative cpufreq_powersave pci_stub
>> vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc
>> nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp
>> xt_conntrack iptable_filter iptable_nat nf_conntrack_ipv4
>> nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables fuse
>> vmwgfx ttm vmxnet3 tp_smapi(O) thinkpad_ec(O) loop ppdev lp btusb
>> bluetooth 6lowpan_iphc crc16 snd_hda_codec_conexant
>> snd_hda_codec_generic coretemp kvm_intel uvcvideo kvm
>> videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media
>> psmouse serio_raw arc4 evdev iwldvm snd_hda_intel snd_hda_codec
>> snd_hwdep snd_pcm_oss thinkpad_acpi mac80211 snd_mixer_oss nvram
>> snd_pcm snd_seq_midi i2c_i801 snd_seq_midi_event lpc_ich snd_rawmidi
>> mfd_core snd_seq snd_seq_device snd_timer iwlwifi cfg80211 snd wmi
>> soundcore rfkill battery ac parport_pc tpm_tis parport i915 tpm video
>> drm_kms_helper drm i2c_algo_bit i2c_core acpi_cpufreq mei_me mei
>> processor button xfs crc32c libcrc32c lzo sg hid_generic usbhid hid
>> sd_mod crct10dif_generic sr_mod crc_t10dif cdrom crct10dif_common
>> firewire_ohci firewire_core crc_itu_t ahci libahci libata scsi_mod
>> thermal thermal_sys uhci_hcd ehci_pci ehci_hcd usbcore usb_common
>> e1000e ptp pps_core
>> [  931.032448] CPU: 0 PID: 4715 Comm: kworker/u8:89 Tainted: G
>>   O 3.14-1-amd64 #1 Debian 3.14.4-1
>> [  931.032456] Hardware name: LENOVO 7417PLU/7417PLU, BIOS 7VET95WW
>> (3.25 ) 10/10/2012
>> [  931.032470] Workqueue: events_unbound async_run_entry_fn
>> [  931.032476]  0000000000000009 ffffffff814b9b42 ffff8800a6369af8
>> ffffffff8105f0a2
>> [  931.032488]  ffff880232b04000 ffff8800a6369b48 ffff8802301ac000
>> 00000000e0000000
>> [  931.032498]  ffff8800b870d000 ffffffff8105f107 ffffffffa0392f9b
>> ffffffff00000018
>> [  931.032508] Call Trace:
>> [  931.032522]  [<ffffffff814b9b42>] ? dump_stack+0x41/0x51
>> [  931.032532]  [<ffffffff8105f0a2>] ? warn_slowpath_common+0x72/0x90
>> [  931.032541]  [<ffffffff8105f107>] ? warn_slowpath_fmt+0x47/0x50
>> [  931.032576]  [<ffffffffa0366782>] ? gen4_read32+0x32/0xa0 [i915]
>> [  931.032609]  [<ffffffffa034f2f2>] ? i965_enable_backlight+0x122/0x150 [i915]
>> [  931.032644]  [<ffffffffa035025c>] ?
>> intel_panel_enable_backlight+0x9c/0xe0 [i915]
>> [  931.032676]  [<ffffffffa03663c0>] ? gen4_write64+0x90/0x90 [i915]
>> [  931.032709]  [<ffffffffa0330181>] ? i9xx_crtc_enable+0x2e1/0x400 [i915]
>> [  931.032743]  [<ffffffffa03329ee>] ? __intel_set_mode+0x85e/0x15a0 [i915]
>> [  931.032779]  [<ffffffffa0338c49>] ?
>> intel_modeset_setup_hw_state+0xb09/0xc10 [i915]
>> [  931.032808]  [<ffffffffa02fd2ca>] ? __i915_drm_thaw+0x15a/0x210 [i915]
>> [  931.032834]  [<ffffffffa02fd3d1>] ? i915_resume+0x51/0x70 [i915]
>> [  931.032844]  [<ffffffff812b0da0>] ? pci_pm_suspend_noirq+0x190/0x190
>> [  931.032854]  [<ffffffff8136cd8e>] ? dpm_run_callback+0x2e/0x70
>> [  931.032862]  [<ffffffff8136ce9c>] ? device_resume+0x8c/0x180
>> [  931.032870]  [<ffffffff8136cfa4>] ? async_resume+0x14/0x40
>> [  931.032880]  [<ffffffff8108503d>] ? async_run_entry_fn+0x2d/0x120
>> [  931.032890]  [<ffffffff81078b9d>] ? process_one_work+0x16d/0x420
>> [  931.032899]  [<ffffffff81079756>] ? worker_thread+0x116/0x3b0
>> [  931.032908]  [<ffffffff81079640>] ? rescuer_thread+0x330/0x330
>> [  931.032917]  [<ffffffff8107f911>] ? kthread+0xc1/0xe0
>> [  931.032925]  [<ffffffff8107f850>] ? kthread_create_on_node+0x180/0x180
>> [  931.032934]  [<ffffffff814c73cc>] ? ret_from_fork+0x7c/0xb0
>> [  931.032943]  [<ffffffff8107f850>] ? kthread_create_on_node+0x180/0x180
>> [  931.032950] ---[ end trace a83af26b25b25474 ]---
>>
>> My hardware is a Lenovo T400 with a GM45.
>>
>> Does this mean anything to you? Please let me know if there is
>> anything else you need.
>>
>> Regards,
>> Pedro
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Jani Nikula, Intel Open Source Technology Center

Re: WARNING on i915 - intel_panel

[Daniel Vetter]

On Mon, May 26, 2014 at 8:07 PM, Pedro Ribeiro <pedrib@gmail.com> wrote:
> On 26 May 2014 10:22, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> On Sat, 24 May 2014, Pedro Ribeiro <pedrib@gmail.com> wrote:
>>> Hi,
>>>
>>> I'm getting this error consistently with the Debian 3.14.4 after
>>> resuming from hibernation:
>>
>> Does this ever happen on a fresh boot or when resuming from suspend to
>> ram?
>>
>> BR,
>> Jani.
>>
>
> Hi Jani,
>
> it seems to happen only on resume from disk (after waking up from
> hibernation, not suspend to ram), and only from the 2nd resume
> forward. It doesn't happen on fresh boot.

Can you please boot with drm.debug=0xe added to your kernel cmdline,
reproduce the issue (i.e. do 2 suspend-to-disk cycles) and then attach
the complete dmesg. You probably need to grab it from logfiles on the
disk to avoid the beginning getting cut off.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

Re: WARNING on i915 - intel_panel

[Pedro Ribeiro]

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

On 26 May 2014 19:19, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Mon, May 26, 2014 at 8:07 PM, Pedro Ribeiro <pedrib@gmail.com> wrote:
>> On 26 May 2014 10:22, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>>> On Sat, 24 May 2014, Pedro Ribeiro <pedrib@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> I'm getting this error consistently with the Debian 3.14.4 after
>>>> resuming from hibernation:
>>>
>>> Does this ever happen on a fresh boot or when resuming from suspend to
>>> ram?
>>>
>>> BR,
>>> Jani.
>>>
>>
>> Hi Jani,
>>
>> it seems to happen only on resume from disk (after waking up from
>> hibernation, not suspend to ram), and only from the 2nd resume
>> forward. It doesn't happen on fresh boot.
>
> Can you please boot with drm.debug=0xe added to your kernel cmdline,
> reproduce the issue (i.e. do 2 suspend-to-disk cycles) and then attach
> the complete dmesg. You probably need to grab it from logfiles on the
> disk to avoid the beginning getting cut off.

Hi Daniel,

sorry for my ignorance, but do you know where in a Debian system would
I have the full log output since boot time? The /var/log/dmesg does
not seem to contain all the output in the "dmesg" command.

Here is a cropped version that shows part of the debug and the error.

Regards,
Pedro


> Thanks, Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch

[-- Attachment #2: dmesg.tar.gz --]
[-- Type: application/x-gzip, Size: 17442 bytes --]

[-- Attachment #3: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: WARNING on i915 - intel_panel

[Daniel Vetter]

On Mon, May 26, 2014 at 9:07 PM, Pedro Ribeiro <pedrib@gmail.com> wrote:
> sorry for my ignorance, but do you know where in a Debian system would
> I have the full log output since boot time? The /var/log/dmesg does
> not seem to contain all the output in the "dmesg" command.

/var/log/kern.log, althought that contains all of dmesg since the last
rotation, so you need to cut away a lot at the top until you hit the
boot messages for the current kernel boot.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

Re: WARNING on i915 - intel_panel

[Pedro Ribeiro]

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

On 26 May 2014 20:14, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Mon, May 26, 2014 at 9:07 PM, Pedro Ribeiro <pedrib@gmail.com> wrote:
>> sorry for my ignorance, but do you know where in a Debian system would
>> I have the full log output since boot time? The /var/log/dmesg does
>> not seem to contain all the output in the "dmesg" command.
>
> /var/log/kern.log, althought that contains all of dmesg since the last
> rotation, so you need to cut away a lot at the top until you hit the
> boot messages for the current kernel boot.
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch


Kern.log is attached, but as you can see it does not contain the same
verbose drm debug information as dmesg... Should I just keep piping
dmesg to a file and then cat it all together?
I never really understood why there are so many logs: kern, messages,
syslog, instead of a single central log.

[-- Attachment #2: kern.log.tar.gz --]
[-- Type: application/x-gzip, Size: 4115 bytes --]

[-- Attachment #3: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: WARNING on i915 - intel_panel

[Daniel Vetter]

On Mon, May 26, 2014 at 9:44 PM, Pedro Ribeiro <pedrib@gmail.com> wrote:
> Kern.log is attached, but as you can see it does not contain the same
> verbose drm debug information as dmesg... Should I just keep piping
> dmesg to a file and then cat it all together?
> I never really understood why there are so many logs: kern, messages,
> syslog, instead of a single central log.

Indeed, that one isn't useful either :( Next idea: Increase the
in-kernel dmesg buffer size and hope it all fits with log_buf_size=4M
(on the kernel cmdline). Maybe you can go even higher, not sure.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

Re: WARNING on i915 - intel_panel

[Pedro Ribeiro]

On 27 May 2014 08:15, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Mon, May 26, 2014 at 9:44 PM, Pedro Ribeiro <pedrib@gmail.com> wrote:
>> Kern.log is attached, but as you can see it does not contain the same
>> verbose drm debug information as dmesg... Should I just keep piping
>> dmesg to a file and then cat it all together?
>> I never really understood why there are so many logs: kern, messages,
>> syslog, instead of a single central log.
>
> Indeed, that one isn't useful either :( Next idea: Increase the
> in-kernel dmesg buffer size and hope it all fits with log_buf_size=4M
> (on the kernel cmdline). Maybe you can go even higher, not sure.
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch

Daniel, doesn't seem like that is working.

I'll leave it be and try to test new kernels and see if it just goes
away. I'll report back if it doesn't.

Regards,
Pedro

Re: WARNING on i915 - intel_panel

[Pedro Ribeiro]

[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]

On 2 June 2014 21:15, Pedro Ribeiro <pedrib@gmail.com> wrote:
> On 27 May 2014 08:15, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Mon, May 26, 2014 at 9:44 PM, Pedro Ribeiro <pedrib@gmail.com> wrote:
>>> Kern.log is attached, but as you can see it does not contain the same
>>> verbose drm debug information as dmesg... Should I just keep piping
>>> dmesg to a file and then cat it all together?
>>> I never really understood why there are so many logs: kern, messages,
>>> syslog, instead of a single central log.
>>
>> Indeed, that one isn't useful either :( Next idea: Increase the
>> in-kernel dmesg buffer size and hope it all fits with log_buf_size=4M
>> (on the kernel cmdline). Maybe you can go even higher, not sure.
>> -Daniel
>> --
>> Daniel Vetter
>> Software Engineer, Intel Corporation
>> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
>
> Daniel, doesn't seem like that is working.
>
> I'll leave it be and try to test new kernels and see if it just goes
> away. I'll report back if it doesn't.
>
> Regards,
> Pedro

Hi Daniel,

the problem is still there with the latest 3.14.14. But the good news
is that I have finally been able to get a full dmesg log!
Please find it attached. I hope this helps and let me know what else I
need to do to assist.

The log shows two hibernate-resume cycles, and you can see the bug
being triggered at line 4274. As I said previously this looks like it
doesn't affect the operation much, although it seems to happen very
frequently as I do more hibernate cycles.

PS: if I hibernate with a external monitor connected, and resume
without that monitor connected, will the kernel handle it correctly?

Regards,
Pedro

[-- Attachment #2: dmesg.tar.gz --]
[-- Type: application/x-gzip, Size: 63428 bytes --]

[-- Attachment #3: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: WARNING on i915 - intel_panel

[Daniel Vetter]

On Mon, Aug 11, 2014 at 12:38:41AM +0100, Pedro Ribeiro wrote:
> On 2 June 2014 21:15, Pedro Ribeiro <pedrib@gmail.com> wrote:
> > On 27 May 2014 08:15, Daniel Vetter <daniel@ffwll.ch> wrote:
> >> On Mon, May 26, 2014 at 9:44 PM, Pedro Ribeiro <pedrib@gmail.com> wrote:
> >>> Kern.log is attached, but as you can see it does not contain the same
> >>> verbose drm debug information as dmesg... Should I just keep piping
> >>> dmesg to a file and then cat it all together?
> >>> I never really understood why there are so many logs: kern, messages,
> >>> syslog, instead of a single central log.
> >>
> >> Indeed, that one isn't useful either :( Next idea: Increase the
> >> in-kernel dmesg buffer size and hope it all fits with log_buf_size=4M
> >> (on the kernel cmdline). Maybe you can go even higher, not sure.
> >> -Daniel
> >> --
> >> Daniel Vetter
> >> Software Engineer, Intel Corporation
> >> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
> >
> > Daniel, doesn't seem like that is working.
> >
> > I'll leave it be and try to test new kernels and see if it just goes
> > away. I'll report back if it doesn't.
> >
> > Regards,
> > Pedro
> 
> Hi Daniel,
> 
> the problem is still there with the latest 3.14.14. But the good news
> is that I have finally been able to get a full dmesg log!
> Please find it attached. I hope this helps and let me know what else I
> need to do to assist.
> 
> The log shows two hibernate-resume cycles, and you can see the bug
> being triggered at line 4274. As I said previously this looks like it
> doesn't affect the operation much, although it seems to happen very
> frequently as I do more hibernate cycles.

Yeah, log looks interesting, but I don't immediately see what's wrong. Can
you please fiel a new bug on bugs.freedeskopt.org against DRI -> DRM
(Intel) and please don't forget to put [regression] into the summary.

Also, if you manually disable the lvds with e.g.

$ xrandr --output LVDS1 --off ; xrandr --output LVDS1 --auto

does it happen, too? Or do you only see this over a hibernate cycle?

> PS: if I hibernate with a external monitor connected, and resume
> without that monitor connected, will the kernel handle it correctly?

Well the kernel won't do much, but it will generate a hotplug event to
inform userspace that the configuration changed. Then userspace needs to
figure out what to do - by default we keep pumping pixels to the screen
presuming that the cable fell out for a bit and that the user will replug.
But a good DE reconfigures or shows you a dialog box on one of the
remaining enabled screens.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

Re: WARNING on i915 - intel_panel

[Pedro Ribeiro]

 Daniel,
>>
>> the problem is still there with the latest 3.14.14. But the good news
>> is that I have finally been able to get a full dmesg log!
>> Please find it attached. I hope this helps and let me know what else I
>> need to do to assist.
>>
>> The log shows two hibernate-resume cycles, and you can see the bug
>> being triggered at line 4274. As I said previously this looks like it
>> doesn't affect the operation much, although it seems to happen very
>> frequently as I do more hibernate cycles.
>
> Yeah, log looks interesting, but I don't immediately see what's wrong. Can
> you please fiel a new bug on bugs.freedeskopt.org against DRI -> DRM
> (Intel) and please don't forget to put [regression] into the summary.
>
> Also, if you manually disable the lvds with e.g.
>
> $ xrandr --output LVDS1 --off ; xrandr --output LVDS1 --auto
>
> does it happen, too? Or do you only see this over a hibernate cycle?

I only see this over a hibernate cycle.

There was a bug opened by another user for this
https://bugs.freedesktop.org/show_bug.cgi?id=80930

So I just added my information there.

Regards,
Pedro