All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198221] New: nouveau DRM driver scheduling invalid work
Date: Thu, 21 Dec 2017 00:59:00 +0000	[thread overview]
Message-ID: <bug-198221-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=198221

            Bug ID: 198221
           Summary: nouveau DRM driver scheduling invalid work
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.15.0-rc3
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: petr@vandrovec.name
        Regression: No

Created attachment 261283
  --> https://bugzilla.kernel.org/attachment.cgi?id=261283&action=edit
Full dmesg

Hi,
   my X server just stopped responding, and ssh from another host revealed that
nouveau driver triggered kernel oops in queue_work_on.  System is using this
new kernel for less than a week.  No similar crash ever happened on the system
before.

[605148.177397] BUG: unable to handle kernel paging request at 00000000000101f8
[605148.180006] IP: queue_work_on+0x12/0x40
[605148.186405] PGD 0 P4D 0
[605148.186405] Oops: 0002 [#1] PREEMPT SMP
[605148.186405] Modules linked in: netlink_diag vmnet(OE) parport_pc
vmw_vsock_vmci_transport vmw_vmci vmmon(OE) loop tcp_diag inet_diag nfsv3 ppdev
parport xt_REDIRECT nf_nat_redirect arc4 md4 nls_iso8859_2 deflate cifs
twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64
twofish_common camellia_generic ccm rpcsec_gss_krb5 nfsv4 fuse nfs fscache
vsock camellia_aesni_avx_x86_64 camellia_x86_64 iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c serpent_avx_x86_64
serpent_sse2_x86_64 serpent_generic lrw blowfish_generic blowfish_x86_64
blowfish_common cast5_avx_x86_64 cast5_generic cast_common ablk_helper
des_generic cmac xcbc rmd160 af_key xfrm_algo binfmt_misc snd_hda_codec_hdmi
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel coretemp hwmon
[605148.234373]  snd_hda_codec x86_pkg_temp_thermal crct10dif_pclmul snd_hwdep
crc32_pclmul crc32c_intel uas ghash_clmulni_intel snd_hda_core dcdbas pcbc
snd_pcm_oss e1000e usb_storage aesni_intel snd_mixer_oss sr_mod snd_pcm
aes_x86_64 crypto_simd glue_helper input_leds cryptd snd_timer cdrom mei_me
i2c_i801 ptp tpm_tis sg snd mei pps_core tpm_tis_core tpm iTCO_wdt
iTCO_vendor_support lpc_ich mfd_core nfsd auth_rpcgss nfs_acl lockd grace
sunrpc ip_tables x_tables ipv6 crc_ccitt autofs4 [last unloaded: vmnet]
[605148.234373] CPU: 0 PID: 8021 Comm: Xorg Tainted: G           OE   
4.15.0-rc3-64-00039-g59217b88e0e1 #7
[605148.234373] Hardware name: Dell Inc. Precision T3610/09M8Y8, BIOS A12
09/09/2016
[605148.234373] RIP: 0010:queue_work_on+0x12/0x40
[605148.234373] RSP: 0018:ffffc90001f53cb0 EFLAGS: 00010002
[605148.234373] RAX: 0000000000000202 RBX: 0000000000000202 RCX:
0000000000000000
[605148.234373] RDX: 00000000000101f8 RSI: ffff88106e40c000 RDI:
0000000000000020
[605148.234373] RBP: ffff88012ba31140 R08: 0000000000000000 R09:
0000000000000000
[605148.234373] R10: ffff880be3fe3f30 R11: ffff88102716ab20 R12:
ffff8810264f00a0
[605148.234373] R13: ffff880df5af3600 R14: ffff881020c95e38 R15:
ffffffff81a9b978
[605148.234373] FS:  00007f701e290a40(0000) GS:ffff88106e800000(0000)
knlGS:0000000000000000
[605148.234373] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[605148.234373] CR2: 00000000000101f8 CR3: 0000000ff7c41005 CR4:
00000000001606f0
[605148.234373] Call Trace:
[605148.234373]  nouveau_gem_object_close+0x162/0x1e0
[605148.234373]  drm_gem_object_release_handle+0x27/0x80
[605148.234373]  drm_gem_handle_delete+0x55/0x80
[605148.234373]  ? drm_gem_handle_create+0x30/0x30
[605148.234373]  drm_ioctl_kernel+0x51/0xa0
[605148.234373]  drm_ioctl+0x2cd/0x370
[605148.234373]  ? drm_gem_handle_create+0x30/0x30
[605148.234373]  nouveau_drm_ioctl+0x5c/0xb0
[605148.234373]  do_vfs_ioctl+0x96/0x610
[605148.234373]  ? __fget+0x62/0xa0
[605148.234373]  ? __fget+0x62/0xa0
[605148.234373]  SyS_ioctl+0x6f/0x80
[605148.234373]  entry_SYSCALL_64_fastpath+0x1e/0x81
[605148.234373] RIP: 0033:0x7f701b75e5d7
[605148.234373] RSP: 002b:00007ffc01902ad8 EFLAGS: 00000246 ORIG_RAX:
0000000000000010
[605148.234373] RAX: ffffffffffffffda RBX: 0000563abec8f1b0 RCX:
00007f701b75e5d7
[605148.234373] RDX: 00007ffc01902b10 RSI: 0000000040086409 RDI:
000000000000000b
[605148.234373] RBP: 00007ffc01902b10 R08: 0000000000000002 R09:
0000000000000001
[605148.234373] R10: 0000563abe7257e0 R11: 0000000000000246 R12:
0000000040086409
[605148.234373] R13: 000000000000000b R14: 0000563abe72b890 R15:
0000563abec8f1b0
[605148.234373] Code: b0 34 c8 81 e8 55 92 03 00 c6 05 01 bd 2e 01 01 e9 68 ff
ff ff 0f 1f 40 00 53 9c 58 0f 1f 44 00 00 48 89 c3 fa 66 0f 1f 44 00 00 <f0> 0f
ba 2a 00 73 10 31 c9 48 89 df 57 9d 0f 1f 44 00 00 89 c8
[605148.234373] RIP: queue_work_on+0x12/0x40 RSP: ffffc90001f53cb0
[605148.234373] CR2: 00000000000101f8
[605148.234373] ---[ end trace 537ebb0d3ac8419d ]---

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-12-21  0:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21  0:59 bugzilla-daemon [this message]
2017-12-21  1:21 ` [Bug 198221] nouveau DRM driver scheduling invalid work bugzilla-daemon
2017-12-21  4:32 ` bugzilla-daemon
2017-12-21  7:17 ` bugzilla-daemon
2017-12-29 21:08 ` bugzilla-daemon
2017-12-29 21:45 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-198221-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.