Re: 3.13.1 - WARNING at drivers/gpu/drm/i915/i915_irq.c:1240

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Montag, den 10.02.2014, 09:58 +0100 schrieb Daniel Vetter:
> On Sat, Feb 08, 2014 at 07:30:54PM +0100, Thomas Meyer wrote:
> > Am Samstag, den 08.02.2014, 17:38 +0100 schrieb Daniel Vetter:
> > > On Sat, Feb 8, 2014 at 12:51 PM, Thomas Meyer <thomas@xxxxxxxx> wrote:
> > > > Am Freitag, den 07.02.2014, 09:46 +0100 schrieb Daniel Vetter:
> > > >> On Thu, Feb 06, 2014 at 11:29:34PM +0100, Thomas Meyer wrote:
> > > >> > Am Dienstag, den 04.02.2014, 21:17 +0100 schrieb Daniel Vetter:
> > > >> > > On Tue, Feb 04, 2014 at 08:37:02PM +0100, Thomas Meyer wrote:
> > > >> > > >
> > > >> > > > Hi,
> > > >> > > >
> > > >> > > > I see a *lot* of these warning in 3.13.1.
> > > >> > > > 3.12.x never showed this problem.
> > > >> > > > Any ideas?!
> > > >> > >
> > > >> > > Can you please try latest the drm-intel-nightly git branch from
> > > >> > > git://anongit.freedesktop.org/drm-intel ?
> > > >> > >
> > > >> > > If that one's still affected then please boot with drm.debug=0xe added to
> > > >> > > your kernel cmdline, reproduce the WARN and attach the complete dmesg.
> > > >> > >
> > > >> >
> > > >> > Hi,
> > > >> >
> > > >> > with 3.13.0-drm-00890-g4055ebc (drm-intel-nightly) I get these warnings:
> > > >>
> > > >> Can you please boot with drm.debug=0xe and attach the complete dmesg?
> > > >
> > > > here you go. dmesg in attachment.
> > > 
> > > Hm, this one doesn't contain the WARN backtrace when the driver loads.
> > > Does it only happen occasionally? If so can you please try to grab a
> > > dmesg with drm debugging enabled and the backtrace in it?
> > 
> > Hi,
> > 
> > the WARNINGs did only show in 3.13.1 without the debug option. With the
> > debug option turned on the WARNINGs show up in neither drm-intel-nightly
> > nor 3.13.2.
> > So either the debug option somehow interfere with the WARNINGs or the
> > bug was fixed between 3.13.1 and drm-intel-nightly resp. 3.13.2.
> 
> Can you please double-check that the bug is gone in 3.13.2, even without
> the debug output enabled? I've looked at the stable patches and there's
> nothing for i915 between .1 and .2.
> -Daniel

Hi,

this WARNING seems to be triggered somehow sporadic...

It happened again after 5 days of uptime:

[74015.754154] WARNING: CPU: 0 PID: 15191 at
drivers/gpu/drm/i915/i915_irq.c:1240 i965_irq_handler+0x4ee/0x670()
[74015.754155] Received HPD interrupt although disabled
[74015.754190] Modules linked in: sit ip_tunnel tunnel4 ipt_MASQUERADE
pppoe pppox ppp_generic slhc tcp_lp fuse ip6t_rpfilter ip6t_REJECT
xt_conntrack ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6
ip6table_mangle ip6table_security ip6table_raw ip6table_filter
ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw
snd_hda_codec_hdmi asix usbnet snd_hda_codec_realtek snd_usb_audio
snd_usbmidi_lib mii snd_hda_intel snd_hda_codec acer_wmi snd_hwdep
kvm_intel kvm arc4 iwldvm mac80211 snd_seq sparse_keymap snd_pcm acerhdf
joydev pcspkr snd_rawmidi iwlwifi btusb snd_seq_device wmi atl1c
acpi_cpufreq bluetooth snd_page_alloc snd_timer snd cfg80211 rfkill
soundcore ipv6 xts gf128mul udl syscopyarea sysfillrect sysimgblt
[74015.754191]  drm_usb
[74015.754193] CPU: 0 PID: 15191 Comm: irq/42-i915 Tainted: G        W
3.13.3 #5
[74015.754194] Hardware name: Acer Aspire 1810T/JM11-MS, BIOS v1.3310
03/25/2010
[74015.754197]  0000000000000009 ffff8802064c3d30 ffffffff815426a4
ffff8802064c3d68
[74015.754199]  ffffffff810391fc 0000000000000005 0000000000080000
ffff880234ff4040
[74015.754201]  ffff880234ff4000 ffffffff815aa924 ffff8802064c3dc8
ffffffff81039267
[74015.754202] Call Trace:
[74015.754205]  [<ffffffff815426a4>] dump_stack+0x19/0x1b
[74015.754208]  [<ffffffff810391fc>] warn_slowpath_common+0x6c/0x90
[74015.754210]  [<ffffffff81039267>] warn_slowpath_fmt+0x47/0x50
[74015.754213]  [<ffffffff81071610>] ? irq_thread_fn+0x40/0x40
[74015.754216]  [<ffffffff8132759e>] i965_irq_handler+0x4ee/0x670
[74015.754218]  [<ffffffff81071610>] ? irq_thread_fn+0x40/0x40
[74015.754221]  [<ffffffff8107162e>] irq_forced_thread_fn+0x1e/0x50
[74015.754223]  [<ffffffff81071610>] ? irq_thread_fn+0x40/0x40
[74015.754225]  [<ffffffff81071838>] irq_thread+0xe8/0x120
[74015.754228]  [<ffffffff81071690>] ? wake_threads_waitq.part.30
+0x30/0x30
[74015.754230]  [<ffffffff81071750>] ? irq_thread_dtor+0xc0/0xc0
[74015.754233]  [<ffffffff81054dbb>] kthread+0xcb/0xf0
[74015.754236]  [<ffffffff81054cf0>] ? kthread_worker_fn+0x170/0x170
[74015.754238]  [<ffffffff81547fba>] ret_from_fork+0x7a/0xb0
[74015.754241]  [<ffffffff81054cf0>] ? kthread_worker_fn+0x170/0x170
[74015.754242] ---[ end trace 8d02e1a7e4846ea9 ]---
[74015.754712] ------------[ cut here ]------------

Rebooting into 3.13.4 now...


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




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux