Trond, Arthur seems to be hitting a similar bug to <https://bugzilla.redhat.com/show_bug.cgi?id=1050206>, and it's still occurring in 3.13.4 even though that has the two fixes you posted there. The full bug report, with screenshots of the oopses, is at <https://bugs.debian.org/734268>. On Tue, 2014-02-25 at 21:45 +0100, Arthur de Jong wrote: > Control: severity -1 critical > Control: found -1 linux/3.12.6-2 > Control: found -1 linux/3.13.4-1 > Control: fixed -1 linux/3.11.10-1 > > Raising severity to critical because it kills the whole system quite > predictably. > > I can still reliably reproduce this with linux-image-3.13-1-amd64 > 3.13.4-1 (see photo) so I'm currently still stuck with a 3.11 kernel. > > If there is any information I can provide to help identify this bug, > please let me know. > > The only thing that could be relevant is that I have NFS mounts from > different NFS servers: > > /etc/fstab: > > server1:/home /home nfs rw,hard,intr,bg,rsize=4096,wsize=1024,acregmin=60,acregmax=600,acdirmin=60,acdirmax=600,noatime,sec=sys,_netdev 0 0 > server2:/share /share nfs ro,soft,intr,bg,rsize=8192,nosuid,nodev,noexec,acregmin=60,acregmax=600,acdirmin=60,acdirmax=600,sec=sys,_netdev 0 0 > > > server1 is Debian wheezy (kernel linux-image-3.2.0-4-amd64 > 3.2.51-1) /etc/exports: > > /home -rw,root_squash,nohide,async,no_subtree_check client1 client2(no_root_squash) client3 > > I'm mostly seeing crashes on client2, my main workstation, but also > other machines. /home is an ext3 file system. > > > server2 runs testing (kernel linux-image-3.12-1-686-pae > 3.12.9-1) /etc/exports: > > /share *.local.domain(ro,all_squash,crossmnt,sync,no_subtree_check) > > Under /share are /share/disk1 and /share/disk2 ext3 file systems. > > > On the client again, from /proc/mounts (running a 3.11 kernel again): > > server1:/home /home nfs4 rw,noatime,vers=4.0,rsize=4096,wsize=1024,namlen=255,acregmin=60,acregmax=600,acdirmin=60,acdirmax=600,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.12.4,local_lock=none,addr=192.168.12.1 0 0 > server2:/share /share nfs4 ro,nosuid,nodev,noexec,relatime,vers=4.0,rsize=8192,wsize=131072,namlen=255,acregmin=60,acregmax=600,acdirmin=60,acdirmax=600,soft,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.12.4,local_lock=none,addr=192.168.12.9 0 0 > server2:/share/disk2 /share/disk2 nfs4 ro,nosuid,nodev,noexec,relatime,vers=4.0,rsize=8192,wsize=131072,namlen=255,acregmin=60,acregmax=600,acdirmin=60,acdirmax=600,soft,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.12.4,local_lock=none,addr=192.168.12.9 0 0 > server2:/share/disk1 /share/disk1 nfs4 ro,nosuid,nodev,noexec,relatime,vers=4.0,rsize=8192,wsize=131072,namlen=255,acregmin=60,acregmax=600,acdirmin=60,acdirmax=600,soft,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.12.4,local_lock=none,addr=192.168.12.9 0 0 > > I have some freedom to change things around to test in this network so > let me know which things to try. > > Thanks, > -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way.
Attachment:
signature.asc
Description: This is a digitally signed message part