Bug 908451 - Crashes at boot, possibly in NFS code
Summary: Crashes at boot, possibly in NFS code
Keywords:
Status: CLOSED DUPLICATE of bug 910457
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-06 17:57 UTC by Tom Horsley
Modified: 2013-04-03 18:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-03 18:13:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Photograph of screen with kernel walkback (2.90 MB, image/jpeg)
2013-02-06 17:57 UTC, Tom Horsley
no flags Details

Description Tom Horsley 2013-02-06 17:57:53 UTC
Created attachment 694062 [details]
Photograph of screen with kernel walkback

Description of problem:

My Fedora 18 system sometimes (not always) crashes during boot with the attached
screenshot showing the kernel oops. This (so far) has only happened when I typed reboot. If I power cycle the machine (which I usually do to recover from this), it seems to boot cleanly (but I don't have a large sample size).

Version-Release number of selected component (if applicable):
kernel-3.7.5-201.fc18.x86_64


How reproducible:
Only sometimes.

Steps to Reproduce:
1.type reboot
2.watch system coming back up get an oops
3.
  
Actual results:
Oops during NFS mount activity at boot

Expected results:
System booting normally.

Additional info:

Comment 1 Tom Horsley 2013-02-07 12:34:09 UTC
The kernel-3.7.3-101.fc17.x86_64 kernel on my fedora 17 partition just did this same thing as well. Something about 3.7.* kernels hates NFS.

It is probably also worth mentioning that the vast majority of NFS servers it is talking to on the remote systems are very very old and must be mounted with the proto=udp parameter.

Comment 2 Josh Boyer 2013-04-03 18:13:21 UTC

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


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