Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 35004 - During install emerge sync either rsync crashes or kernel crashes
Summary: During install emerge sync either rsync crashes or kernel crashes
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Bob Johnson (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-03 12:56 UTC by Jan Van Uytven
Modified: 2003-12-03 16:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Van Uytven 2003-12-03 12:56:39 UTC
I have a dual Xeon machine (Asus PC-DL (i875P chipset)  MB with 2.46GHz CPUs and
1GB or DDR RAM.

I'm trying to install Gentoo on it, so I downloaded and burnt a copy of the 1.4
LiveCD for Pentium 4s. I proceed with the install and everything goes well until
I get to the point where after the chroot I need to 'emerge sync'. At this point
one of a couple of things will happen:

1) At some point during the emerge rsync will die with the message:
"rsync: error in rsync protocol data stream (code12) at io.c ..."
2) The kernel will crash with a seg fault, forcing a reboot
3) The emerge sync will finish, but attempting to bootstrap will fail
immediately with portage complaining of incorrect mdsums.

Trying to reboot after the kernel crash will sometimes give the following
message: <4>socket: no more sockets

I have disabled both hyperthreading and ACPI on the MB. I have tried with both
'smp' and plain boots off the LiveCD. I have tried with the LiveCD Basic x86.



Reproducible: Always
Steps to Reproduce:
1.Boot the machine with a Pentium 4 LiveCD, optionally using smp
2.Start a clean install 
3.At 'emerge sync', problems will begin

Actual Results:  
rsync either died or the kernel crashed with a seg fault. If the rsync succeeds
portage will be unable to bootstrap, complaining of incorrect mdsums. 

Expected Results:  
Emerge sync and bootstrap should have succeeded normally.
Comment 1 Jan Van Uytven 2003-12-03 16:47:20 UTC
Problem turned out to be a problem with the hardware (likely the RAM) as both Fedora Core 1 and Windows 2003 both fail to install on it as well.