From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98638] Panic on shutdown with AMDGPU and Ubuntu Plymouth
Date: Mon, 14 Nov 2016 09:05:05 +0000 [thread overview]
Message-ID: <bug-98638-502-sNYHWd6x8K@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98638-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2128 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #6 from Ernst Sjöstrand <ernstp@gmail.com> ---
Here's a new "backtrace"...
null pointer dereference in amdgpu_fence_wait_empty can't be that many
things...
Is it the rcu_dereference?
https://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c?h=drm-next-4.10-wip#n261
[ 85.216191] [drm] amdgpu: finishing device.
[ 86.336739] Console: switching to colour VGA+ 80x25
[ 86.345463] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 86.345477] IP: [<ffffffffc03882ba>] amdgpu_fence_wait_empty+0x2a/0xd0
[amdgpu]
[ 86.345508] PGD 0 [ 86.345510]
[ 86.345516] Oops: 0000 [#1] SMP
[ 86.345519] Modules linked in: netconsole configfs binfmt_misc eeepc_wmi
asus_wmi sparse_keymap video intel_rapl x86_pkg_temp_thermal kvm_intel kvm
irqbypass input_leds btusb btrtl btbcm crct10dif_pclmul crc32_pclmul btintel
ghash_clmulni_intel bluetooth aesni_intel aes_x86_64 snd_hda_codec_realtek lrw
glue_helper ablk_helper snd_hda_codec_generic cryptd snd_hda_codec_hdmi
intel_cstate snd_hda_intel intel_rapl_perf snd_hda_codec snd_hda_core serio_raw
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq
snd_seq_device snd_timer snd mei_me soundcore mei lpc_ich shpchp mac_hid sbs
sbshc max6650 coretemp parport_pc ppdev lp parport ip_tables x_tables autofs4
btrfs xor raid6_pq hid_generic usbhid hid amdkfd amd_iommu_v2 mxm_wmi amdgpu
i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect ahci sysimgblt
fb_sys_fops libahci e1000e83 ec 08 23 87 88 00 00 00 48 8b 97 90 00 00 00 48 8d
04 c2 18 48 85 db 74 6f 8b 0b 85 c9 74 69 8d 51 01 89 c8 f0 0f
[ 86.346049] RIP [<ffffffffc03882ba>] amdgpu_fence_wait_empty+0x2a/0xd0
[amdgpu]
[ 86.346071] RSP <ffffa46a017f3af0>
[ 86.346073] CR2: 0000000000000000
I only see the backtrace when amdgpu is unloaded before my ethernet module,
which seems to be rare.
Would be nice to force the ethernet driver to be unloaded last.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3066 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
next prev parent reply other threads:[~2016-11-14 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 10:46 [Bug 98638] Panic on shutdown with AMDGPU and Ubuntu Plymouth bugzilla-daemon
2016-11-09 1:05 ` bugzilla-daemon
2016-11-09 8:42 ` bugzilla-daemon
2016-11-09 8:51 ` bugzilla-daemon
2016-11-09 8:54 ` bugzilla-daemon
2016-11-09 14:51 ` bugzilla-daemon
2016-11-14 9:05 ` bugzilla-daemon [this message]
2016-11-14 11:28 ` bugzilla-daemon
2016-11-26 14:28 ` bugzilla-daemon
2016-11-26 14:54 ` bugzilla-daemon
2016-12-06 15:46 ` bugzilla-daemon
2016-12-06 15:47 ` bugzilla-daemon
2016-12-06 19:43 ` bugzilla-daemon
2016-12-07 20:28 ` 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-98638-502-sNYHWd6x8K@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;
as well as URLs for NNTP newsgroup(s).