X crashes with "randr: falling back to unsynchronized pixmap sharing" when connecting to an external monitor via HDMI (I+A)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Fix Released
|
Undecided
|
Timo Aaltonen | ||
Xenial |
Won't Fix
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Timo Aaltonen | ||
xorg-server-hwe-16.04 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
X server crashes in certain cases on I+A hybrid machines with modesetting+amdgpu drivers.
[Test case]
Connect an external monitor, check that it doesn't crash X.
[Regression potential]
This commit was provided by AMD and reviewed by an NVIDIA engineer, and after a few iterations it got applied upstream. We'll test it with many driver combinations (modesetting+
--
Copied from a private bug:
- Steps to see the issue:
1. Connect a monitor to UUT via HDMI port
Expected Result:
Video outputs successfully in the monitor
Actual Result:
X crashes into a login screen
- BIOS: 0.7.3
- AMD driver release: 18.10, 18.20RC8 and 18.20RC9
Changed in xorg-server (Ubuntu Xenial): | |
status: | New → Won't Fix |
Changed in xorg-server-hwe-16.04 (Ubuntu Bionic): | |
status: | New → Invalid |
Changed in xorg-server-hwe-16.04 (Ubuntu): | |
status: | New → Invalid |
Changed in xorg-server (Ubuntu): | |
status: | Incomplete → Triaged |
Changed in xorg-server (Ubuntu Bionic): | |
status: | Incomplete → Triaged |
Changed in xorg-server-hwe-16.04 (Ubuntu Xenial): | |
status: | Incomplete → Triaged |
Changed in xorg-server (Ubuntu): | |
assignee: | nobody → Timo Aaltonen (tjaalton) |
Changed in xorg-server (Ubuntu Bionic): | |
assignee: | nobody → Timo Aaltonen (tjaalton) |
description: | updated |
Standard response :)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https:/ /errors. ubuntu. com/user/ ID where ID is the content of file /var/lib/ whoopsie/ whoopsie- id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.
3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.
Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.