Discuss April 2012

discuss@lists.centos.org

181 participants
173 discussions

help from community
by Prabhpal S. Mavi 13 Apr '12

13 Apr '12

Dear All Greetings, i am admin for ISP two years now, relay emails for more than 300 companies (CentOS/Postfix). Relaying more than 10,000 messages every hours successfully. no one has ever compliant for non delivery. but i cannot relay to this domain. The servers responsible for accepting messages are rejecting. i have given the whole log for experts to monitor. it is something out of control, because it is not my problem. Our server has all record created (A,MX,PTR,SPF etc). i have three relay hosts fully functional. destination server is not accepting from any relay host. can anyone try from his server and see if it is deliverable to ray(a)tata-nigeria.com Thanks / Regards Prabhpal S. Mavi Apr 12 11:06:00 titan postfix/qmgr[11860]: C3C142E4012: from=<****(a)digital-infotech.net>, size=1391, nrcpt=1 (queue active) Apr 12 11:06:02 titan postfix/smtp[12039]: C3C142E4012: host mx2.servershost.net[205.234.223.160] said: 450 4.1.7 <****(a)digital-infotech.net>: Sender address rejected: unverified address: host mail.digital-infotech.net[41.211.25.193] said: 450 4.7.1 Client host rejected: cannot find your hostname, [205.234.223.198] (in reply to RCPT TO command) (in reply to RCPT TO command) Apr 12 11:06:03 titan postfix/smtp[12039]: C3C142E4012: to=<ray(a)tata-nigeria.com>, relay=mx3.servershost.net[66.225.214.101]:25, delay=1381, delays=1377/0.03/3.4/0.31, dsn=4.1.7, status=deferred (host mx3.servershost.net[66.225.214.101] said: 450 4.1.7 <****(a)digital-infotech.net>: Sender address rejected: unverified address: host mail.digital-infotech.net[41.211.25.193] said: 450 4.7.1 Client host rejected: cannot find your hostname, [205.234.223.198] (in reply to RCPT TO command) (in reply to RCPT TO command)) Thanks / Regards Prabhpal S. Mavi

6 13

Installing CentOS 6.2 *TO* a USB drive, not installing from USB.
by Emmanuel Noobadmin 13 Apr '12

13 Apr '12

I'm trying to setup a very small system intended for doing monitoring/logging. It's done on an Intel Atoms in a small box and the idea was to simply run it off a pair of USB flash drives in software RAID 1. Now the problem is that while the 6.2 DVD installer could go through the entire install process, grub will load then just stop at the prompt. The system will work if I use a SATA hard disk so motherboard compatibility is not an issue. Attempting the various methods to re-install grub (via rescue mode) or using the grub prompt to setup the disk does not work either. grub just does not seem to be able to find the USB drives. e.g. commands like root (hd0,0) just says device not found. This is despite grub having just loaded from it and despite that grub-install in rescue mode does not report any error. Same problem even if I just go with one USB drive in a plain vanilla ext3 setup. It seems that some sites are saying that EL variants just don't seem to be adaptable to installing and running off USB drives. Is this really the case and that I should be looking at using another distribution or am I just missing some crucial steps in the process?

6 16

Nvidia security vulnerability (CVE-2012-0946)
by Phil Schaffner 13 Apr '12

13 Apr '12

Not strictly a CentOS issue, but users of the Nvidia drivers should be aware of this. See their announcement[1] for details. Users of the the manufacturer's driver, or the ELRepo kmod-nvidia driver[2] should update ASAP to the new version. Phil [1] http://www.nvnews.net/vbulletin/showthread.php?t=178006 [2] http://elrepoproject.blogspot.com/2012/04/nvidia-driver-that-fixes-security…

1 0

CentOS 6.2 x86_64 Squirrelmail Problem
by Prabhpal S. Mavi 13 Apr '12

13 Apr '12

Greetings Friends, is any one knows why i see squirrelmail login interface like below Live Example Can Be Seen Here: https://mail.digital-infotech.com/webmail i have tried to install configure from source as well rather than RPM but all the same.security permissions have been verified also. and i have no clue any more. help would be greatly appreciated Thanks / Regards <> < bgcolor="#ffffff" border="0" cellspacing="0" cellpadding="0" width="100%"><><> SquirrelMail version 1.4.22-2.el6 By the SquirrelMail Project Team < bgcolor="#ffffff" border="0" width="350"><>< bgcolor="#dcdcdc">Digital Infotech Limited Login <>< bgcolor="#ffffff"> < bgcolor="#ffffff" border="0" width="100%"><>< width="30%">Name: < width="70%"> <>< width="30%">Password: < width="70%"> <><> Thanks / Regards Prabhpal S. Mavi Email: prabhpal(a)digital-infotech.net Sent Through .Net Domain From iPhone

3 4

Problem with latest kernel install
by Arthur Pemberton 13 Apr '12

13 Apr '12

After a simple `yum update` I got the following on reboot. Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or director FATAL: Could not load /lib/module.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory What's the best way to resolve this?

2 2

FSCK on mounted filesystem (LVM/DRBD)?
by Rafał Radecki 13 Apr '12

13 Apr '12

Hi All. I have two running servers (drbd primary, drbd secondary). When there is a problem with one of them we switch to the second one. Currently on the /dev/drbd0 (it has /xxx ext3 filesystem directly on it) we have some filesystem problems (after fsck -n). I would like to correct these errors but the filesystem should be unmounted first (I would like to avoid it if possible). Is there a way to make fsck -a on mounted filesystem for ext3? My setup is: ext3 filesystem (problems) ^ DRBD ^ LVS ^ RAID Any ideas? Best regards, Rafal.

3 4

centos 6.2 md0 boot - no boot actually
by aurfalien 12 Apr '12

12 Apr '12

Hi all, Taken from this link; https://www.centos.org/modules/newbb/print.php?form=1&topic_id=34988&forum=… Seems like I am having the same issue. I assigned my boot loader to be on /dev/md0 rather then the default of /dev/sda1 Does any one have insight to this? Thanks in advance. BTW, I have no swap partition and will do a swap file instead, easier to manage. Do I need swap to boot? - aurf

4 5

Hyper Threading Feature
by Kaushal Shriyan 12 Apr '12

12 Apr '12

Hi, Any performance bottleneck if HT (Hyper Threading) is enabled in quad core processors on CentOS 5.8 running MySQL DB Server ? Please help me understand about pros and cons of this feature. Regards, Kaushal

3 2

screen brightness changes depending on which application is run
by Jeff Cen 12 Apr '12

12 Apr '12

Hi, I found my LCD screen brightness increase when I use firefox and other white background editors and screen brightness decrease when I use dark background applications, such as terminals with black background . The change in screen brightness depending on the applications has been annoying. My centos version is ver 5.7 64 bit. Has anyone seen a similar problem or have a solution for that? Thanks in advance. Jeff

4 5

6.2 x86_64 "mtrr_cleanup: can not find optimal value"
by Michael McNulty 12 Apr '12

12 Apr '12

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 but are bit lost on the impact. The system CPU is a q6600 so it supports mtrr. It has 8gb of RAM and a G33 intel chipset (maximum memory is 8gb), 256mb onboard Intel video. Problem exists with DVD 6.2 kernel and latest in yum update 2.6.32-220.7.1.el6.x86_64. If I disable the Bios "memory remap feature", mtrr appears to have found it settings. But it says total ram covered is 7415M, so I lose some memory since when enabled it shows 8183M but mtrr fails. A little concerned about putting this back into production with this but hope to get it resolved rather than reinstall 5.8. Will mtrr failing result in stability or performance loss? Is there any performance loss disabling memory remap in bios other than losing 600k? thx Is this happening because the chipset only supports 8gb of memory and therefore mtrr cannot remap memory above 8gb? (assuming not since problem did not exist in 5.x centos) -- Mike Bios Memory remap feature: enabled Apr 11 17:25:36 kernel: total RAM covered: 8183M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 64K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 128K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 256K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 512K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 64K chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 64K chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 128K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 256K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 512K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 128K chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 128K chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 256K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 512K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 256K chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 256K chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 512K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 512K chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 512K chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 1M chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 1M chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 2M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 4M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 8M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 16M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 32M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 64M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 128M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 256M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: *BAD*gran_size: 2M chunk_size: 512M num_reg: 8 lose cover RAM: -255M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 1G num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: *BAD*gran_size: 2M chunk_size: 2G num_reg: 8 lose cover RAM: -1023M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 4M num_reg: 8 lose cover RAM: 771M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 8M num_reg: 8 lose cover RAM: 4867M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 16M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 32M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 64M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 128M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 256M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: *BAD*gran_size: 4M chunk_size: 512M num_reg: 8 lose cover RAM: -253M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 1G num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: *BAD*gran_size: 4M chunk_size: 2G num_reg: 8 lose cover RAM: -1021M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 8M num_reg: 8 lose cover RAM: 263M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 16M num_reg: 8 lose cover RAM: 263M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 32M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 64M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 128M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 256M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 512M num_reg: 8 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 1G num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 2G num_reg: 8 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 16M num_reg: 8 lose cover RAM: 263M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 32M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 64M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 128M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 256M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 512M num_reg: 8 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 1G num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 2G num_reg: 8 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 32M num_reg: 8 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 64M num_reg: 7 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 128M num_reg: 7 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 256M num_reg: 7 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 512M num_reg: 8 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 1G num_reg: 7 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 2G num_reg: 8 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 64M num_reg: 7 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 128M num_reg: 7 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 256M num_reg: 7 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 512M num_reg: 8 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 1G num_reg: 7 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 2G num_reg: 8 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 128M num_reg: 6 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 256M num_reg: 7 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 512M num_reg: 8 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 1G num_reg: 7 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 2G num_reg: 8 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 256M chunk_size: 256M num_reg: 5 lose cover RAM: 247M Apr 11 17:25:36 kernel: gran_size: 256M chunk_size: 512M num_reg: 5 lose cover RAM: 247M Apr 11 17:25:36 kernel: gran_size: 256M chunk_size: 1G num_reg: 5 lose cover RAM: 247M Apr 11 17:25:36 kernel: gran_size: 256M chunk_size: 2G num_reg: 6 lose cover RAM: 247M Apr 11 17:25:36 kernel: gran_size: 512M chunk_size: 512M num_reg: 4 lose cover RAM: 503M Apr 11 17:25:36 kernel: gran_size: 512M chunk_size: 1G num_reg: 5 lose cover RAM: 503M Apr 11 17:25:36 kernel: gran_size: 512M chunk_size: 2G num_reg: 6 lose cover RAM: 503M Apr 11 17:25:36 kernel: gran_size: 1G chunk_size: 1G num_reg: 3 lose cover RAM: 1015M Apr 11 17:25:36 kernel: gran_size: 1G chunk_size: 2G num_reg: 3 lose cover RAM: 1015M Apr 11 17:25:36 kernel: gran_size: 2G chunk_size: 2G num_reg: 2 lose cover RAM: 2039M Apr 11 17:25:36 kernel: mtrr_cleanup: can not find optimal value Apr 11 17:25:36 kernel: please specify mtrr_gran_size/mtrr_chunk_size cat /proc/mtrr reg00: base=0x0d0000000 ( 3328MB), size= 256MB, count=1: uncachable reg01: base=0x0e0000000 ( 3584MB), size= 512MB, count=1: uncachable reg02: base=0x000000000 ( 0MB), size= 8192MB, count=1: write-back reg03: base=0x200000000 ( 8192MB), size= 512MB, count=1: write-back reg04: base=0x220000000 ( 8704MB), size= 256MB, count=1: write-back reg05: base=0x0cf700000 ( 3319MB), size= 1MB, count=1: uncachable reg06: base=0x0cf800000 ( 3320MB), size= 8MB, count=1: uncachable cat /proc/meminfo MemTotal: 8050140 kB Now with: Bios Memory remap feature: disabled cat /proc/meminfo MemTotal: 7276000 kB Apr 11 15:33:41 ns2 kernel: total RAM covered: 7415M Apr 11 15:33:41 ns2 kernel: Found optimal setting for mtrr clean up Apr 11 15:33:41 ns2 kernel: gran_size: 64K chunk_size: 16M num_reg: 6 lose cover RAM: 0G /proc/mtrr (bios memory remap disabled) reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back reg02: base=0x0c0000000 ( 3072MB), size= 256MB, count=1: write-back reg03: base=0x0cf700000 ( 3319MB), size= 1MB, count=1: uncachable reg04: base=0x0cf800000 ( 3320MB), size= 8MB, count=1: uncachable reg05: base=0x100000000 ( 4096MB), size= 4096MB, count=1: write-back reg06: base=0x0d0000000 ( 3328MB), size= 256MB, count=1: write-combining

2 2

← Newer
1
...
9
10
11
12
13
14
15
...
18
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2012