Bug 673207 - kernel BUG at net/sunrpc/rpc_pipe.c:474!
Summary: kernel BUG at net/sunrpc/rpc_pipe.c:474!
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-27 17:55 UTC by Ryan Thomson
Modified: 2011-03-07 21:06 UTC (History)
6 users (show)

Fixed In Version: kernel-2.6.35.11-83.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-11 02:44:01 UTC
Type: ---


Attachments (Terms of Use)
2.6.35-10.69 (4.70 KB, text/plain)
2011-01-27 17:55 UTC, Ryan Thomson
no flags Details

Description Ryan Thomson 2011-01-27 17:55:52 UTC
Created attachment 475651 [details]
2.6.35-10.69

Description of problem:

Kernel BUG during normal server operation. Once triggered, no new NFS mounts are possible, mount.nfs simply hangs indefinitely.

The server is F14 x86_64 running autofs pulling maps from LDAP for various NFS mount points. NFS appears to be working correctly up until the crash/bug/oops.

Version-Release number of selected component (if applicable):

kernel-2.6.35-10.74
kernel-2.6.35-10.69
kernel-2.6.35-9.64 

How reproducible:

Happens within a day or two of normal operation. Unsure what triggers the bug but it might be related to autofs because I have seen autofs "ghosting" mount points that don't exist in the maps! (negative cache problem?)

Steps to Reproduce:
1. Boot server, have users login and begin using system and NFS mounts via command line or nautilus file browser
2. Time passes
2. Kernel BUG appears in logs
  
Actual results:

New NFS mounts attempts (manually or via autofs) hang indefinitely until server is rebooted. Network resources basically become unavailable.

Expected results:

No kernel BUG, NFS and autofs continue working normally.

Additional info:

Attached is the full /var/log/messages output from "cut here" to "end trace" for one instance of the bug.

Comment 1 Chuck Ebbert 2011-01-31 03:43:23 UTC
The fix will be in 2.6.35.10-82

Comment 2 Fedora Update System 2011-02-05 20:14:01 UTC
kernel-2.6.34.8-67.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/kernel-2.6.34.8-67.fc13

Comment 4 Fedora Update System 2011-02-07 13:35:28 UTC
kernel-2.6.35.11-83.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/kernel-2.6.35.11-83.fc14

Comment 6 Ryan Thomson 2011-02-09 21:12:45 UTC
The server where we noticed this problem is a production machine so I haven't yet had a chance to schedule a window for updates and testing yet.

I'm scheduling testing for Feb 11 but since this bug tends to take a day or two to manifest in our experience, I won't have results until Feb 14.

Thanks!

Comment 7 Fedora Update System 2011-02-10 21:25:49 UTC
kernel-2.6.35.11-83.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Ryan Thomson 2011-02-14 22:39:01 UTC
The host has been running 2.6.35.11-83.fc14.x86_64 since Feb 11 without any sign of the kernel BUG reported here.

Thanks for the fix!

Comment 10 Fedora Update System 2011-02-24 15:50:11 UTC
kernel-2.6.34.8-68.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/kernel-2.6.34.8-68.fc13

Comment 11 Fedora Update System 2011-03-07 21:06:08 UTC
kernel-2.6.34.8-68.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.