Bug 1741087 - amdgpu_dm_atomic_commit_tail.cold+0xa5/0x103 [amdgpu]
Summary: amdgpu_dm_atomic_commit_tail.cold+0xa5/0x103 [amdgpu]
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-14 08:41 UTC by Dimitris
Modified: 2020-01-11 09:52 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-11 09:52:14 UTC
Type: Bug


Attachments (Terms of Use)
dmesg (157.71 KB, text/plain)
2019-08-14 08:41 UTC, Dimitris
no flags Details

Description Dimitris 2019-08-14 08:41:07 UTC
Created attachment 1603639 [details]
dmesg

1. Please describe the problem:

Switching from windowed mode to full-screen in dosbox, results in a module amdgpu crash, the logs are full of these errors:

WARNING: CPU: 1 PID: 1482 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:5456 amdgpu_dm_atomic_commit_tail.cold+0xa5/0x103 [amdgpu]

I can ssh to the crashed computer via another system, things appear fine with all applications running ok, but without any display output.


2. What is the Version-Release number of the kernel:

kernel-5.2.7-200.fc30.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

unknown.


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

yes, just start dosbox in windowed mode and then hit CTRL-ENTER to switch to full-screen.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

unknown.


6. Are you running any modules that not shipped with directly Fedora's kernel?:

yes, I have installed VirtualBox.


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Dimitris 2020-01-11 09:52:14 UTC
Nobody interested, so closing.


Note You need to log in before you can comment on or make changes to this bug.