![](https://seccdn.libravatar.org/avatar/dcb1cafc096989977947ac1b483706a4.jpg?s=120&d=mm&r=g)
All,
I have a couple machines running AMD FX CPUs. Both are running Gigabyte motherboards. One is a GA-990FXA-UD5 with 32G of RAM and an FX(tm)-8350 (8 core). The second is a 970A-UD3P with 32G of RAM and an FX(tm)-6300 (6 core). The 990FXA uses the 990FX northbridge, the 970A uses the 970 northbridge. Both use the SB950 southbridge.
I upgraded the 970A machine from Leap 42.1 to 42.2 several weeks ago, and immediately started having problems with Google Chrome / chromium crashes, as well as a lot of "bash: fork: retry: No child processes" from shells. I tried upgrading to several different kernels (all from OBS), with similar results. I also tried playing with the IOMMU settings, both in BIOS and in the kernel parameters. The problems persisted (and still do).
Last night, I upgraded the 990FX box, and am now having the same problems. I was hoping the the 990FX chipset would be different enough, but apparently it's not.
At work, I'm running Leap 42.2 on several Intel boxes, and I've not seen this problem, so I'm guessing that it's linked to either the CPU or, I think more likely, the chipset. I don't think that it's relevant, but both boxes are running ATI / AMD video cards: Radeon R7 370 and 360, respectively.
Various searches of the mailing list archives Somebody else must have run into this, I can't believe that I'm the first.
dmesg (and /var/log/messages (I use syslog-ng)) are surprisingly quiet about it all. The most common things I see are messages like:
trap invalid opcode ip:5608d1232a92 sp:7ffe373a73d0 error:0 in chrome[5608cd3fb000+67d5000]traps:
If anybody has any suggestions, requires more information, etc., please don't hesitate.
Thanks!
-Nick I am running 42.2 with 970A-UD3P at my parents (so I do not have the machine under hand. It is a known issue that Iommu has to be set to on, otherwise you do not have usb3 support. But there is also a kernelparameter that has to be set. At boot time do you get a long list of error warnings that suddenly stops? This is an issu related to the chipset that you have to start with a specific
In data martedì 14 febbraio 2017 13:12:36, Nick LeRoy ha scritto: parameter (iommu=soft) to get the USB 3.0 ports running. You may wish to try. As for the 990 I do not know. I am running the board with amd graphics and opensource amd driver. When updating from 42.1 I needed to uninstall the outdated flglrx driver, unblacklist the radeon driver and then do a mkinitrd. After this the system started normally. Hope that helps in any way. P.S. as GUI is heavily graphics dependent these days, you should tell what card and driver you use. You may also wish to controll what OpenGL version you did set to use (provided you are running KDE). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org