From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110225] Kernel panic while “ modprobe amdkfd ; modprobe -r amdkfd " ; 4.14.35 kernel .
Date: Fri, 22 Mar 2019 17:06:44 +0000 [thread overview]
Message-ID: <bug-110225-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2322 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110225
Bug ID: 110225
Summary: Kernel panic while “ modprobe amdkfd ; modprobe -r
amdkfd " ; 4.14.35 kernel .
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: major
Priority: medium
Component: DRM/amdkfd
Assignee: dri-devel@lists.freedesktop.org
Reporter: John.p.donnelly@oracle.com
Hello ,
I am investigating a issue that our test group reported concerning this driver.
Their test loads and unloads every kernel module included in the Oracle
4.14.35 kernel release . You don’t even need a AMD platform . It occurs on any
Intel, or a KVM VM instance too.
Kernel panic while “ modprobe amdkfd ; modprobe -r amdkfd “
[ 329.425334] ? __slab_free+0x9b/0x2ba
[ 329.427836] ? process_slab+0x3c1/0x45c
[ 329.430336] dev_printk_emit+0x4e/0x65
[ 329.432829] __dev_printk+0x46/0x8b
[ 329.435183] _dev_info+0x6c/0x85
[ 329.437435] ? kfree+0x141/0x182
[ 329.439646] kfd_module_exit+0x37/0x39 [amdkfd]
[ 329.442258] SyS_delete_module+0x1c3/0x26f
[ 329.444722] ? entry_SYSCALL_64_after_hwframe+0xaa/0x0
[ 329.447479] ? entry_SYSCALL_64_after_hwframe+0xa3/0x0
[ 329.450206] ? entry_SYSCALL_64_after_hwframe+0x9c/0x0
[ 329.452912] ? entry_SYSCALL_64_after_hwframe+0x95/0x0
[ 329.455586] do_syscall_64+0x79/0x1ae
[ 329.457766] entry_SYSCALL_64_after_hwframe+0x151/0x0
[ 329.460369] RIP: 0033:0x7f1757a1b457
[ 329.462502] RSP: 002b:00007ffd62ce1f48 EFLAGS: 00000206 ORIG_RAX:
Looks like some memory corruption.
Sometimes the unload works but the message logged is garbage:
[root@jpd-vmbase02 ~]# modprobe -r amdkfd
[ 144.449981] ???????????? hn??蟟??xn??ן??kfd: Removed module
Is this something one of team members could have possibly corrected in an
upstream version ?
#define KFD_DRIVER_DESC "Standalone HSA driver for AMD's GPUs"
#define KFD_DRIVER_DATE "20150421"
#define KFD_DRIVER_MAJOR 0
#define KFD_DRIVER_MINOR 7
#define KFD_DRIVER_PATCHLEVEL 2
Thank you,
John
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3663 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-22 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 17:06 bugzilla-daemon [this message]
2019-03-25 18:38 ` [Bug 110225] Kernel panic while “ modprobe amdkfd ; modprobe -r amdkfd " ; 4.14.35 kernel bugzilla-daemon
2019-03-25 18:41 ` 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-110225-502@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 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.