Help with Ubuntu after editing fstab

jrwagh333 · October 17, 2018, 9:29pm

OS: Ubuntu 18.04.1
GPU: AMD R9 290
Boot drive: Samsung 960 Evo NVME - Using Cryptsetup
HDD for media storage

I followed a guide on Ubuntu forum that said to edit the fstab to mount the HDD (ntfs partition) at boot to enable Plex to discover it - That worked and solved my Plex issue.

This has now caused my system to be incredibly sluggish during boot. I have Crytpsetup so need to enter a password before the NVME will un-encrypt. This now takes 3 times as long.

Game also no longer work. CSGO used to run at 300fps now it runs at 10fps

I have reverted back to old fstab - Removed Plex - And I believe I have removed the user Plex. - This has not solved any issues.

I have tried an updated Kernel. I have also tried going back to the stock kernel.

Same problems.

reikoshea · October 17, 2018, 10:34pm

Could be unrelated. Did you check top to see what’s monopolizing system resources?

jrwagh333 · October 17, 2018, 10:38pm

Nothing using CPU really apart from GNOME-Shell and Xorg

I tried unplugging the second HDD but that didn’t change anything

cburn11 · October 17, 2018, 10:46pm

Your startup log, whether you view it through dmesg or kern.log, has each line timestamped. Which is convenient for trying to figure out where your boot is hanging.

jrwagh333 · October 17, 2018, 11:07pm

So these seem to be the relative ones:

Oct 18 00:00:52 JamesLinux kernel: [ 28.599668] IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready

Oct 18 00:00:52 JamesLinux kernel: [ 28.626650] IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready

Oct 18 00:00:53 JamesLinux kernel: [ 29.648231] radeon_dp_aux_transfer_native: 116 callbacks suppressed

Oct 18 00:00:55 JamesLinux kernel: [ 31.428581] igb 0000:05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Oct 18 00:00:55 JamesLinux kernel: [ 31.428907] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready

Oct 18 00:01:04 JamesLinux kernel: [ 41.340030] radeon 0000:0b:00.0: ring 0 stalled for more than 10256msec

Oct 18 00:01:04 JamesLinux kernel: [ 41.340039] radeon 0000:0b:00.0: GPU lockup (current fence id 0x0000000000000001 last fence id 0x0000000000000003 on ring 0)

Oct 18 00:01:05 JamesLinux kernel: [ 41.852035] radeon 0000:0b:00.0: ring 0 stalled for more than 10768msec

Oct 18 00:01:05 JamesLinux kernel: [ 41.852042] radeon 0000:0b:00.0: GPU lockup (current fence id 0x0000000000000001 last fence id 0x0000000000000003 on ring 0)

Oct 18 00:01:05 JamesLinux kernel: [ 42.364028] radeon 0000:0b:00.0: ring 0 stalled for more than 11280msec
…
Oct 18 00:01:25 JamesLinux kernel: [ 61.883397] radeon 0000:0b:00.0: GPU lockup (current fence id 0x0000000000000001 last fence id 0x0000000000000003 on ring 0)

Oct 18 00:01:25 JamesLinux kernel: [ 62.406745] radeon 0000:0b:00.0: ring 0 stalled for more than 31248msec

Oct 18 00:01:25 JamesLinux kernel: [ 62.406752] radeon 0000:0b:00.0: GPU lockup (current fence id 0x0000000000000001 last fence id 0x0000000000000003 on ring 0)

Oct 18 00:01:26 JamesLinux kernel: [ 62.548148] radeon 0000:0b:00.0: Saved 104 dwords of commands on ring 0.

Oct 18 00:01:26 JamesLinux kernel: [ 62.548167] radeon 0000:0b:00.0: GPU softreset: 0x00000009
Oct 18 00:01:26 JamesLinux kernel: [ 62.548170] radeon 0000:0b:00.0: GRBM_STATUS=0xB3503028

Oct 18 00:01:26 JamesLinux kernel: [ 62.548172] radeon 0000:0b:00.0: GRBM_STATUS2=0x50000008

Oct 18 00:01:26 JamesLinux kernel: [ 62.548175] radeon 0000:0b:00.0: GRBM_STATUS_SE0=0x2D000006

Oct 18 00:01:26 JamesLinux kernel: [ 62.548178] radeon 0000:0b:00.0: GRBM_STATUS_SE1=0x28000006

Oct 18 00:01:26 JamesLinux kernel: [ 62.548180] radeon 0000:0b:00.0: GRBM_STATUS_SE2=0x28000006

Oct 18 00:01:26 JamesLinux kernel: [ 62.548182] radeon 0000:0b:00.0: GRBM_STATUS_SE3=0x28000006

Oct 18 00:01:26 JamesLinux kernel: [ 62.548184] radeon 0000:0b:00.0: SRBM_STATUS=0x20000040

Oct 18 00:01:26 JamesLinux kernel: [ 62.548187] radeon 0000:0b:00.0: SRBM_STATUS2=0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.548189] radeon 0000:0b:00.0: SDMA0_STATUS_REG = 0x46CEE557

Oct 18 00:01:26 JamesLinux kernel: [ 62.548192] radeon 0000:0b:00.0: SDMA1_STATUS_REG = 0x46CEE557

Oct 18 00:01:26 JamesLinux kernel: [ 62.548194] radeon 0000:0b:00.0: CP_STAT = 0x84228600
Oct 18 00:01:26 JamesLinux kernel: [ 62.548197] radeon 0000:0b:00.0: CP_STALLED_STAT1 =
0x00000c00

Oct 18 00:01:26 JamesLinux kernel: [ 62.548199] radeon 0000:0b:00.0: CP_STALLED_STAT2 = 0x40000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.548201] radeon 0000:0b:00.0: CP_STALLED_STAT3 = 0x00000400

Oct 18 00:01:26 JamesLinux kernel: [ 62.548204] radeon 0000:0b:00.0: CP_CPF_BUSY_STAT = 0x00000006

Oct 18 00:01:26 JamesLinux kernel: [ 62.548206] radeon 0000:0b:00.0: CP_CPF_STALLED_STAT1 = 0x00000003

Oct 18 00:01:26 JamesLinux kernel: [ 62.548208] radeon 0000:0b:00.0: CP_CPF_STATUS = 0x80000063

Oct 18 00:01:26 JamesLinux kernel: [ 62.548211] radeon 0000:0b:00.0: CP_CPC_BUSY_STAT = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.548213] radeon 0000:0b:00.0: CP_CPC_STALLED_STAT1 = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.548215] radeon 0000:0b:00.0: CP_CPC_STATUS = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.548218] radeon 0000:0b:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.548220] radeon 0000:0b:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.557653] radeon 0000:0b:00.0: GRBM_SOFT_RESET=0x00010001

Oct 18 00:01:26 JamesLinux kernel: [ 62.557707] radeon 0000:0b:00.0: SRBM_SOFT_RESET=0x00000100

Oct 18 00:01:26 JamesLinux kernel: [ 62.558857] radeon 0000:0b:00.0: GRBM_STATUS=0x00003028

Oct 18 00:01:26 JamesLinux kernel: [ 62.558860] radeon 0000:0b:00.0:
GRBM_STATUS2=0x00000008

Oct 18 00:01:26 JamesLinux kernel: [ 62.558862] radeon 0000:0b:00.0: GRBM_STATUS_SE0=0x00000006

Oct 18 00:01:26 JamesLinux kernel: [ 62.558865] radeon 0000:0b:00.0: GRBM_STATUS_SE1=0x00000006

Oct 18 00:01:26 JamesLinux kernel: [ 62.558867] radeon 0000:0b:00.0: GRBM_STATUS_SE2=0x00000006

Oct 18 00:01:26 JamesLinux kernel: [ 62.558869] radeon 0000:0b:00.0: GRBM_STATUS_SE3=0x00000006

Oct 18 00:01:26 JamesLinux kernel: [ 62.558872] radeon 0000:0b:00.0: SRBM_STATUS=0x20000040
Oct 18 00:01:26 JamesLinux kernel: [ 62.558874] radeon 0000:0b:00.0: SRBM_STATUS2=0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558876] radeon 0000:0b:00.0: SDMA0_STATUS_REG = 0x46CEE557

Oct 18 00:01:26 JamesLinux kernel: [ 62.558879] radeon 0000:0b:00.0: SDMA1_STATUS_REG = 0x46CEE557

Oct 18 00:01:26 JamesLinux kernel: [ 62.558881] radeon 0000:0b:00.0: CP_STAT = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558883] radeon 0000:0b:00.0: CP_STALLED_STAT1 =
0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558886] radeon 0000:0b:00.0: CP_STALLED_STAT2 = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558888] radeon 0000:0b:00.0: CP_STALLED_STAT3 = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558890] radeon 0000:0b:00.0: CP_CPF_BUSY_STAT = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558892] radeon 0000:0b:00.0: CP_CPF_STALLED_STAT1 = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558895] radeon 0000:0b:00.0: CP_CPF_STATUS = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558897] radeon 0000:0b:00.0: CP_CPC_BUSY_STAT = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558899] radeon 0000:0b:00.0: CP_CPC_STALLED_STAT1 = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558901] radeon 0000:0b:00.0: CP_CPC_STATUS = 0x00000000

Oct 18 00:01:26 JamesLinux kernel: [ 62.558922] radeon 0000:0b:00.0: GPU reset succeeded, trying to resume

Oct 18 00:01:26 JamesLinux kernel: [ 62.846892] [drm:ci_dpm_enable [radeon]] ERROR ci_start_dpm failed

Oct 18 00:01:26 JamesLinux kernel: [ 62.846926] [drm:radeon_pm_resume [radeon]] ERROR radeon: dpm resume failed

Oct 18 00:01:26 JamesLinux kernel: [ 62.846934] [drm] probing gen 2 caps for device 1022:1453 = 737903/e

Oct 18 00:01:26 JamesLinux kernel: [ 62.846937] [drm] PCIE gen 3 link speeds already enabled

Oct 18 00:01:26 JamesLinux kernel: [ 62.852765] [drm] PCIE GART of 2048M enabled (table at 0x000000000030E000).

Oct 18 00:01:26 JamesLinux kernel: [ 62.852891] radeon 0000:0b:00.0: WB enabled

Oct 18 00:01:26 JamesLinux kernel: [ 62.852898] radeon 0000:0b:00.0: fence driver on ring 0 use
gpu addr 0x0000000100000c00 and cpu addr 0x0000000041bef8b8

Oct 18 00:01:26 JamesLinux kernel: [ 62.852899] radeon 0000:0b:00.0: fence driver on ring 1 use gpu addr 0x0000000100000c04 and cpu addr 0x0000000030d34cf5

Oct 18 00:01:26 JamesLinux kernel: [ 62.852900] radeon 0000:0b:00.0: fence driver on ring 2 use gpu addr 0x0000000100000c08 and cpu addr 0x00000000ef8bfd43

Oct 18 00:01:26 JamesLinux kernel: [ 62.852901] radeon 0000:0b:00.0: fence driver on ring 3 use gpu addr 0x0000000100000c0c and cpu addr 0x00000000930daf8d

Oct 18 00:01:26 JamesLinux kernel: [ 62.852902] radeon 0000:0b:00.0: fence driver on ring 4 use gpu addr 0x0000000100000c10 and cpu addr 0x00000000785c93fb

Oct 18 00:01:26 JamesLinux kernel: [ 62.853281] radeon 0000:0b:00.0: fence driver on ring 5 use gpu addr 0x0000000000078d30 and cpu addr 0x00000000d1e7ab76

Oct 18 00:01:26 JamesLinux kernel: [ 62.853433] radeon 0000:0b:00.0: fence driver on ring 6 use gpu addr 0x0000000100000c18 and cpu addr 0x000000007842fc2f

Oct 18 00:01:26 JamesLinux kernel: [ 62.853434] radeon 0000:0b:00.0: fence driver on ring 7 use gpu addr 0x0000000100000c1c and cpu addr 0x00000000969b26b7

Oct 18 00:01:26 JamesLinux kernel: [ 62.854985] [drm] ring test on 0 succeeded in 3 usecs

Oct 18 00:01:26 JamesLinux kernel: [ 62.855054] [drm] ring test on 1 succeeded in 2 usecs

Oct 18 00:01:26 JamesLinux kernel: [ 62.855067] [drm] ring test on 2 succeeded in 2 usecs

Oct 18 00:01:26 JamesLinux kernel: [ 62.855214] [drm] ring test on 3 succeeded in 3 usecs

Oct 18 00:01:26 JamesLinux kernel: [ 62.855221] [drm] ring test on 4 succeeded in 3 usecs

Oct 18 00:01:26 JamesLinux kernel: [ 62.900913] [drm] ring test on 5 succeeded in 1 usecs

Oct 18 00:01:26 JamesLinux kernel: [ 62.920786] [drm] UVD initialized successfully.

Oct 18 00:01:26 JamesLinux kernel: [ 63.022124] [drm] ring test on 6 succeeded in 894 usecs

Oct 18 00:01:26 JamesLinux kernel: [ 63.022134] [drm] ring test on 7 succeeded in 2 usecs

Oct 18 00:01:26 JamesLinux kernel: [ 63.022134] [drm] VCE initialized successfully.

Oct 18 00:01:26 JamesLinux kernel: [ 63.022175] [drm:radeon_pm_resume [radeon]] ERROR
radeon: dpm resume failed

Oct 18 00:01:27 JamesLinux kernel: [ 64.069246] [drm:cik_ib_test [radeon]] ERROR radeon: fence wait timed out.

Oct 18 00:01:27 JamesLinux kernel: [ 64.069259] [drm:radeon_ib_ring_tests [radeon]] ERROR radeon: failed testing IB on GFX ring (-110).

Oct 18 00:01:27 JamesLinux kernel: [ 64.069372] radeon 0000:0b:00.0: Syncing to a disabled ring!

Oct 18 00:01:27 JamesLinux kernel: [ 64.069373] radeon 0000:0b:00.0: failed to sync rings (-22)

Oct 18 00:01:27 JamesLinux kernel: [ 64.069384] [drm:radeon_gem_va_ioctl [radeon]] ERROR Couldn’t update BO_VA (-22)

Oct 18 00:01:27 JamesLinux kernel: [ 64.069420] WARNING: CPU: 11 PID: 1442 at /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_object.c:84 radeon_ttm_bo_destroy+0xfb/0x100 [radeon]

cburn11 · October 17, 2018, 11:11pm

If you look in /var/log, you will not just have kern.log, but also kern.log.1 kern.log.2.gz kern.log.3.gz … You can compare the startup log from a time prior to your boots becoming slow and see what is different.

cburn11 · October 17, 2018, 11:19pm

I don’t know anything about running an amd graphics card or radeon drivers on linux and tell you if those 20 seconds or messages are significant. But if they don’t appear in your prior bootup logs, your graphics drivers are probably your culprit.

jrwagh333 · October 17, 2018, 11:21pm

Previous log:

Oct 1 22:55:44 JamesLinux kernel: [ 15.587295] IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready
Oct 1 22:55:44 JamesLinux kernel: [ 15.615362] IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready
Oct 1 22:55:45 JamesLinux kernel: [ 16.648218] radeon_dp_aux_transfer_native: 116 callbacks suppressed
Oct 1 22:55:46 JamesLinux kernel: [ 18.364571] igb 0000:05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Oct 1 22:55:46 JamesLinux kernel: [ 18.364887] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready
Oct 1 22:55:51 JamesLinux kernel: [ 23.216246] radeon_dp_aux_transfer_native: 32 callbacks suppressed
Oct 1 22:55:54 JamesLinux kernel: [ 25.778561] rfkill: input handler disabled

cburn11 · October 17, 2018, 11:25pm

So have you recently changed/updated video drivers?

jrwagh333 · October 18, 2018, 7:06am

I have only run sudo apt-update
Sudo apt upgrade

I use the open source drivers bundled with the kernel

jrwagh333 · October 18, 2018, 12:55pm

Ok so I have now installed the AMD proprietary drivers and that has fixed everything.

I would still like to get to the root cause of this issue though if people wouldn’t mind lending a hand?

I’m guessing the apt update and apt upgrade updated the mesa drivers and caused the problem?

corpse_painted · October 18, 2018, 1:04pm

So your problem started when you made an entry into the filesystem table. But the graphics drivers were working and the exact same prior to you appending that change to fstab? Where is this ubuntu forum post that you used to insert the entry into fstab? Sometimes people upvote fixes on stack exchange that don’t work. I’m curious to know if anything else changed because that shouldn’t cause the drivers to go haywire.

corpse_painted · October 18, 2018, 1:25pm

Not trying to be pedantic here but issues like this could go into this thread dedicated for these types of issues if you have them in the future

Thanks for your post.

jrwagh333 · October 18, 2018, 3:38pm

Yes.

But also doing a apt update, apt upgrade might have caused the issue.

I only think this because the log file shows it was a radeon issue during decryption of the boot drive

Dynamic_Gravity · October 18, 2018, 4:55pm

With a 290 you should be using amdgpu not Radeon. If it defaulted to Radeon that could be your issue.

cburn11 · October 19, 2018, 3:55am

You don’t have to wonder if apt altered your graphics drivers. apt keeps its logs in /var/log/apt and it has a history.log which will show you what command you ran and when you ran it, along with the packages that were updated. I think term.log chronicles each commands standard output.

jrwagh333 · October 19, 2018, 5:44pm

Why is that? Just curious as I was using amdgpu and all was well until I did the latest apt upgrade.

Which is a shame because now, although my system is stable and working again, I get MUCH lower FPS in gmes using the proprietary AMD drivers

Dynamic_Gravity · October 19, 2018, 6:13pm

That is because the Hawaii architecture is supposed by amdgpu, the most recent open source driver stack.

Hawaii is old enough to be somewhat supported by Radeon, but amdgpu is really what it should be using.

The arch wiki on amdgpu contains a wealth of information that I suggest you to read.

Radeon isn’t getting any updates, so if you have any problems they will not get fixed.

jrwagh333 · October 19, 2018, 8:03pm

Thank you. I will check out the Arch Wiki.

Do you know if I can find out what version of amdgpu I am on now, what I was on last week (before I updated) and then roll back to that?