CentOS Bug Tracker - ISSUES

0004246: On installation, CentOS 5.4 does not see the Acer Aspire 3810T brightness keys

Fuerthermore, xvattr (from, if I rememebr well, rpmsource) sees the registers but fails to change them.

CentOS, however, sees on installation the related volume keys.

This is, pending a reurn to rpmsource. good news for all Acer newbies like this user who have been struggling with the brightness problem. The merit of the solution that follows belongs to an anonymous, and thus still more commendable, experienced member of the Community who has written here:

http://www.linlap.com/wiki/acer+aspire+timeline+3810t [^]

I have still struggled a bit until I have solved the bug on that basis (without any merit). You will find attached two ooRexx scripts for increasing and lowering the brightness. For those of us still not familiar with that heroic effort that is ooRexx I hwork of ope you will enjoy entering into contact with the ooRexx team at RexxLA - including the glorious chair at Vienna University - before making your own scripts in bash or however. In the menatime, anybody who doesn't feel secure please recur to this user and I will try something in bash -if i can :).

In order to link the scripts with the keys I have used xbindkeys, which works fine under CentOS (still another example of careful, proficient detail in design) and, of course, you will need half an hour to install ooRexx and. I very strongly recommend that, bsf4oorexx from Doktor Professor Ronnie Fläscher and his team in Vienna.

0003766: powernow-k8 module in CentOS-5 has no per-core frequency control

Newer AMD CPUs including newer Opterons, the Phenoms and Phenoms II (and Kuma core Athlons X2) support per-core power control, so one core can run at max speed, and three others run idle, reducing power consumption and dissipated heat amount. The powernow-k8.ko driver in CentOS-5 ties all cores together. Consequently, much of the time the system is running in a full power state and is unable to take advantage of power saving features such as CPU frequency hrottling or reduction of vCore.

0004182: freenx - termination - no confirmation dialog

When I want to close nx session, it is very easy to click "terminate" instead of "suspend". As there is no confirmation dialog (it is present in commercial version of NX from !Machine) it is very easy to destroy a lot of work.

0004245: gfs2_grow core dump

trying top extend a gfs2 filesystem result in a core dump without resizing.
Successive resizings don't work, leaving file sistem's size inalterate.
How I did it:

using "gfs2_grow -Tv /MYMOUNT" obtain a core dump:
gfs2_grow[24415]: segfault at 0000000000000028 rip 0000000000406003 rsp 00007fffb57bb450 error 4

using df -h the size in not touched

0004196: USB drives should have allow_restart set

A 2TB USB Seagate BlackArmor drive initially works fine, but once it
spins down, only certain commands, such as fsck, wake it up. Errors
such as:

sd 6:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, initializing command required
end_request: I/O error, dev sdd, sector 974615595
Buffer I/O error on device sdd2, logical block 30
Buffer I/O error on device sdd2, logical block 31
sd 6:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
Add. Sense: Logical unit not ready, initializing command required
end_request: I/O error, dev sdd, sector 974615355
Buffer I/O error on device sdd2, logical block 0
Buffer I/O error on device sdd2, logical block 1

are seen if the disk is not woken up before access.

https://bugzilla.redhat.com/show_bug.cgi?id=433287 [^]

is a bug note for 4.x,

https://bugzilla.redhat.com/show_bug.cgi?id=480389 [^]

is for 5.x. The latter entry points to a fix in 2.6.24
that sets allow_restart by default for USB drives.

0004192: touchpad on dell E6400 not detected correctly

Using a fully up to date centos 5 x86_64 on a Dell Lattitude E6400, the touchpad is not detected as a synaptics/ALPS device.
As a result, it can work as a regular mouse but the nice capabilities of the synaptics touchpad driver are not available (eg scrolling).

I've tracked this down to a problem in drivers/input/mouse/alps.c , which doesn't know the signature of the newer Dell touchpad.
The attached trivial patch solves the issue. I have tested by rebuilding the latest C5 kernel (kernel-2.6.18-164.11.1.el5.x86_64) with this patch applied via the SPEC file.

The patch comes from:
http://lkml.org/lkml/2008/9/7/133 [^] (solution for E6400 and E6500)
http://lkml.org/lkml/2007/8/4/41 [^] (solves same problem for Vostro 1400)

0004139: HP Pavillion DV7-2250ED Oops on boot and install

I recently bought a HP Pavillion DV7-2250ED (Intel T4300 processor, 4 GB Ram, 64bit kernel). When I try to boot the install dvd, it starts up ok, complains about some missing DSD entries (but continues) and then ends up at the ACPI PnP configuration. After being there for a couple of seconds, I get an oops, of which I can only see the last bits (but those point to ACPI).

I can install CentOS 5.4 if I add acpi=off to the kernel command line. But that means I can only use one CPU, the fans etc aren't usable, and neither are various other things.

Alex Chang created a patch for 2.6.33 that might solve this (see http://lkml.org/lkml/2009/12/20/146 [^] ), and as soon as I can get that integrated I'll see if that helps.

0004100: RFE: centosplus kernel summary

This collects information from all centosplus kernel-related requests and serves as a log book for building an updated kernel.

0004243: OOM killer doesn't work or bug in memory management in 2.6.18

I have swapless nodes, when users tries to go outside of available memory, OOM killer in 2.6.18 (Centos 5.4) is not triggered, as it was with number of SLES/OpenSuSE kernels. And node crashes.

Before the crash I see bunch of messages in the logs about soft-lockups. I attach here grepped log, where I removed messages about loaded modules, repeated before every call trace, and separately attach list of linked modules.

0001646: Missing source repo

In trying to download source rpm files with yum, sources are not available:

$ yumdownloader --source ntp

For this to work, 2 things need to happen:
* a new repo file needs to be created pointing to the SRPMS directory
* the SRPMS directories for updates and os need to be yumified with createrepo

0004242: during installation

A crash occured dungin installation. Saved dump to disc.
May it help you.. ;-)

0004222: Update to nx server wipes nx home directories

The latest update to freenx-0.7.3-3.el5.centos.x86_64 overwrote
/var/lib/nxserver/home
with default settings. In particular, this means that it clobbers any ssh keys the user may have configured.

0004240: Missing debug symbols for python 2.4.3-27.el5 (x86_64)

I have checked the debuginfo repository (here http://debuginfo.centos.org/5/x86_64/ [^] )but I can find no debuginfo package for Python version 2.4.3-27.el5.

0004239: large filesystem corruptions

2.6.18-164.11.1.el5PAE
4GB RAM
CPU 2x Intel(R) Xeon(TM) CPU 3.20GHz

large filesystems are corrupting.
Tried ext4, GFS, XFS

See my upstream post in
http://marc.info/?l=linux-raid&m=126842554606628&w=2 [^]
and
https://bugzilla.redhat.com/show_bug.cgi?id=573185 [^]

regards,

Giannis

0003981: Volumes get NOT mounted at reboot, console drops back to system maintenance asking root password

Linux releases:
***************
I have found this to be a problem with
CentOS 5 Update 2, 3, 4
(expect it to be the same with the RedHat EL and Scientific Linux distros)

Older experiences with SuSE / Novell Linux Enterprise Server 9
and 10 have never shown this problem

When:
*****
When dm-multipath devices are mounted at boot time,
whether LVM2 is in use or not, and /var is on a separate filesystem.

The problem does usually not show up when doing fresh installs and NEW(!) SAN configurations. But, it can clearly be reproduced when re-using existing LVs from the SAN.

Resolution or work-around:
**************************
Don't put /var on a separate filesystem in these circumstances.

0004169: Installation fails on Dell Precision T7500

Install always results in "Unhandled exception. This is most likley a bug. " etc.

I have tried LVM and native linux formats and installing from DVD, USB and NFS using Centos 5.3, Centos 5.4, RedHat 5.4 and I get the same result.

0004238: German translation of description is wrong.

"Tools zum Lesen und Schreiben von Macintosh HFS Lautstärken." is wrong. The translation for "volumes" is not "Lautstärken" in this case. It would be better to use "Partitionen".

0004236: Installation crashes

Installation on 64-bit Celeron E3300, 512 MB RAM, ECS BLACK SERIES P45T-A motherboard. Installation continued after changing the CD-ROM drive. The CD-ROM could have been the culprit. I'm including the Anaconda dump file.

0004235: Xorg crashes on lenovo ThinkPad T61 (Intel 965 GM video controller) when I open Display or Screen Resolution control panels

When I have an external monitor connected, Xorg crashes when I try to open Display or Screen Resolution control panels; therefore I am unable to change the resolution on the external monitor or set up dual-head display.

I managed to change the resolution by deleting /etc/X11/xorg.conf and restarting X which regen'ed the xorg.conf and it automatically used a better (higher) setting; but Xorg still crashes when I open Display or Screen Resolution control panel.

0003987: Vmware Guests crash since upgrades that included glib 2.5-42 & Kernel 2.6.18-164.2.1

Updated 2 CentOS 5.4 hosts running vmware server (v2.0.0)

10/22 (which included glibc-common-2.5-42)
10/31 (which included kernel-2.6.18-164.2.1.el5.i686)

Since 11/1, 3 of the 4 VM Guests running on these servers have crashed at least once (2 Win 2003 guests and 1 CentOS 4.8 guest).

Initially I rebooted to 2.6.18-164.el5 but this had no impact - guest crashed within the hour.

As glibc is mentioned in case 3384 as causing crash of vmware-hostd and libc.so.6 is cited in the vmware log at time of my guest crashes (attached in additional info) I restored glibc 2.5-34 on both hosts.

0004193: ipt_recent unable to cope with > 8191 IP addresses

Bit of an odd one, I think it's down to a kernel regression though I haven't tested many kernels yet to track down where / why.

ipt_recent by default allows you to store details of up to 100 IP addresses, I need to be able to store a lot more than that, routinely 5000+. To give myself some overhead I've been loading the module with the setting of 10000 on a spare box I've got access to running SuSE, and all works nicely, same applies for Ubuntu 9.10.

Doing so on CentOS hits an odd bug. On an x86_64 bit system I see the following

/sbin/modprobe ipt_recent ip_list_tot=10000
/sbin/iptables -A INPUT -m recent --update --seconds 60 -j DROP
iptables: Unknown error 18446744073709551615

That error number is (2^64)-1. Under 32bit I seem to get the response
iptables: Invalid argument. Run 'dmesg' for more information.
Dmesg doesn't provide anything at all, and nor does /var/log/messages for that matter. Could be two different errors, but the straces look rather similar to me

stracing the process on 64bit:

open("/lib64/iptables/libipt_recent.so", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\10\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=9560, ...}) = 0
mmap(NULL, 2104816, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x2b0ef3161000
mprotect(0x2b0ef3163000, 2093056, PROT_NONE) = 0
mmap(0x2b0ef3362000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x2b0ef3362000
close(3) = 0
open("/lib64/iptables/libipt_standard.so", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\5\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=4720, ...}) = 0
mmap(NULL, 2100032, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x2b0ef3363000
mprotect(0x2b0ef3364000, 2093056, PROT_NONE) = 0
mmap(0x2b0ef3563000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0x2b0ef3563000
close(3) = 0
socket(PF_INET, SOCK_RAW, IPPROTO_RAW) = 3
getsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\377\374\377\377\377\0\0\0\0\f\0\0\0\0\0\0\0\3403W,\2\201\377\377"..., [84]) = 0
getsockopt(3, SOL_IP, 0x41 /* IP_??? */, "filter\0\0\310.U35\0\0\0\300\27\200\34\0\0\0\0\300\27\200\34\0\0\0\0"..., [672]) = 0
setsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1128) = -1 EINVAL (Invalid argument)
write(2, "iptables: Unknown error 18446744"..., 45iptables: Unknown error 18446744073709551615
) = 45
exit_group(1) = ?

and 32bit:

open("/usr/local/libexec/xtables/libxt_recent.so", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\5\0\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=16776, ...}) = 0
mmap2(NULL, 10444, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7cd000
mmap2(0x7cf000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0x7cf000
close(3) = 0
open("/usr/local/libexec/xtables/libxt_standard.so", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\3\0\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=8443, ...}) = 0
mmap2(NULL, 5840, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x84b000
mmap2(0x84c000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0x84c000
close(3) = 0
socket(PF_INET, SOCK_RAW, IPPROTO_RAW) = 3
getsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\0\202\200\34\0\0\0\0\0\0\225\230\301p\256N\366)\0\0\0\275sG\300"..., [84]) = 0
getsockopt(3, SOL_IP, 0x41 /* IP_??? */, "filter\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., [656]) = 0
setsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1104) = -1 EINVAL (Invalid argument)
close(3) = 0
write(2, "iptables: Invalid argument. Run "..., 62iptables: Invalid argument. Run `dmesg' for more information.
) = 62
exit_group(1) = ?

32bit appears to die once I set it to over 8191 IP addresses. (8k?)
64bit appears to die once I set it to over 4095 IP addresses. (4k?!)

64bit machine as 8Gb of RAM in it, the 32bit 1Gb, I would expect that to be ample.

0004233: Repeated error about unknown key pressed

I'm running CentOS 5.4 with the kernel marked vmlinuz-2.6.18-164.11.1.e15 and I get the following message over and over on the console:

kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
kernel: atkbd.c: Use 'setkeycodes 00 ' to make it known.

kernel: atkbd.c: Unknown key released(translated set 2, code 0x0 on isa0060/serio0).
kernel: atkbd.c: Use 'setkeycodes 00 ' to make it known.

The system seems to run ok and everything works fine once I'm in X windows, but it makes the console un-usable and is clogging the messages log file. I've searched the web for potential answers and haven't found anything that fixes this. Others refer to problems with a touchpad, but I don't have a touchpad.

I'm running the server in Virtual Server 2005 R2 which just emulates a standard mouse and standard keyboard. I don't have the VM additions installed yet so this is just a basic system install with the latest package updates installed.

0004232: Newline omitted running "sysctl -a"

Newline is omitted at the end of "sysctl -a" output.

0004017: gdm_slave_xioerror_handler Fatal X error

While surfing, gdm crashed and the system rebooted?
After reboot the system ran fine.
This may be normal for gdm but I was concerned that it actually
rebooted the computer!
Please see the error info below.

The system is (cat /etc/redhat-release): CentOS release 5.4 (Final)

==================== Syslog ERROR ==================================
Nov 18 15:32:25 Betty gdm[2921]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Nov 18 15:32:25 Betty gconfd (betty-3033): GConf server is not in use, shutting down.
Nov 18 15:32:25 Betty gconfd (betty-3033): Exiting
Nov 18 15:32:40 Betty gconfd (root-24601): GConf server is not in use, shutting down.
Nov 18 15:32:40 Betty gconfd (root-24601): Exiting
Nov 18 15:33:00 Betty gdm[2836]: Restarting computer...

====================== HDW ==========================
MotherBoard: Asus M2A-VM
Bios Version: 2302

================= Memory ==========================
root->free
total used free shared buffers cached
Mem: 4019968 2347440 1672528 0 34468 2162292
-/+ buffers/cache: 150680 3869288
Swap: 8193140 0 8193140

==================== df ==========================
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 59515556 7780708 48662820 14% /
/dev/sda5 85096412 4195380 76578344 6% /loc
/dev/sda1 194442 11506 172897 7% /boot
tmpfs 2009984 0 2009984 0% /dev/shm
//lin1/data 127443968 90051600 30918580 75% /data

================ cat /proc/cpuinfo =====================
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 75
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping : 2
cpu MHz : 1000.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow nonstop_tsc pni cx16 lahf_lm cmp_legacy svm extapic cr8legacy ts fid vid ttp tm stc
bogomips : 2000.10

processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 75
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping : 2
cpu MHz : 1000.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow nonstop_tsc pni cx16 lahf_lm cmp_legacy svm extapic cr8legacy ts fid vid ttp tm stc
bogomips : 2000.10

0004231: Anaconda crashes during install after I select Centos Extras.

Variations on normal install (at least for me).
Chose manual Hostname "Pegasus".
Packages from Centos Extra

Attempted install twice when I chose "Packages from Centos Extra" it crashed both times. When I did not select "Packages from Centos Extra" it installed ok.