Comment 4 for bug 1767667

Thank you Joseph for your support.
Concerninig the context of this issue: I had an old Ubuntu 12.04;  I decided to upgrade it to 18.04 version and, in the same time, to upgrade the hardware of my old PC: Asus M/B AMD A320M-C (AM4)  as motherboard, and AMD CPU Ryzen 3 2200G (AM4) as processor.
This hardware upgrade was a mistake :
-the kernel didn t manage very well the new Ryzen CPU+GPU processor: as system was very unstable, frozen at any time I finally had to install a graphic card to bypass the gpu included inside the Ryzen chip; automatically all problems dissapeared...
-however I found out another issue: trying to restore my data stored in an external USB disk I realized that the kernel didn t detect 2.0  USB devices , and 3.0 USB devices were detected but followed just after by a system crash... I guess this is a issue with the new motherboard and/or its BIOS/UEFI (I could retrieve my data with ftp from another PC of my local network)
I will try to follow your advice and test with the 4.17 kernel.
Thank you again
Enviado desde Yahoo Mail para Android

  El mar., 1 de may. de 2018 a la(s) 15:01, Joseph Salisbury<email address hidden> escribió: 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.17 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.17-rc3

** Changed in: linux (Ubuntu)
  Importance: Undecided => High

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1767667

Title:
  kernel crash in gnome environment

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Apr 28 10:30:44 tatanka gnome-system-mo[4199]: Allocating size to gnome-system-monitor 0x16542b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
  Apr 28 10:35:49 tatanka kernel: [52343.522224] gmc_v9_0_process_interrupt: 59 callbacks suppressed
  Apr 28 10:35:49 tatanka kernel: [52343.522230] amdgpu 0000:08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:3 pas_id:0)
  Apr 28 10:35:49 tatanka kernel: [52343.522239] amdgpu 0000:08:00.0:  at page 0x0000000109400000 from 27
  Apr 28 10:35:49 tatanka kernel: [52343.522243] amdgpu 0000:08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
  Apr 28 10:35:49 tatanka kernel: [52343.522252] amdgpu 0000:08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:3 pas_id:0)
  Apr 28 10:35:49 tatanka kernel: [52343.522255] amdgpu 0000:08:00.0:  at page 0x0000000109403000 from 27
  Apr 28 10:35:49 tatanka kernel: [52343.522258] amdgpu 0000:08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031
  Apr 28 10:35:49 tatanka kernel: [52343.522266] amdgpu 0000:08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:3 pas_id:0)
  A
  (...)

  then all is freezed including ctrl+alt+F3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Apr 28 12:17:42 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767667/+subscriptions