Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 93031 - Crash while running stage 3
Summary: Crash while running stage 3
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Gentoo Release Team
URL: http://www.gentoo.org/doc/en/handbook...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-17 22:49 UTC by Robert
Modified: 2005-05-19 06:19 UTC (History)
1 user (show)

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 Robert 2005-05-17 22:49:25 UTC
I am a new Linux user - so I am lost as to what all this means...
However, as I was carefully following the install instructions, I experienced a
computer lock-up. As I have no idea what the below means, I took the time to
type it all out in hopes that someone can tell me what is wrong.

I downloaded stage three (stage3-x86-2005.0.tar.bz2) at:
http://prometheus.cs.wmich.edu/gentoo/releases/x86/2005.0/stages/x86/

Afterwards, I did the tar command: "# tar -xvjpf stage?-*.tar.bz2"
As expected, everything started extracting.
Upon reaching the line: ".usr/share/automake-1.5/INSTALL" I received the
following error(s):

Unable to handle kernel NULL pointer dereference at virtual address 00000001
printing eip:
c01332e6
*pde = 00000000
Ooops: 0002 [#1]
SMP
Modules linked in: floppy rtc evdev tulip parport_pc parport ahci sata_qstor
sata_uli sata_sis sata_sx4 sata_nv sata_via sata_svw sata_sil sata_promise
libata dm_mirror dm_mod sbp2 ohci1394 ieee1394 sl811_hcd ohci_hcd usb_storage
usbhid ehci_hcd usbcore
CPU:    0
EIP:    0060:[<c01332e6>]      Tainted: G S     VLI
EFLAGS: 00010086   (2.6.11-gentoo-r3)
eax: c0398c0c   ebx: c0398c0c   ecx: c11e9be0   edx: 00000001
esi: c0398980   edi: 0000000a   ebp: 00000009   esp: cfec5ebc
ds: 007b   es: 007b   ss: 0068
Process kswapd0 (pid: 139, threadinfo=cfec4000 task=cfea0590)
Stack: 00000020 c1054038 c11701b8 00000000 00000001 c10b1920 c10b1640 c11509a0
       c1151c20 c10b2080 c10b2220 c10b22e0 c10b1ec0 c10b1fc0 c10b2020 c10b1b20
       c10b1c00 c10b1d00 c10b18a0 0000000d 00000014 c0398980 cfec5f58 c0133a33
Call Trace:
 [<c0133a33>]
 [<c0133d94>]
 [<c0133fb3>]
 [<c0124e3a>]
 [<c012433a>]
 [<c0133eb5>]
 [<c0100835>]
Code: 00 8b 8e 90 02 00 00 8b 41 04 39 d8 74 07 83 e8 18 0f 0d 08 90 f0 0f ba 71
e8 05 19 c0 85 c0 75 02 0f 0b 8b 51 04 8b 01 89 50 04 <89> 02 c7 41 04 00 02 20
00 c7 01 00 01 10 00 f0 ff 41 ec 0f 94

Reproducible: Didn't try
Steps to Reproduce:
1. Follow step-by-step (fresh) install instructions.
2. Download Stage 3
3. # tar -xvjpf stage?-*.tar.bz2

Actual Results:  
See Details to explain system halt/hang/crash.

Expected Results:  
Should have been able to proceed to installing Portage
(http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=5#installing_portage).

900 Mhz CPU
256 Memory
80 Gig HD

Waiting for reply before continuing.
Comment 1 Daniel Drake (RETIRED) gentoo-dev 2005-05-18 07:02:41 UTC
Are you sure your system has no hardware problems? I suggest you let memtest run
3 times or so to confirm the RAM is ok. (just type memtest at the first Gentoo
livecd boot prompt)
Comment 2 Chris Gianelloni (RETIRED) gentoo-dev 2005-05-18 07:12:19 UTC
Try booting your system with "gentoo nosmp noapic acpi=off" also.  It sounds
like either a problem with your hardware, or possibly a driver not liking your
system.  Can you post the results of "lspci" from the Install CD?

Kernel guys, would you rather stay on the CC, or should I add you back if we
determine it to be a kernel bug that is not fixed in a more recent kernel set?
Comment 3 Daniel Drake (RETIRED) gentoo-dev 2005-05-18 07:45:43 UTC
May as well stay on CC.
Comment 4 Robert 2005-05-18 08:38:05 UTC
No, I am not certain that the hardware is good.
I have replaced the video card, the memory chip, and the LAN card on the board
in hopes of preventing occasional lock-ups I was having with Windows ME.
Directly after replacing the hardware is when I attempted to install Gentoo.

I attempted to run "memtest".
-/bin/bash: memtst: command not found

Results from lspci:
---------------
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
0000:00:07.1 IDE Interface: Via Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:07.2 USB Controller: Via Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 16)
0000:00:07.3 USB Controller: Via Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 16)
0000:00:07.4 Host Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
(rev 40)
0000:00:0b.0 Ethernet controller: Linksys NC100 Netwrok Everywhere Fast Ethernet
10/100 (rev 11)
0000:00:11.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
0000:00:11.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 08)
0000:01:00.0 VGA compatable controller: ATI Technologies Inc Rage 128 PF/PRO AGP
4x TMDS
-----------------


At boot promt I used the folowing command:
"gentoo nosmp noapic acpi=off"

I then used links2 to download the stage 3 again.
"# tar -xvjpf stage?-*.tar.bz2"
This time the unpacking stopped at:
./usr/bin/chkdupexe
then there were a few "Cannot write: No space left on device" error messages.

Do I need to re-do my partitions or something?
Comment 5 Chris Gianelloni (RETIRED) gentoo-dev 2005-05-18 09:02:59 UTC
(In reply to comment #4)
> I attempted to run "memtest".
> -/bin/bash: memtst: command not found

memtest is run from the boot: prompt before the system boots.

> At boot promt I used the folowing command:
> "gentoo nosmp noapic acpi=off"
> 
> I then used links2 to download the stage 3 again.
> "# tar -xvjpf stage?-*.tar.bz2"
> This time the unpacking stopped at:
> ./usr/bin/chkdupexe
> then there were a few "Cannot write: No space left on device" error messages.
> 
> Do I need to re-do my partitions or something?

It definitely looks like it.

/usr usually ends up being at leats a couple GB by the time you're done, so if
your /usr isn't on a separate partition, then / needs to be at least that big.
Comment 6 Robert 2005-05-18 09:13:44 UTC
(In reply to comment #5)

> > 
> > Do I need to re-do my partitions or something?
> 
> It definitely looks like it.
> 
> /usr usually ends up being at leats a couple GB by the time you're done, so if
> your /usr isn't on a separate partition, then / needs to be at least that big.

Well, I did the partitions as described in the install text:

Partition  	Filesystem  	Size  	                Description
/dev/hda1 	ext2 	        32M 	                Boot partition
/dev/hda2 	(swap) 	        512M 	                Swap partition
/dev/hda3 	ext3 	        Rest of the disk 	Root partition

So which one needs to be diffrent?
Comment 7 Robert 2005-05-18 09:15:37 UTC
I will wait an hour or so to see if anyone has anything to add, then I will use
the Maxtor PowerMax utilitiy to erase and start over...
Comment 8 Daniel Drake (RETIRED) gentoo-dev 2005-05-18 09:20:04 UTC
(In reply to comment #4)
> I then used links2 to download the stage 3 again.
> "# tar -xvjpf stage?-*.tar.bz2"
> This time the unpacking stopped at:
> ./usr/bin/chkdupexe
> then there were a few "Cannot write: No space left on device" error messages.

A common mistake is to extract the tarball without mounting your big disk
partition at /mnt/gentoo, or forgetting to "cd /mnt/gentoo" before unpacking the
tarball. If you forget either of these steps, it'll start unpacking it into RAM,
and obviously it doesn't all fit.

Also, the most important thing here is the memtest operation - I'd do that
before you try anything else.
Comment 9 Robert 2005-05-18 09:23:33 UTC
(In reply to comment #8)
> (In reply to comment #4)
> > I then used links2 to download the stage 3 again.
> > "# tar -xvjpf stage?-*.tar.bz2"
> > This time the unpacking stopped at:
> > ./usr/bin/chkdupexe
> > then there were a few "Cannot write: No space left on device" error messages.
> 
> A common mistake is to extract the tarball without mounting your big disk
> partition at /mnt/gentoo, or forgetting to "cd /mnt/gentoo" before unpacking the
> tarball. If you forget either of these steps, it'll start unpacking it into RAM,
> and obviously it doesn't all fit.
> 
> Also, the most important thing here is the memtest operation - I'd do that
> before you try anything else.



Ok, doing that now.
Comment 10 Robert 2005-05-18 15:55:03 UTC
I ran both of my memory sticks through seperate tests.

Both failed - badly.

/me heads out to find new hardware.

Thanks for the support guys.
Comment 11 Chris Gianelloni (RETIRED) gentoo-dev 2005-05-19 06:18:40 UTC
...
Comment 12 Chris Gianelloni (RETIRED) gentoo-dev 2005-05-19 06:19:38 UTC
Sorry to hear about your hardware... Good luck!