Bug 168549 - installer gets signal 11 when trying "NFS Image" method
Summary: installer gets signal 11 when trying "NFS Image" method
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-09-17 00:11 UTC by G.Wolfe Woodbury
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2005-09-17 02:51:57 UTC

Attachments (Terms of Use)

Description G.Wolfe Woodbury 2005-09-17 00:11:52 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.0.6-1.2.fc4 Firefox/1.0.6

Description of problem:
Initial boot asks for the method and the only NFS option is "NFS Image", the current anaconda is only supporting "NFS tree" method, which does not appear.
After selecting "NFS Image" the network screens come up and DHCP initialization appears to work correctly.
Entering the local NFS tree path information fails with a signal 11 (consistently)

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

How reproducible:

Steps to Reproduce:
1. use boot.iso from rawhide images
2. select "NFS Image"
3. enter local rawhide tree information

Actual Results:  Consistently get a signal 11 crash

Expected Results:  I expected an installation dialogue using the NFS Tree I specified

Additional info:

RealTec on-board NIC works fine under rawhide, and DHCP reports a good IP assignment.  Can't get more fine-grained info without some advice on how to do so.

Comment 1 Willem Riede 2005-09-17 02:08:54 UTC
I experience the same signal 11 crash with today's (Sept 16th) rawhide on my
opteron, as soon as nfs mount of the x86_64 rawhide tree is attempted.

<Alt-F3> last two lines are:

going to do nfsGetSetup
mounting nfs path serve.riede.org:/pub/fedora/devel

<Alt-F4> reveals:

loader[414]: segfault at 0000000000000000 rip 0000000000476540 rsp
00007fffffe4f878 error 4

(the rsp value varies between attempts, everything else is invariant)

And before someone says that signal 11 is often hardware - I checked that by 
running memtest86+ v1.60 for an hour - stable, error free.

Comment 2 Jeremy Katz 2005-09-17 02:51:57 UTC
Fixed earlier today :)

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