Re: Problems getting RH 7.2 to boot properly
1047466 Byte in 1 Mail. At 2000 users or more it is a minimum of 2 GB traffic only from You! It' not normal. PLONK ! -- Mach' mal Urlaub http://www.ungarnurlaub.de ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Problems getting RH 7.2 to boot properly
Silviu wrote: Please pardon me, but when exactly did it seem to you like a good idea to post a mail of about 1MB in size to this group ? While I agree with that sentiment, there is also no excuse for the Redhat-list to pass along messages like that. This list uses mailman to run the list, and mailman has a setting for Maximum length in Kb of a message body. I really think that about 3KB would be an appropriate setting. Duane ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Problems getting RH 7.2 to boot properly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 1 Jan 2002 at 01:39:04 , K Old wrote the following on the Problems getting RH 7.2 to boot properly thread: All equipment is brand new and has been exchanged a few times cause certain components weren't working right, but now everything seems ok. I am having all kinds of (what seems to be) memory leaks or something like that, during bootup. I am attaching all sorts of logs for those that can help. I don't know what to do from here. Please pardon me, but when exactly did it seem to you like a good idea to post a mail of about 1MB in size to this group ? - -- Overcome by jealousy, Data dismembers the Energizer Bunny __ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (MingW32) Comment: Member of the PGP-Basics, Encryption Help Team iD8DBQE8M5pd8WBGNj3ut+0RAmEsAKCKT/qmwxJp2pis1zZMlTQPZ+RasACfcd9W uBRbbanvdO2WgdMwsyQGlKI= =g7eX -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Problems getting RH 7.2 to boot properly
On Mon, 31 Dec 2001 18:32:17 -0600 K Old [EMAIL PROTECTED] scribbled in frustration: Hello all, I have setup several RH machines and the latest one I've got has stumped me. The stats of the machine are: Athlon 1 Ghz 128 MB RAM 40GB Maxtor HD Transcend Motherboard All equipment is brand new and has been exchanged a few times cause certain components weren't working right, but now everything seems ok. I am having all kinds of (what seems to be) memory leaks or something like that, during bootup. I am attaching all sorts of logs for those that can help. = More than a MB worth??!! Whew. I thought one of my students was sending me a PowerPoint presentation ;-) Mike -- It is God's job to forgive bin Laden. It is our job to set up the meeting. --U.S. Marine Corp. ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Problems getting RH 7.2 to boot properly
On Tue, 2002-01-01 at 13:33, K Old wrote: I am having all kinds of (what seems to be) memory leaks or something like that, during bootup. I am attaching my boot log, for those that can help, and can send other logs if needed.. I don't know what to do from here. I don't see any memory problems in the log. How about just showing the problematic lines. happy new year charles ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Problems getting RH 7.2 to boot properly
Ok, well, I've looked in the messages log and have found the following. It looks like the xfs is trying to start and can't (cause there is no sound card) and then it seems to start a chain reaction with all other services. Sometimes I can actually get into the OS and start X, but a few minutes into the session, the mouse and keyboard freeze and I have to physically shut the machine down. Any ideas what I can do to fix this? I assume turning off xfs on startup is my first step. Kevin --- from messages- Dec 29 10:38:52 ocproxy gdm(pam_unix)[1257]: session opened for user root by (uid=0) Dec 29 10:38:54 ocproxy kernel: Via 686a audio driver 1.1.14b Dec 29 10:38:54 ocproxy kernel: PCI: Found IRQ 5 for device 00:07.5 Dec 29 10:38:54 ocproxy kernel: PCI: Sharing IRQ 5 with 00:13.0 Dec 29 10:38:54 ocproxy kernel: via82cxxx: Codec rate locked at 48Khz Dec 29 10:38:54 ocproxy kernel: ac97_codec: AC97 Audio codec, id: 0x414c:0x4326 (Unknown) Dec 29 10:38:54 ocproxy kernel: via82cxxx: board #1 at 0xCC00, IRQ 5 Dec 29 10:38:54 ocproxy modprobe: modprobe: Can't locate module sound-service-0-0 Dec 29 10:38:55 ocproxy kernel: Bad swap file entry c788e740 Dec 29 10:38:55 ocproxy kernel: kernel BUG at page_alloc.c:85! Dec 29 10:38:55 ocproxy kernel: invalid operand: Dec 29 10:38:55 ocproxy kernel: CPU:0 Dec 29 10:38:55 ocproxy kernel: EIP:0010:[__free_pages_ok+41/768] Dec 29 10:38:55 ocproxy kernel: EIP:0010:[c012dee9] Dec 29 10:38:55 ocproxy kernel: EFLAGS: 00210282 Dec 29 10:38:55 ocproxy kernel: eax: 001f ebx: c112f0c8 ecx: 0001 edx: 2fea Dec 29 10:38:55 ocproxy kernel: esi: c112f0c8 edi: c112f0c8 ebp: esp: c3e7bb8c Dec 29 10:38:55 ocproxy kernel: ds: 0018 es: 0018 ss: 0018 Dec 29 10:38:55 ocproxy kernel: Process gnome-session (pid: 1424, stackpage=c3e7b000) Dec 29 10:38:55 ocproxy kernel: Stack: c022d0c8 0055 c3e7bbb4 c7c13580 c3e7bbb4 00200282 c8812527 c112f0c8 Dec 29 10:38:55 ocproxy kernel:c112f0c8 7000 c3ecf13c c012eec5 c1397200 c4209b80 Dec 29 10:38:55 ocproxy kernel:c112f0c8 00016000 c0122e96 c112f0c8 0008 0805e000 c3ec1080 Dec 29 10:38:55 ocproxy kernel: Call Trace: [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: [8139too:__insmod_8139too_O/lib/modules/2.4.7-10/kernel/drivers/net/+-486105/96] [8139too:__insmod_8139too_O/lib/modules/2.4.7-10/kernel/drivers/net/+-554793/96] [load_elf_binary+0/2640] [search_binary_handler+113/384] [do_execve+380/480] [getname+94/160] Dec 29 10:38:55 ocproxy kernel:[c8812527] [c88018d7] [c014e280] [c013d991] [c013dc1c] [c013eade] Dec 29 10:38:55 ocproxy kernel:[sys_execve+48/96] [system_call+51/56] Dec 29 10:38:55 ocproxy kernel:[c0105b60] [c0106f2b] Dec 29 10:38:55 ocproxy kernel: Dec 29 10:38:55 ocproxy kernel: Code: 0f 0b 58 5a 8b 77 08 85 f6 74 10 6a 57 68 c8 d0 22 c0 e8 80 Dec 29 10:38:55 ocproxy kernel: exit_mmap: map count is 87 On Tuesday 01 January 2002 12:52 pm, Charles Galpin wrote: On Tue, 2002-01-01 at 13:33, K Old wrote: I am having all kinds of (what seems to be) memory leaks or something like that, during bootup. I am attaching my boot log, for those that can help, and can send other logs if needed.. I don't know what to do from here. I don't see any memory problems in the log. How about just showing the problematic lines. happy new year charles ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Problems getting RH 7.2 to boot properly
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
