[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot & was presented with several messages : general protection fault: 0000 [#31] SMP
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot & was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot & was presented with several messages : general protection fault: 0000 [#31] SMP
My apologies Chris but I am meant to use the LTS releases on my work machines. Also have been running with 3.16.0-57-generic #77~14.04.1-Ubuntu for a while now and not seen a repeat of this very intermittent issue in the last 6 months. I don't think I can confirm what caused the change in behaviour or be sure if the problem does or does not currently exist on this machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot & was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot & was presented with several messages : general protection fault: 0000 [#31] SMP
Thomas A. F. Thorne, to see if this is already resolved, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot & was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.1-rc8 needs-reverse-bisect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
It h as been about 1 month and I am happy to report that I have not seen the issue again while using the upstream kernel. Marking bug as confirmed as requested. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
At some point a software upgrade has switched me back to an older kernel. I was checking uname -r after any reboot following a kernel package update to check I was loaded in the correct way but I missed when this switched. To further complicate things I used purge-old- kernels to free up space on my /boot partition and although I am sure I checked that it didn't say it was removing the 4.1.0 kernel I thought I was on, I now only seem to have the headers in place. This bug seemed to be quite intermittent so ~2 weeks of testing is probably not enough to say it is not present in the updated kernel line. I will try and install the latest kernel again now. Top of that page is: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/ $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/linux-headers-4.1.0-040100rc8-generic_4.1.0-040100rc8.201506150335_amd64.deb $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/linux-headers-4.1.0-040100rc8_4.1.0-040100rc8.201506150335_all.deb $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/linux-image-4.1.0-040100rc8-generic_4.1.0-040100rc8.201506150335_amd64.deb sudo dpkg -i *.deb That seems to install OK. Hopefully the next post from me will be in about 1 month to say that things are still working well or slightly sooner to confirm that I have hit the issue running the newer kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
Not hit this problem again yet and I have been running the updated kernel for a week. I have just hit bug#1462308 which seems to report a problem with X but I don't know if it is related to this issue or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
Reading the instructions again: the latest upstream kernel available from the very top line at the top of the page So does that mean I should be looking to get http://kernel.ubuntu.com /~kernel-ppa/mainline/drm-intel-next/current/ which seems to be a 4.1 Kernel instead of the 3.16 that is currently on my machine. Hey, now I get a different page off of your original link. https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=showredirect=KernelMainlineBuilds now shows a link to http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D and at the top of that page is http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc5-unstable/ I shall follow the instructions for downloading and installing then get back to you with the results. Seems to take a week or two for the problem to surface so it might take a while for me to declare a Kernel good. I suppose it would be quite easy to make it bad though if it fails. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
I think I have been lucky in getting things working on the first try. I have now booted into: $ uname -a Linux thorne-ul-dt 4.1.0-040100rc5-generic #201505250235 SMP Mon May 25 02:37:02 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux I'll keep an eye on things and see if I can repeat the problem or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
apport information ** Tags added: apport-collected ** Description changed: I noticed a problem last week where my GUI locked up while I was trying to unlock it. At the time I was unable to get the system to generate a report or find anything obvious to me in the logs, though I am no expert. I did manage to enable some more analysis tools for next time and it seems that next time has just occurred. Today I tried to login to the system. The screen progressed passed the password entry but failed to display the desktop background, the side bar or the top bar. I left it for a few minutes while I got a coffee but it was still in the same state when I returned. Thinking it might just be the GUI locked up, as it seemed to be last week, I tried to ssh in from another machine. tt@172.16.20.39's password: Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.16.0-37-generic x86_64) * Documentation: https://help.ubuntu.com/ Last login: Fri May 1 12:46:41 2015 from 172.16.20.98 tt@tt-ul-dt:~$ tt@tt-ul-dt:~$ tt@tt-ul-dt:~$ top Segmentation fault tt@tt-ul-dt:~$ ps As you can see, I managed to SSH in but failed to do much else. When I tried to take a look at what was going on with top I got a message about a Segmentation fault. I then tried ps thinking that might be a simpler program and able to show me something. That seemed to lock up the ssh session. Next I did a quick Google to see what I might be able to do remotely to help debug things. Nothing helpful presented itself to me so I did Ctrl + Alt + F4 to try and get access via one of the other virtual terminal things. I was able to enter my username and password but as soon as I had done so I seemed to get some sort of log trace on the screen. It mentioned the USB mouse I had being connected. I was not able to enter any commands so instead I tried unplugging and reconnecting the USB memory stick I had. I could see it registering in the trace. I did the same with a USB temperature probe and could see it connect too. After that I figured a clean shutdown was about the best I could do. I found http://askubuntu.com/questions/53263/shut-down-computer-from- keyboard and started the Alt + SysRq + r, e, i, s, u, o. The first two of three keys reported that they were disabled but after that it seemed to work. After the shutdown, I left the machine till 09:01 and powered it on again. It booted, I logged in and was then presented with several System program problem detected messages. I am now trying to work through them in the sequence they were presented. $ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-37-generic 3.16.0-37.49~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-37.49~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Fri May 8 02:20:53 2015 Failure: oops InstallationDate: Installed on 2015-03-12 (56 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic Title: general protection fault: [#31] SMP UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.14.1-0ubuntu3.11 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: thomasthorne 2648 F pulseaudio + /dev/snd/controlC0: thomasthorne 2648 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca + InstallationDate: Installed on 2015-03-12 (74 days ago) + InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M vt.handoff=7 + ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 + RelatedPackageVersions: + linux-restricted-modules-3.16.0-38-generic N/A + linux-backports-modules-3.16.0-38-generic N/A + linux-firmware 1.127.12 + RfKill: + + Tags: trusty + Uname: Linux 3.16.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin mock plugdev sambashare sudo + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 06/19/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F5 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H81M-DS2V +
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
** Description changed: - I noticed a problem last week where my GUI locked up while I was trying - to unlock it. At the time I was unable to get the system to generate a - report or find anything obvious to me in the logs, though I am no - expert. I did manage to enable some more analysis tools for next time - and it seems that next time has just occurred. + Today I tried to login to the system. The screen progressed passed the + password entry but failed to display the desktop background, the side + bar or the top bar. I left it for a few minutes while I got a coffee but + it was still in the same state when I returned. I managed to SSH in but + failed to do much else. When I tried to take a look at what was going on + with top I got a message about a Segmentation fault. I then tried ps and + the ssh session locked up. - Today I tried to login to the system. The screen progressed passed the - password entry but failed to display the desktop background, the side - bar or the top bar. I left it for a few minutes while I got a coffee - but it was still in the same state when I returned. Thinking it might - just be the GUI locked up, as it seemed to be last week, I tried to ssh - in from another machine. - - tt@172.16.20.39's password: - Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.16.0-37-generic x86_64) - - * Documentation: https://help.ubuntu.com/ - - Last login: Fri May 1 12:46:41 2015 from 172.16.20.98 - - - tt@tt-ul-dt:~$ - tt@tt-ul-dt:~$ - tt@tt-ul-dt:~$ top - Segmentation fault - tt@tt-ul-dt:~$ ps - - As you can see, I managed to SSH in but failed to do much else. When I - tried to take a look at what was going on with top I got a message about - a Segmentation fault. I then tried ps thinking that might be a simpler - program and able to show me something. That seemed to lock up the ssh - session. - - Next I did a quick Google to see what I might be able to do remotely to - help debug things. Nothing helpful presented itself to me so I did Ctrl - + Alt + F4 to try and get access via one of the other virtual terminal - things. I was able to enter my username and password but as soon as I - had done so I seemed to get some sort of log trace on the screen. It - mentioned the USB mouse I had being connected. I was not able to enter + I was able to enter my username and password at a vt but as soon as I + had done so I seemed to get some sort of log trace on the screen. It + mentioned the USB mouse I had being connected. I was not able to enter any commands so instead I tried unplugging and reconnecting the USB - memory stick I had. I could see it registering in the trace. I did the + memory stick I had. I could see it registering in the trace. I did the same with a USB temperature probe and could see it connect too. - After that I figured a clean shutdown was about the best I could do. I - found http://askubuntu.com/questions/53263/shut-down-computer-from- - keyboard and started the Alt + SysRq + r, e, i, s, u, o. The first two - of three keys reported that they were disabled but after that it seemed - to work. - - After the shutdown, I left the machine till 09:01 and powered it on - again. It booted, I logged in and was then presented with several - System program problem detected messages. I am now trying to work - through them in the sequence they were presented. - - $ lsb_release -rd - Description:Ubuntu 14.04.2 LTS - Release:14.04 - - ProblemType: KernelOops - DistroRelease: Ubuntu 14.04 - Package: linux-image-3.16.0-37-generic 3.16.0-37.49~14.04.1 - ProcVersionSignature: Ubuntu 3.16.0-37.49~14.04.1-generic 3.16.7-ckt9 - Uname: Linux 3.16.0-37-generic x86_64 - Annotation: Your system might become unstable now and might need to be restarted. - ApportVersion: 2.14.1-0ubuntu3.10 - Architecture: amd64 - Date: Fri May 8 02:20:53 2015 - Failure: oops - InstallationDate: Installed on 2015-03-12 (56 days ago) - InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) - SourcePackage: linux-lts-utopic - Title: general protection fault: [#31] SMP - UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: thomasthorne 2648 F pulseaudio - /dev/snd/controlC0: thomasthorne 2648 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: thomasthorne 2648 F pulseaudio + /dev/snd/controlC0: thomasthorne 2648 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (74 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + lono wireless
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
I am slightly confused by the instructions. test the latest upstream kernel available from the very top line at the top of the page lease do not test the daily folder The page linked https://wiki.ubuntu.com/KernelMainlineBuilds redirects to https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=showredirect=KernelMainlineBuilds and currently reads: We currently build five sets of upstream kernels. All formal tags from Linus' tree and from the stable trees, plus: 1) the daily tip of Linus' linux kernel source tree, 2) the tip of the drm-next head of Dave Airlie's linux repository daily, 3) the tip of the drm-intel-next head of Keith Packard's linux repository daily until 2012, after which it has been taken over by Daniel Vetter at http://cgit.freedesktop.org/drm-intel/, and in particular, the drm-intel-next branch, 4) the tip of the master branch of the debloat-testing tree daily, 5) tags from the combined v2.6.32.x.y tree (by StefanBader) which is v2.6.32.x with DRM from 2.6.33.y. So should I be using the Daily Tip of Linus's Linux kernel source tree or not? Do you actually want me to go to https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=showredirect=KernelMainlineBuilds#Installing_upstream_kernels which includes a link to http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.4-utopic/ where it seems I can cut out some of the URL to get http://kernel.ubuntu.com/~kernel-ppa/mainline/ which does include a daily folder for me to avoid. I am on Ubuntu 14.04.2 LTS (Trusty Tahr, and the latest build for that seems to be http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.15-rc2-trusty/ so should I download the relevant files from there and start on the install instructions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
Thomas A. F. Thorne, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where XY and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-f5 ** Changed in: linux (Ubuntu) Importance: Low = Medium ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+attachment/4393438/+files/Dependencies.txt ** Attachment removed: OopsText.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+attachment/4393439/+files/OopsText.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
Thomas A. F. Thorne, thank you for reporting this and helping make Ubuntu better. Could you please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1453029 ** Package changed: linux-lts-utopic (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
Nothing has turned up on the longer memory test either. I think the hardware (at least the CPU and RAM) are OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
Out of the many error report windows that popped up, only 1 suggested it was not this bug. I raised https://bugs.launchpad.net/ubuntu/+source /linux-lts-utopic/+bug/1453033 as a result, in case it has any extra debug information in it. Looking over the how to triage page, I can see that checking the memory of the machine is one of the first things that I should do. I have now created a bootable USB stick that should work with my system. I will try and kick off a memory test later today and report the results on Monday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453029] Re: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: 0000 [#31] SMP
I completed 1 pass of the memtest test set without any errors being recorded. I'll see about running a longer test cycle soon in case it turns up anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453029 Title: Tried to login, GUI locked up. Did reboot was presented with several messages : general protection fault: [#31] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1453029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs