“intel_rapl: no valid rapl domains” message upon boot blacklist.conf -1

“intel_rapl: no valid rapl domains” message upon boot

I install fresh Ubuntu 14. 04 server under ESXI 5.1.0.
During my installation I did not get any erorrs or strange things. My problem is when I boot machine at console screen I get messages like

[ 6.958104] intel_rapl: no valid rapl domains found in package 0 
[ 7.508153] intel_rapl: no valid rapl domains found in package 0
[ 8.058695] intel_rapl: no valid rapl domains found in package 0
[ 8.609932] intel_rapl: no valid rapl domains found in package 0
[ 9.163260] intel_rapl: no valid rapl domains found in package 0

After that messages I am able to log in and my to me Ubuntu works OK. I have internet connection I am able to call apt-get update and I am able to login over SSH.

Should I investigate these errors deeply before I continue build my server.
Do I need to react on these Messages or it is ok to run Ubuntu like this.

The intel_rapl message was driving me crazy. The solution for me was to (sudo) edit/etc/modprobe.d/blacklist.conf and add blacklist intel_rapl. No more messages after reboot.

This was a change introduced in October 2013 to support Intel RAPL power capping driver in the Linux kernel. This message is non-obstructive, and when it appears it doesn‘t affect the performance or functionality of the system, since it‘s only a power management module.

If your virtualization software supports this driver (and the host supports advanced power features) then the message disappears.

You can check the source tree of the module to check what it does.

I know in virualbox you can enable PAE/NX which will solve "no valid rapl domains found in package" on Ubuntu 14.04 LTS. I don‘t know how about ESXI if it supports PAE/NX or not.

I install fresh Ubuntu 14. 04 server under ESXI 5.1.0.
During my installation I did not get any erorrs or strange things. My problem is when I boot machine at console screen I get messages like

[ 6.958104] intel_rapl: no valid rapl domains found in package 0  [ 7.508153] intel_rapl: no valid rapl domains found in package 0 [ 8.058695] intel_rapl: no valid rapl domains found in package 0 [ 8.609932] intel_rapl: no valid rapl domains found in package 0 [ 9.163260] intel_rapl: no valid rapl domains found in package 0

After that messages I am able to log in and my to me Ubuntu works OK. I have internet connection I am able to call apt-get update and I am able to login over SSH.

Should I investigate these errors deeply before I continue build my server.
Do I need to react on these Messages or it is ok to run Ubuntu like this.

/etc/modprobe.d/blacklist.conf

blacklist intel_rapl

blacklist the_module name

blacklist i2c_piix4

#
# Listing a module here prevents the hotplug scripts from loading it.
# Usually that‘d be so that some other driver will bind it instead,
# no matter which driver happens to get probed first.  Sometimes user
# mode tools can also control driver binding.
#
# Syntax:  driver name alone (without any spaces) on a line. Other
# lines are ignored.
#

# watchdog drivers
blacklist i8xx_tco

# framebuffer drivers
blacklist aty128fb
blacklist atyfb
blacklist radeonfb
blacklist i810fb
blacklist cirrusfb
blacklist intelfb
blacklist kyrofb
blacklist i2c-matroxfb
blacklist hgafb
blacklist nvidiafb
blacklist rivafb
blacklist savagefb
blacklist sstfb
blacklist neofb
blacklist tridentfb
blacklist tdfxfb
blacklist virgefb
blacklist vga16fb

# ISDN - see bugs 154799, 159068
blacklist hisax
blacklist hisax_fcpcipnp

# sound drivers
blacklist snd-pcsp
blacklist nouveau

时间: 2024-10-11 07:14:08

“intel_rapl: no valid rapl domains” message upon boot blacklist.conf -1的相关文章

intel_rapl: no valid rapl domains found in package 0 错误解决

在VMWARE中安装archlinux时出现 intel_rapl: no valid rapl domains found in package 0 在修改vmware的vmx文件加入 paevm = "TRUE" 依旧不能解决问题,是因为笔记本的CPU不支持 PAE. 最后调试出解决方法:修改 /etc/modprobe.d/blacklist.conf 内容,加入 blacklist intel_rapl 保存重启.

命令6 centos7.

---------------------------------------------------------------------------------------------------------- 在 runlevel 的对应上,大概仅有 runlevel 1, 3, 5 有对应到 systemd 的某些 target 类型而已,没有全部对应:---------------------------------------------------------------------

命令6 centos 7

----------------------------------------------------------------------------------------------------------  在 runlevel 的对应上,大概仅有 runlevel 1, 3, 5 有对应到 systemd 的某些 target 类型而已,没有全部对应: -------------------------------------------------------------------

virtualbox装个 ubuntu

好久没弄 虚拟机了,感觉好不习惯 根据网上的步骤装了一ubuntu 启动报错 virtualbox intel_rapl: no valid rapl domains ...... 搜索到了一片中文博客 " 在virtualbox设置中找到.vdi文件的存储位置, 在存储位置目录下有个.vbox文件用记事本打开并找到PAE这个标签 <PAE enabled="false"/> 把false修改为true,重新启动 " 这个么什么效果,对于我的机子 另一文

centos7开机无法进入图形界面,出现sda assuming drive cache write through的一个解决方案

centos7开机无法进入图形界面,出现sda assuming drive cache write through.no valid rapl domains found in package之类信息. 这个问题是我在VMware里面操作出现的,原因是我在使用虚拟机和实体机之间文件共享功能时,centos系统无法出现hgfs文件夹, 为了解决hgfs的不出现问题,我参考了如下帖子: http://blog.csdn.net/cindy_cheng/article/details/5045697

when you start Windows 7: &quot;The Windows Boot Configuration Data file is missing required information&quot;

When you start Windows 7, you receive the following error message: File: \Boot\BCD Status: 0xc0000034 Info: The Windows Boot Configuration Data file is missing required information 微软官方帮助文档: 当您启动 Windows Vista 的错误消息:"Windows 引导配置数据文件缺少必需的信息" Err

boot loader:grub入门[转]

Boot Loader: Grub 在看完了前面的整个启动流程,以及核心模块的整理之后,你应该会发现到一件事情, 那就是『 boot loader 是加载核心的重要工具』啊!没有 boot loader 的话,那么 kernel 根本就没有办法被系统加载的呢!所以,底下我们会先谈一谈 boot loader 的功能, 然后再讲一讲现阶段 Linux 里头最主流的 grub 这个 boot loader 吧! boot loader 的两个 stage 我们在第一小节启动流程的地方曾经讲过,在 B

手把手教你如何恢复 /boot 目录

前言 /boot目录是一个系统启动最重要的目录,系统在上电自检MBR引导之后,系统就要读取/boot目 录下的文件.详细的内容见:http://vinsent.blog.51cto.com/13116656/1963546.总之/boot被破坏 了是很大的问题,今天就带大家一步步恢复/boot目录中的各文件,欢迎您的阅读!! 一.破坏现象 我们都知道/boot/目录是一个用于引导系统开机启动的目录,如果你不小心破坏了该目录.你将的系统将不能启动.CentOS 6会进入都如下界面: CentOS

修复/boot及/etc/fstab、自制linux、编译安装内核

实验一.破坏dev/sda 的MBR的446字节: 破坏:dd if=/dev/zero of=/dev/sda bs=1 count=446 查看:hexdump -C -n 512 /dev/sda 发现前面的字节都为0 状况一.刚破坏未重启的时候修复: 可以利用grub重新生成: grub grub> root (hd0,0) grub> setup (hd0) quit退出 修复完之后使用hexdump -C -n 512 /dev/sda查看发现已经修复成功 状况二.破坏之后重启了,