*** This bug is a duplicate of bug 974664 ***
https://bugs.launchpad.net/bugs/974664
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: nfs-have-delegation
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** This bug has been marked a
Shawn Haggett, thank you for reporting this bug and helping make Ubuntu
better. If you could also please test the latest upstream kernel
available that would be great. It will allow additional upstream
developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Once
To add more information to this. If I start Lyx on its own (i.e. just
'lyx' at the command line, no file selected), then it starts fine.
However if I then try to open a file I get the same behaviour as above.
The above was triggered when doing 'lyx somefile.lyx' at the command
line. This is
Shawn Haggett, could you please try http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.4-rc2-precise/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981278
Title:
Kernel Oops - BUG: unable to
That kernel has given some different behaviour. Now when open the file
in lyx I get the following messages repeating over and over in the
syslog:
Apr 15 10:19:10 desktop kernel: [ 82.651314] NFS: nfs4_reclaim_open_state:
Lock reclaim failed!
Apr 15 10:19:10 desktop kernel: [ 82.652566] NFS:
After a little bit of googling, it's possible this could be related to
this thread: http://www.spinics.net/lists/linux-nfs/msg24949.html
As soon as the process hangs and the log messages start I'm seeing a
constant 5-9 mbit of network traffic in both directions between the
client and server.
