Bug 921062

Summary: kernel BUG at net/sunrpc/svc.c:559!
Product: [Fedora] Fedora Reporter: Tom Horsley <horsley1953>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-13 12:25:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
photo of kernel oops on screen none

Description Tom Horsley 2013-03-13 12:15:52 UTC
Created attachment 709547 [details]
photo of kernel oops on screen

Description of problem:

I seem to recall getting something similar to this when trying to shutdown
my system, but now I get it during boot if I have filesystems from older
machines which need the proto=udp option in order to mount. If I comment
those out, but leave in the more modern systems that support stream
connections, I can boot without a kernel oops.

If I let it sit, it eventually tries to continue the boot, but it seems
to be completely funny in the head at that point, spewing out messages
about not being able to initialize USB hubs. It never seems to make
it all the way up (at least not in any amount of time I was willing
to wait).

Version-Release number of selected component (if applicable):
kernel-3.7.9-104.fc17.x86_64

How reproducible:
It seems pretty frequent since I got the latest f17 kernel, but perhaps
doesn't happen every time. When I boot fedora 18 on this same machine
running the 3.8.2-206 kernel, I've never seen this problem (even though
I mount the same filesystems).

Steps to Reproduce:
1.boot the fedora 17 partition
2.watch kernel oops show up on screen when nfs mounts start
3.
  
Actual results:
kernel oops

Expected results:
boot normally and mount nfs filesystems

Additional info:
I'll attach some screen photos with the details of the kernel oops.

Comment 1 Josh Boyer 2013-03-13 12:25:27 UTC
(In reply to comment #0)
> It seems pretty frequent since I got the latest f17 kernel, but perhaps
> doesn't happen every time. When I boot fedora 18 on this same machine
> running the 3.8.2-206 kernel, I've never seen this problem (even though
> I mount the same filesystems).

3.8.2-105.fc17 is in updates-testing.  It should fix this issue.

*** This bug has been marked as a duplicate of bug 904870 ***