Your message dated Fri, 23 Apr 2021 14:19:05 +0200 with message-id <[email protected]> and subject line Re: Bug#832905: linux-image-686-pae: kernel warning at drm_irq.c has caused the Debian Bug report #832905, regarding linux-image-686-pae: kernel warning at drm_irq.c to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 832905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832905 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-image-686-pae Version: 4.6+74 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Vinagre session to x11vnc * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? Kernel warning, stack trace, x11vnc crash * What outcome did you expect instead? x11vnc stays up *** End of the template - remove these template lines *** Attached is the kernel stack trace. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.6.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-686-pae depends on: ii linux-image-4.6.0-1-686-pae 4.6.4-1 linux-image-686-pae recommends no packages. linux-image-686-pae suggests no packages. -- no debconf informationJul 29 09:33:59 d1520deb kernel: [ 40.316764] ------------[ cut here ]------------ Jul 29 09:33:59 d1520deb kernel: [ 40.316806] WARNING: CPU: 0 PID: 1989 at /build/linux-sI189k/linux-4.6.4/drivers/gpu/drm/drm_irq.c:1326 dr m_wait_one_vblank+0x191/0x1a0 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.316813] vblank wait timed out on crtc 0 Jul 29 09:33:59 d1520deb kernel: [ 40.317049] CPU: 0 PID: 1989 Comm: Xorg Tainted: G W OE 4.6.0-1-686-pae #1 Debian 4.6.4-1 Jul 29 09:33:59 d1520deb kernel: [ 40.317056] Hardware name: Dell Inc. Inspiron 1520 /0KY767, BIOS A03 08/16/2007 Jul 29 09:33:59 d1520deb kernel: [ 40.317063] 00003286 e186d079 f6697abc c12dbeac f6697ad0 00000000 c106cc4a f8662368 Jul 29 09:33:59 d1520deb kernel: [ 40.317080] f6697af0 000007c5 f8661ff0 0000052e f86383d1 0000052e 00000009 f86383d1 Jul 29 09:33:59 d1520deb kernel: [ 40.317097] f3475000 00000000 00000000 f6697adc c106ccb6 00000009 00000000 f6697ad0 Jul 29 09:33:59 d1520deb kernel: [ 40.317113] Call Trace: Jul 29 09:33:59 d1520deb kernel: [ 40.317130] [<c12dbeac>] ? dump_stack+0x55/0x79 Jul 29 09:33:59 d1520deb kernel: [ 40.317141] [<c106cc4a>] ? __warn+0xea/0x110 Jul 29 09:33:59 d1520deb kernel: [ 40.317165] [<f86383d1>] ? drm_wait_one_vblank+0x191/0x1a0 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317187] [<f86383d1>] ? drm_wait_one_vblank+0x191/0x1a0 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317196] [<c106ccb6>] ? warn_slowpath_fmt+0x46/0x60 Jul 29 09:33:59 d1520deb kernel: [ 40.317218] [<f86383d1>] ? drm_wait_one_vblank+0x191/0x1a0 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317229] [<c10ab8c0>] ? wake_atomic_t_function+0x70/0x70 Jul 29 09:33:59 d1520deb kernel: [ 40.317295] [<f88b6dec>] ? intel_get_load_detect_pipe+0x7bc/0x7f0 [i915] Jul 29 09:33:59 d1520deb kernel: [ 40.317355] [<f88f2eea>] ? intel_tv_detect+0x10a/0x690 [i915] Jul 29 09:33:59 d1520deb kernel: [ 40.317388] [<f8590359>] ? __ext4_handle_dirty_metadata+0x39/0x200 [ext4] Jul 29 09:33:59 d1520deb kernel: [ 40.317407] [<f85fce68>] ? drm_helper_probe_single_connector_modes+0x2e8/0x4d0 [drm_kms_helper] Jul 29 09:33:59 d1520deb kernel: [ 40.317419] [<c11fed9a>] ? generic_write_end+0xca/0x110 Jul 29 09:33:59 d1520deb kernel: [ 40.317446] [<f863edfc>] ? _object_find+0x5c/0xa0 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317470] [<f8644acd>] ? drm_mode_getconnector+0x28d/0x320 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317481] [<c11b1a5a>] ? kmem_cache_alloc_trace+0xaa/0x3f0 Jul 29 09:33:59 d1520deb kernel: [ 40.317494] [<c15709f7>] ? __ww_mutex_lock+0x17/0xa0 Jul 29 09:33:59 d1520deb kernel: [ 40.317517] [<f865020d>] ? drm_modeset_lock+0x8d/0xf0 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317541] [<f8644840>] ? drm_mode_getcrtc+0x140/0x140 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317560] [<f8636529>] ? drm_ioctl+0x149/0x4f0 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317584] [<f8644840>] ? drm_mode_getcrtc+0x140/0x140 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317595] [<c1199e90>] ? page_add_new_anon_rmap+0x70/0xb0 Jul 29 09:33:59 d1520deb kernel: [ 40.317616] [<f86363e0>] ? drm_getmap+0xc0/0xc0 [drm] Jul 29 09:33:59 d1520deb kernel: [ 40.317625] [<c11ddc6c>] ? do_vfs_ioctl+0x8c/0x730 Jul 29 09:33:59 d1520deb kernel: [ 40.317634] [<c11ca6af>] ? new_sync_write+0x8f/0xe0 Jul 29 09:33:59 d1520deb kernel: [ 40.317643] [<c11cb050>] ? vfs_write+0x150/0x1b0 Jul 29 09:33:59 d1520deb kernel: [ 40.317651] [<c11de378>] ? SyS_ioctl+0x68/0x80 Jul 29 09:33:59 d1520deb kernel: [ 40.317663] [<c100383d>] ? do_fast_syscall_32+0x8d/0x140 Jul 29 09:33:59 d1520deb kernel: [ 40.317671] [<c1572e6a>] ? sysenter_past_esp+0x47/0x75 Jul 29 09:33:59 d1520deb kernel: [ 40.317676] ---[ end trace 1ca20551d8427318 ]---
--- End Message ---
--- Begin Message ---Source: linux Source-Version: 5.2.6-1 On Fri, Jul 29, 2016 at 10:18:58AM -0400, Dominique Brazziel wrote: > Package: linux-image-686-pae > Version: 4.6+74 > Severity: wishlist > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > Vinagre session to x11vnc > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > * What was the outcome of this action? > Kernel warning, stack trace, x11vnc crash > > * What outcome did you expect instead? > x11vnc stays up > > *** End of the template - remove these template lines *** > > Attached is the kernel stack trace. If I read the related upstream bugs correctly thiss was fixed upstream in 5.1-rc1. Closing the bug, feel free to reopen if the issue still is present. Regards, Salvatore
--- End Message ---
