Hi, long story short - I've wasted your time. I installed upstream kernel, also then reviewed logs I attached from my bug report.
I think cpus are being managed just fine in 4.15.0-22-generic and 4.17. There were ACPI errors - but googling indicates these are likely triggered by programming errors in the mobo efi os. I didn't capture logs from the first times the system hung, but muddied waters trying different things for some time and lost them in the reformatting. I now think its possible/likely that in upgrading from an earlier cpu, using a boot drive set up for bios under uefi caused, amidst other instabilities, the logging I saw of rejections of some cpus. But I have no evidence and the systems are working normally now. In fact, bloody well, great. Glass half full, after 5 days of intense activity ,I can now follow the bug report process. Thanks for your patience, Bob. ** Description changed: This came about as I had problems with efi while installing a dual boot of ubuntu and linux mint. As I understand it, during the boot process, the kernel sees a cpu count for the processor chip , AMD Ryzen 2400G, as 8 but 4 of them are graphics compute units. A little later in the process, the graphics processors cause errors. Subsequent to discovering this , I have added a line to grub GRUB_CMDLINE_LINUX_ which appears to have improved the boot process. It is 'ruc_nocbs=0-3'. The alteration in grub seems to help limit the cpu count and gets the boot process over the bump. I searched the interweb for clues and this seems to be a successful experiment. I am reporting this because I could not find any pertinent reference to this sort of problem with this particular chip. This search was not exhaustive so I hope I am not wasting your time :) I am attaching a file of concatenated system info for kernel reports as the options on this page only appear to allow one file to be selected (https://bugs.launchpad.net/ubuntu/+source/linux/+filebug/4aca6a90-6dc0-11e8 -b34a-002481e7f48a. - Most of this was my lack of understanding the efi requirements, but the + Most of this was my lack of understanding the efi requirements, but the lack of useful information in the Gigabyte motherboard manual about how the UEFI operation was managed by its operating system prolonged my agony.:) I hope this helps, thank you and keep up the fantastic work Bob. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC1: tpf 1528 F.... pulseaudio - /dev/snd/controlC0: tpf 1528 F.... pulseaudio + USER PID ACCESS COMMAND + /dev/snd/controlC1: tpf 1528 F.... pulseaudio + /dev/snd/controlC0: tpf 1528 F.... pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jun 12 09:38:39 2018 HibernationDevice: RESUME=UUID=150c1cd8-2246-4c18-b40e-dc07d8425777 InstallationDate: Installed on 2018-06-10 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR=<set> - LANG=en_NZ.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR=<set> + LANG=en_NZ.UTF-8 + SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=36d43481-0720-4808-a234-82941b71f750 ro quiet splash RelatedPackageVersions: - linux-restricted-modules-4.15.0-22-generic N/A - linux-backports-modules-4.15.0-22-generic N/A - linux-firmware 1.173.1 + linux-restricted-modules-4.15.0-22-generic N/A + linux-backports-modules-4.15.0-22-generic N/A + linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776325 Title: Error messages during boot - Ubuntu 18.04 & Mint19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
