Bug 145619

Summary:	msr device nodes created in wrong place
Product:	Red Hat Enterprise Linux 4	Reporter:	blbooth <blbooth>
Component:	udev	Assignee:	Harald Hoyer <harald>
Status:	CLOSED ERRATA	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	davej, tao
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2005-388	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-05 13:41:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	156322

Description blbooth 2005-01-20 03:58:38 UTC

Description of problem:

Loading the msr kernel module creates /dev/msr0, but x86info looks for
/dev/cpu/0/msr, and gives an error when the device isn't found.

Creating a symlink /dev/cpu/0/msr -> /dev/msr0 fixes the problem.


Steps to Reproduce:

1. modprobe msr
2. x86info -a
  
Actual results:
x86info output contains line
/dev/cpu/0/msr: No such file or directory


Additional info:
Confirmed on two different single CPU systems (Celeron-Mendocino and
Pentium Pro)

Comment 1 Dave Jones 2005-01-20 04:06:09 UTC

these *should* be in /dev/cpu/0/msr, so udev is creating them in the wrong place.

Comment 5 Guy Streeter 2005-03-31 16:33:29 UTC

# ls -l /dev/cpu*
crw-------  1 root root 203, 0 Mar 31 10:18 /dev/cpu0
crw-------  1 root root 203, 1 Mar 31 10:18 /dev/cpu1

Same problem with cpuid files. See

/dev/cpu/0/cpuid: No such file or directory

error from x86info

Comment 6 Guy Streeter 2005-03-31 16:34:25 UTC

problem still exists in released RHEL4

Comment 16 Konstantin Olchanski 2005-08-11 05:58:18 UTC

On x86_64 Fedora 3, the "msr" device nodes are absent altogether (and there is
no msr.ko loadable module). After I do "mknod msr0 c 202 0", "mknod msr1 c 202
1" (and so forth), access to the msr's seems to work fine. K.O.

Comment 17 Red Hat Bugzilla 2005-10-05 13:41:13 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2005-388.html