Kernel page fault errors [Solved]

[arcenciel]

Hi,
I have a new install on a Ryzen system, fully updated, with following configuration:

Code: Select all

System:    Host: dave-MS-7A34 Kernel: 4.10.0-38-generic x86_64 (64 bit)
           Console: tty 0 Distro: Linux Mint 18.2 Sonya
Machine:   Mobo: Micro-Star model: B350 TOMAHAWK (MS-7A34) v: 1.0
           Bios: American Megatrends v: 1.90 date: 09/19/2017
CPU:       Quad core AMD Ryzen 3 1300X (-MCP-) cache: 2048 KB
           clock speeds: max: 3500 MHz 1: 1550 MHz 2: 1550 MHz 3: 3000 MHz
           4: 1550 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210]
           Display Server: X.org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa)
           tty size: 80x24 Advanced Data: N/A out of X
Audio:     Card-1 Advanced Micro Devices [AMD] Device 1457
           driver: snd_hda_intel
           Card-2 NVIDIA High Definition Audio Controller
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
Network:   Card-1: Qualcomm Atheros AR9227 Wireless Network Adapter
           driver: ath9k
           IF: wlp32s0 state: up mac: 18:d6:c7:46:14:1b
           Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169
           IF: enp33s0 state: up speed: 1000 Mbps duplex: full
           mac: 30:9c:23:0e:0c:fe
Drives:    HDD Total Size: 460.1GB (3.2% used)
           ID-1: /dev/sda model: ST3300831AS size: 300.1GB
           ID-2: /dev/sdb model: ST3160827AS size: 160.0GB
Partition: ID-1: / size: 139G used: 6.3G (5%) fs: ext4 dev: /dev/sdb2
           ID-2: swap-1 size: 8.54GB used: 0.00GB (0%) fs: swap dev: /dev/sdb3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 32.0C mobo: 40.0C gpu: 56.0
           Fan Speeds (in rpm): cpu: N/A fan-1: 0 fan-2: 819 fan-3: 0 fan-4: 0 fan-5: 0
Info:      Processes: 203 Uptime: 1:24 Memory: 566.7/7995.3MB
           Init: systemd runlevel: 5 Client: Shell (bash) inxi: 2.2.35

It seems to work well, no crashes but I'm getting the following errors in syslog:
Nov 17 11:43:49 dave-MS-7A34 kernel: [ 5075.103597] AMD-Vi: Event logged [
Nov 17 11:43:49 dave-MS-7A34 kernel: [ 5075.103602] IO_PAGE_FAULT device=20:00.0 domain=0x000b address=0x00000000fbe5d000 flags=0x0000]

The memory passes bios checks. Memory speed is 2666mhz but running slightly slower. 2133mhz

Any help would be appreciated...
Dave

[ClixTrix]

There is a problem using the default nouveau (from your inxi) video driver with ryzen. Upgrade to the proprietary nVidia driver using Menu - Administration - Driver Manager.

[arcenciel]

Thanks, You were right. The system was not using the recommended video driver. I changed to the Radeon one and rebooted. Sadly the AMD-Vi errors are still there. All I can find is that AMD-Vi is an implementation of virtualization IOMMU. I suspect it may involve the onboard video which doesn't work with the Rizen CPU, only the gen 7 Athlon, which is not out yet. In my current bios. The onboard graphics configuration os greyed out as I am using a PCI-e card Asus 210.
Still stuck. It is just cluttering up the log and I have no failures other than the syslog error...

[catweazel]

There is a problem using the default nouveau (from your inxi) video driver with ryzen.

Really? Do you have a reputable cite for that?

[arcenciel]

This is a snip of inxi after replacing the nouveau driver. I still have the AMD-Vi errors...
Graphics: Card: NVIDIA GT218 [GeForce 210]
Display Server: N/A drivers: nvidia (unloaded: fbdev,vesa,nouveau)
tty size: 80x24 Advanced Data: N/A out of X

[catweazel]

As a first step, in the update manager, select View then Kernels, and install at least 4.11. You'll need to reboot.

[ClixTrix]

I was/am reasonably certain it is video involved, and that prompted by suggestion to move to what most would consider a better driver solution for nVidia.

https://www.reddit.com/r/Amd/comments/6 ... m-comments

However, let's check to make sure.

Please run the following command from Terminal and post back the result:

Code: Select all

lspci | grep 20:00.0

That should confirm which device.

I'm also curious about a full dump of lspic for cross-checks. Run the following and post back:

Code: Select all

lspci -v

I looked at your BIOS date, and it's the most current.

Any specific activity you're doing that's generating the error?

Which desktop are you running?

Since this is a new build, you might try running MEMTEST86 to make sure memory is good.

[arcenciel]

Thanks for the help.
here's the result of lspci
dave@dave-MS-7A34 ~ $ lspci | grep 20:00.0
20:00.0 Network controller: Qualcomm Atheros AR9227 Wireless Network Adapter (rev 01)

lspci -v

20:00.0 Network controller: Qualcomm Atheros AR9227 Wireless Network Adapter (rev 01)
Subsystem: Qualcomm Atheros AR9227 Wireless Network Adapter
Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 225
Memory at fd600000 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: ath9k
Kernel modules: ath9k
And yes, I'm on 4.10.0-38-generic x86_64 (64 bit)
And yes, The wireless adapter is having issues...
I removed the wireless card and so far, the errors have stopped.
Once again Thanks

[markedward88]

according to other websites i believe that installing linux kernel 4.13 might be a solution because the more current the linux kernel is the more support there is
if this doesn't help then lts 4.14 might help
the steps to follow are to:
install the nouveau driver not the nvidia this is because the nvidia driver compiles with linux kernel installed
after install linux kernel 4.13.
update grub via sudo update-grub
reboot
install the latest nvidia driver that that shows up in driver manager
reboot
see if this helps
easy linux tips project might offer some tips to help you

[ClixTrix]

I removed the wireless card and so far, the errors have stopped.

I would carefully inspect and lightly clean the contacts on that card and try again. I usually use 99% Isopropyl Alcohol and qtips for that task. I'd also check to make sure the card is fully seated in the PCI slot. I think I recall that board has more than one PCI slot. If so, you could also try another slot.

[arcenciel]

Sadly, Neither 4.11 nor 4.13 generic seem to work with this motherboard. They don't probe devices and I end up with no video driver and no network driver, so I rolled back to 4.08 and it works fine. Had a problem with 4.10 afterwards.
Question:
is there a step I missed? I did sudo grub-update. And there were no errors.
What are the upstart versions of the kernel? A boot using one hangs at 5 dots...

[ClixTrix]

When it hangs at the traveling 5 Dots, hit the [ESC] key and see if there are messages indicating cause.

My Ryzen-Gigabyte system did that due to the Vector 07 bug in Kernel 4.08 for my board.

Kernel 4.10 was the first Kernel to provide full Ryzen support. Although, there is a patch that has been added to just released Kernel 4.14 for Turbo support.

Did you install 4.11 and 4.13 from Update Manager and did you use the latest listed?

[arcenciel]

Success...
Using UKUU i was able to upgrade to 4.14.0-041400-generic x86_64. I then restored the Nvidia driver and all is good...
Thanks for your help