similar to: Unknown KERNEL Warning in boot messages

CentOS Experts, I am receiving the following in /var/spool/mail/root. I cleaned out the file and then rebooted and the same errors came back. Is it possible to analyze the data and advise if there is an issue with my system? This is a completely fresh install. From user at localhost.srv.net Tue Jan 17 08:11:56 2012 Return-Path: <user at localhost.srv.net> X-Original-To: root at

Hello, is anyone experiencing this ? I have a sympa process (bulk.pl) which triggers this bug: ------------[ cut here ]------------ WARNING: at kernel/sched.c:5914 thread_return+0x232/0x79d() (Not tainted) Hardware name: X8DTU-LN4+ Modules linked in: cpufreq_ondemand acpi_cpufreq freq_table mperf ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6

I have a machine with a recent install of centos (2.6.32-220.2.1.el6.x86_64 kernel). It crashed 3 times this week, and sent emails like the one below complaining about kernel taint. I've gone back to a previous kernel to see if that helps, but otherwise I don't know how to investigate this. What should I do? Here's stuff from the log and one of the emails:

After fresh installation of CentOS 6.2 on my server, I get following errors in my dmesg output: ------- MTRR default type: uncachable MTRR fixed ranges enabled: 00000-9FFFF write-back A0000-BFFFF uncachable C0000-D7FFF write-protect D8000-E7FFF uncachable E8000-FFFFF write-protect MTRR variable ranges enabled: 0 base 000000000 mask C00000000 write-back 1 base 400000000 mask

Hi, I have server that has been running 5.x - 5.8 for a few years without issue and decided to move it to a fresh install of 6.2. First thing I noticed is a good part of the log has these mtrr messages finally ending with "mtrr_cleanup: can not find optimal value" and "please specify mtrr_gran_size/mtrr_chunk_size". I have been searching around and reading the kernel docs

We have had some problems bringing up SLES10/Xen on DL360 box (dual processor). The Compaq boxes have this notion of "auto" mode for MPS/APIC to deal with buggy OSes and under this setting (which is the default setting), vanilla Linux (2.6.16) comes up on this box in UP mode since it finds the local APIC disabled in bios. However, the xen based kernel tries to come up MP and fails in a

Good Day All, Today I looked at the dmesg log and I notice that the following messages regarding mtrr_gran_size/mtrr_chunk_size. I am currently running CentOS 6.3 and I installed CentOS 6.2 and 6.1 and I was seeing the same errors. When I installed CentOS 5.8 on the same laptop I do not see these errors. $ lsb_release -a LSB Version:

Hi all! After upgrading to Squeeze, I am watching a Xen VMHost that after a while it hangs. This did not happen when I was using Xen with Debian Lenny (in this case as with Squeeze, the Xen components are from Debian repositories). In each case I connected a keyboard and monitor to the computer and the screen remained black without answering any key. This problem seems to also affect domUs,

ipmi_sdr_ctx_destroy is already called in libfreeipmi_get_sensors_info but sdr_ctx isn't nulled so libfreeipmi_cleanup is trying to destroy it second time. *** Error in `nut-ipmipsu': munmap_chunk(): invalid pointer: 0x000055de01edee50 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x77a8d)[0x7fec04122a8d] /lib64/libc.so.6(cfree+0x79d)[0x7fec0412eefd]

Good Day, I am not 100% certain if here is the right place to bring this up, however if this is the wrong place for this please redirect me to right place. A few weeks ago I was trying to install KVM on my laptop, I bought a new laptop and immediately after I install the nVidia drivers I receive the following error "libfcoe_device_notification: NETDEV_UNREGISTER lo" I spent several

Hi, I''ve got similar problem - after HW failure - two of three disks became unavailable and now I''m unable to btrfsck. Btrfs lays on /dev/sdb1,/dev/sdc1,/dev/sdd1 - sdc+sdd became unavailable Here is kernel log: ============================================ Mar  9 23:56:28 ftp2 kernel: [121492.593338] ata7.00: exception Emask 0x60 SAct 0x1 SErr 0x800 action 0x6 frozen Mar  9

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine