All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194843] [amdgpu] oops [drm:gfx_v8_0_priv_reg_irq] *ERROR* Illegal register access in command stream
Date: Sun, 12 Mar 2017 11:26:23 +0000	[thread overview]
Message-ID: <bug-194843-2300-SBzXsHlzll@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194843-2300@https.bugzilla.kernel.org/>

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

--- Comment #5 from Johannes Hirte (johannes.hirte@datenkhaos.de) ---
Ok, it's not 4.11 specific. Now I had a system hang with 4.10.0 and found in
the logs after reboot only this:

Mar 12 12:12:48 probook kernel: ------------[ cut here ]------------
Mar 12 12:12:48 probook kernel: WARNING: CPU: 1 PID: 872 at
./include/linux/dma-fence.h:349 amdgpu_vm_grab_id+0x7ef/0x810
Mar 12 12:12:48 probook kernel: Modules linked in: uas usb_storage cmac rfcomm
uhid bnep btusb btrtl btbcm btintel bluetooth hp_wmi kvm_amd kvm iwlmvm
irqbypass mac80211 aesni_intel aes_x86_64 crypto_simd cryptd glue_hel
per fam15h_power snd_hda_codec_conexant snd_hda_codec_generic i2c_piix4 k10temp
snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_pcm
iwlwifi rtsx_pci_ms snd_timer cfg80211 memstick snd rfkill r81
69 soundcore mii wmi i2c_designware_platform i2c_designware_core hp_wireless
rtsx_pci_sdmmc mmc_core ehci_pci ehci_hcd xhci_pci xhci_hcd rtsx_pci mfd_core
efivarfs autofs4
Mar 12 12:12:48 probook kernel: CPU: 1 PID: 872 Comm: sdma0 Not tainted 4.10.0
#91
Mar 12 12:12:48 probook kernel: Hardware name: HP HP ProBook 645 G2/80FE, BIOS
N77 Ver. 01.07 11/01/2016
Mar 12 12:12:48 probook kernel: Call Trace:
Mar 12 12:12:48 probook kernel:  dump_stack+0x4f/0x73
Mar 12 12:12:48 probook kernel:  __warn+0xc6/0xe0
Mar 12 12:12:48 probook kernel:  warn_slowpath_null+0x18/0x20
Mar 12 12:12:48 probook kernel:  amdgpu_vm_grab_id+0x7ef/0x810
Mar 12 12:12:48 probook kernel:  ? dma_fence_wait_timeout+0x110/0x110
Mar 12 12:12:48 probook kernel:  amdgpu_job_dependency+0x5a/0x90
Mar 12 12:12:48 probook kernel:  amd_sched_main+0x9e/0x500
Mar 12 12:12:48 probook kernel:  ? wake_atomic_t_function+0x50/0x50
Mar 12 12:12:48 probook kernel:  kthread+0xfc/0x130
Mar 12 12:12:48 probook kernel:  ? amd_sched_process_job+0xe0/0xe0
Mar 12 12:12:48 probook kernel:  ? kthread_create_on_node+0x40/0x40
Mar 12 12:12:48 probook kernel:  ret_from_fork+0x29/0x40
Mar 12 12:12:48 probook kernel: ---[ end trace 4591763eee9b4ab4 ]---
Mar 12 12:12:48 probook kernel: ------------[ cut here ]------------
Mar 12 12:12:48 probook kernel: WARNING: CPU: 2 PID: 863 at
./include/linux/dma-fence.h:349 amdgpu_vm_grab_id+0x7ef/0x810
Mar 12 12:12:48 probook kernel: Modules linked in: uas usb_storage cmac rfcomm
uhid bnep btusb btrtl btbcm btintel bluetooth hp_wmi kvm_amd kvm iwlmvm
irqbypass mac80211 aesni_intel aes_x86_64 crypto_simd cryptd glue_hel
per fam15h_power snd_hda_codec_conexant snd_hda_codec_generic i2c_piix4 k10temp
snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_pcm
iwlwifi rtsx_pci_ms snd_timer cfg80211 memstick snd rfkill r81
69 soundcore mii wmi i2c_designware_platform i2c_designware_core hp_wireless
rtsx_pci_sdmmc mmc_core ehci_pci ehci_hcd xhci_pci xhci_hcd rtsx_pci mfd_core
efivarfs autofs4
Mar 12 12:12:48 probook kernel: CPU: 2 PID: 863 Comm: gfx Tainted: G        W  
    4.10.0 #91
Mar 12 12:12:48 probook kernel: Hardware name: HP HP ProBook 645 G2/80FE, BIOS
N77 Ver. 01.07 11/01/2016
Mar 12 12:12:48 probook kernel: Call Trace:
Mar 12 12:12:48 probook kernel:  dump_stack+0x4f/0x73
Mar 12 12:12:48 probook kernel:  __warn+0xc6/0xe0
Mar 12 12:12:48 probook kernel:  warn_slowpath_null+0x18/0x20
Mar 12 12:12:48 probook kernel:  amdgpu_vm_grab_id+0x7ef/0x810
Mar 12 12:12:48 probook kernel:  ? dma_fence_wait_timeout+0x110/0x110
Mar 12 12:12:48 probook kernel:  amdgpu_job_dependency+0x5a/0x90
Mar 12 12:12:48 probook kernel:  amd_sched_main+0x9e/0x500
Mar 12 12:12:48 probook kernel:  ? wake_atomic_t_function+0x50/0x50
Mar 12 12:12:48 probook kernel:  kthread+0xfc/0x130
Mar 12 12:12:48 probook kernel:  ? amd_sched_process_job+0xe0/0xe0
Mar 12 12:12:48 probook kernel:  ? kthread_create_on_node+0x40/0x40
Mar 12 12:12:48 probook kernel:  ? umh_complete+0x40/0x40
Mar 12 12:12:48 probook kernel:  ? call_usermodehelper_exec_async+0x137/0x140
Mar 12 12:12:48 probook kernel:  ret_from_fork+0x29/0x40
Mar 12 12:12:48 probook kernel: ---[ end trace 4591763eee9b4ab5 ]---

-- 
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

  parent reply	other threads:[~2017-03-12 11:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 20:34 [Bug 194843] New: [amdgpu] oops [drm:gfx_v8_0_priv_reg_irq] *ERROR* Illegal register access in command stream bugzilla-daemon
2017-03-10 20:40 ` [Bug 194843] " bugzilla-daemon
2017-03-10 21:05 ` bugzilla-daemon
2017-03-10 21:05 ` bugzilla-daemon
2017-03-10 21:08 ` bugzilla-daemon
2017-03-12 11:26 ` bugzilla-daemon [this message]
2017-04-18 19:40 ` bugzilla-daemon
2017-04-19  3:23 ` bugzilla-daemon
2017-04-24 12:49 ` bugzilla-daemon
2017-04-24 14:23 ` bugzilla-daemon
2017-06-21 19:04 ` 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-194843-2300-SBzXsHlzll@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.