Bug 78246

Summary:	when issue dmesg command, got error message
Product:	[Retired] Red Hat Linux	Reporter:	Jian Wu <wuj>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED WORKSFORME	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	oliver
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-06-27 21:56:32 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:

Description Jian Wu 2002-11-20 16:08:49 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; YComp 
5.0.0.0; .NET CLR 1.0.3705)

Description of problem:
errors message when do "dmesg", not the expected output

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.issue command dmesg
2.
3.
	

Actual Results:  Directory sread (sector 0x20) failed
attempt to access beyond end of device
02:00: rw=0, want=16, limit=4
Directory sread (sector 0x20) failed
attempt to access beyond end of device
02:00: rw=0, want=16, limit=4
Directory sread (sector 0x20) failed
attempt to access beyond end of device
02:00: rw=0, want=16, limit=4
Directory sread (sector 0x20) failed
attempt to access beyond end of device
02:00: rw=0, want=16, limit=4
Directory sread (sector 0x20) failed

Additional info:

Comment 1 Oliver Schulze L. 2003-02-06 13:49:53 UTC

dmesg print kernel messages, and I think dmesg is printing just what the kernel
has detected.
Check in /var/log/messages to see those same errors messages you are receiving
after running dmesg.

It think bug can be closed, since dmesg works as spected.

Comment 2 Oliver Schulze L. 2003-02-06 14:05:32 UTC

Close as: NOTABUG

Comment 3 Alan Cox 2003-06-27 21:56:04 UTC

*** Bug 78245 has been marked as a duplicate of this bug. ***