On Tue, 1 Jan 2002, K Old wrote: <snip>
> [call_spurious_interrupt+118835/144011] > [8139too:__insmod_8139too_O/lib/modules/2.4.7-10/kernel/drivers/net/+-486105/96] > [free_page_and_swap_cache+197/208] [zap_page_range+422/624] > [update_atime+74/80] > Dec 29 10:38:55 ocproxy kernel: Call Trace: [<c022d0c8>] [<c8812527>] > [<c012eec5>] [<c0122e96>] [<c01492ba>] > Dec 29 10:38:55 ocproxy kernel: [do_generic_file_read+1314/1328] > [exit_mmap+184/288] [file_read_actor+0/224] [exec_mmap+35/288] > [flush_old_exec+113/608] [load_elf_binary+1151/2640] > Dec 29 10:38:55 ocproxy kernel: [<c01271a2>] [<c0125748>] [<c01271b0>] > [<c013d213>] [<c013d381>] [<c014e6ff>] > Dec 29 10:38:55 ocproxy kernel: </snip> If it helps, I recently got a similar trace and was unable to boot up although at irregular intervals. It was because I had been playing with the memory DIMMs and ended up installing a combination unsupported by the motherboard (combination of four 72 pin DIMMs with one 168 pin DIMM). I get most of the computer equipment handed down from friends and relatives, and they never come with any manuals, etc. So, I come across errors like this when replacing parts a little bit at random to see how I can get it to work. All in all, every single time I came across that particular trace it was due to either an erroneous memory configuration or bad memory chips. -- Nitebirdz Mozilla--> http://www.mozilla.org Linux XFS--> http://oss.sgi.com/projects/xfs _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
