** Branch linked: lp:ubuntu/precise-proposed/linux-lowlatency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
Title:
Kernel Oops - BUG: unable to handle kernel paging request at
** Branch linked: lp:ubuntu/precise-proposed/linux-armadaxp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
Title:
Kernel Oops - BUG: unable to handle kernel paging request at
Tagging this bug as verified for Precise. Patch is already released with
Precise, but showing up on ti-omap4 SRU report where it isn't a specific
ti-omap4 change.
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I observe the same kernel bug on Ubuntu 11.10 (oneiric) with kernel
3.0.0-19-generic, see the attached syslog. Interestingly, it's not there
in the vanilla install of Ubuntu 11.10 with kernel 3.0.0-12-generic
(tested by booting an older kernel from grub). This issue manifests
itself when I log in
** Branch linked: lp:ubuntu/precise-proposed/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
Title:
Kernel Oops - BUG: unable to handle kernel paging request at
This bug was fixed in the package linux - 3.2.0-24.37
---
linux (3.2.0-24.37) precise-proposed; urgency=low
[ Herton Ronaldo Krzesinski ]
* d-i: Add hid-logitech-dj to input-modules
- LP: #975198
* d-i: Add rtl8187 driver to nic-usb-modules
- LP: #971719
[ Ian
This bug was fixed in the package linux - 3.2.0-24.37
---
linux (3.2.0-24.37) precise-proposed; urgency=low
[ Herton Ronaldo Krzesinski ]
* d-i: Add hid-logitech-dj to input-modules
- LP: #975198
* d-i: Add rtl8187 driver to nic-usb-modules
- LP: #971719
[ Ian
Hello rvaliant, or anyone else affected,
Accepted linux into precise-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
Title:
Kernel Oops - BUG: unable to handle kernel paging request at
ffb8; RIP: 0010:[a05a5839]
That's great, thank you for testing. So, to summarise, here's the list
of commits that were present in this last kernel you have tested:
- From Linux mainline:
- 14977489ffdb80d4caf5a184ba41b23b02fbacd9
- 96dcadc2fdd111dca90d559f189a30c65394451a
- From linux-nfs, branch bugfixes:
-
I can confirm as well that using the kernel from #18 and performing the
same steps as before fails to generate the bug and everything seems to
work correctly.
Thanks as well!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same here, thank you so much Luis!
Is there any way this will make it into precise before launch now? It
seems almost unthinkable that an LTS could be released without the
ability to mount NFS home directories :s
Is there anything we can do to help this process?
--
You received this bug
** Also affects: linux (Ubuntu Precise)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
Title:
Kernel Oops - BUG: unable to handle kernel paging
** Description changed:
+ == Precise SRU Justification ==
+
+ This bug is preventing users from using NFS clients on Precise.
+ Several users have reported the issue, which has been already fixed
+ upstreams but did not made it into stable yet.
+
+ == Fix ==
+
+ There are four commits that are
Re: #10, Luis, thanks for your efforts on this. By running
http://people.canonical.com/~henrix/lp974664v2, the Oops is indeed
resolved and the rate limiting is definitely reducing the numbers of
messages produced but none the less there are many many dozens of
messages produced still -- just like
Can this not be marked as confirmed now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
Title:
Kernel Oops - BUG: unable to handle kernel paging request at
ffb8; RIP:
Ian, there's something I forgot to ask: could you take a look at the
server logs (running Lucid, I believe) and check whether there's some
extra information there? Please attach any relevant information (in
particular the kernel logs).
** Changed in: linux (Ubuntu)
Status: Incomplete =
Same Problem here:
Server 10.04 LTS Stock-Kernel
Clients: 11.04 - Custom Kernel, nfs-home
Kernel 3.1, 3.2 from kernel.org:
BUG: unable to handle kernel paging request at ffb8
IP: [a0e83bfb] nfs_have_delegation+0xb/0x40 [nfs]
Kernel 3.4 from kernel.org:
NFS:
Re: #15, Correct -- server running lucid with stock kernel (from
updates). There's no messages in the server logs that I can see (same as
#16)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
I have ping'ed upstreams about the issue and two new patches (not yet
upstream) have been provided. I have uploaded a new test kernel here:
http://people.canonical.com/~henrix/lp974664v3/
It contains the two mentioned patches and the other two you have already
tested.
Please let me know if
Re: #18, Luis, I think you've cracked it! I have just installed that
kernel and I am happy to report that I'm not getting an oops, Nor am I
getting any messages on the client, the network traffic is back down to
normal levels, I'm not getting any messages on the server side and last
but not
Thats it, Luis! Bug is gone with your kernel.
Where can i get the patches to compile my own? When are the fixes
@kernel.org?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
Title:
It looks like commit 14977489ffdb80d4caf5a184ba41b23b02fbacd9 should fix
this issue. I have built a test kernel that includes this commit.
Could someone check if it solves the problem? The test kernel can be
obtained here:
http://people.canonical.com/~henrix/lp974664/
--
You received this bug
Re: #8, tried this kernel with the same effect as running the mainline
kernel in #7 specifically many many messages of the type:
NFS: nfs4_reclaim_open_state: Lock reclaim failed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ian: Thanks for testing the kernel. Apparently, these messages are
harmless and the mainline kernel has already a ratelimiting patch for
this. I have backported the ratelimiting commit
(96dcadc2fdd111dca90d559f189a30c65394451a) on top of the kernel you
tested and uploaded it here:
Re: #10, Luis, thanks for your efforts on this. By running
http://people.canonical.com/~henrix/lp974664v2, the Oops is indeed
resolved and the rate limiting is definitely reducing the numbers of
messages produced but none the less there are many many dozens of
messages produced still -- just like
Ian, thanks again for testing and helping triagging this bug.
When I said harmless (and I'm far from being an expert on NFS as
well!) I was not aware that the flood of messages being logged would be
kept that high. Obviously, logging such a huge amount of messages will
at least impact the
This problem is reproduced by logging into Ubuntu with a user's home
directory mounted over NFS... though only if the server is also running
12.04.
I have a stable server running 10.04 and 12.04 clients can still mount
NFS home directories from there, moving to the test server, configured
in the
Has anyone affected by this bug had a chance to test the latest mainline
kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/
** Tags added: kernel-da-key kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Actually, my server is Ubuntu 11.10, so if this is an NFS related issue,
it's not confined to 12.04. I have some time today and will try the
latest mainline kernel on my client as suggested by jsalisbury and
report back - if someone doesn't beat me to it.
--
You received this bug notification
I'm seeing the same OOps -- again Logging into a 12.04 client system
with autofs5, LDAP, kerberos authenticated nfs4 mounts. However this is
to a server which is running 10.04 (contrary to #4 it seems) In my case
the triggering process is gnome-keyring-d.
Running the mainline kernel (linux-
This bug has also been reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=811138
** Bug watch added: Red Hat Bugzilla #811138
https://bugzilla.redhat.com/show_bug.cgi?id=811138
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: linux via
https://bugzilla.redhat.com/show_bug.cgi?id=811138
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
Title:
Kernel
rvaliant, thank you for reporting this bug and helping make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Could you also please test the latest upstream kernel available? It will
allow additional upstream
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: nfs-have-delegation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974664
Title:
Kernel Oops - BUG: unable to handle
35 matches
Mail list logo
