very very strange errors compiling the kernel with 64MB ram

very very strange errors compiling the kernel with 64MB ram

Post by Marco De Benedett » Wed, 18 Dec 1996 04:00:00



I have a, new, pc:
MotheBoard ASUS PCI, Pentium 133, 64MB (4*16)
RedHat 3.0.3
compiling the kernel (2.0.xx) with 64MB, gcc reads strange characters in
the word, 'unsigned' but in different files every time, it never occours
errors reading other words.
It does not happen with 32MB. The ram is good and it does not depends on
wich bank I use when using 32MB. I have also used different HDs.

All, but compiling, seems to work ok, by now. Also windows 95 :(((

Did somebody hear about this kind of problem?

-thanks in advance

 
 
 

1. kernel fails to compile with 64MB RAM

In the 2.1.5-RELEASE the kernel fails to compile when I have 64MB of RAM in
the machine. I placed 16MB of RAM in the machine and everything compiled
just fine. Possible bug?? Anyone else have the same experience?

System specs:

        P166 with 256k pipeline burst
        64MB EDO RAM
        1.2 GB IDE Seagate drive (used for system disk)
        AHA2940W SCSI Controller
        4.2 GB SCSI Seagate HDD

We just purchased two machines that are identical. The same error occurs on
both. The error is not the same all the time. Here is a list of some:

-----

Aug 6 08:19:23 python /kernel: pid 1443 (as), uid 0: exited on signal 11
cc: Internal compiler error: program as got fatal signal 11
*** Error code 1

-----

assertion "(fragP->fr_next == 0) || ((fragP->fr_next->fr_address - fragP->fr_address) == fragP->fr_fix)" failed: file "/usr/src/gnu/usr.bin/as/write.c", line 354
cc: Internal compiler error: program cc1 got fatal signal 6
*** Error code 1

-----

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x48f12bb6
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xf01272d2
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 3255 (make)
interrupt mask          =
panic: page fault

syncing disks... etc

-----

Of course the last error is a complete system failure.

Any information on this problem would be appreciated. Please send e-mail.

                                Paul Manuel
                                Systems Programmer
                                (709) 737-2661
                                Memorial University of Newfoundland
                                St. John's, NF Canada

2. Network Config w/TRENDnet

3. Q: 128 MB, 64MB cachable -> 64MB RAM disk, swap space?

4. CNet CN930E PCI (slave) Ethernet w/ RedHat 5.1/5.2?

5. RedHat7 "unable to handle kernel paging request" and other strange errors - RAM problem?

6. Sharp Zaurus ( linux pda )

7. Install 128MB RAM on 430VX chipset with 64MB cacheable RAM support

8. Installation help

9. how much ram cache for 64MB ram under linux?

10. can kernel handle 64MB RAM ?

11. strange error compiling kernel

12. Strange error compiling kernel...

13. Strange kernel compile errors with GCC 2.7.2 and Linux 2.0.5