[Touch-packages] [Bug 1386834] Re: Second display stops working on repeated detection
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386834 Title: Second display stops working on repeated detection Status in xorg package in Ubuntu: Won't Fix Bug description: The first time a secondary display/projector is connected to my laptop, it is detected and works in mirrored mode. However, once I open System Settings > Displays, the seconday display gets disabled. Loging out and rebooting doesn't solve the problem. At least not right away. A few reboots later secondary display starts working again. Occasioally I'm able to use Fn+F4 to switch between different modes (mirrored, extended), but it usually doesn't last long. As soon as System Settings is activated, the secondary display is disable and no longer detected. Additional clues: 1) If I leave a display plugged in and reboot, it is activated on login screen, but shuts off as soon as I login. Pressing 'Detect Displays' button is Displays settings does not bring it back. 2) Every time I open System Settings (even without external displayed plugged in) there is a short lag and even the moust stops moving for about a second. The following shows up in the log: Oct 28 11:34:12 hostname kernel: [ 649.193034] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 Oct 28 11:34:12 hostname kernel: [ 649.193038] [drm] PCIE gen 2 link speeds already enabled Oct 28 11:34:12 hostname kernel: [ 649.197195] [drm] PCIE GART of 1024M enabled (table at 0x00276000). Oct 28 11:34:12 hostname kernel: [ 649.197453] radeon :03:00.0: WB enabled Oct 28 11:34:12 hostname kernel: [ 649.197455] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880432d0cc00 Oct 28 11:34:12 hostname kernel: [ 649.197457] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880432d0cc04 Oct 28 11:34:12 hostname kernel: [ 649.197458] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880432d0cc08 Oct 28 11:34:12 hostname kernel: [ 649.197459] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880432d0cc0c Oct 28 11:34:12 hostname kernel: [ 649.197460] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880432d0cc10 Oct 28 11:34:12 hostname kernel: [ 649.198991] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90012535a18 Oct 28 11:34:12 hostname kernel: [ 649.388989] [drm] ring test on 0 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388994] [drm] ring test on 1 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388998] [drm] ring test on 2 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.389009] [drm] ring test on 3 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.389016] [drm] ring test on 4 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.574547] [drm] ring test on 5 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.574553] [drm] UVD initialized successfully. Oct 28 11:34:12 hostname kernel: [ 649.574583] [drm] ib test on ring 0 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574610] [drm] ib test on ring 1 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574637] [drm] ib test on ring 2 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574664] [drm] ib test on ring 3 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574692] [drm] ib test on ring 4 succeeded in 0 usecs Oct 28 11:34:13 hostname kernel: [ 649.725287] [drm] ib test on ring 5 succeeded 3) Some plugging and unplugging of the display occasionally shows the same messages in the log followed by the following: Oct 28 11:34:13 hostname kernel: [ 649.734010] snd_hda_intel :03:00.1: Enabling via VGA-switcheroo Oct 28 11:34:13 hostname kernel: [ 649.734117] snd_hda_intel :03:00.1: irq 70 for MSI/MSI-X Oct 28 11:34:18 hostname kernel: [ 654.876455] snd_hda_intel :03:00.1: Disabling via VGA-switcheroo Oct 28 11:34:18 hostname kernel: [ 654.908444] snd_hda_intel :03:00.1:
[Touch-packages] [Bug 1386834] Re: Second display stops working on repeated detection
** Tags removed: vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386834 Title: Second display stops working on repeated detection Status in xorg package in Ubuntu: Triaged Bug description: The first time a secondary display/projector is connected to my laptop, it is detected and works in mirrored mode. However, once I open System Settings > Displays, the seconday display gets disabled. Loging out and rebooting doesn't solve the problem. At least not right away. A few reboots later secondary display starts working again. Occasioally I'm able to use Fn+F4 to switch between different modes (mirrored, extended), but it usually doesn't last long. As soon as System Settings is activated, the secondary display is disable and no longer detected. Additional clues: 1) If I leave a display plugged in and reboot, it is activated on login screen, but shuts off as soon as I login. Pressing 'Detect Displays' button is Displays settings does not bring it back. 2) Every time I open System Settings (even without external displayed plugged in) there is a short lag and even the moust stops moving for about a second. The following shows up in the log: Oct 28 11:34:12 hostname kernel: [ 649.193034] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 Oct 28 11:34:12 hostname kernel: [ 649.193038] [drm] PCIE gen 2 link speeds already enabled Oct 28 11:34:12 hostname kernel: [ 649.197195] [drm] PCIE GART of 1024M enabled (table at 0x00276000). Oct 28 11:34:12 hostname kernel: [ 649.197453] radeon :03:00.0: WB enabled Oct 28 11:34:12 hostname kernel: [ 649.197455] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880432d0cc00 Oct 28 11:34:12 hostname kernel: [ 649.197457] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880432d0cc04 Oct 28 11:34:12 hostname kernel: [ 649.197458] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880432d0cc08 Oct 28 11:34:12 hostname kernel: [ 649.197459] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880432d0cc0c Oct 28 11:34:12 hostname kernel: [ 649.197460] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880432d0cc10 Oct 28 11:34:12 hostname kernel: [ 649.198991] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90012535a18 Oct 28 11:34:12 hostname kernel: [ 649.388989] [drm] ring test on 0 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388994] [drm] ring test on 1 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388998] [drm] ring test on 2 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.389009] [drm] ring test on 3 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.389016] [drm] ring test on 4 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.574547] [drm] ring test on 5 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.574553] [drm] UVD initialized successfully. Oct 28 11:34:12 hostname kernel: [ 649.574583] [drm] ib test on ring 0 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574610] [drm] ib test on ring 1 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574637] [drm] ib test on ring 2 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574664] [drm] ib test on ring 3 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574692] [drm] ib test on ring 4 succeeded in 0 usecs Oct 28 11:34:13 hostname kernel: [ 649.725287] [drm] ib test on ring 5 succeeded 3) Some plugging and unplugging of the display occasionally shows the same messages in the log followed by the following: Oct 28 11:34:13 hostname kernel: [ 649.734010] snd_hda_intel :03:00.1: Enabling via VGA-switcheroo Oct 28 11:34:13 hostname kernel: [ 649.734117] snd_hda_intel :03:00.1: irq 70 for MSI/MSI-X Oct 28 11:34:18 hostname kernel: [ 654.876455] snd_hda_intel :03:00.1: Disabling via VGA-switcheroo Oct 28 11:34:18 hostname kernel: [ 654.908444] snd_hda_intel :03:00.1: Cannot lock devices! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 28 11:26:19 2014 DistUpgraded: 2014-10-24 11:32
[Touch-packages] [Bug 1386834] Re: Second display stops working on repeated detection
** Tags removed: bios-outdated-1.30 ** Tags added: latest-bios-1.31 ** Tags added: vivid ** Changed in: xorg (Ubuntu) Importance: Low => Medium ** Changed in: xorg (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386834 Title: Second display stops working on repeated detection Status in xorg package in Ubuntu: Triaged Bug description: The first time a secondary display/projector is connected to my laptop, it is detected and works in mirrored mode. However, once I open System Settings > Displays, the seconday display gets disabled. Loging out and rebooting doesn't solve the problem. At least not right away. A few reboots later secondary display starts working again. Occasioally I'm able to use Fn+F4 to switch between different modes (mirrored, extended), but it usually doesn't last long. As soon as System Settings is activated, the secondary display is disable and no longer detected. Additional clues: 1) If I leave a display plugged in and reboot, it is activated on login screen, but shuts off as soon as I login. Pressing 'Detect Displays' button is Displays settings does not bring it back. 2) Every time I open System Settings (even without external displayed plugged in) there is a short lag and even the moust stops moving for about a second. The following shows up in the log: Oct 28 11:34:12 hostname kernel: [ 649.193034] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 Oct 28 11:34:12 hostname kernel: [ 649.193038] [drm] PCIE gen 2 link speeds already enabled Oct 28 11:34:12 hostname kernel: [ 649.197195] [drm] PCIE GART of 1024M enabled (table at 0x00276000). Oct 28 11:34:12 hostname kernel: [ 649.197453] radeon :03:00.0: WB enabled Oct 28 11:34:12 hostname kernel: [ 649.197455] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880432d0cc00 Oct 28 11:34:12 hostname kernel: [ 649.197457] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880432d0cc04 Oct 28 11:34:12 hostname kernel: [ 649.197458] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880432d0cc08 Oct 28 11:34:12 hostname kernel: [ 649.197459] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880432d0cc0c Oct 28 11:34:12 hostname kernel: [ 649.197460] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880432d0cc10 Oct 28 11:34:12 hostname kernel: [ 649.198991] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90012535a18 Oct 28 11:34:12 hostname kernel: [ 649.388989] [drm] ring test on 0 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388994] [drm] ring test on 1 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388998] [drm] ring test on 2 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.389009] [drm] ring test on 3 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.389016] [drm] ring test on 4 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.574547] [drm] ring test on 5 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.574553] [drm] UVD initialized successfully. Oct 28 11:34:12 hostname kernel: [ 649.574583] [drm] ib test on ring 0 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574610] [drm] ib test on ring 1 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574637] [drm] ib test on ring 2 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574664] [drm] ib test on ring 3 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574692] [drm] ib test on ring 4 succeeded in 0 usecs Oct 28 11:34:13 hostname kernel: [ 649.725287] [drm] ib test on ring 5 succeeded 3) Some plugging and unplugging of the display occasionally shows the same messages in the log followed by the following: Oct 28 11:34:13 hostname kernel: [ 649.734010] snd_hda_intel :03:00.1: Enabling via VGA-switcheroo Oct 28 11:34:13 hostname kernel: [ 649.734117] snd_hda_intel :03:00.1: irq 70 for MSI/MSI-X Oct 28 11:34:18 hostname kernel: [ 654.876455] snd_hda_intel :03:00.1: Disabling via VGA-switcheroo Oct 28 11:34:18 hostname kernel: [ 654.908444] snd_hda_intel :03:00.1: Cannot lock devices! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz
[Touch-packages] [Bug 1386834] Re: Second display stops working on repeated detection
I was able to update the BIOS (1.31 now) and also updated Ubuntu to 15.04. The issue is still there and here is the output from the request command. (sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date) L71 Ver. 01.31 03/24/2015 ** Changed in: xorg (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386834 Title: Second display stops working on repeated detection Status in xorg package in Ubuntu: New Bug description: The first time a secondary display/projector is connected to my laptop, it is detected and works in mirrored mode. However, once I open System Settings > Displays, the seconday display gets disabled. Loging out and rebooting doesn't solve the problem. At least not right away. A few reboots later secondary display starts working again. Occasioally I'm able to use Fn+F4 to switch between different modes (mirrored, extended), but it usually doesn't last long. As soon as System Settings is activated, the secondary display is disable and no longer detected. Additional clues: 1) If I leave a display plugged in and reboot, it is activated on login screen, but shuts off as soon as I login. Pressing 'Detect Displays' button is Displays settings does not bring it back. 2) Every time I open System Settings (even without external displayed plugged in) there is a short lag and even the moust stops moving for about a second. The following shows up in the log: Oct 28 11:34:12 hostname kernel: [ 649.193034] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 Oct 28 11:34:12 hostname kernel: [ 649.193038] [drm] PCIE gen 2 link speeds already enabled Oct 28 11:34:12 hostname kernel: [ 649.197195] [drm] PCIE GART of 1024M enabled (table at 0x00276000). Oct 28 11:34:12 hostname kernel: [ 649.197453] radeon :03:00.0: WB enabled Oct 28 11:34:12 hostname kernel: [ 649.197455] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880432d0cc00 Oct 28 11:34:12 hostname kernel: [ 649.197457] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880432d0cc04 Oct 28 11:34:12 hostname kernel: [ 649.197458] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880432d0cc08 Oct 28 11:34:12 hostname kernel: [ 649.197459] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880432d0cc0c Oct 28 11:34:12 hostname kernel: [ 649.197460] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880432d0cc10 Oct 28 11:34:12 hostname kernel: [ 649.198991] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90012535a18 Oct 28 11:34:12 hostname kernel: [ 649.388989] [drm] ring test on 0 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388994] [drm] ring test on 1 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388998] [drm] ring test on 2 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.389009] [drm] ring test on 3 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.389016] [drm] ring test on 4 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.574547] [drm] ring test on 5 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.574553] [drm] UVD initialized successfully. Oct 28 11:34:12 hostname kernel: [ 649.574583] [drm] ib test on ring 0 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574610] [drm] ib test on ring 1 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574637] [drm] ib test on ring 2 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574664] [drm] ib test on ring 3 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574692] [drm] ib test on ring 4 succeeded in 0 usecs Oct 28 11:34:13 hostname kernel: [ 649.725287] [drm] ib test on ring 5 succeeded 3) Some plugging and unplugging of the display occasionally shows the same messages in the log followed by the following: Oct 28 11:34:13 hostname kernel: [ 649.734010] snd_hda_intel :03:00.1: Enabling via VGA-switcheroo Oct 28 11:34:13 hostname kernel: [ 649.734117] snd_hda_intel :03:00.1: irq 70 for MSI/MSI-X Oct 28 11:34:18 hostname kernel: [ 654.876455] snd_hda_intel :03:00.1: Disabling via VGA-switcheroo Oct 28 11:34:18 hostname kernel: [ 654.908444] snd_hda_intel :03:00.1: Cannot lock devices! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value
[Touch-packages] [Bug 1386834] Re: Second display stops working on repeated detection
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386834 Title: Second display stops working on repeated detection Status in xorg package in Ubuntu: Expired Bug description: The first time a secondary display/projector is connected to my laptop, it is detected and works in mirrored mode. However, once I open System Settings > Displays, the seconday display gets disabled. Loging out and rebooting doesn't solve the problem. At least not right away. A few reboots later secondary display starts working again. Occasioally I'm able to use Fn+F4 to switch between different modes (mirrored, extended), but it usually doesn't last long. As soon as System Settings is activated, the secondary display is disable and no longer detected. Additional clues: 1) If I leave a display plugged in and reboot, it is activated on login screen, but shuts off as soon as I login. Pressing 'Detect Displays' button is Displays settings does not bring it back. 2) Every time I open System Settings (even without external displayed plugged in) there is a short lag and even the moust stops moving for about a second. The following shows up in the log: Oct 28 11:34:12 hostname kernel: [ 649.193034] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 Oct 28 11:34:12 hostname kernel: [ 649.193038] [drm] PCIE gen 2 link speeds already enabled Oct 28 11:34:12 hostname kernel: [ 649.197195] [drm] PCIE GART of 1024M enabled (table at 0x00276000). Oct 28 11:34:12 hostname kernel: [ 649.197453] radeon :03:00.0: WB enabled Oct 28 11:34:12 hostname kernel: [ 649.197455] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880432d0cc00 Oct 28 11:34:12 hostname kernel: [ 649.197457] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880432d0cc04 Oct 28 11:34:12 hostname kernel: [ 649.197458] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880432d0cc08 Oct 28 11:34:12 hostname kernel: [ 649.197459] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880432d0cc0c Oct 28 11:34:12 hostname kernel: [ 649.197460] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880432d0cc10 Oct 28 11:34:12 hostname kernel: [ 649.198991] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90012535a18 Oct 28 11:34:12 hostname kernel: [ 649.388989] [drm] ring test on 0 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388994] [drm] ring test on 1 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388998] [drm] ring test on 2 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.389009] [drm] ring test on 3 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.389016] [drm] ring test on 4 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.574547] [drm] ring test on 5 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.574553] [drm] UVD initialized successfully. Oct 28 11:34:12 hostname kernel: [ 649.574583] [drm] ib test on ring 0 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574610] [drm] ib test on ring 1 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574637] [drm] ib test on ring 2 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574664] [drm] ib test on ring 3 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574692] [drm] ib test on ring 4 succeeded in 0 usecs Oct 28 11:34:13 hostname kernel: [ 649.725287] [drm] ib test on ring 5 succeeded 3) Some plugging and unplugging of the display occasionally shows the same messages in the log followed by the following: Oct 28 11:34:13 hostname kernel: [ 649.734010] snd_hda_intel :03:00.1: Enabling via VGA-switcheroo Oct 28 11:34:13 hostname kernel: [ 649.734117] snd_hda_intel :03:00.1: irq 70 for MSI/MSI-X Oct 28 11:34:18 hostname kernel: [ 654.876455] snd_hda_intel :03:00.1: Disabling via VGA-switcheroo Oct 28 11:34:18 hostname kernel: [ 654.908444] snd_hda_intel :03:00.1: Cannot lock devices! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
[Touch-packages] [Bug 1386834] Re: Second display stops working on repeated detection
Vitaly Korolev, thank you for reporting this and helping make Ubuntu better. As per http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=5405097&swLangOid=8&swEnvOid=4060 an update to your computer's buggy and outdated BIOS is available (1.30). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status New. Thank you for your understanding. ** Tags added: bios-outdated-1.30 ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386834 Title: Second display stops working on repeated detection Status in xorg package in Ubuntu: Incomplete Bug description: The first time a secondary display/projector is connected to my laptop, it is detected and works in mirrored mode. However, once I open System Settings > Displays, the seconday display gets disabled. Loging out and rebooting doesn't solve the problem. At least not right away. A few reboots later secondary display starts working again. Occasioally I'm able to use Fn+F4 to switch between different modes (mirrored, extended), but it usually doesn't last long. As soon as System Settings is activated, the secondary display is disable and no longer detected. Additional clues: 1) If I leave a display plugged in and reboot, it is activated on login screen, but shuts off as soon as I login. Pressing 'Detect Displays' button is Displays settings does not bring it back. 2) Every time I open System Settings (even without external displayed plugged in) there is a short lag and even the moust stops moving for about a second. The following shows up in the log: Oct 28 11:34:12 hostname kernel: [ 649.193034] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 Oct 28 11:34:12 hostname kernel: [ 649.193038] [drm] PCIE gen 2 link speeds already enabled Oct 28 11:34:12 hostname kernel: [ 649.197195] [drm] PCIE GART of 1024M enabled (table at 0x00276000). Oct 28 11:34:12 hostname kernel: [ 649.197453] radeon :03:00.0: WB enabled Oct 28 11:34:12 hostname kernel: [ 649.197455] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880432d0cc00 Oct 28 11:34:12 hostname kernel: [ 649.197457] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880432d0cc04 Oct 28 11:34:12 hostname kernel: [ 649.197458] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880432d0cc08 Oct 28 11:34:12 hostname kernel: [ 649.197459] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880432d0cc0c Oct 28 11:34:12 hostname kernel: [ 649.197460] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880432d0cc10 Oct 28 11:34:12 hostname kernel: [ 649.198991] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90012535a18 Oct 28 11:34:12 hostname kernel: [ 649.388989] [drm] ring test on 0 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388994] [drm] ring test on 1 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388998] [drm] ring test on 2 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.389009] [drm] ring test on 3 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.389016] [drm] ring test on 4 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.574547] [drm] ring test on 5 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.574553] [drm] UVD initialized successfully. Oct 28 11:34:12 hostname kernel: [ 649.574583] [drm] ib test on ring 0 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574610] [drm] ib test on ring 1 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574637] [drm] ib test on ring 2 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574664] [drm] ib test on ring 3 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574692] [drm] ib test on ring 4 succeeded in 0 usecs Oct 28 11:34:13 hostname kernel: [ 649.725287] [drm] ib test on ring 5 succ
[Touch-packages] [Bug 1386834] Re: Second display stops working on repeated detection
I can consistently "revive" the second display by unplugging it, going to stand by, resuming the laptop, and finally plugging the display again. It works and I can switch between different modes even through setting, but at some point if I open Displays settings it gets disabled as described above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386834 Title: Second display stops working on repeated detection Status in “xorg” package in Ubuntu: New Bug description: The first time a secondary display/projector is connected to my laptop, it is detected and works in mirrored mode. However, once I open System Settings > Displays, the seconday display gets disabled. Loging out and rebooting doesn't solve the problem. At least not right away. A few reboots later secondary display starts working again. Occasioally I'm able to use Fn+F4 to switch between different modes (mirrored, extended), but it usually doesn't last long. As soon as System Settings is activated, the secondary display is disable and no longer detected. Additional clues: 1) If I leave a display plugged in and reboot, it is activated on login screen, but shuts off as soon as I login. Pressing 'Detect Displays' button is Displays settings does not bring it back. 2) Every time I open System Settings (even without external displayed plugged in) there is a short lag and even the moust stops moving for about a second. The following shows up in the log: Oct 28 11:34:12 hostname kernel: [ 649.193034] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 Oct 28 11:34:12 hostname kernel: [ 649.193038] [drm] PCIE gen 2 link speeds already enabled Oct 28 11:34:12 hostname kernel: [ 649.197195] [drm] PCIE GART of 1024M enabled (table at 0x00276000). Oct 28 11:34:12 hostname kernel: [ 649.197453] radeon :03:00.0: WB enabled Oct 28 11:34:12 hostname kernel: [ 649.197455] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x880432d0cc00 Oct 28 11:34:12 hostname kernel: [ 649.197457] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x880432d0cc04 Oct 28 11:34:12 hostname kernel: [ 649.197458] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x880432d0cc08 Oct 28 11:34:12 hostname kernel: [ 649.197459] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x880432d0cc0c Oct 28 11:34:12 hostname kernel: [ 649.197460] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu addr 0x880432d0cc10 Oct 28 11:34:12 hostname kernel: [ 649.198991] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90012535a18 Oct 28 11:34:12 hostname kernel: [ 649.388989] [drm] ring test on 0 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388994] [drm] ring test on 1 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.388998] [drm] ring test on 2 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.389009] [drm] ring test on 3 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.389016] [drm] ring test on 4 succeeded in 1 usecs Oct 28 11:34:12 hostname kernel: [ 649.574547] [drm] ring test on 5 succeeded in 2 usecs Oct 28 11:34:12 hostname kernel: [ 649.574553] [drm] UVD initialized successfully. Oct 28 11:34:12 hostname kernel: [ 649.574583] [drm] ib test on ring 0 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574610] [drm] ib test on ring 1 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574637] [drm] ib test on ring 2 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574664] [drm] ib test on ring 3 succeeded in 0 usecs Oct 28 11:34:12 hostname kernel: [ 649.574692] [drm] ib test on ring 4 succeeded in 0 usecs Oct 28 11:34:13 hostname kernel: [ 649.725287] [drm] ib test on ring 5 succeeded 3) Some plugging and unplugging of the display occasionally shows the same messages in the log followed by the following: Oct 28 11:34:13 hostname kernel: [ 649.734010] snd_hda_intel :03:00.1: Enabling via VGA-switcheroo Oct 28 11:34:13 hostname kernel: [ 649.734117] snd_hda_intel :03:00.1: irq 70 for MSI/MSI-X Oct 28 11:34:18 hostname kernel: [ 654.876455] snd_hda_intel :03:00.1: Disabling via VGA-switcheroo Oct 28 11:34:18 hostname kernel: [ 654.908444] snd_hda_intel :03:00.1: Cannot lock devices! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set fo
