kernel panic while using nfs4/kerberos/autofs5

[Fede]

Fresh install of 12.04 desktop. Updated 22 May with latest updates. The system mounts kerberized NFS4 shares with autofs5 from an ubuntu 10.04 server. After a variable amount of time (minutes to a few hours) the system crashes with no shutdown possibility (neither local nor remote). Only option is a hard power-off.

The system crashed 4 times in a single afternoon. Before configuring the NFS4 shares I did use the system for 2 days with no single crash. At the moment I disabled the mounts and for the moment the system is running OK.

WORKAROUND: Use Samba.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.38
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices: aplay: device_list:252: no soundcards found...
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:252: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Tue May 22 21:36:32 2012
HibernationDevice: RESUME=UUID=731d6ae7-2f24-45b4-a874-cdda7c83aaed
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Dell Inc. Precision WorkStation T5500
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=a575b9e5-0f12-432e-9e78-cef745e15837 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic N/A
 linux-backports-modules-3.2.0-24-generic N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0D883F
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/30/2010:svnDellInc.:pnPrecisionWorkStationT5500:pvr:rvnDellInc.:rn0D883F:rvrA04:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T5500
dmi.sys.vendor: Dell Inc.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/

[Fede (beffa)]

I've tested with the upsteam kerned as indicated and have the same problem.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Joseph Salisbury (jsalisbury)]

Also, Was there a kernel version or Ubuntu release where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced.

[Fede (beffa)]

Dear Joseph, I would greatly appreciate if the bug could be reported upsteam by the ubuntu developers. Temporarity (hopefully) we switched to using samba. I will be away from our IT systems for the next couple of weeks and will therefore not be able to do any further debugging.

Before upgrading to ubuntu 12.04 we did use 10.04. I did use NFS4/kerberos/autofs with it, but not as intensively as we are doing now. In any case with that wersion we never had kernel panic problems.

[Fede (beffa)]

I reported the bug upsteam:

https://bugzilla.kernel.org/show_bug.cgi?id=45191

[Niklas Hagman (blinkiz)]

I may be having the same bug.
Installed 12.10 kubuntu today. After installing autofs and mounting my nfs4 share, I get a kernel panic.
Interesting is that if I mount this nfs4 share manually, I do not get a kernel panic.
I do not know if this is related to this bug, just thought I give me two cents..

[Niklas Hagman (blinkiz)]

Hmm, interesting again :)
I installed kernel 3.6.2 and now I do not get kernel panics anymore. Also, autofs works great.

[penalvch (penalvch)]

Fede, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue with nsf4? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc6

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Fede (beffa)]

Dear Christopher,

unfortunately the answer is yes. The problem still exists. However, since
we were not able to fix it we moved from nfs4 to samba. Now that machine is
used productively. At the moment we do not have a suitable machine
available to perform the tests you ask for. Maybe in the future things will
change.

Thanks for looking into this bug.
Best Regards,
Fede

On Mon, Dec 30, 2013 at 3:55 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> Fede, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue
> with nsf4? If so, could you please test for this with the latest
> development release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> If reproducible, could you also please test the latest upstream kernel
> available (not the daily folder) following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue. Once you've tested the upstream
> kernel, please comment on which kernel version specifically you tested. If
> this bug is fixed in the mainline kernel, please add the following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For
> example:
> kernel-fixed-upstream-v3.13-rc6
>
> This can be done by clicking on the yellow circle with a black pencil icon
> next to the word Tags located at the bottom of the bug description. As
> well, please remove the tag:
> needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1003096
>
> Title:
> kernel panic while using nfs4/kerberos/autofs5
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> Fresh install of 12.04 desktop. Updated 22 May with latest updates.
> The system mounts kerberized NFS4 shares with autofs5 from an ubuntu
> 10.04 server. After a variable amount of time (minutes to a few hours)
> the system crashes with no shutdown possibility (neither local nor
> remote). Only option is a hard power-off.
>
> The system crashed 4 times in a single afternoon. Before configuring
> the NFS4 shares I did use the system for 2 days with no single crash.
> At the moment I disabled the mounts and for the moment the system is...

[penalvch (penalvch)]

Fede, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003096/comments/11 regarding you no longer use nsf4. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.