[Kernel-packages] [Bug 1820031] Re: My Ubuntu 18.04 GUI seems frozen
Nothing new comes out in the crash report. When I visit https://errors.ubuntu.com/user/1d81a00d35531ca846cc8b470c853c9c4cc299c3a0a42040e68da92210168a3d96818f5de95d8f7d85e66516d77e481a6259123145189d1685f6d22ac584114a the most recent report is: https://errors.ubuntu.com/oops/0d2b0694-2b7d-11e9-9d81-fa163e102db1 I shall try to apply the work around from https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/994921 as suggested in step 3 of the instructions you have linked to. I do not need to apply it as it is already in place. So what next... apport-collect perhapse although it seems that enough debug may be already posted. Maybe just a reboot of my system (as I cannot restart a service) and move on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820031 Title: My Ubuntu 18.04 GUI seems frozen Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This will possibly be a duplicate of Bug #1820028 or Bug #1820029 or Bug #1820030 I was trying to report a frozen GUI over SSH. This is the second report that apport-cli generated when I ran it with xorg as the target package. I made three four reports to see if different diagnostics were geneereated as Ihave no way of knowing what is causing the lock up at present. The symptoms I see are that I started running a go test last night and my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless mouse or keyboard to move anything on the display and the time shown on the clock matches when things froze last night. Before I made the report I looked for any process using high amounts of CUP with top and htop but spotted none. I tried to local a SIGTERM the go test process but that made no difference. I shall attempt to restart my desktop service ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 14 09:12:51 2019 DistUpgraded: 2018-07-27 11:19:59,510 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] InstallationDate: Installed on 2017-11-16 (482 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=473dc1b9-3a5c-4f95-8cc0-e3b0f628ca41 ro quiet splash vt.handoff=1 SourcePackage: xorg UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused Error: unable to open display UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago) dmi.bios.date: 09/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0811 dmi.board.asset.tag: Default string dmi.board.name: STRIX H270F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0811:bd09/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Mar 12 13:46:44 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: modeset To manage notifications about thi
[Kernel-packages] [Bug 1653636] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)
Thank you Joseph, the upstream kernel from months ago was the cause of the issue. I had completely forgotten about it being there and did not recognise the change in version numbering as significant. I followed the steps outlined in http://askubuntu.com/a/594484/109072 to remove the kernel and a reboot now comepletes cleanly. The steps I performed were: > If compiled and installed via make install, you will need to manually remove > the following entries: > > /boot/vmlinuz*KERNEL-VERSION* > /boot/initrd*KERNEL-VERSION* > /boot/System-map*KERNEL-VERSION* > /boot/config-*KERNEL-VERSION* > /lib/modules/*KERNEL-VERSION*/ > /var/lib/initramfs/*KERNEL-VERSION*/ Where KERNEL-VERSION for me was 4.4.21*. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technolo
[Kernel-packages] [Bug 1653636] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)
I expect I got the kernel the same way I get most of my kernels, though an `apt-get upgrade`. Although I did try and compile a kernel a while ago... I wonder if that got left around as an install option and it was so long since I last rebooted I forgot about it! Now isn't that a silly thing to do. I will reboot into 4.4.0-57 and apply updates. Then probably remove the upstream kernel or at least try updating it and seeing if it boots then remove it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscri
[Kernel-packages] [Bug 1653636] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)
apport information ** Tags added: apport-collected ** Description changed: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. - If there are any more steps I can take to aid diagnosis please let me - know. + If there are any more steps I can take to aid diagnosis please let me know. + --- + ApportVersion: 2.20.1-0ubuntu2.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: thomasthorne 4613 F pulseaudio + /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio + /dev/snd/controlC1: thomasthorne 4613 F pulseaudio + /dev/snd/controlC0: thomasthorne 4613 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca + InstallationDate: Installed on 2015-03-12 (662 days ago) + InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) + IwConfig: + lono wireless extensions. + + eth1 no wireless extensions. + + eth0 no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M + ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-57-generic N/A + linux-backports-modules-4.4.0-57-generic N/A + linux-firmware1.157.6 + RfKill: + + Tags: xenial + Uname: Linux 4.4.0-57-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 08/11/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F6 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H81M-DS2V + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.name: H81M-DS2V + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799327/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended wit
[Kernel-packages] [Bug 1653636] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799338/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799330/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] Re: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)
I have executed the command `apport-collect 1653636` as requested by brad-figg. I can see that log files have been added. Note that this command was performed while running 4.4.0-57-generic not the 4.4.21 kernel that causes the issue. It is also worth noting that as the filesystem could not be mounted the kernel panic trace was not recorded to disk and as a result is not included in any of the attached log files. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pac
[Kernel-packages] [Bug 1653636] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799336/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799332/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799331/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799333/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799337/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799328/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799334/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799329/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799335/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653636] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1653636/+attachment/4799339/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653636 Title: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) Status in linux package in Ubuntu: Confirmed Bug description: On powering my PC up after the holiday break I got a welcome back in the form of a kernel panic. I had completed some upgrades before the holiday and was seeing a restart to use the newly upgraded packages message. When the PC powered on the Caps Lock and Scroll Lock lights on my keyboard were blinking. After passing through grub and attempting to boot the kernel the boot message ended with the following message (typed out by me by hand, please see the attached photograph of the screen for more details): Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ cut here ] WARNING: CPU: 0 PID: 1 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x60/0x70( Modules linked in: CPU: 0 PID 1: Comm: swapper/0 Not tainted 4.4.21 #1 Hardware name: Gigabyte Technology Cp., Ltd. H81M-DS2V/H81M-DS2V, BIOS F6 08/11/2015 ... Call Trace: ... dump_stack ... warn_slowpath_common ... warn_slowpath_null ... native_smp_send_rescheduale ... trigger_load_balance ... scheduler_tick ... ? tick_sched_handle.isra ... update_process_times ... tick_sched_handle.isra I can type out more of the message if people want but I think the chances of my typing it all in correctly are slim. I tried to boot using the (recovery mode) version of 4.4.21 and the .old version of 4.4.21 that seemed to have appeared from somewhere. To my eye the problem looked the same in each version. Once I selected 4.4.0-57-generic I was able to complete the boot and begin reporting this bug. If there are any more steps I can take to aid diagnosis please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomasthorne 4613 F pulseaudio /dev/snd/pcmC1D0p: thomasthorne 4613 F...m pulseaudio /dev/snd/controlC1: thomasthorne 4613 F pulseaudio /dev/snd/controlC0: thomasthorne 4613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3c3104a1-5ead-4ebf-b2df-f9397f572dca InstallationDate: Installed on 2015-03-12 (662 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1618771] Re: package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 on
I have raised bug 1618778 to cover the kernel panic that we had. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1618771 Title: package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 on boot after autoupgrade while /boot was 100% full Status in linux-lts-vivid package in Ubuntu: New Bug description: A virtual machine running on a Windows Server 2012R2 Hyper-V system rebooted as part of an automated upgrade last night. It seems to have just installed the new 3.19.0-68-generic kernel. The system failed to boot and instead kernel paniced. As part of investigating the problem we tried booting the previously installed kernel (66 I think) and could bring up the system OK. It asked to perform a disk check on / and /boot as it came up, which seemed to go fine. Once we were running a `df -h` showed that /boot was 100% full with no space left at all. To improve the system an `apt-get autoremove` was run which uninstalled a bunch of older kernels, freeing just over 100MB of space from /boot. Power cycling the system allowed us to boot successfully under the new 3.19.0-68 kernel. Hopefully the /var/crash/linux-image-3.19.0-68-generic.0.crash file I found and am using the file this report related to the issue I have described. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Aug 30 06:51:28 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-02-08 (204 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1618771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1618778] [NEW] Kernel Panic from 3.19.0-68-generic VFS: Unable to mount root fs on unknown-block(0, 0)
Public bug reported: This is the same machine as I just reported bug 1618771 against. I am raising this bug by hand to report the kernel panic that I was talking about in 1618771. A virtual machine running on a Windows Server 2012R2 Hyper-V system rebooted as part of an automated upgrade last night. It seems to have just installed the new 3.19.0-68-generic kernel. The system failed to boot and instead kernel paniced. As part of investigating the problem we tried booting the previously installed kernel (66 I think) and could bring up the system OK. It asked to perform a disk check on / and /boot as it came up, which seemed to go fine. Once we were running a `df -h` showed that /boot was 100% full with no space left at all. To improve the system an `apt-get autoremove` was run which uninstalled a bunch of older kernels, freeing just over 100MB of space from /boot. Power cycling the system allowed us to boot successfully under the new 3.19.0-68 kernel. We have an image of the failed boot message & I will type out a few of the lines here: VFS: Cannot open root device "mapper/warden--vg-root" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 0b00 1048575 sr0 driver: sr Kernel panic - not syncing: VFS: Unable to mount root fs unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-68-generic #76~14.04.1-Ubuntu Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006 05/23/2012 ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Image of the end of the kernel panic output" https://bugs.launchpad.net/bugs/1618778/+attachment/4731414/+files/kernel-panic-on-boot.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1618778 Title: Kernel Panic from 3.19.0-68-generic VFS: Unable to mount root fs on unknown-block(0,0) Status in linux-lts-vivid package in Ubuntu: New Bug description: This is the same machine as I just reported bug 1618771 against. I am raising this bug by hand to report the kernel panic that I was talking about in 1618771. A virtual machine running on a Windows Server 2012R2 Hyper-V system rebooted as part of an automated upgrade last night. It seems to have just installed the new 3.19.0-68-generic kernel. The system failed to boot and instead kernel paniced. As part of investigating the problem we tried booting the previously installed kernel (66 I think) and could bring up the system OK. It asked to perform a disk check on / and /boot as it came up, which seemed to go fine. Once we were running a `df -h` showed that /boot was 100% full with no space left at all. To improve the system an `apt-get autoremove` was run which uninstalled a bunch of older kernels, freeing just over 100MB of space from /boot. Power cycling the system allowed us to boot successfully under the new 3.19.0-68 kernel. We have an image of the failed boot message & I will type out a few of the lines here: VFS: Cannot open root device "mapper/warden--vg-root" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 0b00 1048575 sr0 driver: sr Kernel panic - not syncing: VFS: Unable to mount root fs unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-68-generic #76~14.04.1-Ubuntu Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006 05/23/2012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1618778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1618771] Re: package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 on
Oh, this is not the kernel panic I was thinking that I was reporting. It does show that there was some kind of problem with the upgrade process though. That may relate to the kernel panic which I saw. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1618771 Title: package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 on boot after autoupgrade while /boot was 100% full Status in linux-lts-vivid package in Ubuntu: New Bug description: A virtual machine running on a Windows Server 2012R2 Hyper-V system rebooted as part of an automated upgrade last night. It seems to have just installed the new 3.19.0-68-generic kernel. The system failed to boot and instead kernel paniced. As part of investigating the problem we tried booting the previously installed kernel (66 I think) and could bring up the system OK. It asked to perform a disk check on / and /boot as it came up, which seemed to go fine. Once we were running a `df -h` showed that /boot was 100% full with no space left at all. To improve the system an `apt-get autoremove` was run which uninstalled a bunch of older kernels, freeing just over 100MB of space from /boot. Power cycling the system allowed us to boot successfully under the new 3.19.0-68 kernel. Hopefully the /var/crash/linux-image-3.19.0-68-generic.0.crash file I found and am using the file this report related to the issue I have described. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Aug 30 06:51:28 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-02-08 (204 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1618771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1618771] [NEW] package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 o
Public bug reported: A virtual machine running on a Windows Server 2012R2 Hyper-V system rebooted as part of an automated upgrade last night. It seems to have just installed the new 3.19.0-68-generic kernel. The system failed to boot and instead kernel paniced. As part of investigating the problem we tried booting the previously installed kernel (66 I think) and could bring up the system OK. It asked to perform a disk check on / and /boot as it came up, which seemed to go fine. Once we were running a `df -h` showed that /boot was 100% full with no space left at all. To improve the system an `apt-get autoremove` was run which uninstalled a bunch of older kernels, freeing just over 100MB of space from /boot. Power cycling the system allowed us to boot successfully under the new 3.19.0-68 kernel. Hopefully the /var/crash/linux-image-3.19.0-68-generic.0.crash file I found and am using the file this report related to the issue I have described. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Aug 30 06:51:28 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-02-08 (204 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1618771 Title: package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 on boot after autoupgrade while /boot was 100% full Status in linux-lts-vivid package in Ubuntu: New Bug description: A virtual machine running on a Windows Server 2012R2 Hyper-V system rebooted as part of an automated upgrade last night. It seems to have just installed the new 3.19.0-68-generic kernel. The system failed to boot and instead kernel paniced. As part of investigating the problem we tried booting the previously installed kernel (66 I think) and could bring up the system OK. It asked to perform a disk check on / and /boot as it came up, which seemed to go fine. Once we were running a `df -h` showed that /boot was 100% full with no space left at all. To improve the system an `apt-get autoremove` was run which uninstalled a bunch of older kernels, freeing just over 100MB of space from /boot. Power cycling the system allowed us to boot successfully under the new 3.19.0-68 kernel. Hopefully the /var/crash/linux-image-3.19.0-68-generic.0.crash file I found and am using the file this report related to the issue I have described. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-68.76~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Aug 30 06:51:28 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-02-08 (204 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1618771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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. 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 same with a USB temperature probe and could see it connect too. --- 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 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Confirmed Bug description: 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. 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 same with a USB temperature probe and could see it connect too. --- 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 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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. 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 same with a USB temperature probe and could see it connect too. --- 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 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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. 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 same with a USB temperature probe and could see it connect too. --- 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 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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. 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 same with a USB temperature probe and could see it connect too. --- 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 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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=show&redirect=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 Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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. 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 same with a USB temperature probe and could see it connect too. --- 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 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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=show&redirect=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=show&redirect=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 Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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. 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 same with a USB temperature probe and could see it connect too. --- 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 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.
[Kernel-packages] [Bug 1453029] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404618/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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 RfKi
[Kernel-packages] [Bug 1453029] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404629/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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:
[Kernel-packages] [Bug 1453029] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404621/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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:
[Kernel-packages] [Bug 1453029] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404624/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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
[Kernel-packages] [Bug 1453029] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404625/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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
[Kernel-packages] [Bug 1453029] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404627/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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 RfKi
[Kernel-packages] [Bug 1453029] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404622/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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:
[Kernel-packages] [Bug 1453029] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404623/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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
[Kernel-packages] [Bug 1453029] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404619/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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: T
[Kernel-packages] [Bug 1453029] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404628/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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:
[Kernel-packages] [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 + dmi.b
[Kernel-packages] [Bug 1453029] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404626/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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
[Kernel-packages] [Bug 1453029] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1453029/+attachment/4404620/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Incomplete Bug description: 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
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-lts-utopic in 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 Status in linux-lts-utopic package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1453029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-lts-utopic in 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 Status in linux-lts-utopic package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1453029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-lts-utopic in 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 Status in linux-lts-utopic package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1453029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1453033] [NEW] Rebooted after updates and then this morning : general protection fault: 0000 [#26] SMP
Public bug reported: The first 4 error reports suggested that they were duplicates, so I have only raised https://bugs.launchpad.net/ubuntu/+source/linux-lts- utopic/+bug/1453029 this error report seems to have not done so so I have raised a 2nd ticket in case it gets more debug added automatically that is of use. --- 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 after rebooting it last night. 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. 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: Thu May 7 17:37:48 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: [#26] SMP UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1453033 Title: Rebooted after updates and then this morning : general protection fault: [#26] SMP Status in linux-lts-utopic package in Ubuntu: New Bug description: The first 4 error reports suggested that they were duplicates, so I have only raised https://bugs.launchpad.net/ubuntu/+source/linux-lts- utopic/+bug/1453029 this error report seems to have not done so so I have raised a 2nd ticket in case it gets more debug added automatically that is of use. --- 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 after rebooting it last night. 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
[Kernel-packages] [Bug 1453029] [NEW] Tried to login, GUI locked up. Did reboot & was presented with several messages : general protection fault: 0000 [#31] SMP
Public bug reported: 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) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in 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 Status in linux-lts-utopic package in Ubuntu: New Bug description: 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 th