Thanks for getting back to me. I've been running the system as a web server for 8 years round the clock and this is the first and only time I had an unexplained kernel crash. I sent the bug in because I was unable to interpret the dump and I was actually worried someone had hacked my system causing the failure.
I'm willing to check the upstream kernel but I've been running on the rebooted system since and have not seen the problem again so I'm not sure how long I'd have to run to verify the new kernel made any difference. If you can tell me either that this was a straight failure and not a hack or tell me how I could break down the dump and understand where and how it failed I'd be ok with closing this out. I just wanted to be sure it wasn't caused by malicious outside activity. The only thing different I noticed from my last automatic server upgrade is that I'm getting periodic java exceptions seemingly trace to gnome when I'm on the system. Which way should I go? Thanks again for getting back to me, John > On Mar 27, 2018, at 5:54 PM, Joseph Salisbury > <joseph.salisb...@canonical.com> wrote: > > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.16 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc7 > > ** Changed in: linux (Ubuntu) > Importance: Undecided => High > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > > ** Tags added: kernel-da-key > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1758796 > > Title: > Kernel Crash > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Have the logs around this. Failed while running unattended. > > ProblemType: KernelCrash > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-117-generic 4.4.0-117.141 > ProcVersionSignature: Ubuntu 4.4.0-117.141-generic 4.4.114 > Uname: Linux 4.4.0-117-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: johnny 8301 F.... pulseaudio > Date: Sun Mar 25 06:09:20 2018 > HibernationDevice: RESUME=UUID=5ed7ec2d-76de-4b8d-b427-f94d429221a5 > InstallationDate: Installed on 2011-12-21 (2285 days ago) > InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) > IwConfig: > lo no wireless extensions. > > eth0 no wireless extensions. > MachineType: MSI MS-7680 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-117-generic > root=UUID=430a9050-fa68-406c-812c-8a6384c75d43 ro quiet splash > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M > crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M > crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M > crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: > linux-restricted-modules-4.4.0-117-generic N/A > linux-backports-modules-4.4.0-117-generic N/A > linux-firmware 1.157.17 > RfKill: > > SourcePackage: linux > UpgradeStatus: Upgraded to xenial on 2016-08-18 (583 days ago) > dmi.bios.date: 04/11/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: V17.1 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: H61M-P21 (MS-7680) > dmi.board.vendor: MSI > dmi.board.version: 3.0 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: MSI > dmi.chassis.version: 3.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrV17.1:bd04/11/2011:svnMSI:pnMS-7680:pvr3.0:rvnMSI:rnH61M-P21(MS-7680):rvr3.0:cvnMSI:ct3:cvr3.0: > dmi.product.name: MS-7680 > dmi.product.version: 3.0 > dmi.sys.vendor: MSI > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758796/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758796 Title: Kernel Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
