From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)
Date: Fri, 15 Dec 2017 04:27:07 +0000 [thread overview]
Message-ID: <bug-104274-502-1NwgcomRRD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104274-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 4097 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104274
--- Comment #1 from Sverd Johnsen <sverd.johnsen@googlemail.com> ---
with 4.15rc (linus tree from today)
[ 78.807441] [drm] amdgpu: finishing device.
[ 78.887439] amdgpu: [powerplay]
[ 78.887454] amdgpu: [powerplay]
[ 78.968349] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 78.968352] IP: (null)
[ 78.968352] PGD 45af1d067 P4D 45af1d067 PUD 45b065067 PMD 0
[ 78.968354] Oops: 0010 [#1] PREEMPT SMP
[ 78.968355] Modules linked in: amdgpu(-) chash ttm cls_u32 sch_htb af_packet
nft_limit nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nf_log_ipv6
nf_log_ipv4 nf_log_common nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4
nf_defrag_ipv4 nft_log nft_ct nf_conntrack xfrm_user xfrm_algo nft_counter
nft_meta nft_set_bitmap nft_set_hash nft_set_rbtree nf_tables_netdev
nf_tables_inet nf_tables_ipv6 nf_tables_ipv4 dm_cache_smq dm_cache
dm_bio_prison dm_persistent_data dm_bufio libcrc32c bcache x86_pkg_temp_thermal
intel_powerclamp kvm_intel vhost_net raid0 raid1 tun vhost tap kvm
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel
snd_hda_codec md_mod snd_hwdep irqbypass snd_hda_core intel_cstate mei_me
efi_pstore intel_uncore plusb mei input_leds usbnet snd_pcm intel_rapl_perf
[ 78.968375] led_class mii efivars tpm_crb usbip_host usbip_core efivarfs
algif_skcipher af_alg mousedev joydev psmouse atkbd libps2 crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel pcspkr tpm_tis shpchp tpm_tis_core thermal fan
tpm i8042 acpi_pad vfat fat
[ 78.968383] CPU: 1 PID: 1493 Comm: rmmod Not tainted 4.15.0-1-rc #2
[ 78.968384] Hardware name: Gigabyte Technology Co., Ltd.
Z170X-UD3/Z170X-UD3-CF, BIOS F23d 12/01/2017
[ 78.968384] RIP: 0010: (null)
[ 78.968385] RSP: 0018:ffff9c6a8281bd00 EFLAGS: 00010286
[ 78.968386] RAX: ffff9294612676e0 RBX: ffff92948b2a3300 RCX:
000000018020001e
[ 78.968386] RDX: 000000018020001f RSI: 0000000000005c02 RDI:
ffff929461267120
[ 78.968387] RBP: ffff9294658a6c90 R08: 0000000000000001 R09:
ffff929476247000
[ 78.968387] R10: 0000000000000000 R11: 0000000000000033 R12:
0000000000000003
[ 78.968388] R13: ffff929453e42f18 R14: 0000000000000000 R15:
ffffffffc09b13e8
[ 78.968389] FS: 00007f0d7f498b80(0000) GS:ffff92949ec80000(0000)
knlGS:0000000000000000
[ 78.968389] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 78.968390] CR2: 0000000000000000 CR3: 000000046b3f8001 CR4:
00000000003606e0
[ 78.968390] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 78.968391] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[ 78.968391] Call Trace:
[ 78.968429] ? destroy+0x1d/0xa0 [amdgpu]
[ 78.968440] ? dal_i2caux_destruct+0x58/0x90 [amdgpu]
[ 78.968449] ? destroy+0x10/0x30 [amdgpu]
[ 78.968458] ? dal_i2caux_destroy+0x17/0x30 [amdgpu]
[ 78.968467] ? destruct+0x89/0x110 [amdgpu]
[ 78.968476] ? dc_destroy+0xc/0x20 [amdgpu]
[ 78.968488] ? dm_hw_fini+0x19/0x20 [amdgpu]
[ 78.968493] ? amdgpu_fini+0x90/0x2f0 [amdgpu]
[ 78.968499] ? amdgpu_device_fini+0x5f/0x1c0 [amdgpu]
[ 78.968505] ? amdgpu_driver_unload_kms+0x45/0x90 [amdgpu]
[ 78.968507] ? drm_dev_unregister+0x37/0xe0
[ 78.968512] ? amdgpu_pci_remove+0x14/0x40 [amdgpu]
[ 78.968514] ? pci_device_remove+0x31/0xa0
[ 78.968516] ? device_release_driver_internal+0x152/0x210
[ 78.968517] ? driver_detach+0x32/0x70
[ 78.968518] ? bus_remove_driver+0x4c/0xc0
[ 78.968519] ? pci_unregister_driver+0x25/0xa0
[ 78.968529] ? amdgpu_exit+0x11/0x3b6 [amdgpu]
[ 78.968530] ? SyS_delete_module+0x19c/0x2a0
[ 78.968532] ? do_syscall_64+0x48/0xe0
[ 78.968533] ? entry_SYSCALL64_slow_path+0x25/0x25
[ 78.968534] Code: Bad RIP value.
[ 78.968536] RIP: (null) RSP: ffff9c6a8281bd00
[ 78.968537] CR2: 0000000000000000
[ 78.968538] ---[ end trace bbf73cfe467dd4c8 ]---
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5044 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:[~2017-12-15 4:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 3:01 [Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock) bugzilla-daemon
2017-12-15 4:27 ` bugzilla-daemon [this message]
2017-12-15 9:17 ` bugzilla-daemon
2017-12-15 15:59 ` bugzilla-daemon
2017-12-21 19:41 ` bugzilla-daemon
2018-01-29 16:16 ` bugzilla-daemon
2018-02-22 19:28 ` bugzilla-daemon
2018-02-22 20:50 ` bugzilla-daemon
2018-02-25 5:44 ` bugzilla-daemon
2018-02-26 8:09 ` bugzilla-daemon
2018-02-26 21:46 ` bugzilla-daemon
2018-02-28 2:01 ` bugzilla-daemon
2018-02-28 17:26 ` bugzilla-daemon
2018-04-05 13:12 ` bugzilla-daemon
2018-04-05 13:16 ` bugzilla-daemon
2018-06-05 3:39 ` bugzilla-daemon
2018-06-17 6:17 ` bugzilla-daemon
2019-11-19 8:27 ` 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-104274-502-1NwgcomRRD@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