dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105684] Loading amdgpu hits general protection fault: 0000 [#1] SMP NOPTI
Date: Thu, 22 Mar 2018 08:31:22 +0000	[thread overview]
Message-ID: <bug-105684-502-HbVaFmze9c@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105684-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 3410 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105684

--- Comment #2 from jian-hong@endlessm.com ---
Sorry for the messages before, the editing error.

I have an AMD Ryzen 5 2400G with Radeon Vega Graphics computer.  When I loading
amdgpu module manually, it will hit the panic.

<6>[  128.532951] [drm] Found VCN firmware Version: 1.45 Family ID: 18
<7>[  128.696866] [drm:amdgpu_dm_irq_init [amdgpu]] DM_IRQ
<7>[  128.697060] [drm:dal_firmware_parser_init_cmd_tbl [amdgpu]] Don't have
set_crtc_timing for v1
<7>[  128.697357] [drm:dc_create [amdgpu]] DC: create_links: connectors_num:
physical:4, virtual:0
<7>[  128.697443] [drm:log_to_debug_console [amdgpu]] Connector[0]
description:signal 32
<7>[  128.697551] [drm:log_to_debug_console [amdgpu]] Connector[1]
description:signal 4
<7>[  128.697652] [drm:log_to_debug_console [amdgpu]] Connector[2]
description:signal 4
<4>[  128.697663] general protection fault: 0000 [#1] SMP NOPTI
<4>[  128.697670] Modules linked in: amdkfd amd_iommu_v2 amdgpu(+) chash
gpu_sched ttm drm_kms_helper drm i2c_algo_bit fb_sys_fops syscopyarea
sysfillrect sysimgblt efi_pstore edac_mce_amd kvm_amd ccp kvm irqbypass cmac
bnep crct10dif_pclmul crc32_pclmul ghash_clmulni_intel arc4 pcbc aesni_intel
btusb btrtl btbcm btintel bluetooth input_leds aes_x86_64 ecdh_generic
snd_hda_codec_realtek ath10k_pci ath10k_core ath mac80211 cfg80211
snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec
snd_hda_core snd_hwdep snd_pcm snd_timer snd r8169 soundcore mii crypto_simd
glue_helper cryptd shpchp i2c_piix4 sparse_keymap wmi_bmof psmouse mac_hid wmi
tpm_crb video ip_tables x_tables serio_raw uas usb_storage ahci libahci
hid_generic usbhid hid
<4>[  128.697752] CPU: 1 PID: 1216 Comm: modprobe Not tainted 4.16.0-rc6+ #6
<4>[  128.697756] Hardware name: Acer Aspire TC-380/Aspire TC-380, BIOS D05
02/01/2018
<4>[  128.697766] RIP: 0010:prefetch_freepointer+0x15/0x30
<4>[  128.697770] RSP: 0018:ffffbc1143f973e8 EFLAGS: 00010286
<4>[  128.697775] RAX: 0000000000000000 RBX: ffff9681b67cd000 RCX:
00000000000004cd
<4>[  128.697779] RDX: 00000000000004cc RSI: b8036bfcc8b36eaa RDI:
ffff9681de806e80
<4>[  128.697783] RBP: ffffbc1143f973e8 R08: ffff9681dec67160 R09:
ffffffffc0c4ac0c
<4>[  128.697787] R10: ffffe3f45fdcaa40 R11: 00000000000003c9 R12:
00000000014080c0
<4>[  128.697790] R13: ffff9681de806e80 R14: ffff9681b67cd000 R15:
ffff9681de806e80
<4>[  128.697795] FS:  00007fc7a7ea9700(0000) GS:ffff9681dec40000(0000)
knlGS:0000000000000000
<4>[  128.697800] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[  128.697804] CR2: 0000559d453ef0c0 CR3: 00000007f8d8a000 CR4:
00000000003406e0
<4>[  128.697808] Call Trace:
<4>[  128.697815]  kmem_cache_alloc_trace+0xa5/0x1c0
<4>[  128.697877]  ? dal_ddc_service_create+0x3c/0x120 [amdgpu]
<4>[  128.697929]  dal_ddc_service_create+0x3c/0x120 [amdgpu]
<4>[  128.697985]  ? dal_gpio_service_create_irq+0x4a/0x70 [amdgpu]
<4>[  128.698030]  construct+0x25b/0x780 [amdgpu]
<4>[  128.698077]  link_create+0x38/0x60 [amdgpu]
<4>[  128.698121]  dc_create+0x2e6/0x6b0 [amdgpu]
<4>[  128.698169]  dm_hw_init+0x107/0xed0 [amdgpu]

Then, system hangs up and could not change the tty terminal nor be ssh into.
This happens about 50-50%.

The debug messages as the attachment.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4391 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-03-22  8:31 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22  8:19 [Bug 105684] Loading amdgpu hits general protection fault: 0000 [#1] SMP NOPTI bugzilla-daemon
2018-03-22  8:22 ` bugzilla-daemon
2018-03-22  8:31 ` bugzilla-daemon [this message]
2018-03-22  9:08 ` bugzilla-daemon
2018-03-22 13:56 ` bugzilla-daemon
2018-03-23  2:58 ` bugzilla-daemon
2018-03-23  2:59 ` bugzilla-daemon
2018-03-23  3:00 ` bugzilla-daemon
2018-03-23  3:01 ` bugzilla-daemon
2018-03-23  3:01 ` bugzilla-daemon
2018-03-23  3:01 ` bugzilla-daemon
2018-03-23  3:02 ` bugzilla-daemon
2018-03-23  3:02 ` bugzilla-daemon
2018-03-23  3:12 ` bugzilla-daemon
2018-03-27  6:39 ` bugzilla-daemon
2018-04-09  7:30 ` bugzilla-daemon
2018-04-17  7:56 ` bugzilla-daemon
2018-04-26  3:54 ` bugzilla-daemon
2018-05-09 18:49 ` bugzilla-daemon
2018-05-09 19:06 ` bugzilla-daemon
2018-05-10  7:10 ` bugzilla-daemon
2018-05-10  9:27 ` bugzilla-daemon
2018-05-10  9:50 ` bugzilla-daemon
2018-05-10 13:20 ` bugzilla-daemon
2018-05-11  3:20 ` bugzilla-daemon
2018-05-11 15:23 ` bugzilla-daemon
2018-05-11 15:51 ` bugzilla-daemon
2018-05-11 17:51 ` bugzilla-daemon
2018-05-12 20:30 ` bugzilla-daemon
2018-05-12 20:37 ` bugzilla-daemon
2018-05-14  3:00 ` bugzilla-daemon
2018-05-14  3:04 ` bugzilla-daemon
2018-07-18 13:47 ` bugzilla-daemon
2018-07-19 17:27 ` bugzilla-daemon
2018-07-20 14:57 ` bugzilla-daemon
2018-07-23 11:33 ` bugzilla-daemon
2018-07-24  9:27 ` bugzilla-daemon
2018-07-25 10:10 ` bugzilla-daemon
2018-07-25 14:13 ` bugzilla-daemon
2018-07-25 16:38 ` bugzilla-daemon
2018-07-26  8:21 ` bugzilla-daemon
2018-08-09  7:24 ` bugzilla-daemon
2018-08-09  9:56 ` bugzilla-daemon
2018-08-09 12:21 ` bugzilla-daemon
2019-04-29 15:24 ` bugzilla-daemon
2019-04-29 15:53 ` bugzilla-daemon
2019-05-29 13:36 ` bugzilla-daemon
2019-06-05 12:39 ` bugzilla-daemon
2019-11-19  8:33 ` 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-105684-502-HbVaFmze9c@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox