https://bugs.freedesktop.org/show_bug.cgi?id=98638
Alex Deucher changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #11 from Ernst Sjöstrand ---
That seems to work great! I can try a few more reboots if you want. Won't make
it into 4.9 in time anyway right?
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=98638
Alex Deucher changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #10 from Alex Deucher ---
Created attachment 128356
--> https://bugs.freedesktop.org/attachment.cgi?id=128356&action=edit
possible fix
Does this patch help?
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #9 from Ernst Sjöstrand ---
(gdb) l *(amdgpu_fence_wait_empty+0x29)
0x112d9 is in amdgpu_fence_wait_empty
(drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:270).
270 ptr = &ring->fence_drv.fences[seq &
ring->fence_drv.num_fences
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #8 from Ernst Sjöstrand ---
Now I got this interesting blob:
[ 1457.810773] systemd-shutdown[1]: All swaps deactivated.
[ 1457.810777] systemd-shutdown[1]: Detaching loop devices.
[ 1457.814471] kvm: exiting hardware virtualization
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #7 from Christian König ---
Try loading the amdgpu.ko module in gdb like this (Obviously please use the
correct one for your kernel version):
gdb /lib/modules/4.7.0+/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
And then run
l *(amd
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #6 from Ernst Sjöstrand ---
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/a
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #5 from Alex Deucher ---
Shutdown and remove use same code in the driver. Can you reproduce the issue
by unloading the amdgpu module? E.g., as root:
echo 0 > /sys/class/vtconsole/vtcon1/bind
modprobe -r amdgpu
--
You are receivin
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #4 from Ernst Sjöstrand ---
Perhaps the netconsole runs into problems because of the panic?
I'll try to turn on some more debug options in my kernel perhaps...
And maybe just try a few times and see if I'm lucky.
--
You are receivi
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #3 from Michel Dänzer ---
The bootsplash doesn't (directly) affect netconsole though, does it? Can you
try getting more complete output from netconsole?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #2 from Ernst Sjöstrand ---
The bootsplash hides any console prints and if I disable the bootsplash it
doesn't happen.
I guess it happens after filesystems go read-only so nothing is written to
logs, even if I do alt-sysrq-S.
The co
https://bugs.freedesktop.org/show_bug.cgi?id=98638
--- Comment #1 from Michel Dänzer ---
It looks like netconsole dropped a lot of information there, and what's left
isn't very helpful to figure out what's going on I'm afraid. Please keep trying
to get more information about it.
--
You are rec
https://bugs.freedesktop.org/show_bug.cgi?id=98638
Bug ID: 98638
Summary: Panic on shutdown with AMDGPU and Ubuntu Plymouth
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: norma
14 matches
Mail list logo
