[Bug 1761999] Re: general protection fault: 0000 [#1] SMP NOPTI

2019-03-06 Thread Kai-Heng Feng
Does this issue still happen on an up-to-date system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761999 Title: general protection fault: [#1] SMP NOPTI To manage notifications about this b

[Bug 1761999] Re: general protection fault: 0000 [#1] SMP NOPTI

2018-09-08 Thread Hubert Johannsen
I had an ugly instance of this problem on an EPYC processor. Not sure what it was related to. It all started with errors during package upgrades. sudo apt-get update >> success sudo apt-get upgrade >> segmentation fault The upgrade left several packages in a half-installed state (attach Part 1),

[Bug 1761999] Re: general protection fault: 0000 [#1] SMP NOPTI

2018-09-08 Thread Hubert Johannsen
The logs have been anonymised. Problem started around the time 00:50 ** Attachment added: "paste1.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761999/+attachment/5186535/+files/paste1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is su

[Bug 1761999] Re: general protection fault: 0000 [#1] SMP NOPTI

2018-04-12 Thread Saxfusion
So i removed virtualbox and guest dkms and installed Mainline 4.16.1-041601 and i conclude 'kernel-bug-exists-upstream' The filebot window as well as the nautilus window that i drag the files from freeze. The system and Desktop is still responsive (but sometimes was before as well with Kernel 4

Re: [Bug 1761999] Re: general protection fault: 0000 [#1] SMP NOPTI

2018-04-10 Thread Saxfusion
Will try to do so, but Friday at the earliest since I am not at home during the week. Hope I get it right with uninstalling VirtualBox and stuff and getting all necessary packages for the mainline build. Joseph Salisbury schrieb am Di., 10. Apr. 2018, 17:51: > Would it be possible for you to tes

[Bug 1761999] Re: general protection fault: 0000 [#1] SMP NOPTI

2018-04-10 Thread Joseph Salisbury
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 t