From thierry at mailhub.co.za Sat Jul 8 18:29:26 2006 From: thierry at mailhub.co.za (Thierry de Montaudry) Date: Sat, 08 Jul 2006 20:29:26 +0200 Subject: Tux kernel panic In-Reply-To: <44A3018D.7070208@ore.org> Message-ID: <4p5qoo$154vie@mail-03.jhb.wbs.co.za> Hi all, Just started a new machine with CentOS 4.3 right off the box, minimum install to run Tux only, and I get some kernal panic after a few hours (and a few 100000 hits). See attached logs from /var/log/messages, crash1.log includes full dump... crash2.txt includes full startup log. The machine is a Intel P4-3.2Ghz with 1GB mem. The only parameter that was changed for tux is: net.tux.ignore_query = 2 IPV6 is disabled in the kernel... can it be a problem? If there is a know problem with CentOS 4.3, will I get a chance to have a more stable tux with Fedora Core 4 or 5? Regards and thanks by advance, Thierry -------------- next part -------------- A non-text attachment was scrubbed... Name: crash1.log Type: application/octet-stream Size: 2408 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: crash2.log Type: application/octet-stream Size: 24520 bytes Desc: not available URL: From mcd at daviesinc.com Sat Jul 8 18:34:52 2006 From: mcd at daviesinc.com (Chris Davies) Date: Sat, 08 Jul 2006 14:34:52 -0400 Subject: Tux kernel panic In-Reply-To: <4p5qoo$154vie@mail-03.jhb.wbs.co.za> References: <4p5qoo$154vie@mail-03.jhb.wbs.co.za> Message-ID: <44AFFACC.1070004@daviesinc.com> I would guess you are using a kernel with SMT -- try using one without SMT/SMP and I bet the problem goes away. Thierry de Montaudry wrote: > Hi all, > > Just started a new machine with CentOS 4.3 right off the box, minimum install to run Tux only, and I get some kernal panic > after a few hours (and a few 100000 hits). > See attached logs from /var/log/messages, crash1.log includes full dump... crash2.txt includes full startup log. > The machine is a Intel P4-3.2Ghz with 1GB mem. From thierry at mailhub.co.za Sat Jul 8 19:15:35 2006 From: thierry at mailhub.co.za (Thierry de Montaudry) Date: Sat, 08 Jul 2006 21:15:35 +0200 Subject: Tux kernel panic In-Reply-To: <44AFFACC.1070004@daviesinc.com> Message-ID: <4p5qoo$15511f@mail-03.jhb.wbs.co.za> Hi Chris, Thanks for the info. Just a pity to not be able to use the SMP side of the kernel and tux. After I sent my mail, I discovered that the /etc/rc.d/ini.d/tux script has a bug and will report 0 CPUs instead of 2 could that create problems with tux? If I execute the following line manually, I always get 0 as result. NRCPUS=$(cat /proc/cpuinfo | grep '^processor[ 0-9]*:' | wc -l) Regards, Thierry On Sat, 08 Jul 2006 14:34:52 -0400, Chris Davies wrote: >I would guess you are using a kernel with SMT -- try using one without >SMT/SMP and I bet the problem goes away. >Thierry de Montaudry wrote: >> Hi all, >> >> Just started a new machine with CentOS 4.3 right off the box, minimum install to run Tux only, and I get some kernal panic >> after a few hours (and a few 100000 hits). >> See attached logs from /var/log/messages, crash1.log includes full dump... crash2.txt includes full startup log. >> The machine is a Intel P4-3.2Ghz with 1GB mem. >_______________________________________________ >tux-list mailing list >tux-list at redhat.com >https://www.redhat.com/mailman/listinfo/tux-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry at mailhub.co.za Mon Jul 10 16:48:14 2006 From: thierry at mailhub.co.za (Thierry de Montaudry) Date: Mon, 10 Jul 2006 18:48:14 +0200 Subject: Tux kernel panic In-Reply-To: <44AFFACC.1070004@daviesinc.com> Message-ID: <200607101647.k6AGltm19086@belgium.iface.co.za> Hi, Restarted the machine without SMP kernel... and got the exact same problem after a few hours. Any clue? Regards, Thierry On Sat, 08 Jul 2006 14:34:52 -0400, Chris Davies wrote: >I would guess you are using a kernel with SMT -- try using one without >SMT/SMP and I bet the problem goes away. >Thierry de Montaudry wrote: >> Hi all, >> >> Just started a new machine with CentOS 4.3 right off the box, minimum install to run Tux only, and I get some kernal panic >> after a few hours (and a few 100000 hits). >> See attached logs from /var/log/messages, crash1.log includes full dump... crash2.txt includes full startup log. >> The machine is a Intel P4-3.2Ghz with 1GB mem. >_______________________________________________ >tux-list mailing list >tux-list at redhat.com >https://www.redhat.com/mailman/listinfo/tux-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From keskinege at gmail.com Thu Jul 13 08:36:48 2006 From: keskinege at gmail.com (Kursad Keskinege) Date: Thu, 13 Jul 2006 11:36:48 +0300 Subject: tux installation Message-ID: <99f30dbd0607130136x1324259dne7b13e883ac8bd4e@mail.gmail.com> hi, i am trying to install tux to a centos 4.3 distribution, the deafult kernel arriving with it is 2.6.9-34.EL I have installed everything, tux started to work with a decent work, but after about 10 hours, system crashed with: Jul 12 22:48:55 new kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000024 Jul 12 22:48:55 new kernel: printing eip: Jul 12 22:48:55 new kernel: deaba432 Jul 12 22:48:55 new kernel: *pde = 01ba4067 Jul 12 22:48:55 new kernel: Oops: 0002 [#1] Jul 12 22:48:55 new kernel: Modules linked in: tux zlib_deflate md5 ipv6 parport_pc lp parport autofs4 sunrpc button battery ac snd_azx snd_hda_cod ec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc 8139too mii dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod sata_sil liba ta sd_mod scsi_mod Jul 12 22:48:55 new kernel: CPU: 0 Jul 12 22:48:55 new kernel: EIP: 0060:[] Not tainted VLI Jul 12 22:48:55 new kernel: EFLAGS: 00010246 (2.6.9-34.EL) Jul 12 22:48:55 new kernel: EIP is at do_send_abuf+0xa1/0x17c [tux] Jul 12 22:48:55 new kernel: eax: 00000000 ebx: dadce980 ecx: 00004040 edx: 00000000 Jul 12 22:48:55 new kernel: esi: 00000000 edi: dadceab4 ebp: dadce980 esp: d9b3ff10 Jul 12 22:48:55 new kernel: ds: 007b es: 007b ss: 0068 Jul 12 22:48:55 new kernel: Process tux (pid: 30315, threadinfo=d9b3f000 task=d9b80bd0) Jul 12 22:48:55 new kernel: Stack: 00000000 dadce980 00000000 dadce9a8 00000004 deaab478 deac8b40 dadce980 Jul 12 22:48:55 new kernel: deaac401 d9b3ff4c deac8b40 00000000 00000000 d9b3f000 deab72e5 00000000 Jul 12 22:48:55 new kernel: 00000005 00000005 deab9112 c0177c22 00000000 c0167808 c17bc8d0 deac8b40 Jul 12 22:48:55 new kernel: Call Trace: Jul 12 22:48:55 new kernel: [] tux_schedule_atom+0x2a/0x42 [tux] Jul 12 22:48:55 new kernel: [] process_requests+0x170/0x1cb [tux] Jul 12 22:48:55 new kernel: [] event_loop+0x74/0x177 [tux] Jul 12 22:48:55 new kernel: [] __sys_tux+0x543/0xb8a [tux] Jul 12 22:48:55 new kernel: [] path_release+0xa/0x2c Jul 12 22:48:55 new kernel: [] sys_chdir+0x57/0x5f Jul 12 22:48:55 new kernel: [] sys_setuid+0xfc/0x108 Jul 12 22:48:55 new kernel: [] syscall_call+0x7/0xb Jul 12 22:48:55 new kernel: Code: ff ff 5f 89 c2 58 89 73 18 85 d2 79 79 83 fa f5 74 4a c6 85 e8 03 00 00 03 8b 45 6c 31 d2 c7 45 04 00 00 00 00 8d bd 34 01 00 00 40 24 00 00 00 00 c7 40 28 00 00 00 00 8b 85 34 01 00 00 e8 My only understanding is the kernel and tux must be somehow correct versions/patches can you point me/help me with the correct kernel/patch + tux to run it stable? thanks a lot, -------------- next part -------------- An HTML attachment was scrubbed... URL: