Re: [Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

2016-04-27 Thread Jani Nikula 
On Wed, 27 Apr 2016, Florian Zumbiehl  wrote:
>> Florian, if you're using drm-intel-nigthly submit a bug at
>> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI, with DRM/intel
>> as component. This way we can track some kind of progress/regress. The FIFO
>
> Gee ... is there any way without "creating an account"? Having to create
> accounts everywhere to be able to communicate with people just sucks. I
> mean, do you want to create an account in my todo tracker and use my todo
> tracker's web interface to coordinate the bug investigation? Use whatever
> software you like for managing your todo lists, but please, don't bother me
> with having to use it for you.

The Bugzilla at https://bugs.freedesktop.org is our tool of choice for
tracking bugs in drm/i915. It's your choice to not create an account
there, but please, don't expect us to work as a proxy between you and
bugzilla either. It's a much bigger and unscalable inconvenience for us
than it is for you to create that account.

I won't claim your bug will be fixed any faster if you choose to create
an account, but it's much more likely it won't get lost and forgotten in
the never ending stream of emails we all get.

> You mean the ones I reported a month ago should be fixed? Should I try a
> newer nightly to check?

Yes, please.

I'd also like to get a full dmesg from you, with drm.debug=14 module
parameter set, all the way from boot to the problem.

However, personally I find it a bit obnoxious to send big logs by mail
to hundreds or thousands of other people on the lists who really aren't
at all interested in them. Maybe you don't mind bothering them? It's
also not good to hide it away in my private inbox alone, because there
are other developers who will be interested. It has also proven to be
problematic to upload files to pastebins etc. where they expire at some
point in time, usually when we'd like to have a look.

Again, the obvious solution to the above is to file that bug and attach
the dmesg there, at the unfortunate slight inconvenience of you creating
an account there.

Your call.


BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

2016-04-27 Thread Florian Zumbiehl 
Hi,

> Florian, if you're using drm-intel-nigthly submit a bug at
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI, with DRM/intel
> as component. This way we can track some kind of progress/regress. The FIFO

Gee ... is there any way without "creating an account"? Having to create
accounts everywhere to be able to communicate with people just sucks. I
mean, do you want to create an account in my todo tracker and use my todo
tracker's web interface to coordinate the bug investigation? Use whatever
software you like for managing your todo lists, but please, don't bother me
with having to use it for you.

> underruns should've have been fixed, but maybe there's something related
> to your platform.

You mean the ones I reported a month ago should be fixed? Should I try a
newer nightly to check?

What about the Xv stuttering?

Regards, Florian
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

2016-04-27 Thread Marius Vlad 
Florian, if you're using drm-intel-nigthly submit a bug at
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI, with DRM/intel
as component. This way we can track some kind of progress/regress. The FIFO
underruns should've have been fixed, but maybe there's something related
to your platform.

On Tue, Apr 12, 2016 at 03:23:08AM +0200, Florian Zumbiehl wrote:
> Hi,
> 
> > > We've fixed piles of those in recent kernels, but didn't backport all the
> > > fixes (since usually it's a silent failure, but it can correlate with
> > > black screens).
> > 
> > Not quite completely, it seems ...
> > 
> > I have built drm-intel-nightly (f261f82359), and I'm getting this:
> [...]
> 
> ping?
> 
> Regards, Florian
> ___
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx


signature.asc
Description: Digital signature
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

2016-04-11 Thread Florian Zumbiehl 
Hi,

> > We've fixed piles of those in recent kernels, but didn't backport all the
> > fixes (since usually it's a silent failure, but it can correlate with
> > black screens).
> 
> Not quite completely, it seems ...
> 
> I have built drm-intel-nightly (f261f82359), and I'm getting this:
[...]

ping?

Regards, Florian
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

[Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

2016-03-30 Thread Florian Zumbiehl 
Hi,

> We've fixed piles of those in recent kernels, but didn't backport all the
> fixes (since usually it's a silent failure, but it can correlate with
> black screens).

Not quite completely, it seems ...

I have built drm-intel-nightly (f261f82359), and I'm getting this:

| [   15.855007] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
| [   15.855007] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* 
pipe B underrun
| [   15.855007] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun
| [   15.863175] [drm] RC6 disabled, disabling runtime PM support
| [   15.863543] [drm] initialized overlay support
| [   15.98] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
| [   15.997130] i915 :00:02.0: fb0: inteldrmfb frame buffer device
| [   16.061856] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* 
pipe A underrun
| [   16.725274] [drm] Initialized i915 1.6.0 20160330 for :00:02.0 on 
minor 0
| [   16.805727] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun

> > | [ 2520.457732] WARNING: CPU: 0 PID: 3193 at 
> > drivers/gpu/drm/i915/i915_gem.c:4508 i915_gem_free_object+0x277/0x280 
> > [i915]()
> > | [ 2520.457736] WARN_ON(obj->frontbuffer_bits)
> 
> Hm, this one should be fixed, and the patches should all be correctly
> marked for stable. Either there's a backlog somewhere, or we failed.
> 
> Would be great if you can test a drm-intel-nightly build (or 4.6-rc1) for
> either and confirm that they're gone. And for the later we really should
> hunt down the bugfix if it's stuck.

| [  141.999803] [ cut here ]
| [  141.16] WARNING: CPU: 0 PID: 3349 at 
drivers/gpu/drm/i915/i915_gem.c:4568 i915_gem_free_object+0x25f/0x270 [i915]
| [  141.23] WARN_ON(obj->frontbuffer_bits)
| [  141.28] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CT 
iptable_raw xt_nat xt_tcpudp xt_addrtype iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables dummy tun 
nfsd exportfs nfs lockd grace sunrpc ipv6 fbcon bitblit softcursor font loop 
mousedev i915 i2c_algo_bit drm_kms_helper cfbfillrect syscopyarea cfbimgblt 
sysfillrect sysimgblt fb_sys_fops cfbcopyarea snd_intel8x0 drm snd_ac97_codec 
ac97_bus i2c_core snd_pcm_oss fb snd_mixer_oss fbdev snd_pcm ipw2200 snd_timer 
snd libipw soundcore lib80211 nsc_ircc thinkpad_acpi cfg80211 pcmcia psmouse 
sdhci_pci irda uhci_hcd ehci_pci sdhci crc_ccitt ehci_hcd serio_raw e1000 
mmc_core nvram evdev usbcore parport_pc yenta_socket hwmon parport pcmcia_rsrc 
video usb_common pcmcia_core backlight ac battery acpi_cpufreq intel_agp 
processor button intel_gtt agpgart twofish_generic twofish_i586 twofish_common 
xts gf128mul dm_crypt dm_mod thermal
| [  142.000114] CPU: 0 PID: 3349 Comm: Xorg Not tainted 4.6.0-rc1+ #1
| [  142.000120] Hardware name: IBM 23716JG/23716JG, BIOS 1UETD3WW (2.08 ) 
12/21/2006
| [  142.000127]  c11b8f7a c1037247 f8dea59b c0051dc4 0d15 f8dda000 
11d8 f8d3ff2f
| [  142.000141]  f8d3ff2f 11d8 f3ef1dcc f3ef1e30 f3ef1dcc f3ef1dc0 
c1037309 0009
| [  142.000154]   c0051dac f8dea59b c0051dc4 f8d3ff2f f8dda000 
11d8 f8dea59b
| [  142.000168] Call Trace:
| [  142.000185]  [] ? dump_stack+0xa/0x20
| [  142.000197]  [] ? __warn+0xe7/0x100
| [  142.000269]  [] ? i915_gem_free_object+0x25f/0x270 [i915]
| [  142.000337]  [] ? i915_gem_free_object+0x25f/0x270 [i915]
| [  142.000347]  [] ? warn_slowpath_fmt+0x39/0x40
| [  142.000416]  [] ? i915_gem_free_object+0x25f/0x270 [i915]
| [  142.000452]  [] ? drm_gem_object_free+0x23/0x40 [drm]
| [  142.000478]  [] ? 
drm_gem_object_handle_unreference_unlocked+0xcf/0xe0 [drm]
| [  142.000504]  [] ? drm_gem_object_release_handle+0x47/0x90 [drm]
| [  142.000529]  [] ? drm_gem_handle_delete+0x4e/0x80 [drm]
| [  142.000554]  [] ? drm_gem_handle_create+0x30/0x30 [drm]
| [  142.000580]  [] ? drm_ioctl+0x230/0x570 [drm]
| [  142.000606]  [] ? drm_gem_handle_create+0x30/0x30 [drm]
| [  142.000618]  [] ? unmap_page_range+0x433/0x530
| [  142.000627]  [] ? __rb_erase_color+0xf3/0x250
| [  142.000637]  [] ? unlink_file_vma+0x36/0x70
| [  142.000645]  [] ? tlb_finish_mmu+0x9/0x30
| [  142.000671]  [] ? drm_ioctl_permit+0x80/0x80 [drm]
| [  142.000682]  [] ? do_vfs_ioctl+0x80/0x6a0
| [  142.000690]  [] ? timerqueue_del+0x20/0x70
| [  142.000699]  [] ? kmem_cache_free+0x95/0xa0
| [  142.000708]  [] ? remove_vma+0x3e/0x50
| [  142.000717]  [] ? do_munmap+0x219/0x2d0
| [  142.000726]  [] ? SyS_ioctl+0x43/0x80
| [  142.000735]  [] ? do_fast_syscall_32+0x82/0x110
| [  142.000745]  [] ? sysenter_past_esp+0x40/0x6a
| [  142.000777] ---[ end trace c0f77cdb5434 ]---

Each time an Xv window disappears from view--sometimes with slight
variations in the stacktrace. Do you need full debug info or a bunch more
stacktraces or is this enough to get an idea?

> > Also, I have occasional X