devel January 2008

devel@lists.centos.org

28 participants
26 discussions

Help offer on Sparc front
by Hugo van der Kooij 09 Jan '09

09 Jan '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have just received a SunBlade150 which I would like to put to good use. I understand there is a Centos port underway for the Sparc line. If it is possible to trash the harddisk and fill it with the bare stuff to make it work I am willing to lend access to the system for developers and also do some things myself. I am not a programmer but I can spot the incidental error and maybe fix a typo or at least do my best to provide serious feedback in attempts to capture, reproduce and solve issues. If there is a basic kit somewhere to turn the former Solaris machine and set it on the road to Centos 5 I am willing to add my weight and push the cart along. Hugo. - -- hvdkooij(a)vanderkooij.org http://hugo.vanderkooij.org/ PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc A: Yes. >Q: Are you sure? >>A: Because it reverses the logical flow of conversation. >>>Q: Why is top posting frowned upon? Bored? Click on http://spamornot.org/ and rate those images. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHHl8BBvzDRVjxmYERAtwIAKCajwRD8ZIbbQsVRiA89+9OYD30KQCfR6gw uIbicj9rZqC/HdYv0fXosB0= =Iaaf -----END PGP SIGNATURE-----

4 5

presto / deltarpm
by Karanbir Singh 05 Jan '09

05 Jan '09

hi, The idea of yum-presto and deltarpm support on mirror.centos.org is something that seems to be worth visiting again. I am just wondering if there is anyone who would like to grab the issue, do the testing, workout whats involved and then try and come up with an implementation plan ? Would be good if you already knew how yum and repomd type repositories worked. Anyone interested and have the time ? -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

4 4

kmod-xfs and 2.6.18-53.1.6.el5 kernel
by Jon Ernster 31 Jan '08

31 Jan '08

Is there an ETA for a kmod-xfs build against the latest kernel? Cheers.

2 1

CentOS-5 Cross-Build Environment (arm, mips, sparc, others..) / pre-alpha released
by Brian Schueler 26 Jan '08

26 Jan '08

thank you for this hint. That is nearly what I need. This week the OpenSUSE Build Service, which is similar to thetango but comes with a complete Software management and a http frontend, has been released for RHEL/CentOS 5 and became very popular. I'm now dealing with the buildroot (the minimalistic set of Software for rebuilding SRPMS) which is generated by obs. Its dependency resolution on SRPM information is said to work much better. I have to tune a little bit to make this work right for CentOS source SRPMS and later for the cross build environment. At this time obs is able to create complete SuSE binary Distributions entirely from the SRPMs (requiring the minset (binutils,gcc,python,rpm)). Brian

1 0

CentOS 5.1 for ppc
by Kazuki Ohara 25 Jan '08

25 Jan '08

Hi, When is it planned to release the CentOS 5.1 for ppc? I heard the ppc version of CentOS will be released with 5.1. Is it soon? Regards, -- Kazuki Ohara

2 1

Gnupanel Development
by Lance Davis 23 Jan '08

23 Jan '08

The gnupanel guys are looking to support CentOS and it would be good if we could have some involvement / ownership of the CentOS hooks ... Is anyone willing to own the CentOS version of the template file for packages - which would look something like :- http://dev.gnupanel.org/annex/unistall.hg/?file/79955850dcdf/libs/dists/PLD… (which is the file for PLD linux) Regards Lance -- uklinux.net - The ISP of choice for the discerning Linux user.

1 0

Re: [CentOS-devel] RE: [CentOS-virt] BUG: soft lockup detected onCPU#?
by Ross S. W. Walker 23 Jan '08

23 Jan '08

Thanks Johnny, and sorry for the top post (blackberry). I d/l'd the src rpm and found their patches all in 1 patch file called xen.patch (I did an ls -lt and picked the files with the latest timestamps). There may also be kernel config changes as several config files were touched, but I couldn't get a hold of the original 8.1.8 src rpm to diff them. I would be happy to help in getting the parts needed so they can be rolled up into a single patch to apply to the current plus kernel. Just let me know what you need. I wonder if anybody at XenSource notified upstream of the fixes? -Ross ----- Original Message ----- From: centos-devel-bounces(a)centos.org <centos-devel-bounces(a)centos.org> To: The CentOS developers mailing list. <centos-devel(a)centos.org> Sent: Wed Jan 23 07:37:04 2008 Subject: Re: [CentOS-devel] RE: [CentOS-virt] BUG: soft lockup detected onCPU#? Ross S. W. Walker wrote: > Ross S. W. Walker wrote: >> Brett Worth wrote: >>> Hello All. >>> >>> I've just started looking into Xen and have a test >>> environment in place. I'm seeing an >>> annoying problem that I thought worthy of a post. >>> >>> Config: >>> >>> I have 2 x HP DL585 servers each with 4 Dual core Opterons >>> (non-vmx) and 16GB RAM >>> configured as Xen servers. These run CentOS 5.1 with the >>> latest updates applied. These >>> system both attach to an iSCSI target which is an HP DL385 >>> running ietd and serving SAN >>> based storage. >>> >>> I have a test VM running CentOS 5.1 also updated. >>> >>> Problem: >>> >>> If I run the VM on a single server everything is OK. If I do >>> a migrate of the VM to the >>> other server I start getting random "BUG: soft lockup >>> detected on CPU#?" messages on the >>> VM console. The messages seem to happen with IO but not >>> every time. A reboot of the VM >>> on the new server will stop these messages. >>> >>> I've also left the VM running overnight a couple of times and >>> when I do I find that any >>> external sessions (ssh) are hung in the morning but the >>> console session is not. New ssh >>> sessions can be started and seem to work. >>> >>> After much googling it looks like the kernel messages can >>> occur if dom0 is very busy but >>> mine is not. >>> >>> Any suggestions? >> The soft lockup is technically not a BUG. >> >> You will see these errors if an IRQ takes more then 10 seconds >> to respond. >> >> In your case I would take a look at your iSCSI setup and the >> time it takes to migrate the VM from one node to another along >> with SCSI reserve/release setup on the iSCSI target. >> >> I also have been using the Xen 3.2 RPMs off xen.org to CentOS >> 5.1 which good results, the VM migration may run smoother and >> quicker in Xen 3.2, but in doing so you take Xen off the >> reservation, if your OK with that it may fix your issues. > > After seeing this same issue on my Xen 3.2 install, but with NO > migration or iSCSI happening I decided it is probably NOT iSCSI's > fault, so I decided to research it a little more and this is what > I found: > > http://docs.xensource.com/XenServer/4.0.1/guest/ch04s08.html#rhel5_limitati… > > XenSource does provide a repo of CentOS 5 kernels that have been > patched to fix this though: > > http://updates.xensource.com/XenServer/4.0.1/centos5x/ > > But these seem to be woefully out of date. > > I wonder if a kind soul would add the fix to the centosplus kernel > with XenSource's patch so those rogue Xen users could benefit from > this fix until upstream decides to include it. > > I suppose the centosplus patch would need to be flagged interm in > case it needs removed when upstream has their own fix. Ross, Thanks for researching this. I can probably add this to the next centosplus kernels, though I usually do not like to add patches ... and I will need to grab their kernels and work out what is patched and try to roll it into our kernels. -- Johnny Hughes ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

1 0

RE: [CentOS-virt] BUG: soft lockup detected on CPU#?
by Ross S. W. Walker 23 Jan '08

23 Jan '08

Ross S. W. Walker wrote: > > Brett Worth wrote: > > > > Hello All. > > > > I've just started looking into Xen and have a test > > environment in place. I'm seeing an > > annoying problem that I thought worthy of a post. > > > > Config: > > > > I have 2 x HP DL585 servers each with 4 Dual core Opterons > > (non-vmx) and 16GB RAM > > configured as Xen servers. These run CentOS 5.1 with the > > latest updates applied. These > > system both attach to an iSCSI target which is an HP DL385 > > running ietd and serving SAN > > based storage. > > > > I have a test VM running CentOS 5.1 also updated. > > > > Problem: > > > > If I run the VM on a single server everything is OK. If I do > > a migrate of the VM to the > > other server I start getting random "BUG: soft lockup > > detected on CPU#?" messages on the > > VM console. The messages seem to happen with IO but not > > every time. A reboot of the VM > > on the new server will stop these messages. > > > > I've also left the VM running overnight a couple of times and > > when I do I find that any > > external sessions (ssh) are hung in the morning but the > > console session is not. New ssh > > sessions can be started and seem to work. > > > > After much googling it looks like the kernel messages can > > occur if dom0 is very busy but > > mine is not. > > > > Any suggestions? > > The soft lockup is technically not a BUG. > > You will see these errors if an IRQ takes more then 10 seconds > to respond. > > In your case I would take a look at your iSCSI setup and the > time it takes to migrate the VM from one node to another along > with SCSI reserve/release setup on the iSCSI target. > > I also have been using the Xen 3.2 RPMs off xen.org to CentOS > 5.1 which good results, the VM migration may run smoother and > quicker in Xen 3.2, but in doing so you take Xen off the > reservation, if your OK with that it may fix your issues. After seeing this same issue on my Xen 3.2 install, but with NO migration or iSCSI happening I decided it is probably NOT iSCSI's fault, so I decided to research it a little more and this is what I found: http://docs.xensource.com/XenServer/4.0.1/guest/ch04s08.html#rhel5_limitati… XenSource does provide a repo of CentOS 5 kernels that have been patched to fix this though: http://updates.xensource.com/XenServer/4.0.1/centos5x/ But these seem to be woefully out of date. I wonder if a kind soul would add the fix to the centosplus kernel with XenSource's patch so those rogue Xen users could benefit from this fix until upstream decides to include it. I suppose the centosplus patch would need to be flagged interm in case it needs removed when upstream has their own fix. -Ross ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

2 1

Redhat Directory Server 8.0
by Paul 23 Jan '08

23 Jan '08

Now that RHDS 8.0 has been released any plans of rebuilding it for CentOS? Regards, Paul Berger

5 5

XEN 3.1 centos5.1 x86_64 domU 32bit
by Theurl Michael 20 Jan '08

20 Jan '08

Hello Centos, I do not know if someone out there had/have this problems. We have two HP-bl20p-G4 2xQuadCore Xeon E5320 Intel cpu's Blade. with following software on it * centos 5.1 x86_64 * xen hypervisior 3.1 from centos distri. And run on it following guests: 32bit centos4.6 domU's with xen_domU_kernel from update repo. Some of this machines are running fine and some of this are dying sometimes under load or no load. It look's for me strange. So my question is there a basic problem to run domU32 bit systems on a 64bit hardware ? If i read the newest messages on xen this is now a big goal for xen 3.1 but i know it can be a bug or a misunderstood config on my side. Hopefully someone out there can help me with this problem. I attached some error outputs. If you need some more information's please let me know. greets Michael Here are some domU error's and core dumps: --- one of the error with an older xen domU kernel: ----------------------------------------------- kernel BUG at arch/i386/mm/hypervisor.c:195! invalid operand: 0000 [#1] SMP Modules linked in: md5(U) ipv6(U) sunrpc(U) dm_mirror(U) dm_mod(U) ext3(U) jbd(U) CPU: 0 EIP: 0061:[<c0115709>] Not tainted VLI EFLAGS: 00010282 (2.6.9-42.0.3.EL.xs0.4.0.263xenU) EIP is at xen_pgd_pin+0x44/0x52 eax: ffffffea ebx: eb500e4c ecx: 00000001 edx: 00000000 esi: 00007ff0 edi: ebb7b840 ebp: ebb7b0c0 esp: eb500e4c ds: 007b es: 007b ss: 0068 Process sh (pid: 2872, threadinfo=eb500000 task=eb712d10) Stack: 00000002 00225f7b 2b70c000 ebb7b0c0 0056e180 ebb7b0c0 c011222f ebb7b104 c01122bb ebb7b870 eb500000 c0160cf0 ebb7b840 eb712d10 c013ae9c 00000080 c016fcd9 00000080 ebb07580 00000080 ebc90840 c0157cd9 00000000 eb500000 ebbaa740 c2338c00 c0160ed9 c0160c05 eb500ec0 00000080 eb87d4c0 00400000 Call Trace: [<c011222f>] __pgd_pin+0x2a/0x3b [<c01122bb>] mm_pin+0x1f/0x2b [<c0160cf0>] exec_mmap+0xe1/0x223 [<c013ae9c>] generic_file_aio_read+0x40/0x47 [<c016fcd9>] dnotify_parent+0x1b/0x6e [<c0157cd9>] vfs_read+0xda/0xe2 [<c0160ed9>] flush_old_exec+0x43/0x21e [<c0160c05>] kernel_read+0x31/0x3b [<c017c497>] load_elf_binary+0x520/0xc83 [<c0145d99>] kmap_high +0x1e9/0x1f3 [<c0145e1b>] kunmap_high+0x78/0x95 [<c0160755>] copy_strings+0x22b/0x235 [<c017bf77>] load_elf_binary+0x0/0xc83 [<c016191c>] search_binary_handler+0xb7/0x22a [<c0161bfc>] do_execve +0x16d/0x1fd [<c0105d82>] sys_execve+0x2b/0x8a [<c02564f7>] syscall_call+0x7/0xb [<c025007b>] unix_stream_sendmsg+0x147/0x33a Code: 00 75 0d a1 a4 40 33 c0 8b 04 90 25 ff ff ff 7f 89 44 24 04 89 e3 b9 01 00 00 00 31 d2 be f0 7f 00 00 e8 3b bc fe ff 85 c0 79 08 <0f> 0b c3 00 a4 c4 26 c0 83 c4 10 5b 5e c3 56 89 c2 c1 ea 0c 53 <0>Fatal exception: panic in 5 seconds And one of the new one: ----------------------- Jan 17 13:15:22 PHOEBE kernel: ------------[ cut here ]------------ Jan 17 13:15:22 PHOEBE kernel: kernel BUG at mm/swap.c:324! Jan 17 13:15:22 PHOEBE kernel: invalid operand: 0000 [#1] Jan 17 13:15:22 PHOEBE kernel: SMP Jan 17 13:15:22 PHOEBE kernel: Modules linked in: md5 ipv6 nfs lockd nfs_acl sunrpc iptable_filter ip_tables dm_mirror dm_mod xennet ext3 jbd xenblk

4 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2008