Bug 118431 - sysinstall stalls at "Located INDEX..."
Summary: sysinstall stalls at "Located INDEX..."
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: sparc64 (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: kensmith
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-04 18:20 UTC by Salvador Fandino
Modified: 2008-02-03 05:21 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Salvador Fandino 2007-12-04 18:20:02 UTC
Hi,

I am trying to install FreeBSD 7.0-Beta3 in a SunBlade 100 (mem: 512MB,
cpu: 500MHz), but the installation process stalls at the "Located INDEX,
now reading package data from it..." screen.

Running top in another console shows that CPU consumption at that screen
goes slowly increasingly from a few percent to 99%. It looks like if a
non-linear cost algorithm was used to process the index.

I have tried to install a couple of times with different package
configuration (mostly all and x-user) with the same result.

Cheers,

 - Salva


(I had already sent this bug report to the "bugs" mailing list)
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2007-12-30 11:44:04 UTC
Responsible Changed
From-To: freebsd-sparc64->kensmith

Ken maintains sysinstall ;)
Comment 2 kensmith freebsd_committer freebsd_triage 2007-12-30 12:17:14 UTC
State Changed
From-To: open->patched


Would you mind giving this another try with 7.0-RC1?  I'm actually a 
little surprised the install stalled on sparc64, on the other architectures 
it died due to a signal.  There are two other bugs related to installing 
packages that were not part of 7.0-RC1 but the bug related to parsing 
the INDEX file was part of 7.0-RC1. 

Thanks.
Comment 3 kensmith freebsd_committer freebsd_triage 2008-02-03 05:17:11 UTC
State Changed
From-To: patched->closed


I think this was part of the "general issues" sysinstall had that I 
fixed as we moved into the RCs.   No response from the user about 
whether or not those fixes solved his problem but testing with the 
package sets on the ISOs made during the RCs have worked.