Public bug reported:

Kind of a follow up/extension to
https://bugs.launchpad.net/ubuntu/disco/+source/linux/+bug/1858832

== Original Bug Report (for the most part, still holds true) ==

RELEASE=19.3
CODENAME=tricia
EDITION="Cinnamon"
DESCRIPTION="Linux Mint 19.3 Tricia"
DESKTOP=Gnome
TOOLKIT=GTK
NEW_FEATURES_URL=https://www.linuxmint.com/rel_tricia_cinnamon_whatsnew.php
RELEASE_NOTES_URL=https://www.linuxmint.com/rel_tricia_cinnamon.php
USER_GUIDE_URL=https://www.linuxmint.com/documentation.php
GRUB_TITLE=Linux Mint 19.3 Cinnamon

My home dir is mounted through nfs on a local server via nfs4 and krb5i.
When stressing the mounted directory or its sub-directories (sometimes starting 
firefox, sometimes starting thunderbird, nearly guaranteed when compiling, 
sometimes the login itself), it will eventually lead to the following 
stack-trace. The corresponding process is then stuck and
accessing the mounted directory (like calling ls) easily yields further and 
similar stack trace and causing the process to also stuck.

Currently I am running an AMD 3950x on a ASUS Crosshair VII Hero Wifi
(chipset x470).

I installed Ubuntu 20.04 LTS Desktop to check if the newer kernels (5.4)
work without issues, but sadly, they **do not**.

With a little compile-stress-test, I have tested the following kernels which 
seem to run fine:
 * 4.15.0-69
 * 4.15.0-70
 * 4.15.0-72
 * 5.0.0-32
 * 5.0.0-47 (current daily driver, runs without a hassle, max test length >7d - 
I am writing this bug report on it)

But the following kernels do not run stable:
 * 5.3.0-51 (Linux Mint 19.3 HWE)
 * 5.4.0-28 (Ubuntu 20.04)

$ lspci | grep -i ether
06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection 
(rev 03

$ mount | grep filer
filer:/ on /share type nfs4 
(rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.3.55,local_lock=none,addr=192.168.2.33)
filer:/home/michael on /share/home/michael type nfs4 
(rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.3.55,local_lock=none,addr=192.168.2.33)

$ cat /etc/fstab | grep -i filer
filer:/ /share/ nfs4 
nfsvers=4,sec=krb5i,rw,x-systemd.automount,soft,intr,tcp,noatime 0 0

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete


** Tags: focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1876567

Title:
  ubuntu 20.04 nfs page fault since Kernel 5.3 (?)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kind of a follow up/extension to
  https://bugs.launchpad.net/ubuntu/disco/+source/linux/+bug/1858832

  == Original Bug Report (for the most part, still holds true) ==

  RELEASE=19.3
  CODENAME=tricia
  EDITION="Cinnamon"
  DESCRIPTION="Linux Mint 19.3 Tricia"
  DESKTOP=Gnome
  TOOLKIT=GTK
  NEW_FEATURES_URL=https://www.linuxmint.com/rel_tricia_cinnamon_whatsnew.php
  RELEASE_NOTES_URL=https://www.linuxmint.com/rel_tricia_cinnamon.php
  USER_GUIDE_URL=https://www.linuxmint.com/documentation.php
  GRUB_TITLE=Linux Mint 19.3 Cinnamon

  My home dir is mounted through nfs on a local server via nfs4 and krb5i.
  When stressing the mounted directory or its sub-directories (sometimes 
starting firefox, sometimes starting thunderbird, nearly guaranteed when 
compiling, sometimes the login itself), it will eventually lead to the 
following stack-trace. The corresponding process is then stuck and
  accessing the mounted directory (like calling ls) easily yields further and 
similar stack trace and causing the process to also stuck.

  Currently I am running an AMD 3950x on a ASUS Crosshair VII Hero Wifi
  (chipset x470).

  I installed Ubuntu 20.04 LTS Desktop to check if the newer kernels
  (5.4) work without issues, but sadly, they **do not**.

  With a little compile-stress-test, I have tested the following kernels which 
seem to run fine:
   * 4.15.0-69
   * 4.15.0-70
   * 4.15.0-72
   * 5.0.0-32
   * 5.0.0-47 (current daily driver, runs without a hassle, max test length >7d 
- I am writing this bug report on it)

  But the following kernels do not run stable:
   * 5.3.0-51 (Linux Mint 19.3 HWE)
   * 5.4.0-28 (Ubuntu 20.04)

  $ lspci | grep -i ether
  06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network 
Connection (rev 03

  $ mount | grep filer
  filer:/ on /share type nfs4 
(rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.3.55,local_lock=none,addr=192.168.2.33)
  filer:/home/michael on /share/home/michael type nfs4 
(rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.3.55,local_lock=none,addr=192.168.2.33)

  $ cat /etc/fstab | grep -i filer
  filer:/ /share/ nfs4 
nfsvers=4,sec=krb5i,rw,x-systemd.automount,soft,intr,tcp,noatime 0 0

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to