devel

devel@lists.centos.org

2 participants
4652 discussions

Warnings building centosplis kernel-xen from .SRPM
by Andy Burns 19 Jul '08

19 Jul '08

A few weeks back I needed to rebuild the centosplus kernel-xen on x86_64, I don't recall getting anything other than the "usual" sprinkling of compiler warnings. Now I've needed to rebuild the centosplus kernel-xen, this time on i686, I do get a built and working kernel+modules, but I get a particularly "hairy" set of warnings as follows, anyone else rebuilt this from the .SRPMs and had similar, do those warnings look bad to anyone else? Or is it normal with 32bit xen? MODPOST WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between '_text' (at offset 0xc040006b) and 'L6' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc04020ff) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'cpu_init' (at offset 0xc040c6c3) and 'c_start' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'online_page' (at offset 0xc0412ce9) and 'pgd_ctor' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a3fe) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a409) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a414) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a41f) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a42a) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a435) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a440) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a44b) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a456) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a461) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060a46c) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem_low from .text between 'swiotlb_init_with_default_size' (at offset 0xc04e6b79) and 'swiotlb_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'swiotlb_init_with_default_size' (at offset 0xc04e6bd9) and 'swiotlb_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'swiotlb_init_with_default_size' (at offset 0xc04e6c1e) and 'swiotlb_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem_low from .text between 'swiotlb_init_with_default_size' (at offset 0xc04e6c34) and 'swiotlb_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'vgacon_startup' (at offset 0xc04f675f) and 'vgacon_scrolldelta' WARNING: vmlinux - Section mismatch: reference to .init.data:logo_linux_clut224 from .text between 'fb_find_logo' (at offset 0xc04ff08c) and 'cfb_fillrect' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem_low from .text between 'xen_machine_kexec_setup_resources' (at offset 0xc054a10d) and 'xen_machine_kexec_load' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060b263) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc060b26e) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text:reserve_ibft_region from __ksymtab between '__ksymtab_reserve_ibft_region' (at offset 0xc065590c) and '__ksymtab_ibft_addr'

2 1

Network on CentOS 5.2
by Marcus Moeller 19 Jul '08

19 Jul '08

Hi all. I am not yet sure if this is a general problem and already known, but on my machine (a FSC M9400 Notebook) the network was slightly broken until I installed the latest updates. The IP address has been correctly assigned and is shown by ifconfig. The network access worked for a while (about 5 minutes) until it broke. Then, pinging external ressources was still possible but trying to access Webservers or other TCP links did no longer work. After an yum update (including a kernel upgrade) and a reboot the problem has gone. Best Regards Marcus

1 0

Create my own CentOS mug?
by Niels de Vos 17 Jul '08

17 Jul '08

Hello, as I can't find any (cool) CentOS merchandise, I'm thinking about creating/ordering my own mug. In the CentOS wiki there is a very cool anaconda splashscreen; it's a real eye-catcher :) Unfortunately the image is not of high quality (probably because anaconda can't handle that). Some images have the corresponding .svg with it, the anaconda splashscreen doesn't. Can sombody point me to or provide me with a higher quality version of the splashscreen? I could offer help for getting a small shop started. However I'm not directly affiliated with the CentOS project, nor do I have any experience with creating webshops... Thanks in advance, Niels Anaconda plashscreen: <http://wiki.centos.org/ArtWork/DistroDesign/modern-CentOS#head-97ae478f9492…>

1 0

New Horde version ... should we upgrade?
by Johnny Hughes 17 Jul '08

17 Jul '08

There is a new version of the Horde framework and the other packages that go with it. The new framework is 3.2.x and most of the other <name>-h3-<version> apps also go up a minor number. The problem with this upgrade is that there is a new database schema and it is a "lots of admin action required" upgrade to a new version. I can't really run the database upgrade SQL script during the upgrade process, so the user is left with a broken system after the upgrade. With enterprise linux distros, upgrades like this are to be avoided. So the question is ... do we just leave Horde at latest 3.1.x level and use 3.2.X in CentOS-6? There is the possibility of a horde32 (and all the others apps also as required) and set that to conflict with "horde < 3.2" on C5, BUT that introduces it's own issues. My feeling is that we stick with the latest horde in the 3.1.x series in CentOS-4 and CentOS-5 (which is 3.1.8) and we wait until CentOS-6 where we will introduce the 3.2.x series (and all the associated apps). What does everyone else think? Thanks, Johnny Hughes

5 7

Status of PHP 5.2?
by Hugo van der Kooij 17 Jul '08

17 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Could someone tell me what the status is of PHP 5.2 for Centos 5? I actually found software I would like to run but roundcubemail 0.2 needs PHP 5.2 and it seems an improvement over v0.1 which allready seems to be a better user experience compared to the aging squirrelmail. 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) iD8DBQFIft9rBvzDRVjxmYERAhO6AJ41GDfyv2aM9I2VK4nbTA2A4kex1ACfT+OJ cmXX+jABIfFz7WzVq7Tz4Gs= =xjLG -----END PGP SIGNATURE-----

1 0

Need kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm
by Jerry Amundson 15 Jul '08

15 Jul '08

Short story: Would it be possible to get kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm on di.c.o? I have a need to run crash on a 2.6.9-67.0.20.ELxenU xm dump-core. Long story: Two Dell 6950 (now called R905, 4 Dual-Core AMD Opteron 8200 series) heartbeat/drbd nodes running the stock CentOS 5.2 Dom0. The domU's are the only resources in heartbeat. Dom1 is a perfectly running, updated, CentOS 5.2 Apache/MySQL/Samba server (2.6.18-92.1.6.el5xen). It's xen config: name = "guinan" bootloader = "/usr/bin/pygrub" uuid = "8fa0ac9e-fe28-17f5-6a72-07f84b4daa24" memory = 4097 vcpus = 6 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1,keymap=en-us" ] disk = [ "phy:/dev/drbd1,xvda,w", "phy:/dev/drbd2,xvdb,w" ] vif = [ "mac=00:16:3e:68:16:5d,bridge=xenbr0", "bridge=xenbr1" ] Dom2 is a CentOS 4.6 software development and database server (2.6.9-67.0.20.ELxenU). Every so often, could be several hours or several days, it just hangs, locks up, becomes unresponsive. Nothing to the console. Nothing logged. When it gets to this point, the only recourse is an xm destroy. It's occurred with every combination of Dom0/DomU. The hardware of both servers checks out OK. The only sign of life, on Dom2's current Dom0, xentop shows CPU usage, and at a high percent, at that: xentop - 12:02:36 Xen 3.1.2-92.1.6.el5 2 domains: 2 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 16775712k total, 11629904k used, 5145808k free CPUs: 8 @ 2194MHz NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID Domain-0 -----r 50891 1.5 901352 5.4 no limit n/a 8 4 17720114 18765713 0 0 0 0 0 monolith -----r 965342 599.2 10486632 62.5 10486784 62.5 6 2 332672635 30178285 2 0 15805538 60805435 0 I've experimented with various xen config's. Currently it's this: name = "monolith" uuid = "283746fa-c708-cfa0-f5df-cad6abea568e" memory = 10241 vcpus = 4 bootloader = "/usr/bin/pygrub" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1,keymap=en-us" ] disk = [ "phy:/dev/drbd3,xvda,w", "phy:/dev/drbd4,xvdb,w" ] vif = [ "mac=00:16:3e:08:8d:c3,bridge=xenbr0", "bridge=xenbr1" ] Previously, I'd tried adjusting memory, but the problem resurfaced. Currently, I've gone from 6 vcpus to the 4 shown above in the hopes that stabilizes it. I'm at wits end. I've committed these machines to production status, so this instability has everyone kind of on edge, and wanting to go back to bare metal... jerry -- "Your life is trite and jaded, boring and confiscated." - Twisted Sister

2 2

Point yum repos to centos gpg key in /etc/pki/
by Jeff Sheltren 14 Jul '08

14 Jul '08

Hi, as a follow up to a conversation in #centos-devel, I'd like to get input from the list on this issue. The question is where to point people, and tools like yum, for the centos gpg key used to verify rpm signatures. My opinion is that pointing to the key in /etc/pki/ which gets installed by the centos- release makes the most sense. This is already installed locally on any centos (-5) machine. See ie. http://bugs.centos.org/view.php?id=2419 From a security standpoint, there are issues with either choice. However, if your install media has been compromised, then there would be many other ways to bypass the gpg checks rather than just changing the gpg key from the centos-release package. Pointing to a URL for the gpg key opens up more security issues such as dns poisoning. -Jeff

6 11

perl and perl::IO conflict
by Hugo van der Kooij 13 Jul '08

13 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The MailScanner software requires Perl IO v1.23 but perl still ships with v1.22 of the IO module. In the past the IO version was even older and the conflict betwen packages was limited to some manual pages. For that I could create a workaround by putting the manual pages in a different package. But with recent perl updates this no longer works. So the MailScanner community advises one to do the following: ~ - rpm -e perl-IO ~ - yum update (to update perl) ~ - rpm -i --force perl-IO... The bit about the --force option is something I am not at all comfortable with. Using --force on the rm command is about as bad as using it on the F* command. So I was thinking of rebuilding perl to include a new version of the IO module but I can not get my head around it. The goal is to make a repository that can be used beside the normal repositories of Centos and rpmforge to install and maintain MailScanner and the minimal required packages. Anyone any ideas on how to tackle this? BTW the conflict shows up as: ~ file /usr/lib/perl5/5.8.8/i386-linux-thread-multi/IO.pm from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/lib/perl5/5.8.8/i386-linux-thread-multi/IO/Dir.pm from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/lib/perl5/5.8.8/i386-linux-thread-multi/IO/File.pm from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/lib/perl5/5.8.8/i386-linux-thread-multi/IO/Handle.pm from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/lib/perl5/5.8.8/i386-linux-thread-multi/IO/Socket.pm from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/lib/perl5/5.8.8/i386-linux-thread-multi/auto/IO/IO.so from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::Dir.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::File.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::Handle.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::Pipe.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::Poll.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::Seekable.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::Select.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::Socket.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::Socket::INET.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 ~ file /usr/share/man/man3/IO::Socket::UNIX.3pm.gz from install of perl-IO-1.2301-1 conflicts with file from package perl-5.8.8-10.el5_2.3 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) iD8DBQFIecLEBvzDRVjxmYERAsikAJ9LJfU2a/7Ud6QceOS3K+c7RQS+owCfcaQM xvYVSAZDtkapHoReTSJXnVc= =d92R -----END PGP SIGNATURE-----

2 2

fixing broken yum update
by Ned Slider 10 Jul '08

10 Jul '08

Hi all, Not quite sure where best to float this idea so I thought I try here first to reach a wider audience. Recently we have seen a number of threads on the fora dealing with broken 'yum update' issues during updates from 5.1 to 5.2. I guess the mailing list has probably seen it's share of similar issues. Here's an example of one such thread: http://www.centos.org/modules/newbb/viewtopic.php?topic_id=14999&forum=37 I'm wondering if it would be useful to put together a *generic* procedure to recover from such issues, one that should work in most cases. In addition, maybe some advice/tips to minimise the risk of performing a large update. I'm thinking of things like performing updates in a screen session when remotely updating over an ssh login in case the ssh connection gets lost mid-update. Also, I tend to perform updates in smaller chunks like: manually install new kernel packages yum update yum\* rpm\* yum update open\* yum update gnome\* kde\* xorg\* etc to minimise the damage if it goes horribly wrong at any point. Not sure if that's good practice or not but it works for me. Plus any other advice relevant to the update procedure - how many times did people ask the difference between 'yum upgrade' and 'yum update', and which they should use :) If it's deemed a good idea, I'm happy to help put together a Wiki page or something although some help with the content (ie, a generic fix, tips and advice) would be appreciated.

2 1

Any news about next kvm release for centos 5.2?
by carlopmart 10 Jul '08

10 Jul '08

Hi all, Which will be next stable release for CentOS 5.2?? Can i use on a production enviromment?? Thanks. -- CL Martinez carlopmart {at} gmail {d0t} com

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel