Hi again,
Trying for the 4'th time gave me an oops, but the install seems to be
successful. I got the oops at the exact time that anaconda said it was
100% done, then the oops. Anaconda then unmounted filesystems and said
that I could safely reboot my system.
The output was:
---------------- CUT ----------------
Oops: 0002
CPU: 0
EIP: 0060:[<c013cca3>] Not tainted
EFALGS: 00010202
EIP is at(2.4.20-8BOOT)
eax: 00000000 ebx: ca8000a0 ecx: 00000b15 edx: 000000e6
esi: 00000001 edi: cb85eae0 ebp: 00000000 esp: dfccde8c
ds: 0068 es: 0068 ss: 0068
Process anaconda (pid: 19, stackpage=dfccd000)
Stack: ca8000a0 c013d43f ca8000a0 0b150e4c ca8000a0 c013d758 ca8000a0 0b150e4c
00001ad6 c013d81a ca8000a0 c12c72e8 c6a45348 00000000 00000000 c012ad89
c12c72e8 00000000 00000001 c012addc c12c72e8 00000000 c12c72e8 c012ae9d
Call Trace: [<c013d43f>] (0xdfccde90)
[<c013d758>] (0xdfccdea0)
[<c013d81a>] (0x0xdfccdeb0)
[<c012ad89>] (0x0xdfccdec8)
[<c012addc>] (0x0xdfccded8)
[<c012ae9d>] (0x0xdfccdee8)
[<c012aff9>] (0x0xdfccdf1c)
[<c014e0a4>] (0x0xdfccdf34)
[<c014e1a5>] (0x0xdfccdf4c)
[<c0140759>] (0x0xdfccdf68)
[<c01502e4>] (0x0xdfccdf84)
[<c015033f>] (0x0xdfccdb4)
[<c0108d73>] (0x0xdfccdc0)
Code: 89 50 20 89 42 24 39 1c 8d 84 33 2d c0 74 22 c7 43 20 00 00
install exited abnormally -- recieved signal 11
---------------- CUT ----------------
and then anaconda said that it was unmounting the disks and that I could
reboot safely. Is this a memory problem?
Thanks for any help,
jules
On Sat, 2003-09-27 at 11:54, Jules Colding wrote:
> Hi,
>
> I got a kernel panic when I tried to install, rh9 on my new machine.
> This happen while doing a harddisk install from /dev/hda5 (fat -
> partitioned and formatted by W2K).
>
> My hardware is:
> Asus A7V600 Via KT600 DDR400 AGP x8
> 1 AMD Athlon Thoroughbred XP 2000+ (1667 MHz)
> 2 Seagate Barracuda 7200.7 80GB, 7200RPM, 2MB
> 1 Kingston 512 MB DDR-RAM PC32000 400 MHz KVR400X64C3
> 1 Nvidia GeForce4 MX 440-8X, 128MB DDR
>
> Both Seagates are at IDE1. I have installed W2K on hda and was trying to
> install rh9 on hdb as a dual boot. I have a fat partition (hda5) on my
> W2K disk. I also have a cdrom on hdc.
>
> I have replicated the entire error screen below:
>
> ---------------- CUT ----------------
> /mnt/runtime umount failed (16)
> disabling /dev/loop1 LOOP_CLR_FD failed: 16
> ------------- [ cut here ] -------------
> kernel BUG at inode.c:564!
> invalid operand: 0000
> CPU: 0
> EIP: 0060:[<c014dfaa]> Not tainted
> EFLAGS: 00010202
>
> EIP is at (2.4.20-8BOOT)
> eax: 00000001 ebx: dce37420 ecx: dce37440 edx: 00000000
> esi: dfcd1f60 edi: dfcd1f60 ebp: c0271280 esp: dfcd1f44
> ds: 0068 es: 0068 ss: 0068
> Process linuxrc (pid: 17, stackpage=dfcd1000)
> Stack: dce37420 c014e07a dce37420 defe4c64 00000000 c014e1a5 dfcd1f60 dce37258
> d85685d8 defe4c44 defe4c00 dee64ca0 c0140759 defe4c00 c0271348 00000000
> dfcd1f98 0000000d bffec894 c01502e4 defe4c00 dee64ca0 c25a2590 c250a270
> Call Trace: [<c014e07a>] (0xdfcd1f48)
> [<c014e1a5>] (0xdfcd1f58)
> [<c0140759>] (0xdfcd1f74)
> [<c01502e4>] (0xdfcd1f90)
> [<c0108d73>] (0xdfcd1fc0)
>
> Code: 0f 0b 34 02 39 da 23 c0 8b 83 fc 00 00 00 a9 10 00 00 00 75
> VFS: Cannot open root device "" or 48:05
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 48:05
> ---------------- CUT ----------------
>
> This was the first time I got a kernel panic. The install have halted
> trice before. Two times when I tried to install from cdrom, and one time
> when I tried the hard disk install from the same partition. I have
> checked the media and the isos. They all PASS.
>
> So, is there a newer boot image or some other solution to this problem?
>
> Thanks in advance,
> jules
>
>
> --
> Jules Colding <jules@xxxxxxxxxx>
--
Jules Colding <jules@xxxxxxxxxx>
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
