CentOS Bug Tracker - Issues

0006511: tar --verify is broken

Wed, 19 Jun 2013 23:03:18 +0000

Verification of files while adding never succeeds in CentOS 6. It works fine in CentOS 5.

0006510: Setting lower screen resolution on Intel X4500HD (Eaglelake) fails and causes rendering glitches

Wed, 19 Jun 2013 22:55:48 +0000

I am unable to set the screen resolution to anything lower than the native resolution (1920x1080) on an HP Compaq 6000 Pro All-in-One PC with the Q43 chipset + Intel X4500HD (Eaglelake) graphics. This occurs on the default GNOME 2.28.2 environment of the 6.4 LiveCD as well as on a fresh install, using either the GNOME Preferences->Display applet or xrandr -s. After the new resolution is "set", the display area simply shrinks proportionately into the top left corner, the bottom of the screen is filled with a white space that appears to be a distorted remnant GNOME panel, while the right side, and the right side of the screen is filled with a series of black bars. If a window is dragged so that it touches the right edge of the display area, the edge content becomes stretched and distorted. Finally, the monitor itself reports that it is still displaying at native resolution.

Actual results:
Rendering glitches, unsuccessful resolution change

Expected results:
Successful resolution change

0006271: Postfix 2.3.3-6.el5 requires mysql (client) which conflicts with Oracle and MariaDB MySQL-server package

Wed, 19 Jun 2013 20:44:26 +0000

Description of problem:

As of CentOS 5.9, Postfix 2.3.3-6.el5 requires mysql (client) package.

This causes conflicts with Oracle and MariaDB MySQL packages, as their packages claim to provide "mysql" in their server package.

This forces you to install MySQL-server on all servers that have postfix installed.

I have also logged this on the MariaDB bugzilla: https://mariadb.atlassian.net/browse/MDEV-4199 [^]

And on RHEL bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=915901 [^]

The reason I am logging this here also is that in CentOS 6, postfix also has MySQL support, but it requires "mysql-libs", which is provided by MySQL-shared-compat and MariaDB-compat, meaning that there are no conflicts.

I wondered why the CentOS 5 postfix requires "mysql", rather than "mysql-libs".

What's worse is that as of MySQL 5.5.30, Oracle has not providing "mysql" in it's RPMs, which means that if you install postfix it pulls in the vanilla mysql client package, which then prevents you installing the Oracle MySQL-client package due to file conflicts.

Version-Release number of selected component (if applicable):

Postfix 2.3.3-6.el5

Actual results:

RPM/YUM conflict about conflicting files in mysql package.

Expected results:

Postfix to require mysql-libs and pull in MySQL-shared-compat using yum.

0006500: CentOS should provide a separate repository for security-related updates

Wed, 19 Jun 2013 20:33:02 +0000

Hello!

CentOS really lacks a feature that allows the user to separate security-related updates from all other ones.

As yum-security is not working with CentOS (I suppose because the upstream provider restricts usage of the contents required for yum-security to work), we need an alternative.
Inspecting the changelogs of every update for CVE and Bugzilla IDs and then inspecting the Bugzilla tickets for CVE and RHSA is a situation as dissatisfying as error-prone.

So I suggest to provide a new repository "updates-security".
To maintain full compatibility with yum configurations for the current repository layout, this repository should contain only packages that are included in the "updates" repository, too, but the packages in "updates-security" should use a priority mechanism such as the ones provided by yum-plugin-priorities or yum-plugin-protectbase, so running yum update shall show security-related updates originating from the repository "updates-security" only.
Also the updates-security repository configuration could be provided by a package centos-release-security, so the changes to the repositories only affect people explicitely installing this optional package. A yum plugin providing the chosen priority mechanism shall be required by this package centos-release-security.

0004978: Install fails when Updates repository is added to install.

Tue, 18 Jun 2013 22:29:44 +0000

When running an install with an updates repository included the install fails usually during the MAKEDEV package installation. The install UI reports: "A fatal error has occurred when reading the installation media. Installation cannot continue. [Exit Installer]"

0006493: In case of a high i/o load, system kernel has crashed.

Tue, 18 Jun 2013 06:03:29 +0000

When heavy i/o load has happend, we met frequently a kernel crash
and show following mesagges.

Kernel panic - not syncing: Fatal exception in interrupt
Pid: 2976, comm: ipoib Tainted:G D --------------------
2.6.32-358.6.1.el6.x86_64 0000001
Call Trace:
[] ? panic+0xa7/0x16f
[] ? oops_end+0xf2/0x100
[] ? die+0x5b/0x90
[] ? do_general_protection+0x152/0x160
[] ? general_protection+0x25/0x30
[] ? list_del+0x1b/0xa0
[] ? ipoib_cm_tx_reap+0xc9/0x510 [ib_ipoib]
[] ? ipoib_cm_tx_reap+0x0/0x510 [ib_ipoib]
[] ? worker_thread+0x170/0x2a0
[] ? autoremove_wake_function+0x0/0x40
[] ? worker_thread+0x0/0x2a0
[] ? kthread+0x96/0xa0
[] ? child_rip+0x96/0xa0
[] ? kthread+0x0/0xa0
[] ? child_rip+0x0/0x20

0006504: Missing bluez-debuginfo package in repository

Tue, 18 Jun 2013 00:04:27 +0000

Package bluez-debuginfo is not included in the repository for CentOS 6. The following is the comment in the Wiki:

"debuginfo - This repository contains packages with debugging symbols generated when the primary packages were built. No repo config is provided by default. Tools like oprofile, crash, and systemtap require debuginfo packages. Note that debuginfo packages may not be signed so must be installed with "--nogpgcheck" or using "gpgcheck=0" in the repo definition. These packages are found at http://debuginfo.centos.org/" [^]

Looking at http://debuginfo.centos.org/6/i386/, [^] there is no package for bluez.

0006505: yum install postgis2 conflict

Mon, 17 Jun 2013 09:06:31 +0000

Trying to install postgis2 package on an existing Postgres 9.2 Database on CentOS release 6.0(Final)

yum install postgis2_92
...

Running rpm_check_debug
ERROR with rpm_check_debug vs depsolve:
postgis <= 2.0.0 conflicts with postgis2_92-2.0.3-2.rhel6.x86_64
Please report this error in http://bugs.centos.org/set_project.php?project_id=16&ref=http://bugs.centos.org/bug_report_page.php?category=yum [^]
You could try running: rpm -Va --nofiles --nodigest

0006508: NFS client performance drops in EL6.4/Centos6.4

Sun, 16 Jun 2013 10:32:38 +0000

Description of problem:

NFS Client READ performance drops significantly after a while , maybe after the filling up of the memory with cache data. For a large enough binary file on the nfs server read on the client with
dd if=bigfile of=/dev/null bs=1M
the read performance will significantly drop after some time (the file needs to be large enough ).
This performance degradation does NOT happen if dd is used with iflag=direct
Also, it seems that older (EL5 generation) kernels do not suffer from this issue.

Version-Release number of selected component (if applicable):

Tests were made with :
Servers :
2.6.32-358.2.1.el6.x86_64 and another machine with
2.6.32-279.22.1.el6.x86_64
Storage IS fast enough.

Clients :
2.6.32-358.6.2.el6.x86_64,24G RAM - this one drops in performance (unless the sequential read is done in direct mode).
2.6.18-348.6.1.el5 also 24G RAM - this one works fine.

Network used was gigabit; Issue is not caused by the network, iperf is able to fill the bandwidth for an indefinite ammount of time.

0006491: Occasional system crash with "unable to handle kernel NULL pointer dereference" message

Sun, 16 Jun 2013 05:42:22 +0000

Over the last month I had 19 kernel crashes, all with the above message. Happens randomly. Running straight OS,no VM environment.
ASUS P6T motherboard, Intel Core i7-920 (http://ark.intel.com/products/37147 [^]), 32GiB RAM.
All 19 pairs of vmcore/vmcore-dmesg.txt files are available. Let me know which one you want to see first if any.

In brief:

[crash]$ pwd
/var/crash

[crash]$ grep "unable to handle kernel NULL pointer dereference at" */*txt
127.0.0.1-2013-05-19-12:04:05/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at (null)
127.0.0.1-2013-05-20-07:38:22/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-07:53:54/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-08:37:11/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-08:53:14/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-09:03:09/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-09:07:26/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-09:11:22/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-09:34:59/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-09:44:02/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-10:24:19/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-10:27:35/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-10:32:38/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-10:41:34/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-10:51:51/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-05-20-10:54:18/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at (null)
127.0.0.1-2013-05-20-12:02:22/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
127.0.0.1-2013-06-08-15:10:15/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218
127.0.0.1-2013-06-08-17:44:43/vmcore-dmesg.txt:<1>BUG: unable to handle kernel NULL pointer dereference at 0000000000000218

[crash]$ grep RIP */*txt | grep "<4>"
127.0.0.1-2013-05-19-12:04:05/vmcore-dmesg.txt:<4>RIP: 0010:[] [] list_del+0x10/0xa0
127.0.0.1-2013-05-20-07:38:22/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-07:53:54/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-08:37:11/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-08:53:14/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-08:59:52/vmcore-dmesg.txt:<4>RIP: 0010:[] [] avtab_search_node+0x60/0x90
127.0.0.1-2013-05-20-09:03:09/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-09:07:26/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-09:11:22/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-09:34:59/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-09:38:32/vmcore-dmesg.txt:<4>RIP: 0010:[] [] list_del+0x1b/0xa0
127.0.0.1-2013-05-20-09:44:02/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-10:24:19/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-10:27:35/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-10:32:38/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-10:41:34/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-10:51:51/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-05-20-10:54:18/vmcore-dmesg.txt:<4>RIP: 0010:[] [] __set_page_dirty_nobuffers+0x2b/0x160
127.0.0.1-2013-05-20-12:02:22/vmcore-dmesg.txt:<4>RIP: 0010:[] [] list_del+0x1b/0xa0
127.0.0.1-2013-06-08-15:10:15/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350
127.0.0.1-2013-06-08-17:44:43/vmcore-dmesg.txt:<4>RIP: 0010:[] [] rt_worker_func+0x115/0x350

0006507: serial port baud cannot be set

Sat, 15 Jun 2013 20:48:35 +0000

kppp cannot set more than one baud to external modem using /dev/ttyS1
using add-on PCI card w/2 ser, 1 par port (MB has 1 ser port)
only 460800 baud can be set which communicates at 45-49k
with USR hardware external ser 56k v92 modem.

$lspci -vv

01:01.1 Parallel controller: Oxford Semiconductor Ltd OX16PCI952 Integrated Parallel Port (prog-if 01 [BiDir])
Subsystem: Oxford Semiconductor Ltd Device 0001
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Interrupt: pin A routed to IRQ 22
Region 0: I/O ports at ac00 [size=8]
Region 1: I/O ports at a800 [size=4]
Region 2: I/O ports at a400 [size=32]
Region 3: Memory at ff7ff000 (32-bit, non-prefetchable) [size=4K]
Capabilities:
Kernel driver in use: parport_pc
Kernel modules: parport_pc

0006364: virt-manager LVM storage pool "New Volume" issue

Sat, 15 Jun 2013 13:34:46 +0000

On Centos 6.4 + most recent updates, using virt-manager-0.9.0-18.el6.x86_64

I have a LVM volume group as a storage pool in virt-manager.
When I create a New Volume in that pool, everything looks fine
but the lvm volume it creates is actually an active 4Mib SNAPSHOT instead of a normal volume and is therefore unusable to install a guest on.

I re-installed the Centos 6.4 virtual host multiple times on clean disks and
this issue won't go away.

Using "virsh vol-create-as vgname name size" seems to work fine though,
as does lvcreate. So it's probably not some LVM bug.

0006429: dpt_i2o missing

Sat, 15 Jun 2013 01:16:58 +0000

dpt_i2o module missing, can't install on a box that has the Adaptec SmartRAID controller.

0006506: LiveDVD gives Kernel Panic when booting on Acer Aspire M

Fri, 14 Jun 2013 13:20:45 +0000

Hello,

I've been trying to install CentOS 6.4 on my Acer Aspire M5-481T notebook using the LiveDVD, but it keeps giving me a Kernel Panic during boot (not matter if I boot from DVD or USB stick).

I've attached a photo of the panic message with the full output!

When I use CentOS 6.4 DVD1 instead of the LiveDVD everything works perfectly, no panic at all and installation works fine (works with DVD and with USB stick).

0006503: Error 13 invaild or unsupported executable format

Thu, 13 Jun 2013 18:05:35 +0000

Upon install Centos 6.3 EFI with all avalible packages
"Invalid Magic Number :0
Error: 13 invaild or unsupported executable format"
is reported OS will not boot
access to GRUB is availible

0006502: Automatic Bug tool is coming

Thu, 13 Jun 2013 08:38:39 +0000

When we are rebooting our system and giving the username and password a automatic bug tool is coming and giving errors and this is not allowing us to enter in GUI mode. Please check the attached screen shots.

0006501: The perl version distributed is ancient.

Thu, 13 Jun 2013 06:57:14 +0000

Perl 5.10 is more than a decade old and is no longer supported. The current version is 5.18. There are any number of bugs resolved, language enhancements, and security fixes lacking due to using something this old.

Q: Why isn't the perl distributed with Centos kept up to date?

$ /usr/bin/perl -V
Summary of my perl5 (revision 5 version 10 subversion 1) configuration:

Platform:
osname=linux, osvers=2.6.32-44.2.el6.x86_64, archname=x86_64-linux-thread-multi
uname='linux c6b5.bsys.dev.centos.org 2.6.32-44.2.el6.x86_64 0000001 smp wed jul 21 12:48:32 edt 2010 x86_64 x86_64 x86_64 gnulinux '
config_args='-des -Doptimize=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DDEBUGGING=-g -Dversion=5.10.1 -Dmyhostname=localhost -Dperladmin=root@localhost -Dcc=gcc -Dcf_by=Red Hat, Inc. -Dprefix=/usr -Dvendorprefix=/usr -Dsiteprefix=/usr/local -Dsitelib=/usr/local/share/perl5 -Dsitearch=/usr/local/lib64/perl5 -Dprivlib=/usr/share/perl5 -Darchlib=/usr/lib64/perl5 -Dvendorlib=/usr/share/perl5/vendor_perl -Dvendorarch=/usr/lib64/perl5/vendor_perl -Dinc_version_list=5.10.0 -Darchname=x86_64-linux-thread-multi -Dlibpth=/usr/local/lib64 /lib64 /usr/lib64 -Duseshrplib -Dusethreads -Duseithreads -Duselargefiles -Dd_dosuid -Dd_semctl_semun -Di_db -Ui_ndbm -Di_gdbm -Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio -Dinstallusrbinperl=n -Ubincompat5005 -Uversiononly -Dpager=/usr/bin/less -isr -Dd_gethostent_r_proto -Ud_endhostent_r_proto -Ud_sethostent_r_proto -Ud_endprotoent_r_proto -Ud_setprotoent_r_proto -Ud_endservent_r_proto -Ud_setservent_r_proto -Dscriptdir=/usr/bin'
hint=recommended, useposix=true, d_sigaction=define
useithreads=define, usemultiplicity=define
useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
use64bitint=define, use64bitall=define, uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='gcc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
optimize='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic',
cppflags='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include'
ccversion='', gccversion='4.4.5 20110214 (Red Hat 4.4.5-6)', gccosandvers=''
intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='gcc', ldflags =' -fstack-protector'
libpth=/usr/local/lib64 /lib64 /usr/lib64
libs=-lresolv -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lpthread -lc
perllibs=-lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
libc=, so=so, useshrplib=true, libperl=libperl.so
gnulibc_version='2.12'
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-rpath,/usr/lib64/perl5/CORE'
cccdlflags='-fPIC', lddlflags='-shared -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic'

Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY PERL_DONT_CREATE_GVSV
PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP USE_64_BIT_ALL
USE_64_BIT_INT USE_ITHREADS USE_LARGE_FILES
USE_PERLIO USE_REENTRANT_API
Built under linux
Compiled at Nov 6 2011 00:38:44
%ENV:
PERLDOC="-t"
@INC:
/usr/local/lib64/perl5
/usr/local/share/perl5
/usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl
/usr/lib64/perl5
/usr/share/perl5
.
(prod_y_etl) slembark@i-b454d1da ordr.in $

This is perl, v5.10.1 (*) built for x86_64-linux-thread-multi

Copyright 1987-2009, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, [^] the Perl Home Page.

0006421: Upgrade from CentOS 6.3 to 6.4 causes insane CPU time values, increasing load

Wed, 12 Jun 2013 16:01:59 +0000

During routine upgrades on hosts, we started seeing some hosts that experience issues. When we run a yum update on them to bring them up to 6.4, and reboot them, when they come up they start having slowly increasing CPU load, and insane CPU time numbers for processes. CPU load starts out at a normal level, and over the course of a few minutes continues to ramp up, to several hundred. The CPU time for some processes also goes up into several hundreds of thousands or even millions of hours, almost immediately after it comes up from a reboot.

The confusing part is that is we do a fresh install on the same host, it works completely as expected, with none of these issues.

We have looked at a package comparison between a host freshly installed directly to CentOS 6.4 and the upgraded host with the issues, and the only package we could find that was missing on the upgraded host was libitm, however installing this on the upgraded host and rebooting did not solve any issues. The only other package differences are the upgraded machine kept some old kernels installed, and had some extra perl packages.

Here is the output of top:

Tasks: 483 total, 5 running, 478 sleeping, 0 stopped, 0 zombie
Cpu(s): 11.5%us, 0.5%sy, 0.0%ni, 87.7%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 32798944k total, 28187760k used, 4611184k free, 105968k buffers
Swap: 10256376k total, 0k used, 10256376k free, 1424572k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3481 jhickson 20 0 13392 1404 812 R 3.8 0.0 0:00.03 top
1 root 20 0 21444 1552 1240 S 0.0 0.0 8596343h init
2 root 20 0 0 0 0 S 0.0 0.0 1290835h kthreadd
3 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
4 root 20 0 0 0 0 S 0.0 0.0 10222396h ksoftirqd/0
5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
6 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
7 root RT 0 0 0 0 R 0.0 0.0 300194:20 migration/1
8 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/1
9 root 20 0 0 0 0 S 0.0 0.0 900583:01 ksoftirqd/1
10 root RT 0 0 0 0 R 0.0 0.0 0:00.00 watchdog/1
11 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/2
12 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/2
13 root 20 0 0 0 0 S 0.0 0.0 20012,57 ksoftirqd/2
14 root RT 0 0 0 0 S 0.0 0.0 300194:20 watchdog/2
15 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/3
16 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/3
17 root 20 0 0 0 0 S 0.0 0.0 300194:20 ksoftirqd/3
18 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/3
19 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/4
20 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/4
21 root 20 0 0 0 0 S 0.0 0.0 300194:20 ksoftirqd/4
22 root RT 0 0 0 0 S 0.0 0.0 300194:20 watchdog/4
23 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/5
24 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/5
25 root 20 0 0 0 0 S 0.0 0.0 0:00.11 ksoftirqd/5
26 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/5
27 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/6
28 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/6

uname -a:

Linux brokenhost.keek.com 2.6.32-358.6.1.el6.x86_64 0000001 SMP Tue Apr 23 19:29:00 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

On a physical console on the machine, we have been seeing lines like:

INFO: task sh:3426 blocked for more than 120 seconds

Where sh could be various things from a shell to kernel components, it's more or less seems to be random.

Has anyone seen anything like this before? Is there any other information I can provide?

0005377: ISOLINUX not booting with CentOS-6.1-x86_64-bin-DVD1.iso

Wed, 12 Jun 2013 15:32:43 +0000

The iso image is not booting from DVD.
MD5:
ca0c13c4c0e1ce93b66232edc10ad415 CentOS-6.1-x86_64-bin-DVD1.iso

0006217: XFS hang on reboot

Tue, 11 Jun 2013 18:28:59 +0000

Special configuration -- md raid1 root filesystem is on XFS. I know this isn't formally supported, but I've been running RHEL and CentOS this way since the RedHat 7.2 days. And have many machines deployed and tested with this configuration.

As of CentOS 5.9, kernel 2.6.18-348.el5, a reboot of the system results in a hang immediately after printing:

"md: md1 switched to read-only mode"

After 120 seconds, a traceback is produced. I can provide the traceback later if it would be helpful.

It's important to note that:
* Same hardware, kickstarted with same configuration -- CentOS 5.8 does not hang on reboot.
* Same hardware, kickstarted with same configuration -- CentOS 5.9 and downgraded kernel to 2.6.18-308.el5 does NOT hang on reboot.
* Same hardware, kickstarted with same configuration -- CentOS 5.[678] and upgraded kernel to 2.6.18-348.el5 hangs on reboot.
* Same hardware, kickstarted with same configuration -- CentOS 5.9 using ext3 for root fs does not hang on reboot.
* Same hardware, kickstarted with same configuration -- CentOS 5.9 using ext3 for root fs, and a XFS data partition (md and non-md) does not hang on reboot.
* Same hardware, kickstarted with same configuration -- CentOS 5.9 and NO md raid1, does NOT hang on reboot

I suspect something changed between kernel level 308 and 348 to interfere with XFS and md raid1 on the root filesystem.

Looking at the changelog for the 348 kernel, I do see mention of a FREEZE/THAW change and this could have irritated XFS. And perhaps a few other suspicious changes that could also impact XFS. But I'm not sure.

Any insight as to the cause is appreciated. I can stay at 5.8 for now, but this seems like a potentially serious regression (albeit an edge case) that shouldn't go unreported, either here or upstream.

0006499: kernel: NETDEV WATCHDOG: eth1 (bnx2): transmit queue 0 timed out

Tue, 11 Jun 2013 17:58:15 +0000

after upgrading from 2.6.32-279.22.1.el6.x86_64 to 2.6.32-358.6.2.el6.x86_64

i have had 2 different occurrences of an issue that looks like bug 6249.

backtrace:
:WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Tainted: G I--------------- )
:Hardware name: ProLiant DL360 G5
:NETDEV WATCHDOG: eth1 (bnx2): transmit queue 0 timed out
:Modules linked in: iptable_filter ip_tables xt_iprange bnx2fc cnic uio fcoe libfcoe 8021q garp libfc stp llc scsi_transport_fc scsi_tgt ipv6 bnx2 hpilo hpwdt microcode sg serio_raw iTCO_wdt iTCO_vendor_support i5000_edac edac_core i5k_amb shpchp ext3 jbd mbcache sr_mod cdrom pata_acpi ata_generic ata_piix hpsa cciss radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core dm_mirror dm_region_hash dm_log dm_mod [last unloaded: ip_tables]
:Pid: 0, comm: swapper Tainted: G I--------------- 2.6.32-358.6.2.el6.x86_64 0000001
:Call Trace:
: [] ? warn_slowpath_common+0x87/0xc0
:[] ? warn_slowpath_fmt+0x46/0x50
:[] ? dev_watchdog+0x26d/0x280
:[] ? dev_watchdog+0x0/0x280
:[] ? run_timer_softirq+0x197/0x340
:[] ? tick_sched_timer+0x0/0xc0
:[] ? lapic_next_event+0x1d/0x30
:[] ? __do_softirq+0xc1/0x1e0
:[] ? hrtimer_interrupt+0x14b/0x260
:[] ? call_softirq+0x1c/0x30
:[] ? do_softirq+0x65/0xa0
:[] ? irq_exit+0x85/0x90
:[] ? smp_apic_timer_interrupt+0x70/0x9b
:[] ? apic_timer_interrupt+0x13/0x20
: [] ? mwait_idle+0x77/0xd0
:[] ? atomic_notifier_call_chain+0x1a/0x20
:[] ? cpu_idle+0xb6/0x110
:[] ? start_secondary+0x2ac/0x2ef

0006498: Package boost-*mpi-python is missing python module

Tue, 11 Jun 2013 12:49:40 +0000

The packages boost-openmpi-python and boost-mpich2-python do not provide a python module boost.mpi.

0006496: glxinfo, glxgears crashes

Mon, 10 Jun 2013 23:46:48 +0000

I have a Matrox Electronics Systems Ltd. MGA G400/G450 video card and am using the mga driver. I updated the system via yum and now openGL programs crash.

0006495: Cannot list directory contents of mounted DFS share

Mon, 10 Jun 2013 18:54:49 +0000

I can mount the DFS namespace root but I cannot list contents of any of the shares.

0005716: Random 'stalls' ocurring often up to several minutes - broken transparent hugepage support

Mon, 10 Jun 2013 18:15:44 +0000

Processes stall for an extended period of time, often tasks were reported as 'blocked for more that 120 seconds' and for a number of reasons I was suspecting issues with the LSI Raid driver.

Other symptoms included:

+ Occasional High CPU for kswapd - even with no swap used on the system.
+ Occasional High CPU for khugepaged.
+ Frequent high system CPU for no apparent reason.

Following several threads I've found and self diagnoses lead to issues in transparent hugepage support (aka memory defrag).

Disabling this support stopped all occurrences of the problem and the systems have been stable for a week now. It is worth noting the Redhat 6 appears to have this functionality disabled by default - where Centos has it enabled.

To disable:

echo no > /sys/kernel/mm/redhat_transparent_hugepage/khugepaged/defrag
echo never >/sys/kernel/mm/redhat_transparent_hugepage/defrag