WARN_ON(atomic_read(&obj->frontbuffer_bits))

WARN_ON(atomic_read(&obj->frontbuffer_bits))

[Helmut Grohne]

Hi,

after upgrading a Debian jessie system to Debian stretch, I've seen the
following output in my kern.log once. The system was responding to
network pings, but not to anything else (keyboard, ssh, ...). The hang
happened during boot (which includes starting a display manager). Most
boots don't hang.

[28883.953358] ------------[ cut here ]------------
[28883.953414] WARNING: CPU: 0 PID: 3486 at /build/linux-ttVKu9/linux-4.9.88/drivers/gpu/drm/i915/i915_gem.c:4217 i915_gem_free_object+0x23e/0x280 [i915]
[28883.953417] WARN_ON(atomic_read(&obj->frontbuffer_bits))
[28883.953420] Modules linked in:
[28883.953423]  cpufreq_conservative cpufreq_powersave cpufreq_userspace binfmt_misc joydev nls_utf8 ntfs iTCO_wdt iTCO_vendor_support arc4 iwl3945 snd_hda_codec_si3054 snd_hda_codec_realtek iwlegacy e100 i915 mac80211 snd_hda_codec_generic pcspkr snd_hda_intel snd_hda_codec i2c_i801 psmouse sr_mod mii cdrom sdhci_pci sdhci snd_hda_core cfg80211 pcmcia i2c_smbus sg mmc_core firewire_ohci firewire_core tifm_7xx1 crc_itu_t tifm_core snd_hwdep snd_pcm yenta_socket ehci_pci snd_timer drm_kms_helper uhci_hcd rfkill pcmcia_rsrc ehci_hcd pcmcia_core snd usbcore drm lpc_ich soundcore mfd_core rng_core usb_common i2c_algo_bit battery shpchp video ac button coretemp acpi_cpufreq parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb xts lrw gf128mul ablk_helper cryptd aes_i586 mbcache dm_mod sd_mod ata_generic ata_piix evdev serio_raw libata scsi_mod fan thermal
[28883.953509] CPU: 0 PID: 3486 Comm: Xorg Not tainted 4.9.0-6-686-pae #1 Debian 4.9.88-1+deb9u1
[28883.953512] Hardware name: TOSHIBA Satellite A100/MPAD-MSAE Customer Reference Boards, BIOS 2.00    08/30/2006
[28883.953515]  f3f5fd08 de2f7652 f3f5fd1c 00000000 de067a6a f8ba2c04 f3f5fd3c 00000d9e
[28883.953522]  f8b8da18 00001079 f8aec49e 00001079 00000009 f8aec49e f21c1748 f21c17c0
[28883.953529]  f21c1840 f3f5fd28 de067ad6 00000009 00000000 f3f5fd1c f8ba2c04 f3f5fd3c
[28883.953536] Call Trace:
[28883.953545]  [<de2f7652>] ? dump_stack+0x55/0x73
[28883.953551]  [<de067a6a>] ? __warn+0xea/0x110
[28883.953579]  [<f8aec49e>] ? i915_gem_free_object+0x23e/0x280 [i915]
[28883.953607]  [<f8aec49e>] ? i915_gem_free_object+0x23e/0x280 [i915]
[28883.953611]  [<de067ad6>] ? warn_slowpath_fmt+0x46/0x60
[28883.953639]  [<f8aec49e>] ? i915_gem_free_object+0x23e/0x280 [i915]
[28883.953668]  [<f8b18e14>] ? intel_user_framebuffer_destroy+0x44/0x90 [i915]
[28883.953683]  [<f868cfba>] ? drm_framebuffer_free+0x1a/0x30 [drm]
[28883.953693]  [<f8691a76>] ? __setplane_internal+0xa6/0x230 [drm]
[28883.953704]  [<f868a444>] ? drm_modeset_lock_all_ctx+0xa4/0xb0 [drm]
[28883.953714]  [<f869278d>] ? drm_mode_setplane+0x12d/0x1b0 [drm]
[28883.953723]  [<f8692660>] ? drm_plane_check_pixel_format+0x40/0x40 [drm]
[28883.953734]  [<f8676bb1>] ? drm_ioctl+0x211/0x480 [drm]
[28883.953743]  [<f8692660>] ? drm_plane_check_pixel_format+0x40/0x40 [drm]
[28883.953765]  [<f8720e90>] ? nl80211_register_beacons+0xd0/0xd0 [cfg80211]
[28883.953770]  [<de086781>] ? notifier_call_chain+0x51/0x70
[28883.953775]  [<de20656f>] ? __inode_wait_for_writeback+0x5f/0xc0
[28883.953780]  [<de0a9fd0>] ? wake_atomic_t_function+0x70/0x70
[28883.953790]  [<f86769a0>] ? drm_getunique+0x60/0x60 [drm]
[28883.953795]  [<de1efa64>] ? do_vfs_ioctl+0x94/0x730
[28883.953799]  [<de1de2e9>] ? __fput+0x169/0x210
[28883.953802]  [<de1de2e9>] ? __fput+0x169/0x210
[28883.953806]  [<de1f0160>] ? SyS_ioctl+0x60/0x70
[28883.953811]  [<de003728>] ? do_fast_syscall_32+0x98/0x160
[28883.953816]  [<de5b7b02>] ? sysenter_past_esp+0x47/0x75
[28883.953819] ---[ end trace 64366833e49e9e96 ]---

Since I've not found a similar traceback with google, I figured that
maybe you are interested in it although 4.9 is a bit dated by todays
standards.

The cpu is a T1350, lspci says

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

Hope this helps with fixing some bug

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

Re: WARN_ON(atomic_read(&obj->frontbuffer_bits))

[Jani Nikula]

On Tue, 22 May 2018, Helmut Grohne <helmut@subdivi.de> wrote:
> after upgrading a Debian jessie system to Debian stretch, I've seen the
> following output in my kern.log once. The system was responding to
> network pings, but not to anything else (keyboard, ssh, ...). The hang
> happened during boot (which includes starting a display manager). Most
> boots don't hang.

I suggest updating to a more recent kernel. You can get v4.16 from
stretch-backports.

If the problem persists, please file a bug over at [1].

BR,
Jani.


[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel


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