general protection fault: 0000 [#1] SMP NOPTI

[Saxfusion]

Filebot tried to write to network storage, chrashed nautilus and the system

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Sat Apr 7 15:55:03 2018
Failure: oops
HibernationDevice: RESUME=UUID=16b94b21-aecc-4d2e-93f5-13640ea3517b
InstallationDate: Installed on 2014-04-20 (1448 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-790XT-USB3
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic root=UUID=2e3a0b23-1dde-4570-aa78-bd8253bbd52a ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:

SourcePackage: linux
Title: general protection fault: 0000 [#1] SMP NOPTI
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: GA-790XT-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-790XT-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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

[Saxfusion (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 <email address hidden> schrieb am Di., 10. Apr.
2018, 17:51:

> 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
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1761999
>
> Title:
> general protection fault: 0000 [#1] SMP NOPTI
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761999/+subscriptions
>

[Saxfusion (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.15)

[Hubert Johannsen (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), and basic os command started to crash (attach Part 2).
In the syslog I had "general protection fault: 0000 [#1] SMP NOPTI" with multiple processes, see a detail failure log in attach Part 3 and Part 4. Attach Part 5 lists numerous processes that had the same failure as Part 4.
The system load started to climb, from idle, progressively by about 1 point per 3-5 min, until levels like 20-30, at this point it was very difficult to enter and reboot the system. I tried and managed to have it respond with reboot -f but it had the problem still and system did not come up correctly, until we performed a physical shutdown and restart. From then the system seems clean. I corrected the packages by reinstallation, and so far no problem.
Very frightening!
Can it be related to some problem between Ubuntu and the Ryzen/EPYC technology?

Please comment if you think this is a completely different bug.
Thanks!

[Hubert Johannsen (hubert-johannsen)]

The logs have been anonymised. Problem started around the time 00:50

[Kai-Heng Feng (kaihengfeng)]

Does this issue still happen on an up-to-date system?