Bug 141143 - RHEL4-B2-X86-Dmesg shows "ide1: Wait for ready failed before probe "
Summary: RHEL4-B2-X86-Dmesg shows "ide1: Wait for ready failed before probe "
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-29 16:37 UTC by Stuart Hayes
Modified: 2015-01-04 22:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-07 22:08:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Stuart Hayes 2004-11-29 16:37:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET 
CLR 1.1.4322)

Description of problem:
After booting a Dell PE2650 into RHEL4 beta 2, dmesg has the 
following messages:

"ide1: Wait for ready failed before probe "

System configuration:

System : PE2650 
BIOS : A20
H/W config : 2* 2.4 Ghz /12GB 
memory /PERC3Di/PERC4DC/Intel1000MT/2*BCM570X/AIC-39160

Comments (from Amit Bhutani):

Looks like this got introduced in the 2.6.9 kernel.

This is what the IDE maintainer (Bartlomiej Zolnierkiewicz) had to 
say about it --> 

Looks like someone needs to write a patch as Bartlomiej indicated to 
replace the printks with pr_debugs and submit the patch to 
kernel.org. This may already be done. Just need to verify. Absolutely 
need to open a Bugzilla against Red Hat to ensure that patch gets 
included in RHEL 4 RC.

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

How reproducible:

Steps to Reproduce:
1. boot up system
2. look at dmesg

Actual Results:  error message above is in log

Expected Results:  no errors in log

Additional info:

Comment 1 Alan Cox 2004-11-29 21:07:19 UTC
These are debug level messages not errors. They were switched to pr_debug in
2.6.10rc once we were happy with testing the changes.

Comment 2 Stuart Hayes 2004-11-29 21:17:12 UTC
I just found that out when I tried to reproduce this myself.

Comment 3 Amit Bhutani 2004-12-07 22:08:17 UTC
Verified fixed in 860 build. Thanks. Closing.

Note You need to log in before you can comment on or make changes to this bug.