I am running fully up to date 13.10 on 64 bit and get the following
under heavy NFS load when using cachefilesd and the 'fsc' flag on the
nfs mount line. My PC hangs on this.
54.035972] Call Trace:
Jan 19 10:44:46 hyperion kernel: [ 54.035977] [816e7335]
dump_stack+0x45/0x56
Jan 19
Ken Pratt, thank you for your comment. So your hardware and problem may be
tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into a Ubuntu repository kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please read the
** Also affects: linux (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Saucy)
Importance: Medium
Status: Fix Released
** Changed in: linux (Ubuntu Raring)
Status: New = Confirmed
** Changed in: linux (Ubuntu Raring)
Importance:
Jason Gunthorpe, would you need a backport to a release prior to Saucy,
or may we close this as Status Invalid?
--
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/1212818
Title:
Using
I'm not familiar with Ubuntu's process. This is clearly a bug in Raring,
fixed in upstream and I would certainly like a backport to the Raring
kernel package as we have no plans here to use Saucy, which isn't even
in beta yet :)
--
You received this bug notification because you are a member of
Jason Gunthorpe, thank you for taking the time to report this bug and
helping to make Ubuntu better. However, I am closing it because the bug
has been fixed in the latest development version of Ubuntu - Saucy
Salamander.
This is a significant bug in Ubuntu. If you need a fix for the bug in
Well, if I understand https://wiki.ubuntu.com/KernelTeam/KernelUpdates
properly, oops fixes for raring will not be accepted since it is not a
LTS and it is past 4 months after release.
So I guess that is the end of it.
--
You received this bug notification because you are a member of Kernel
Jason Gunthorpe, testing the live environment would be just fine.
--
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/1212818
Title:
Using fscache with NFS causes random kernel oops
Status
I don't have a recipe to quickly reproduce the oops, so a live environment
doesn't help. I actually have to setup and use the install which takes a
long time to do.
Besides, this is a kernel oops, not a user space problem, changing out the
user space isn't going to provide any more information
So, it has been 11 days and 3.11.0-031100rc5-generic hasn't crashed, I
think that is enough to confirm it is fixed in this version.
Per Joseph's instructions I've added the 'kernel-fixed-upstream' and
marked the bug complete.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
Jason Gunthorpe, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal
No, installing a whole new release from ISO is simply way too much work.
I can test another kernel .deb if you send me a link, but if it is newer
than 3.11 that seems wasteful.
It would probably be more productive to test a build that includes the
patches I linked to in my original report, since
Pending update.
** Tags added: latest-bios-l01-v02.05 needs-upstream-testing regression-
release
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
apport information
** Tags added: apport-collected
** Description changed:
It is hard to get an oops because the entire FS system seems to hang and
/var/log/kern.log won't capture it. I have managed to get a kdump
capture. I think I told apport to submit the crash dump, but I'm not
Joseph:
I have successfully booted:
Linux jggl 3.11.0-031100rc5-generic #201308112135 SMP Mon Aug 12
01:35:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Since I don't know how to reproduce the crash, I will update this bug
either when 3.11 crashes or in about a weeks time.
** Changed in: linux
16 matches
Mail list logo
