Activity log for bug #1763273

Date Who What changed Old value New value Message
2018-04-12 06:51:11 Chris Darroch bug added bug
2018-04-12 06:51:11 Chris Darroch attachment added radeon_kernel_panic1.jpg https://bugs.launchpad.net/bugs/1763273/+attachment/5111739/+files/radeon_kernel_panic1.jpg
2018-04-12 06:55:27 Chris Darroch description I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.3 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.3 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen, or we get a kernel panic text screen (see attached screen photo). I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.3 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.3 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much!
2018-04-12 07:00:53 Chris Darroch description I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.3 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.3 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.1 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.1 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much!
2018-04-12 07:06:06 Simon Quigley bug task added xorg (Ubuntu)
2018-04-12 07:06:25 Simon Quigley bug task added linux (Ubuntu)
2018-04-12 07:06:52 Simon Quigley bug task deleted ubuntu
2018-04-12 07:30:05 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2018-04-16 01:20:20 RBL Admin attachment added Full kern.log from April 1 crash https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117229/+files/apr1.full.kern.log
2018-04-16 03:18:29 RBL Admin attachment added Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117322/+files/Xorg.0.log
2018-04-16 03:19:19 RBL Admin attachment added rom.vga.bin https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117323/+files/rom.vga.bin
2018-04-16 03:19:36 RBL Admin attachment added gdb-Xorg.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117324/+files/gdb-Xorg.txt
2018-04-16 03:31:23 RBL Admin attachment added syslog with output from Alt-SysRq-t in ssh session https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117347/+files/syslog
2018-04-16 06:42:14 Chris Darroch tags amd64 apport-bug compiz-0.9 freeze ubuntu xenial
2018-04-16 06:49:40 Chris Darroch attachment added CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117628/+files/CurrentDmesg.txt
2018-04-16 06:50:00 Chris Darroch attachment added Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117629/+files/Dependencies.txt
2018-04-16 06:50:21 Chris Darroch attachment added DpkgLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117630/+files/DpkgLog.txt
2018-04-16 06:51:11 Chris Darroch attachment added JournalErrors.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117651/+files/JournalErrors.txt
2018-04-16 06:51:23 Chris Darroch attachment added LightdmDisplayLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117652/+files/LightdmDisplayLog.txt
2018-04-16 06:52:43 Chris Darroch attachment added Lspci.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117653/+files/Lspci.txt
2018-04-16 06:53:29 Chris Darroch attachment added Lsusb.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117654/+files/Lsusb.txt
2018-04-16 06:53:40 Chris Darroch attachment added ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117655/+files/ProcCpuinfo.txt
2018-04-16 06:53:50 Chris Darroch attachment added ProcCpuinfoMinimal.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117656/+files/ProcCpuinfoMinimal.txt
2018-04-16 06:54:00 Chris Darroch attachment added ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117657/+files/ProcInterrupts.txt
2018-04-16 06:54:21 Chris Darroch attachment added ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117658/+files/ProcModules.txt
2018-04-16 06:54:46 Chris Darroch attachment added UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117660/+files/UdevDb.txt
2018-04-16 06:54:56 Chris Darroch attachment added UnitySupportTest.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117661/+files/UnitySupportTest.txt
2018-04-16 06:55:06 Chris Darroch attachment added XorgLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117662/+files/XorgLog.txt
2018-04-16 06:55:17 Chris Darroch attachment added XorgLogOld.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117663/+files/XorgLogOld.txt
2018-04-16 06:55:26 Chris Darroch attachment added Xrandr.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117664/+files/Xrandr.txt
2018-04-16 06:55:38 Chris Darroch attachment added xdpyinfo.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117665/+files/xdpyinfo.txt
2018-04-16 06:55:49 Chris Darroch attachment added xserver.outputs.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117666/+files/xserver.outputs.txt
2018-04-16 06:56:32 Chris Darroch attachment added LightdmLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117670/+files/LightdmLog.txt
2018-04-16 06:59:10 Launchpad Janitor xorg (Ubuntu): status New Confirmed
2018-04-23 18:33:55 Chris Darroch linux (Ubuntu): status Incomplete Confirmed
2018-04-24 04:36:01 Chris Darroch attachment added radeon_kernel_panic2.jpg https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5126315/+files/radeon_kernel_panic2.jpg
2018-11-12 06:46:59 Daniel van Vugt bug task deleted xorg (Ubuntu)